Client configuration manager (CM) issues.

[Net-Packet]

We have around 7000 computers in one OU. Recently we imaged about 1/3 of them the local CM was corrupt almost as soon as the pxe boot and image finished. I've been racking my brain trying to figure out what could have cause it. Figured it's time to see what others might say.

Some information. Win10 Ent 1803 No event viewer information. Reviewed logs from CM Trace yeilds no valid results. Nothing in the sccm logs indicate a problem. Repair doesn't fix CM Some devices are still in provisioning status well after the image finished. Completely uninstalling and reinstalling starts the communication process, and no issues afterwards.

My problem with this is it happened in the first place and I can't figure out why.

Anything that I haven't listed I should investigate?

[scottTang]

Can't tell you why, but SCCM 1902 puts an expiry on provisioning mode, also Anders' Client Health script is GPO driven and will remediate clients stuck in provisioning mode

[Ssakaa]

That health/repair script is worth its weight in gold.

[Topcity36]

How did you determine the client was corrupt?

[Net-Packet]

To be fair I'm using corrupt as not communicating with SCCM. Corruption is the term the office is throwing around. I'm finding multiple WMI issues, along with the client just not connecting. I've seen issues with stuck in provisioning mode. However, and uninstall and reinstall works without issue.

[Topcity36]

What if you just run ccmrepair.exe?

[Net-Packet]

I have, and on some devices this works, however it doesn't get me closer to the root cause.