Featured Posts

System Center Orchestrator 2012 overview At Microsoft Teched North America 2011, Adam Hall presented on System Center Orchestrator 2012. System Center Orchestrator is the new name for Opalis, aquired last year -- Microsoft's premier tool for...

Read more

System Center Operations Manager 2012 network monitoring This thursday, at Microsoft Teched North America 2011, Rob Kuehfus and myself will be presenting a breakout session (SIM354) on System Center Operations Manager 2012 network monitoring. Network monitoring...

Read more

SC Operations Manager Connector for VS Team Foundation... Using the System Center Operations Manager 2007 R2 connector for Microsoft Visual Studio Team Foundation Server 2010 (download CTP1 here), operations teams can easily forward application performance...

Read more

Teched NA 2011: Day 1 Keynote Microsoft's premier and flagship IT event, Teched North America 2011, kicked off today with they "day 1 keynote". Around 15 minutes before the keynote started, two DJ's were on stage playing 'Daft Punk...

Read more

Teched NA 2011: Day 0 summary While Teched North America 2011 officially starts tomorrow, day zero or better known as the pre-conference day is done. Several hundreds of people attended these technical one-day workshops which varied...

Read more

Repair a broken client in System Center Configuration Manager 2012

Posted by Aad Noman | Posted in System Center Configuration Manager | Posted on 19-05-2011

0

All who work with Configuration Manager know that clients sometimes stop working correctly. This means that the Configuration Manager client is not communicating anymore with its management point. This will result for example in that advertisements are not being presented to the users. Two well-known causes of this are: corrupted or broken WMI on the client computer or the Client Agent services has been stopped.

System Center Configuration Manager 2012 has a built-in health feature to repair the client. The program is called Ccmeval.exe and can be found in the folder C:\Windows\Ccm. When the client is installed a scheduled task is created on the client computer to run this program daily. This means that a client should not be dysfunctional for more than 1 day.


Let see if this works.. (more)
I have a Configuration Manager 2012 environment with a computer where the Configuration Manager client is installed. When we look at the properties of the Configuration Manager client we see that most tabs are empty, meaning the client is not function as it should.

This client must be repaired in order to restore communications with the site. We can wait for the schedule task to run but in this case I run the Ccmeval.exe manually to trigger the repair process. We can track the process of repairing the client. We can this this by tracing the log file: C:\Windows\CCM\Logs\CcmEval.log.

 

 

 

 

 

 

In the log file you can see that the client health mechanism has determined that the WMI is corrupted on the client. To fix this the SMS Agent Host service is reinstalled from the client locally. Note that it is not installing from the management point. After the client is repaired the client will automatically create a DDR(Discovery Data Record) and sent this heartbeat DDR to the management point. After the Site server has processed this request the client is healthy and will receive policies again. The verify this we open the properties of the Configuration Manager in the Control Panel. As you can see the tabs are now filled with the properties of the site.

Conclusion: The client Healt feature in Configuration Manager 2012 is very welcome. it keeps the client connected to the site. When for some reason the client is not function well it gets automatically repaired.

Comments are closed.