I have pecular issue in my network. I'm searching a method to deliver the SCCM 2007 client to all machines and i use Client push method and Startup script. But still i have 20% of clients as unhealthy and i'm trying to fix those. The main issues are; 1. WMI is not working or SCCM related classes are not functional(Rebuilding is not a solution as this will affect other applications too) 2. Admin$ share access issue : Some how(not controlled by myself) admin$ is not able to access on client machine Is there any script which can list out all these issues(at this moment i'm not looking a solution) and may be i can provide these as a sample machines to management to convey there infrastructure isn't good or if you have any suggestion that would be great help. Thanks, Suraj.S

So don't rebuild the repository, repair it. Rebuilding is strongly discouraged: http://blogs.technet.com/b/configmgrteam/archive/2009/05/08/wmi-troubleshooting-tips.aspx Who's not able to access admin$? Is it available at all? Have you verified this on the local box using something like wmic share get caption,name,path?Jason | http://blog.configmgrftw.com

WMI repair has been tried. The observation in that is once we repair WMI for a week the client will be healthier and all of sudden WMI breaks again. As of now we tried, repairing the wmi and registering the dll files, but no smile on administrator face yet :( Admin$ share isn't accessible by client installation account and alo by the administrator(domain user part of local admin) not checked wmic share get caption,name,path? yet, but what it does? and what to look for? Thanks Suraj S

The you need to figure out the root cause of the issue - contrary to popular belief, WMI does not break on its own. Have you run WMIDiag as suggested by the article I linked to? Have you deployed the latest WMI stability hotfixes: http://blogs.technet.com/b/askperf/archive/2011/08/05/suggested-hotfixes-for-wmi-related-issue-on-windows-platforms.aspx ? For admin$ command-line, it will show you if the admin$ share is actually shared on the system or not. There is no way to change permissions for the admin shares so as long as it exists, accessing it is a permissions issue. I have also seen anti-malware products block access to it.Jason | http://blog.configmgrftw.com

The you need to figure out the root cause of the issue - contrary to popular belief, WMI does not break on its own. Have you run WMIDiag as suggested by the article I linked to? Have you deployed the latest WMI stability hotfixes: http://blogs.technet.com/b/askperf/archive/2011/08/05/suggested-hotfixes-for-wmi-related-issue-on-windows-platforms.aspx ? For admin$ command-line, it will show you if the admin$ share is actually shared on the system or not. There is no way to change permissions for the admin shares so as long as it exists, accessing it is a permissions issue. I have also seen anti-malware products block access to it.Jason | http://blog.configmgrftw.com

"Broken WMI", in my experience, is most often caused by clumsy system shutdowns (using the power switch, power failure, etc.). Check the timestamps on the files in \windows\system32\wbem\repository\fs\. If the timestamps are up-to-date, WMI is probably OK. If they are "stale", WMI is broken. WMI in Windows-7 is much more rugged than WMI in Windows-XP. Can't connect to ADMIN$ share? That can be caused by a number of things. Check that SCCM has security rights to the remote machine; confirm that the remote machine is actually turned on; check that the firewall isn't getting in the way; check that "File and Printer Sharing for Microsoft Networks" is turned on; check that ADMIN$ hasn't been disabled. I would suggest that you take a random sampling of problematic machines... say 10 machines. Do some in-depth troubleshooting to figure out what the true story is. You may find that more than one thing is causing issues. Once you figure out the story with those 10 machines, you probably have a pretty good idea of what's going on in your environment as a whole. There is no magic solution. Nick.

"Broken WMI", in my experience, is most often caused by clumsy system shutdowns (using the power switch, power failure, etc.). Check the timestamps on the files in \windows\system32\wbem\repository\fs\. If the timestamps are up-to-date, WMI is probably OK. If they are "stale", WMI is broken. WMI in Windows-7 is much more rugged than WMI in Windows-XP. Can't connect to ADMIN$ share? That can be caused by a number of things. Check that SCCM has security rights to the remote machine; confirm that the remote machine is actually turned on; check that the firewall isn't getting in the way; check that "File and Printer Sharing for Microsoft Networks" is turned on; check that ADMIN$ hasn't been disabled. I would suggest that you take a random sampling of problematic machines... say 10 machines. Do some in-depth troubleshooting to figure out what the true story is. You may find that more than one thing is causing issues. Once you figure out the story with those 10 machines, you probably have a pretty good idea of what's going on in your environment as a whole. There is no magic solution. Nick.