SCCM 2012 R2 Client Push Failing

[Gongalong]

Hi folks,

 

It's been a while since I've touched SCCM.

 

I installed 2012 R2 a couple of years ago, and used it briefly to deploy some updates and one app.

 

Around a year ago we spotted that the client had uninstalled itself from around 100 PCs (in a total of 500 or so PCs). I didn't have the time then to troubleshoot what the problem was, and it wasn't urgent to resolve.

 

Fast forward to today, and I would like to get CM working again. One possible problem was that we changed the admin passwords across all domains, so I have deleted and added them back under Client Push Installation Properties. The WDS service was also crashing, and via some googling I found KB2910552 which has resolved that problem.

 

But still no client deployment on the problem machines. Firewall is disabled on the machines. I've looked on some of the machines, and no C:\WINDOWS\CCM folder.

 

Can anyone give me some ideas as to where to start looking for why the client is not installing?

 

Thanks

[mukz]

Check the ccm.log file on sccm server using cmtrace. I believe that will help you further to check where it is failing. Our one failed due to dns issues and sccm not being able to correctly identify a client.

 

This is taken from technet.

 

ccmsetup.log

Records ccmsetup tasks for client setup, client upgrade, and client removal. Can be used to troubleshoot client installation problems.

 

ccmsetup-ccmeval.log

Records ccmsetup tasks for client status and remediation.

 

CcmRepair.log

Records the repair activities of the client agent.

 

client.msi.log

Records setup tasks performed by client.msi. Can be used to troubleshoot client installation or removal problems.

Edited August 9, 2016 by mukz

[Gongalong]

Thanks for the reply.

 

In ccm.log I see this essentially over and over. There are some red and yellow entries, listed below this dating from yesterday, but I'm not sure if they are significant:

 

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 10/08/2016 10:10:29 6176 (0x1820)

CCR count in queue "Incoming" is 0. SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:10:30 6932 (0x1B14)

CCR count in queue "Processing" is 0. SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:10:30 6932 (0x1B14)

Sleeping for 300 seconds... SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:10:30 6932 (0x1B14)

Sleeping for 60 minutes for queue "Retry". SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:13:29 6640 (0x19F0)

CCR count in queue "Retry" is 0. SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:15:30 6932 (0x1B14)

Sleeping for 279 seconds... SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:15:30 6932 (0x1B14)

The Site Control File has not changed since the last parameter update. SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14)

Updating Site Parameters SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14)

MP Ports: 80 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14)

IISPreferedPort: 80 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14)

MP SSL Ports: 443 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14)

IISSSLPreferedPort: 443 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14)

Default MP: SCCM.DOMAIN.local SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14)

Default MP Type: 1 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14)

Default MP: [None] SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14)

Certificate Selection Criteria: SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14)

Certificate Store: SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14)

SSL State: 224 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14)

Select First Certificate: 1 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14)

Certificate Issuers: SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14)

Checking configuration information for server: SCCM.DOMAIN.LOCAL. SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14)

No Fallback Status Point installed on the Site SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14)

Install on DC: False SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14)

Option for installing using IP address: 0 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14)

Sleeping for 1200 seconds... SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:20:09 6932 (0x1B14)

The Site Control File has not changed since the last parameter update. SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14)

Updating Site Parameters SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14)

MP Ports: 80 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14)

IISPreferedPort: 80 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14)

MP SSL Ports: 443 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14)

IISSSLPreferedPort: 443 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14)

Default MP: SCCM.DOMAIN.local SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14)

Default MP Type: 1 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14)

Default MP: [None] SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14)

Certificate Selection Criteria: SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14)

Certificate Store: SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14)

SSL State: 224 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14)

Select First Certificate: 1 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14)

Certificate Issuers: SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14)

Checking configuration information for server: SCCM.DOMAIN.LOCAL. SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14)

No Fallback Status Point installed on the Site SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14)

Install on DC: False SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14)

