Client push installation failing

[xerxes2985]

OK, I am encountering an issue when attempting to manually push the client. (Right click on the object and click "Install Client") This issue occurs on every system.

I've verified that using my client installation account I am using is a member of the local administrators group on each system, and I've also verified that I can browse to the admin$ using explorer and connecting via the particular account. I also can connect to the registry, etc. Any suggestions or tips for resolving this issue?

 

Thanks

[xerxes2985]

======>Begin Processing request: "2097152181", machine name: "LIB-HP-5"	SMS_CLIENT_CONFIG_MANAGER	5/4/2017 3:59:30 PM	9716 (0x25F4)
Execute query exec [sp_IsMPAvailable] N'LIB'	SMS_CLIENT_CONFIG_MANAGER	5/4/2017 3:59:30 PM	9716 (0x25F4)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)	SMS_CLIENT_CONFIG_MANAGER	5/4/2017 3:59:30 PM	9716 (0x25F4)
---> Attempting to connect to administrative share '\\COMPNAME.domain.edu\admin$' using account 'DOMAIN\lib-sccm-client-adm'	SMS_CLIENT_CONFIG_MANAGER	5/4/2017 3:59:30 PM	9716 (0x25F4)
---> The 'best-shot' account has now succeeded 1 times and failed 0 times.	SMS_CLIENT_CONFIG_MANAGER	5/4/2017 3:59:30 PM	9716 (0x25F4)
---> Connected to administrative share on machine LIB-HP-5.ad.auburn.edu using account 'DOMAIN\lib-sccm-client-adm'	SMS_CLIENT_CONFIG_MANAGER	5/4/2017 3:59:30 PM	9716 (0x25F4)
---> Attempting to make IPC connection to share <\\COMPNAME.domain.edu\IPC$>	SMS_CLIENT_CONFIG_MANAGER	5/4/2017 3:59:30 PM	9716 (0x25F4)
---> Searching for SMSClientInstall.* under '\\COMPNAME.domain.edu\admin$\'	SMS_CLIENT_CONFIG_MANAGER	5/4/2017 3:59:30 PM	9716 (0x25F4)
Submitted request successfully	SMS_CLIENT_CONFIG_MANAGER	5/4/2017 3:59:32 PM	5168 (0x1430)
Getting a new request from queue "Incoming" after 100 millisecond delay.	SMS_CLIENT_CONFIG_MANAGER	5/4/2017 3:59:32 PM	5168 (0x1430)
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	5/4/2017 3:59:32 PM	5168 (0x1430)
---> Unable to connect to WMI on remote machine "LIB-HP-5.domain.edu", error = 0x800706ba.	SMS_CLIENT_CONFIG_MANAGER	5/4/2017 4:00:14 PM	9716 (0x25F4)
---> Unable to connect to WMI on remote machine "LIB-HP-5", error = 0x800706ba.	SMS_CLIENT_CONFIG_MANAGER	5/4/2017 4:00:16 PM	9716 (0x25F4)
---> Deleting SMS Client Install Lock File '\\COMPNAME.domain.edu\admin$\SMSClientInstall.LIB'	SMS_CLIENT_CONFIG_MANAGER	5/4/2017 4:00:16 PM	9716 (0x25F4)
Execute query exec [sp_CP_SetLastErrorCode] 2097152181, -2147023174	SMS_CLIENT_CONFIG_MANAGER	5/4/2017 4:00:16 PM	9716 (0x25F4)
Stored request "2097152181", machine name "LIB-HP-5", in queue "Retry".	SMS_CLIENT_CONFIG_MANAGER	5/4/2017 4:00:16 PM	9716 (0x25F4)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152181, 2	SMS_CLIENT_CONFIG_MANAGER	5/4/2017 4:00:16 PM	9716 (0x25F4)
Execute query exec [sp_CP_SetLatest] 2097152181, N'05/04/2017 21:00:17', 8	SMS_CLIENT_CONFIG_MANAGER	5/4/2017 4:00:17 PM	9716 (0x25F4)
<======End request: "2097152181", machine name: "LIB-HP-5".	SMS_CLIENT_CONFIG_MANAGER	5/4/2017 4:00:17 PM	9716 (0x25F4)

Here is the text for another one.

It does this on every system when trying to do a Client Push Installation. What is causing this??

 

[simulacra75]

Are there services not running on the remote clients that the Client Push requires in order to connect to the admin$ share? For example, RemoteRegistry? Have you tried manually connecting to these remote machines \\machine-name\admin$ with the network account? If you're getting an error, what is that error when you try manually?

[xerxes2985]

2 hours ago, simulacra75 said:

Are there services not running on the remote clients that the Client Push requires in order to connect to the admin$ share? For example, RemoteRegistry? Have you tried manually connecting to these remote machines \\machine-name\admin$ with the network account? If you're getting an error, what is that error when you try manually?

I don't get any error. I can manually browse just fine to the Admin share, I can access remote registry with the network account.

[simulacra75]

Is the firewall enabled on all your client machines? If it is, you could dry disabling the firewall temporarily on a few clients, restart them and then try the installation again on those clients.

 

I should have pointed out in my first post, are you able to browse to those remote clients, using the Network Service Account from the Primary Site that's attempting the installation process. It's important that the client is accessible from the Primary Site itself, obviously.

[xerxes2985]

2 hours ago, simulacra75 said:

Is the firewall enabled on all your client machines? If it is, you could dry disabling the firewall temporarily on a few clients, restart them and then try the installation again on those clients.

 

I should have pointed out in my first post, are you able to browse to those remote clients, using the Network Service Account from the Primary Site that's attempting the installation process. It's important that the client is accessible from the Primary Site itself, obviously.

So interesting enough, disabling the Firewall worked.

I read here about Firewall ports, and went ahead and created a GPO to test if its the right ports, can you confirm (or anyone).

 

[simulacra75]

Windows Firewall and Port Settings for Client Computers in Configuration Manager

[xerxes2985]

3 hours ago, simulacra75 said:

Windows Firewall and Port Settings for Client Computers in Configuration Manager

Thanks, It looks like I didn't have the ports opened. Now the client is installed, however I am still seeing the following two errors:

---> Unable to connect to WMI (root\ccm) on remote machine "COMPUTERNAME.DOMAIN.EDU", error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 5/5/2017 12:55:51 PM 3776 (0x0EC0)
and
---> Execute query exec [sp_CP_SetLastErrorCode] 2097152268, 0 SMS_CLIENT_CONFIG_MANAGER 5/5/2017 12:56:13 PM 3776 (0x0EC0)

Any thoughts?

[simulacra75]

The error, 0x8004100e, translates to "Invalid WMI namespace". I would run a repair of WMI on the machines that are giving that error.