I have over 10% of computers without functional sccm client (client = NO). I became frastruated because all computers are not online all the time, and mostly reason is that WMI is not working correctly. Before today I had to manually repair WMI on every computer (still there is 170 machines without working client). Now I came up with solution - I will gather these computers to a group, apply new group policy object with shutdown script which will do this: net stop winmgmt /Y ren %systemroot%\System32\wbem\Repository RepositoryX.old net start winmgmt Now I just have to envent a method, how this batch file would be run only once. Feel free to comment my suggestion :)

http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/f314693f-d5aa-4625-82c9-f56ad43a33b5http://sccm.com.ua/

Slamming the repository (what the commands above are doing) is generally very bad practice and is not fixing the issue, just the symptom. http://blogs.technet.com/b/configmgrteam/archive/2009/05/08/wmi-troubleshooting-tips.aspx Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Hi, It's not certain that WMI is the root casuse to the problem. I would find out why clients are not being installed. A good place to start is by spcifying a Fallback Status Point in the installation attemp and use the reports to get a little extra information.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

Thanks you guys. Reason for renewing WMI is, that when I investigate ccmsetup.log, installation fails because of some WMI namespace error. I will paste specific results in monday.

Thanks you guys. Reason for renewing WMI is, that when I investigate ccmsetup.log, installation fails because of some WMI namespace error. I will paste specific results in monday.

What the lines of code above are doing is not a repair though, it's a complete deletion which can cause data loss. This should always be an absolute last resort.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

What the lines of code above are doing is not a repair though, it's a complete deletion which can cause data loss. This should always be an absolute last resort.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Here are some scennarios of computer which are not registered on ConfMgr console as clients=YES. Scennario 1: C$ cannot be mapped WMI Control Properites cannot be contacted: Win32: The RPC server is unavailable. Scennario 2: c$ contacted WMI Control Properites failed to connect because WMI: initialization failure. ccmsetup.log MSI: Warning 25001. Setup failed due to unexpected circumstances MSI: Warning 25151. Setup was unable to unregister the UpdatesAgent endpoint The error code is 80004005 MSI: Warning 25002. Failed to delete __MethodProviderRegistration.Provider="__Win32Provider.Name=\"SmsClientMethodProvider\"" from CCM The error code is 80041014 MSI: Warning 25002. Failed to delete __MethodProviderRegistration.Provider="__Win32Provider.Name=\"SmsClientMethodProvider\"" from CCM The error code is 80041014 Installation failed with error code 1603 Scennario 3: C$ contacted WMI Control Properties successfully connected Client installation succeeded execmgr.log Failed to open to WMI namespace '\\.\root\ccm\Policy\Machine' (8007045b) Failed to ConnectSettings for ICcmPolicyAgent in CSoftDistPolicyNamespace::ConnectToNamespace Failed to ConnectToNamespace in CSoftDistPolicyNamespace::GetMachinePolicy Failed to connect to machine policy name space. 0x8007045b CSoftwareDistPolicyMgr::GetSWDistSiteSettings failed to connect to machine namespace Failed to instantiate UI Server {C2F23AE4-82D8-456F-A4AF-A2655D8CA726} with error 8000401a Failed to instantiate UI Server 2 {E8425D59-451B-4978-A2AB-641470EB7C02} with error 8000401a Failed to instantiate Updates UI Server {2D023958-73D0-4542-8AD6-9A507364F70E} with error 8000401a Failed to instantiate VApp UI Server {00AAB372-0D6D-4976-B5F5-9BC7605E30BB} with error 0x8000401A Scennario 4: C$ contacted WMI Control Properties successfully connected Client installtion succeeded ccmsetup.log: Control Properties successfully connected Ccmsetup is not registered in the Run key CFSPStateMessage::CFSPStateMessage CFSPStateMessage::IsFSPHostSet CFSPStateMessage::IsFSPHostSet CFSPStateMessage::~CFSPStateMessage No errors on other logs. Scennario 5: c$ contacted WMI control properties successfully connected Client installation succeeded execmgr.log Common Client Agent Settings for the client are missing from WMI. Failed to open to WMI namespace '\\.\root\ccm\Policy\Machine' (8007045b) Failed to ConnectSettings for ICcmPolicyAgent in CSoftDistPolicyNamespace::ConnectToNamespace Failed to connect to machine policy name space. 0x8007045b CSoftwareDistPolicyMgr::GetSWDistSiteSettings failed to connect to machine namespace CSoftwareDistPolicyMgr::GetSWDistSiteSettings failed to connect to machine namespace I'm sure I can find more different scennarios. I know I should probably just google around those error codes, but my knowledge of WMI is quite limited, and it makes it difficult that there is so many errors in different cases. What should I do to solve this problem all in once and for all :) ..and we are still running under Windows XP. The ratio of Client=NO machines is something like 12% of the whole workstation enviroment.