Option for installing using IP address: 0 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14)

Sleeping for 1200 seconds... SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:40:09 6932 (0x1B14)

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 10/08/2016 10:40:28 6176 (0x1820)

 

:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

Parameters for queue: "Incoming" SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

Inbox Path "C:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

Read Queue Every DIR CHANGE NOTIFICATION SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

Retry CCR For 168 Hours SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

Report Error After ERROR REPORTING OFF SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

Warn when Queue Exceeds 100 CCRs SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

Delay Between CCRs 100 Millisec SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

Parameters for queue: "Retry" SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

Inbox Path "C:\Program Files\Microsoft Configuration Manager\inboxes\ccrretry.box" SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

Read Queue Every 60 Minutes SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

Retry CCR For 168 Hours SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

Report Error After 24 Hours SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

Warn when Queue Exceeds 150 CCRs SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

Delay Between CCRs 100 Millisec SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

Parameters for queue: "Processing" SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

Inbox Path "C:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box\InProc" SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

Read Queue Every DIR CHANGE NOTIFICATION SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

Retry CCR For CCR DOESN'T EXPIRE SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

Report Error After ERROR REPORTING OFF SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

Warn when Queue Exceeds 150 CCRs SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

Delay Between CCRs 0 Millisec SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: SMS_CLIENT_CONFIG_MANAGER 09/08/2016 19:05:30 6932 (0x1B14)

[mukz]

Hi Mate,

 

You should see something like this:

 

======>Begin Processing request: "2097152263", machine name: "CJA-LAP" SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:50:21 20360 (0x4F88)

Execute query exec [sp_IsMPAvailable] N'LSU' SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:50:21 20360 (0x4F88)

---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:50:21 20360 (0x4F88)

---> Attempting to connect to administrative share '\\CJA-LAP\admin$' using account 'LSUSCH\SCCMAdmin' SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:50:21 20360 (0x4F88)

---> Connected to administrative share on machine CJA-LAP using account 'LSUSCH\SCCMAdmin' SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:50:21 20360 (0x4F88)

---> Attempting to make IPC connection to share <\\CJA-LAP\IPC$> SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:50:21 20360 (0x4F88)

---> Searching for SMSClientInstall.* under '\\CJA-LAP\admin$\' SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:50:21 20360 (0x4F88)

---> Unable to connect to WMI on remote machine "CJA-LAP", error = 0x800706ba. SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:51:03 20360 (0x4F88)

---> Unable to connect to WMI on remote machine "CJA-LAP", error = 0x80070005. SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:51:03 20360 (0x4F88)

---> Deleting SMS Client Install Lock File '\\CJA-LAP\admin$\SMSClientInstall.LSU' SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:51:03 20360 (0x4F88)

Execute query exec [sp_CP_SetLastErrorCode] 2097152263, -2147024891 SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:51:03 20360 (0x4F88)

Stored request "2097152263", machine name "CJA-LAP", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 10/08/2016 10:51:03 20360 (0x4F88)

[Gongalong]

I've searched back in the log, which seems to cover 184 hours, and no mention of the above. I guess this raises the question, why is not trying to deploy to any of the clients that don't have the CM client?

[mukz]

Yup, check the services to see if all is okay and running as should be.

 

Can you check if the ccm client is properly deployed to a DP

Edited August 10, 2016 by mukz

[Geoff]

I'd check your site boundaries are correct. Did you forget to add an IP range for example?

[Gongalong]

I have a boundary (IP based) and boundary group in place, so not sure why automatic push isn't working, unless these need to be assigned somewhere. Also I'm still not sure why last year these PCs decided to uninstall the CM client.

 

But I have remembered that I manually installed the client anyway, via a right-click on the device collection, as I preferred that method to ensure the client went where I wanted. This explains why I hadn't enabled automatic client distribution :-)

 

Having manually installed the client on a couple of test PCs it's definitely installing, so I think the issue is sort of resolved, aside from why automatic push isn't working.