Hi All, I tried to push the client but i got the following error in the CCM.log: failed to connect to \\computername\ admin$ share using account "Machine Account" mentioning that Im using the domain administrator account for the push installation and the SCCM machine account also is a member in the domain admins group

Have you rebooted your server after adding it's account to the domain admins group? This is necessary for the changes to take effect.

Ididn't reboot the server, I did but now I got another error : CWmi::Connect(): ConnectServer(Namespace) failed. - 0x800706baSMS_CLIENT_CONFIG_MANAGER > Unable to connect to WMI on remote machine "Computer name", error = 0x800706ba.SMS_CLIENT_CONFIG_MANAGER

I guess it's a firewall issue on the client. See http://technet.microsoft.com/en-us/library/bb694088.aspxfor details ("File and Printer Sharing" and "Windows Management Instrumentation (WMI)").

Clientfirewall is not running on both the SCCM serevr and the client (win 2k3)

You still need remote access to WMI on the target client. We use that during a push process. To see if you have it working successfully: * From the site server, start wbemtest.exe from a command prompt * Click Connect * In the Namespace box, type \\clientname\root\default or \root\cimv2 If you get an error, then you don't have remote WMI enabled yet. If that works, then we should work also.

Hi Wally, I tried to type \\clientname\c:\cimv2,but I got an error, as you mentioned we need to have remote WMI enabled, please send me how to enabled it ?

The connection to remote WMI is more like a UNC path \\clientname\root\cimv2. The c: reference in the path will not work

The connection to remote WMI is more like a UNC path \\clientname\root\cimv2. The c: reference in the path will not work

Stan is correct, you did not use the path I mentioned, yours won't work. Use the exact text, just change "clientname" to the actual computer name. If you can't connect, then you do have to enable remote WMI. I think you do this on the WMI component in Computer Management, but I'd suggest you search http://support.microsoft.com for it, as I always have the firewall enabled, and it is a different command with the firewall enabled.

I found solution -on client machine add registry path: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\Internet]"Ports"=hex(7):37,00,30,00,30,00,30,00,2d,00,37,00,31,00,30,00,30,00,00,00,00,\ 00"PortsInternetAvailable"="Y""UseInternetPorts"="Y" http://support.microsoft.com/kb/154596/ Pozdrav od Safeta Grahica

Hi All. Idisable the firewall windows on some machines that im using to test the installation of SCCM client, although i already give permission to my service account (domain admin)on the WMI ( remote enable ) but with no successfully result, i use the webmtest.exe utility and i can connect to the machine but on the ccm.log the line "CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e" is still appearing, some other lines are: ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account service account (000004b3), Im already install the client on 1100 machines with the same account. Like I say before I have my firewall with the necessary exceptions and on the problematic machines the service is disable, so this is not the problem. My account is a domain admin, so this is not the problem I give permission to my service account on WMI im very tired to fight with SMS 2003 and SCCM 2007 because im seeing that the same problems occur on the two version, I have never see a version of SMS2003 or SCCM with no problems. Any idea?? Thanks for your help Greetings from Colombia.

Well a lot of us have had great success with both SMS and Configuration Manager - you just have to have knowledge about it, and how to make it do what you want it to do :-) Error 4b3 is a transient network error (No network provider accepted the given network path) - so it is NOT a Configuration Manager issue. Error 0x8004100e is "Invalid namespace", which sounds like a WMI corruption issue to me - again NOT a Configuration Manager issue.

Hi, thanks for you reply, I agree with you with the cause of error 4b3, but i have a live ping to the machines that mention on the line that i post, so in this case forgeret about that error, in the other caseof error 0x8004100e i already follow all the steps and workarrounds too, i can connect to the namespace, the WMI test says that the wmi is fine i use scriptomatic to connect to the cimv2 and works fine, the line is still apearing and i have about 400 machines with the same error. all my 400 machines have invalid namesapace??? thaks for your knowledge.

