PENDING SCCM Client does not initialize after OS deployment

[Knopper]

Hello everyone.

I have an issue with my SCCM 1902 environment which is simple - it consists of 2 servers - 1 MP+DP and 1 DP. I have a task sequence for OS deployment which specifies the Client package for deployment as part of the (re)imaging process. The OS deployment succeeds, however the SCCM client does not seem to initialize. The client is there, however it's not fully installed - in Configuration Manager Properties there is None under Client Certificate and it should be PKI (autoenrollment is configured, so a certificate exists in the machine store). Under Actions there are only two actions: Machine and User Policy Retrieval and Evaluation Cycle. If I manually push the client to the machine and force a reinstall, it initializes properly. However, this is not OK, I think it should be happening automatically after OS installation. In Component Status on the server I have 72 components which are 100% Green, no Warnings or Errors. All clients in the environment work fine - they receive policy, deployments, etc., this happens only with newly imaged or reinstalled clients. Client connections to the MP are configured to use HTTP (and clients themselves are configured with PKI certificates autoenrolled), however even with HTTPS there shouldn't be an issue. Any idea where to look to troubleshoot this problem?

 

[Prajwal Desai]

In the task sequence, are you modifying anything while deploying the client agent ?.

If nothing has been modified and if you see just two cycles under Actions tab, i would suggest you wait for sometime and check the cycles again. After the imaging is over, it usually shows just 2 cycles initially. Did you check any client log files to see if there are errors ?.

 

[Knopper]

Prajwal, thanks for your reply. The task sequence is deploying the Configuration Manager Client Package which should be sufficient. Nothing else is specified in the Setup Operating System group. I checked the logs on one of the clients, but did not find anything suspicious initially. Today I will be testing with an OS image that has the SCCM client prestaged in it. I am not sure if there will be any difference. I have waited for a week for the client to kick off after deployment, but it doesn't. I have the cycles configured to run every 15 minutes, so I should not be waiting for more than half an hour after deployment is finished and it usually happens within a couple of minutes. Which are the relevant logs on the client that I should look at?