
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-16-2014 11:52 AM
Hi all,
the subject pretty much explains my problem: scanning my 2008(R2) servers gives me this error message. Windows 2003 servers seem unaffected as are Windows 7 clients.
This seems to be happening since yesterday. Only thing that has changed is our new VMWare-server that went live but doesn't host any of the affected machines.
Any idea what is causing this?
Regards
J. Berner
the subject pretty much explains my problem: scanning my 2008(R2) servers gives me this error message. Windows 2003 servers seem unaffected as are Windows 7 clients.
This seems to be happening since yesterday. Only thing that has changed is our new VMWare-server that went live but doesn't host any of the affected machines.
Any idea what is causing this?
Regards
J. Berner
Solved! Go to Solution.
Labels:
- Labels:
-
General Discussion
1 ACCEPTED SOLUTION

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-18-2014 12:52 PM
This error is likely caused by corrupt WMI (Windows Management Instrumentation) on the client machines. We recommend that you:
- Run the following WMI repair script on the client machines: http://www.lansweeper.com/files/repairwmi.zip
- Rescan the machines by clicking the Assets link at the top of the Lansweeper web console, ticking the checkboxes in front of the assets and hitting the Rescan button on the left.
- Run the following WMI repair script on the client machines: http://www.lansweeper.com/files/repairwmi.zip
- Rescan the machines by clicking the Assets link at the top of the Lansweeper web console, ticking the checkboxes in front of the assets and hitting the Rescan button on the left.
1 REPLY 1

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-18-2014 12:52 PM
This error is likely caused by corrupt WMI (Windows Management Instrumentation) on the client machines. We recommend that you:
- Run the following WMI repair script on the client machines: http://www.lansweeper.com/files/repairwmi.zip
- Rescan the machines by clicking the Assets link at the top of the Lansweeper web console, ticking the checkboxes in front of the assets and hitting the Rescan button on the left.
- Run the following WMI repair script on the client machines: http://www.lansweeper.com/files/repairwmi.zip
- Rescan the machines by clicking the Assets link at the top of the Lansweeper web console, ticking the checkboxes in front of the assets and hitting the Rescan button on the left.