I can only offer what I see from the error messages. A ping doesn't necessarily mean you can connect through SMB, which is what we are doing. It also does not mean that you have admin rights, which are also required. I've heard of people having issues with 3rd party firewalls that have prevented connections to clients also, something else to consider. Outside that, product support.

Thanks Wally, you are right, I remember the last year I was installing SMS2003 and I have a lot of issues with Mcafee EPO, I think that thisis the same problem but the difference is that with this client I cannot access and manipulate the EPo so I will have to ask for help to the EPO Engineers on that bank. For people who have EPO there are two logs that you can find under the user profile that records all the activity of the epo client so those logs are very helpful to troubleshoot this type of problems. if this it is not possible I will have to use some hours with Colinas Microsoft, soon i have an answer I will post the solution here for all people. Again thanks for your comments, and your patient. regards from Colombia!.

Hi Did you find any solution we have the exact same error during client pushWe have disabled the firewallOpened exception for File and printersharing and remote managementstill the same wmi errorBest regards Anders

Hi all, I face the same problem as well...I got wmi error 0x8004100e! although I have done the following:- Firewall has been disabled Antivirus has been shotdown All port has been opened between the sccm server and client I could connect wmi from sccm server to the clientPlease help me if u have solve this problem. Thanks.

Hi everyone!Ihave same problem. ... CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e ---> Unable to connect to WMI (r) on remote machine "PC-Name", error = 0x8004100e. ... ---> ERROR: Unable to start service "ccmsetup" on machine "A-EXTAUDIT", error = 1068. .... Chek service dependensis on ccmsetup.exe 1. Check WMI connections - ok!2. BITS - was not working!3. Remote RPC - ok!SoI Start BITS service and setup process started !!!p.s.Environment:Win srv 2008 SP1,SQL 2005Win srv 2008 SP1, SCCMSP1Win XP SP 3

Has anyone found a solution yet? i am having similar issue

Hi - I am having same issue. My SCCM Server is on Windows 2008 and clinet is Windows XP.I am able to access WMI from both sides and I tested by running query that is also sucessful.Still getting CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e ---> Unable to connect to WMI (r) on remote machine "ABC", error = 0x8004100e.Please help me if any one got solution. ravi

error = 0x8004100e = WBEM_E_INVALID_NAMESPACE. Is this happening on one or more clients? If it's only one: WMI might have problems.

Thanks for reply.WBEM_E_INVALID_NAMESPACE is not found in the log file. I am getting this looged in error.I am facing this issue in my test lab where this is the only client.Can you please send me any specific refrence for WMI.ravi

ConnectServer(Namespace) failed. i get the same error

Windows Management Instrumentation (WMI) error=0x8004100e in Sccm 2007 on win 2008,SQL 2005 on win xpsp3 client The issue is still not resolved.....

The issue is still not resolved..... Which issue is *still* not resolved? That's your first posting here in this thread ... could you please add some more details, log snipppets?

I tried all possible work around mention above and also google it around.Still WMI error while pushing client agent. Please check below logs and suggest. Thanks for reply Sleeping for 611 seconds... $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 11:47:09.107 2010 India Standard Time><thread=4760 (0x1298)> CCR count in queue "Incoming" is 0. $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 11:57:20.133 2010 India Standard Time><thread=4760 (0x1298)> CCR count in queue "Processing" is 0. $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 11:57:20.133 2010 India Standard Time><thread=4760 (0x1298)> CCR count in queue "Retry" is 3. $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 11:57:20.133 2010 India Standard Time><thread=4760 (0x1298)> Sleeping for 589 seconds... $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 11:57:20.133 2010 India Standard Time><thread=4760 (0x1298)> Waiting for change in directory "C:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:00:20.842 2010 India Standard Time><thread=4692 (0x1254)> The Site Control File has not changed since the last parameter update. $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:07:09.158 2010 India Standard Time><thread=4760 (0x1298)> Updating Site Parameters $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:07:09.158 2010 India Standard Time><thread=4760 (0x1298)> ~MP Ports: 80 $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:07:09.158 2010 India Standard Time><thread=4760 (0x1298)> ~MP SSL Ports: 443 $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:07:09.158 2010 India Standard Time><thread=4760 (0x1298)> ~IISPreferedPort: 80 $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:07:09.158 2010 India Standard Time><thread=4760 (0x1298)> ~IISSSLPreferedPort: 443 $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:07:09.158 2010 India Standard Time><thread=4760 (0x1298)> ~Default MP: SCMANAGER $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:07:09.158 2010 India Standard Time><thread=4760 (0x1298)> ~SSL State: 0 $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:07:09.158 2010 India Standard Time><thread=4760 (0x1298)> ~Certificate Selection Criteria: $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:07:09.158 2010 India Standard Time><thread=4760 (0x1298)> ~Certificate Store: $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:07:09.158 2010 India Standard Time><thread=4760 (0x1298)> ~Select First Certificate: 0 $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:07:09.158 2010 India Standard Time><thread=4760 (0x1298)> Checking configuration information for server: SCMANAGER.~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:07:09.158 2010 India Standard Time><thread=4760 (0x1298)> Checking configuration information for server: SCMANAGER.~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:07:09.158 2010 India Standard Time><thread=4760 (0x1298)> ~Fallback Status Point: SCMANAGER.SQUARE.COM $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:07:09.158 2010 India Standard Time><thread=4760 (0x1298)> ~Install on DC: True $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:07:09.158 2010 India Standard Time><thread=4760 (0x1298)> Sleeping for 1200 seconds... $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:07:09.220 2010 India Standard Time><thread=4760 (0x1298)> Received request: "XRYIZOO3" for machine name: "SCMANAGER" on queue: "Incoming". $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:07.804 2010 India Standard Time><thread=4692 (0x1254)> Stored request "XRYIZOO3", machine name "SCMANAGER", in queue "Processing". $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:07.804 2010 India Standard Time><thread=4692 (0x1254)> ----- Started a new CCR processing thread. Thread ID is 0x1290. There are now 1 processing threads $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:09.805 2010 India Standard Time><thread=4692 (0x1254)> Submitted request successfully $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:09.805 2010 India Standard Time><thread=4692 (0x1254)> Getting a new request from queue "Incoming" after 100 millisecond delay. $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:09.805 2010 India Standard Time><thread=4692 (0x1254)> Waiting for change in directory "C:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:09.805 2010 India Standard Time><thread=4692 (0x1254)> ======>Begin Processing request: "XRYIZOO3", machine name: "SCMANAGER" $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:09.898 2010 India Standard Time><thread=4752 (0x1290)> ---> Trying each entry in the SMS Client Remote Installation account list~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:09.898 2010 India Standard Time><thread=4752 (0x1290)> ---> Attempting to connect to administrative share '\\SCmanager.square.com\admin$' using account 'square.com\administrator'~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:09.898 2010 India Standard Time><thread=4752 (0x1290)> ---> Connected to administrative share on machine SCmanager.square.com using account 'square.com\administrator'~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:10.289 2010 India Standard Time><thread=4752 (0x1290)> ---> Attempting to make IPC connection to share <\\SCmanager.square.com\IPC$> ~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:10.289 2010 India Standard Time><thread=4752 (0x1290)> ---> Searching for SMSClientInstall.* under '\\SCmanager.square.com\admin$\'~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:10.289 2010 India Standard Time><thread=4752 (0x1290)> ---> System OS version string "6.0.6002" converted to 6.00 $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:16.555 2010 India Standard Time><thread=4752 (0x1290)> CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:17.618 2010 India Standard Time><thread=4752 (0x1290)> ---> Unable to connect to WMI (r) on remote machine "SCMANAGER", error = 0x8004100e. $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:17.618 2010 India Standard Time><thread=4752 (0x1290)> ---> Creating \ VerifyingCopying exsistance of destination directory \\SCMANAGER\admin$\system32\ccmsetup.~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:17.649 2010 India Standard Time><thread=4752 (0x1290)> ---> Copying client files to \\SCMANAGER\admin$\system32\ccmsetup.~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:17.961 2010 India Standard Time><thread=4752 (0x1290)> ---> Copying file "C:\Program Files\Microsoft Configuration Manager\bin\I386\MobileClient.tcf" to "\\SCMANAGER\admin$\system32\ccmsetup\MobileClient.tcf" $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:17.977 2010 India Standard Time><thread=4752 (0x1290)> ---> Updated service "ccmsetup" on machine "SCMANAGER". $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:18.430 2010 India Standard Time><thread=4752 (0x1290)> ---> Started service "ccmsetup" on machine "SCMANAGER". $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:23.946 2010 India Standard Time><thread=4752 (0x1290)> ---> Deleting SMS Client Install Lock File '\\SCmanager.square.com\admin$\SMSClientInstall.GPO'~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:23.946 2010 India Standard Time><thread=4752 (0x1290)> ---> Completed request "XRYIZOO3", machine name "SCMANAGER". $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:23.962 2010 India Standard Time><thread=4752 (0x1290)> Deleted request "XRYIZOO3", machine name "SCMANAGER" $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:23.962 2010 India Standard Time><thread=4752 (0x1290)> <======End request: "XRYIZOO3", machine name: "SCMANAGER". $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:23.962 2010 India Standard Time><thread=4752 (0x1290)>

