Jump to content


  • 0
Ironman

Push Agent

Question

Is this error something we can overlook........... Push agent deployment works 100%..... yet we still get " CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e SMS_CLIENT_CONFIG_MANAGER ---> Unable to connect to WMI ® on remote machine "ROFUSRDSK101", error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER" when push agent gets initiated. below is the log error from CCM.log.

As mentioned, push agent works and agent gets installed...

 

Waiting for change in directory "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:31 39616 (0x9AC0)

======>Begin Processing request: "JHJG1T8T", machine name: "ROFUSRDSK101" SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:31 39380 (0x99D4)

---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x1) SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:31 39380 (0x99D4)

---> Attempting to connect to administrative share '\\rofusrdsk101.CompanyX.local\admin$' using account 'Datacash\svc-sccm-client_inst' SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:31 39380 (0x99D4)

---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account Datacash\svc-sccm-client_inst (00000005) SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:31 39380 (0x99D4)

---> LogonUser failed (LOGON32_LOGON_INTERACTIVE) using account Datacash\svc-sccm-client_inst (00000569) SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:32 39380 (0x99D4)

---> The 'best-shot' account has now succeeded 11 times and failed 2 times. SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:32 39380 (0x99D4)

---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:32 39380 (0x99D4)

---> Attempting to connect to administrative share '\\rofusrdsk101.CompanyX.local\admin$' using account 'Companyx\SVC-SCCM_Client_Inst' SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:32 39380 (0x99D4)

---> Connected to administrative share on machine rofusrdsk101.CompanyX.local using account 'Companyx\SVC-SCCM_Client_Inst' SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:32 39380 (0x99D4)

---> Attempting to make IPC connection to share <\\rofusrdsk101.CompanyX.local\IPC$> SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:32 39380 (0x99D4)

---> Searching for SMSClientInstall.* under '\\rofusrdsk101.CompanyX.local\admin$\' SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:32 39380 (0x99D4)

---> System OS version string "5.1.2600" converted to 5.10 SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:32 39380 (0x99D4)

---> Service Pack version from machine "ROFUSRDSK101" is 3 SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:32 39380 (0x99D4)

CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:32 39380 (0x99D4)

---> Unable to connect to WMI ® on remote machine "ROFUSRDSK101", error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:32 39380 (0x99D4)

---> Creating \ VerifyingCopying exsistance of destination directory \\ROFUSRDSK101\admin$\system32\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:32 39380 (0x99D4)

---> Copying client files to \\ROFUSRDSK101\admin$\system32\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:32 39380 (0x99D4)

---> Copying file "C:\Program Files (x86)\Microsoft Configuration Manager\bin\I386\MobileClient.tcf" to "\\ROFUSRDSK101\admin$\system32\ccmsetup\MobileClient.tcf" SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:32 39380 (0x99D4)

---> Created service "ccmsetup" on machine "ROFUSRDSK101". SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:33 39380 (0x99D4)

---> Started service "ccmsetup" on machine "ROFUSRDSK101". SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:34 39380 (0x99D4)

---> Deleting SMS Client Install Lock File '\\rofusrdsk101.CompanyX.local\admin$\SMSClientInstall.P02' SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:34 39380 (0x99D4)

---> Completed request "JHJG1T8T", machine name "ROFUSRDSK101". SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:34 39380 (0x99D4)

Deleted request "JHJG1T8T", machine name "ROFUSRDSK101" SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:34 39380 (0x99D4)

<======End request: "JHJG1T8T", machine name: "ROFUSRDSK101". SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:40:34 39380 (0x99D4)

Thread has been inactive too long. Closing thread SMS_CLIENT_CONFIG_MANAGER 02/08/2011 12:50:34 39380 (0x99D4)

Share this post


Link to post
Share on other sites

1 answer to this question

Recommended Posts

  • 0

Yes, if the client deployment / assignment process is working, you should be able to safely overlook this error. I have a feeling that the site server is attempting to make a connection to the remote system's root\ccm WMI namespace (exists only if the SCCM client is installed). Assuming this is true, it probably does this as a check to ensure that the client is not already installed (but perhaps unassigned or broken).

 

Just a theory, but seems probable ...

 

Hope this helps.

 

Cheers,

Trevor Sullivan

http://trevorsullivan.net

http://twitter.com/pcgeek86

  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.