Wednesday, October 27, 2010

Dealing with WMI Issues – Part 2

Assuming that the WMIDiag script did not repair the WMI Subsystem sufficiently to allow for a successful client reinstall, the next step is to run a more "invasive" WMI Repair process. Luckily, it doesn't need to come with a lot of legwork on your part.

Enter the SCCM Client Center

If you haven't done so already, download the SCCM Client Center v2.0.2 from SourceForge. This tool gives you the ability to gain a great deal of info about the clients remotely including site assignment, recent advertisement and inventory activity, and the ability to trigger a number of actions on a healthy client. The Client Center also provides a number of actions that are invaluable when trying to repair clients. Unfortunately, the tool can be a bit "clunky" to use when addressing a significant number of machines and the uninstall action doesn't end up completing on a significant number of machines. However, the WMIRepair service that is included is a great follow-up to the Microsoft WMIDiag process as it goes a little bit further in trying to address the WMI subsystem. This service will also take a look at several of the key registry and DLL files, but will take it a big step beyond that. This WMIRepair process will also:
  • Reregister every DLL and EXE in the WMI folders
  • Force a full service reregistration
  • Recompile every MOF and MTL file in the repository
To perform the WMIRepair process, simply enter the name of the machine you wish to repair in the upper left corner and click Connect. Once connected, navigate to the Install/Repair tab and click the WMIRepair button. You can track the progress of the service by clicking the folder icon next to the WMI Repair button and navigating to the WMIRepair.log file.
Once the service completes and uninstalls itself, you can once again try to install the SCCM client again to see if you can get a successful installation.
Even this thorough revisiting of the WMI subsystem doesn't end up solving every WMI problem, it definitely addresses a significant number of issues. In tomorrow's article, we will cover what to do when this approach still doesn't solve the problem.

No comments:

Post a Comment