---> Unable to connect to WMI (r) on remote machine "SCMANAGER", error = 0x8004100e. $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:17.618 2010 India Standard Time><thread=4752 (0x1290)> [...] ---> Started service "ccmsetup" on machine "SCMANAGER". $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:23.946 2010 India Standard Time><thread=4752 (0x1290)> No need to worry, because the ccmsetup service was started successful after that. Check ccmsetup.log on the client.

Thanks for the reply... ccm service installed but it is not starting. attaching ccmsetup.log ==========[ ccmsetup started in process 1792 ]========== ccmsetup 12/3/2010 3:24:53 PM 1804 (0x070C) Version: 4.0.6221.1000 ccmsetup 12/3/2010 3:24:53 PM 1804 (0x070C) Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 12/3/2010 3:24:53 PM 1804 (0x070C) Command line: "C:\WINDOWS\system32\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf ccmsetup 12/3/2010 3:24:53 PM 1804 (0x070C) CCMHTTPPORT: 80 ccmsetup 12/3/2010 3:24:53 PM 1804 (0x070C) CCMHTTPSPORT: 443 ccmsetup 12/3/2010 3:24:53 PM 1804 (0x070C) CCMHTTPSSTATE: 0 ccmsetup 12/3/2010 3:24:53 PM 1804 (0x070C) CCMHTTPSCERTNAME: ccmsetup 12/3/2010 3:24:53 PM 1804 (0x070C) FSP: SCMANAGER.SQUARE.COM ccmsetup 12/3/2010 3:24:53 PM 1804 (0x070C) CCMFIRSTCERT: 0 ccmsetup 12/3/2010 3:24:53 PM 1804 (0x070C) Config file: C:\WINDOWS\system32\ccmsetup\MobileClient.tcf ccmsetup 12/3/2010 3:24:53 PM 1804 (0x070C) Retry time: 10 minute(s) ccmsetup 12/3/2010 3:24:53 PM 1804 (0x070C) MSI log file: ccmsetup 12/3/2010 3:24:53 PM 1804 (0x070C) MSI properties: INSTALL="ALL" SMSSITECODE="GPO" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" FSP="SCMANAGER.SQUARE.COM" CCMFIRSTCERT="0" ccmsetup 12/3/2010 3:24:53 PM 1804 (0x070C) Source List: ccmsetup 12/3/2010 3:24:53 PM 1804 (0x070C) \\SCMANAGER.SQUARE.COM\SMSClient ccmsetup 12/3/2010 3:24:53 PM 1804 (0x070C) \\SCMANAGER\SMSClient ccmsetup 12/3/2010 3:24:53 PM 1804 (0x070C) MPs: ccmsetup 12/3/2010 3:24:53 PM 1804 (0x070C) SCMANAGER.SQUARE.COM ccmsetup 12/3/2010 3:24:53 PM 1804 (0x070C) Updated security on object C:\WINDOWS\system32\ccmsetup\. ccmsetup 12/3/2010 3:24:54 PM 1804 (0x070C) Sending Fallback Status Point message, STATEID='100'. ccmsetup 12/3/2010 3:24:54 PM 1804 (0x070C) Running as user "SYSTEM" ccmsetup 12/3/2010 3:25:12 PM 1936 (0x0790) Detected 18803 MB free disk space on system drive. ccmsetup 12/3/2010 3:25:12 PM 1936 (0x0790) DetectWindowsEmbeddedFBWF() Detecting OS Version ccmsetup 12/3/2010 3:25:12 PM 1936 (0x0790) Client OS is not Windows XP Embedded ccmsetup 12/3/2010 3:25:12 PM 1936 (0x0790) Successfully ran BITS check. ccmsetup 12/3/2010 3:25:14 PM 1936 (0x0790) Failed to send HTTP request. (Error at WinHttpSendRequest: 12007) ccmsetup 12/3/2010 3:25:29 PM 1936 (0x0790) DownloadFileByWinHTTP encountered an unrecoverable error. ccmsetup 12/3/2010 3:25:29 PM 1936 (0x0790) Sending Fallback Status Point message, STATEID='308'. ccmsetup 12/3/2010 3:25:29 PM 1936 (0x0790) sending with winhttp failed; 80072ee7 FSPStateMessage 12/3/2010 3:25:44 PM 1936 (0x0790) ==========[ ccmsetup started in process 1820 ]========== ccmsetup 12/3/2010 4:04:43 PM 1836 (0x072C) Version: 4.0.6221.1000 ccmsetup 12/3/2010 4:04:44 PM 1836 (0x072C) Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 12/3/2010 4:04:44 PM 1836 (0x072C) Command line: "C:\WINDOWS\system32\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf ccmsetup 12/3/2010 4:04:44 PM 1836 (0x072C) CCMHTTPPORT: 80 ccmsetup 12/3/2010 4:04:44 PM 1836 (0x072C) CCMHTTPSPORT: 443 ccmsetup 12/3/2010 4:04:44 PM 1836 (0x072C) CCMHTTPSSTATE: 0 ccmsetup 12/3/2010 4:04:44 PM 1836 (0x072C) CCMHTTPSCERTNAME: ccmsetup 12/3/2010 4:04:44 PM 1836 (0x072C) FSP: SCMANAGER.SQUARE.COM ccmsetup 12/3/2010 4:04:44 PM 1836 (0x072C) CCMFIRSTCERT: 0 ccmsetup 12/3/2010 4:04:44 PM 1836 (0x072C) Config file: C:\WINDOWS\system32\ccmsetup\MobileClient.tcf ccmsetup 12/3/2010 4:04:44 PM 1836 (0x072C) Retry time: 10 minute(s) ccmsetup 12/3/2010 4:04:44 PM 1836 (0x072C) MSI log file: ccmsetup 12/3/2010 4:04:44 PM 1836 (0x072C) MSI properties: INSTALL="ALL" SMSSITECODE="GPO" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" FSP="SCMANAGER.SQUARE.COM" CCMFIRSTCERT="0" ccmsetup 12/3/2010 4:04:44 PM 1836 (0x072C) Source List: ccmsetup 12/3/2010 4:04:44 PM 1836 (0x072C) \\SCMANAGER.SQUARE.COM\SMSClient ccmsetup 12/3/2010 4:04:44 PM 1836 (0x072C) \\SCMANAGER\SMSClient ccmsetup 12/3/2010 4:04:44 PM 1836 (0x072C) MPs: ccmsetup 12/3/2010 4:04:44 PM 1836 (0x072C) SCMANAGER.SQUARE.COM ccmsetup 12/3/2010 4:04:44 PM 1836 (0x072C) Updated security on object C:\WINDOWS\system32\ccmsetup\. ccmsetup 12/3/2010 4:04:44 PM 1836 (0x072C) Sending Fallback Status Point message, STATEID='100'. ccmsetup 12/3/2010 4:04:44 PM 1836 (0x072C)