Here are some scennarios of computer which are not registered on ConfMgr console as clients=YES. Scennario 1: C$ cannot be mapped WMI Control Properites cannot be contacted: Win32: The RPC server is unavailable. Scennario 2: c$ contacted WMI Control Properites failed to connect because WMI: initialization failure. ccmsetup.log MSI: Warning 25001. Setup failed due to unexpected circumstances MSI: Warning 25151. Setup was unable to unregister the UpdatesAgent endpoint The error code is 80004005 MSI: Warning 25002. Failed to delete __MethodProviderRegistration.Provider="__Win32Provider.Name=\"SmsClientMethodProvider\"" from CCM The error code is 80041014 MSI: Warning 25002. Failed to delete __MethodProviderRegistration.Provider="__Win32Provider.Name=\"SmsClientMethodProvider\"" from CCM The error code is 80041014 Installation failed with error code 1603 Scennario 3: C$ contacted WMI Control Properties successfully connected Client installation succeeded execmgr.log Failed to open to WMI namespace '\\.\root\ccm\Policy\Machine' (8007045b) Failed to ConnectSettings for ICcmPolicyAgent in CSoftDistPolicyNamespace::ConnectToNamespace Failed to ConnectToNamespace in CSoftDistPolicyNamespace::GetMachinePolicy Failed to connect to machine policy name space. 0x8007045b CSoftwareDistPolicyMgr::GetSWDistSiteSettings failed to connect to machine namespace Failed to instantiate UI Server {C2F23AE4-82D8-456F-A4AF-A2655D8CA726} with error 8000401a Failed to instantiate UI Server 2 {E8425D59-451B-4978-A2AB-641470EB7C02} with error 8000401a Failed to instantiate Updates UI Server {2D023958-73D0-4542-8AD6-9A507364F70E} with error 8000401a Failed to instantiate VApp UI Server {00AAB372-0D6D-4976-B5F5-9BC7605E30BB} with error 0x8000401A Scennario 4: C$ contacted WMI Control Properties successfully connected Client installtion succeeded ccmsetup.log: Control Properties successfully connected Ccmsetup is not registered in the Run key CFSPStateMessage::CFSPStateMessage CFSPStateMessage::IsFSPHostSet CFSPStateMessage::IsFSPHostSet CFSPStateMessage::~CFSPStateMessage No errors on other logs. Scennario 5: c$ contacted WMI control properties successfully connected Client installation succeeded execmgr.log Common Client Agent Settings for the client are missing from WMI. Failed to open to WMI namespace '\\.\root\ccm\Policy\Machine' (8007045b) Failed to ConnectSettings for ICcmPolicyAgent in CSoftDistPolicyNamespace::ConnectToNamespace Failed to connect to machine policy name space. 0x8007045b CSoftwareDistPolicyMgr::GetSWDistSiteSettings failed to connect to machine namespace CSoftwareDistPolicyMgr::GetSWDistSiteSettings failed to connect to machine namespace I'm sure I can find more different scennarios. I know I should probably just google around those error codes, but my knowledge of WMI is quite limited, and it makes it difficult that there is so many errors in different cases. What should I do to solve this problem all in once and for all :) ..and we are still running under Windows XP. The ratio of Client=NO machines is something like 12% of the whole workstation enviroment.

http://eskonr.com/2009/03/how-to-troubleshoot-the-systems-which-has-wmi-issues-rebuild-wmi-repository/http://sccm.com.ua/

Well, first of all, I don´t have enough manpower to fix every computer´s WMI manually, even by Remote Desktop connection. So this must be done with centralized method. I ran through your links, and even I understand method to fix, not wipe out, I don´t know how to spread the method all over the computer management, not single computer.

Well, first of all, I don´t have enough manpower to fix every computer´s WMI manually, even by Remote Desktop connection. So this must be done with centralized method. I ran through your links, and even I understand method to fix, not wipe out, I don´t know how to spread the method all over the computer management, not single computer.

How about using PSexec as the need arises? Or Roger Zander's Client Center; it has three methods built in to help you try to remediate WMI issues on remote systems (the third one is slamming the repository).Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

How about using PSexec as the need arises? Or Roger Zander's Client Center; it has three methods built in to help you try to remediate WMI issues on remote systems (the third one is slamming the repository). Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys Could you please provide me the link what are you talking about? Thank you and have a nice weekend to everybody!

http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx http://sourceforge.net/projects/smsclictr/Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys