Hi,Im running a medium to large SCCM park (8000 clients) and currently I have around 400+ machine with a disfunctional SCCM client.From my investigation it seems like 50% of the problem are due to WMI being corrupt.I have been testing with various SCCM client health scripts but I was wondering if someone had experience with a good and simple WMI health/repair script that I could integrate into our logon script which is running on all machines?Thank you.

This should get you started:http://myitforum.com/cs2/blogs/cstauffer/archive/2008/06/13/client-health-check-script-and-scheduled-task-version-1-1-release.aspxandhttp://myitforum.com/cs2/blogs/scassells/archive/2009/01/28/sms-2003-client-health-startup-script-v4-18.aspx

Thank you for the link.I had a look on this myself but as far as I understand this suggests to run an advertisement daily on all clients to check for problems. My problem is that the clients are so broken that they don't have a client at all.The health check vbs in the example has a WMI check but it seems like its not done yet: Health_Check.VBS Check System Health i. Check for existence of Admin$ 1. Repair if possible ii. Check for existence of SCCM admin account 1. Add if needed iii. Check WMI 1. Still thinking about solution but dont want to destroy and rebuild

Most problems are WMI related (as far as I can tell). I haven't found a solution on how to check if WMI is really healthy. Just successfully connecting to root\whatever is not enough.

Hi JesperHave a look at the The WMI Diagnosis Utility -- Version 2.0 (http://www.microsoft.com/downloads/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en) and ccmrepair.exe in the .\Syste32\CCM folder.Hopefully this could help you in repairing your clients :-)Ulrik Skadhauge Jensen

Those tools are helpful when trying to troubleshoot single machines, but Jesper is looking for "a good and simple WMI health/repair script that I could integrate into our logon script which is running on all machines?"

Hi!has anybody managed to get this work?I got so far that client starts installing ConfigMgr client, but stops. Last entry in the CCMSetup.log file is:Successfully ran BITS check.Any ideas?Thanks,Peteris

http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/f314693f-d5aa-4625-82c9-f56ad43a33b5/?prof=requiredI'm going to give this a try.