---> Unable to connect to WMI (r) on remote machine "SCMANAGER", error = 0x8004100e. $$<SMS_CLIENT_CONFIG_MANAGER><Fri Dec 03 12:14:17.618 2010 India Standard Time><thread=4752 (0x1290)> Have you tried following: 1. Use the Start menu to right-click My Computer. 2. Press the Manage item. 3. Double-click Services and Applications in the left-hand pane. 4. Press Services to expand it. 5. Scroll to Windows Management Instrumentation in the right-hand pane and right-click it. 6. Press Stop. 7. Use Windows Explorer to delete all the files in the %SystemRoot%\System32\Wbem\Repository folder. 8. Shutdown and restart your computer. The Windows Management Instrumentation service will start and the files will be re-created

I know that this thread is old and probably dead and buried, however, I must add that I've had this exact same error message. Here is a snippet of my log: ======>Begin Processing request: "XCPIUICA", machine name: "TOP02" $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 01 08:28:31.132 2011 W. Europe Daylight Time><thread=4408 (0x1138)> ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)~ $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 01 08:28:31.132 2011 W. Europe Daylight Time><thread=4408 (0x1138)> ---> Attempting to connect to administrative share '\\TOP02.top.local\admin$' using account 'MGMT\SVCSCCM'~ $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 01 08:28:31.132 2011 W. Europe Daylight Time><thread=4408 (0x1138)> ---> The 'best-shot' account has now succeeded 34 times and failed 0 times. $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 01 08:28:31.226 2011 W. Europe Daylight Time><thread=4408 (0x1138)> ---> Connected to administrative share on machine TOP02.top.local using account 'MGMT\SVCSCCM'~ $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 01 08:28:31.226 2011 W. Europe Daylight Time><thread=4408 (0x1138)> ---> Attempting to make IPC connection to share <\\TOP02.top.local\IPC$> ~ $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 01 08:28:31.226 2011 W. Europe Daylight Time><thread=4408 (0x1138)> ---> Searching for SMSClientInstall.* under '\\TOP02.top.local\admin$\'~ $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 01 08:28:31.226 2011 W. Europe Daylight Time><thread=4408 (0x1138)> CWmi::Connect(): ConnectServer(Namespace) failed. - 0x800706ba~ $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 01 08:28:31.896 2011 W. Europe Daylight Time><thread=4408 (0x1138)> ---> Unable to connect to WMI on remote machine "TOP02", error = 0x800706ba. $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 01 08:28:31.896 2011 W. Europe Daylight Time><thread=4408 (0x1138)> ---> Deleting SMS Client Install Lock File '\\TOP02.top.local\admin$\SMSClientInstall.ASP'~ $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 01 08:28:31.896 2011 W. Europe Daylight Time><thread=4408 (0x1138)> Retry request id for "XCPIUICA" set to "TOP02_top_local" $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 01 08:28:31.912 2011 W. Europe Daylight Time><thread=4408 (0x1138)> Stored request "TOP02_top_local", machine name "TOP02", in queue "Retry". $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 01 08:28:31.912 2011 W. Europe Daylight Time><thread=4408 (0x1138)> <======End request: "TOP02_top_local", machine name: "TOP02". $$<SMS_CLIENT_CONFIG_MANAGER><Wed Jun 01 08:28:31.912 2011 W. Europe Daylight Time><thread=4408 (0x1138)> This client is on a different domain than my SCCM server, and therefore has a different DNS suffix. It turns out that WMI needs to be able to resolve the NETBIOS name, rather than the fully distinguished name. Seems a bit of a step backwards to me, however I resolved this problem by adding additional DNS suffixes to the network on the SCCM server, so that even if I just typed "ping TOP02" it found an IP, rather than specifying FQDN.