SOLVED Unable to connect remote machine, error = 0x8004100e.

[NewbieIssues]

I have been researching this issue for a day or two now and I am still unable to get the client pushed to a machine is our Dev environment. There is a production SCCM on our network as well and I am not sure if this would cause an issue however, I have the firewall turned off on both the server side and the client. When I try to connect to the root\ccm namespace it shows as invalid. I have also Use Windows Explorer to delete all the files in the %SystemRoot%\System32\Wbem\Repository folder and restarted the client computer. I will attach the CCM.log file from the server.


Here is the CCM.log from the SCCM server

The Site Control File has not changed since the last parameter update. SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:02:48 AM 188 (0x00BC)
Updating Site Parameters SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:02:48 AM 188 (0x00BC)
MP Ports: 80 SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:02:48 AM 188 (0x00BC)
IISPreferedPort: 80 SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:02:48 AM 188 (0x00BC)
MP SSL Ports: 443 SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:02:48 AM 188 (0x00BC)
IISSSLPreferedPort: 443 SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:02:48 AM 188 (0x00BC)
Default MP: cob-sccm12d-01.xxx SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:02:48 AM 188 (0x00BC)
Default MP Type: 1 SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:02:48 AM 188 (0x00BC)
Default MP: [None] SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:02:48 AM 188 (0x00BC)
Certificate Selection Criteria: SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:02:48 AM 188 (0x00BC)
Certificate Store: SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:02:48 AM 188 (0x00BC)
SSL State: 224 SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:02:48 AM 188 (0x00BC)
PKI Cert Options: 0x1 SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:02:48 AM 188 (0x00BC)
Select First Certificate: 1 SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:02:48 AM 188 (0x00BC)
Certificate Issuers: SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:02:48 AM 188 (0x00BC)
Checking configuration information for server: COB-SCCM12D-01.xxx. SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:02:48 AM 188 (0x00BC)
No Fallback Status Point installed on the Site SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:02:48 AM 188 (0x00BC)
Install on DC: False SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:02:48 AM 188 (0x00BC)
Option for installing using IP address: 0 SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:02:48 AM 188 (0x00BC)
Sleeping for 1200 seconds... SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:02:49 AM 188 (0x00BC)
Thread has been inactive too long. Closing thread SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:10:11 AM 724 (0x02D4)
--- This thread is terminating due to inactivity SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:10:11 AM 724 (0x02D4)
----- Terminated CCR processing thread. There are now 0 processing threads SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:10:11 AM 724 (0x02D4)
Execute query exec [sp_CP_GetNewPushMachines] N'DEV' SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:09 AM 5196 (0x144C)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152009, 1 SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:09 AM 5196 (0x144C)
Execute query exec [sp_CP_GetPushRequestMachine] 2097152009 SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:09 AM 5196 (0x144C)
Successfully retrieved information for machine W10-SCCM-VM01 from DB SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:09 AM 5196 (0x144C)
Execute query exec [sp_CP_GetPushRequestMachineIP] 2097152009 SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:09 AM 5196 (0x144C)
Execute query exec [sp_CP_GetPushRequestMachineResource] 2097152009 SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:09 AM 5196 (0x144C)
Execute query exec [sp_CP_GetPushMachineName] 2097152009 SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:09 AM 5196 (0x144C)
Received request: "2097152009" for machine name: "W10-SCCM-VM01" on queue: "Incoming". SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:10 AM 5196 (0x144C)
Stored request "2097152009", machine name "W10-SCCM-VM01", in queue "Processing". SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:10 AM 5196 (0x144C)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152009, 1 SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:10 AM 5196 (0x144C)
----- Started a new CCR processing thread. Thread ID is 0x10e0. There are now 1 processing threads SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 5196 (0x144C)
Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 5196 (0x144C)
Getting a new request from queue "Incoming" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 5196 (0x144C)
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 2/27/2019 10:22:12 AM 5196 (0x144C)
======>Begin Processing request: "2097152009", machine name: "W10-SCCM-VM01" SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)
Execute query exec [sp_IsMPAvailable] N'DEV' SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)
---> Attempting to connect to administrative share '\\W10-SCCM-VM01.xxx\admin$' using account 'NT\admin-Win10' SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)
---> The 'best-shot' account has now succeeded 7 times and failed 2 times. SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)
---> Connected to administrative share on machine W10-SCCM-VM01.xxx using account 'NT\admin-Win10' SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)
---> Attempting to make IPC connection to share <\\W10-SCCM-VM01.xxx\IPC$> SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)
---> Searching for SMSClientInstall.* under '\\W10-SCCM-VM01.xxx\admin$\' SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)
---> System OS version string "10.0.17763" converted to 10.00 SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)
---> Unable to connect to WMI (root\ccm) on remote machine "W10-SCCM-VM01.xxx", error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)
---> Creating \ VerifyingCopying existence of destination directory \\W10-SCCM-VM01.xxx\admin$\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)
---> Copying client files to \\W10-SCCM-VM01.xxx\admin$\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)
---> Copying file "C:\Program Files\Microsoft Configuration Manager\bin\I386\MobileClient.tcf" to "MobileClient.tcf" SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)
---> Copying file "C:\Program Files\Microsoft Configuration Manager\bin\I386\ccmsetup.exe" to "ccmsetup.exe" SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)
---> Created service "ccmsetup" on machine "W10-SCCM-VM01.xxx". SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)
---> Started service "ccmsetup" on machine "W10-SCCM-VM01.xxx". SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)
---> Deleting SMS Client Install Lock File '\\W10-SCCM-VM01.xxx\admin$\SMSClientInstall.DEV' SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)
Execute query exec [sp_CP_SetLastErrorCode] 2097152009, 0 SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)
---> Completed request "2097152009", machine name "W10-SCCM-VM01". SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)
Deleted request "2097152009", machine name "W10-SCCM-VM01" SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152009, 4 SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)
Execute query exec [sp_CP_SetLatest] 2097152009, N'02/27/2019 15:22:12', 14 SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)
<======End request: "2097152009", machine name: "W10-SCCM-VM01". SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)

 

[Garth]

Everything look good with the log file. there is nothing wrong.

 

[NewbieIssues]

Everything look good with the log file. there is nothing wrong.

Then why is it that no matter what I do I can’t get the client pushed to the computer?

 

[Garth]

Then why is it that no matter what I do I can’t get the client pushed to the computer?

It has clearly successfully push to the client in question. you can see that directly from the log.

---> Started service "ccmsetup" on machine "W10-SCCM-VM01.xxx". SMS_CLIENT_CONFIG_MANAGER 2/27/2019 10:22:12 AM 4320 (0x10E0)

Have you looked at the setup log on the computer in question to see if it is failing there?

 

[NewbieIssues]

After checking the logs on the computer I was trying to install the client on it had trouble reached the DP. I removed the DP and MP role and added them back and it installed after that.