SCCM Client showing as "No" or "Not Installed"

Copper Contributor

Hi

After a little support if possible please,

 

We are preparing to upgrade and replace circa 50 PCs in our office.

 

We have prepared a custom build of Windows 11 Enterprise, with all of the required applications installed. We are able to provision a PC via our custom Task Sequence in SCCM, this all works well.

 

However, when the task sequence installs the SCCM client on the PC, the ccmsetup.log reports "CcmSetup is exiting with return code 0" - the Computer registers and is visible within the SCCM console, but, the "Client" column states "No" which would indicate that there is some sort of communication issue from the Client to the SCCM server.

 

Attached is an example of where the newly provisioned PC has had the Client installed, but it does not appear to be communicating to the SCCM server.

01.jpg

 

The same happens even if we uninstall the client via the "ccmsetup.exe /uninstall" command and manually re-install by just running "ccmsetup.exe"

 

 

This is not all PCs that we are having this issue with.

Any pre-existing PCs that were provisioned a couple of years back continue to work and respond ok with SCCM.

 

Attached is an example of a pre-existing PC where the SCCM client is reporting to the server ok :

02.jpg

This only appears to be with any PCs we provision recently (we had an in-place server upgrade take place approx 12 months ago and went from MS Server 2016 to MS Server 2019)

 

Would anyone be able to offer any assistance or be able to take a look at any log files to help out?

 

Thanks in advance!

19 Replies

Are you only using IP Ranges for your boundaries? Your problem sound like the boundaries are wrong.

@Garth-MVP 

 

Hey Garth

 

Thanks for your reply, I really appreciate it.

I've checked our boundaries following your message and yes, we are only using IP Ranges and they all appear correct and in line to what we have? (see images below)

 

cerbast_0-1712347248356.png

 

cerbast_1-1712347290175.png

 

cerbast_2-1712347319565.png

 

Have you checked the clientidmanagerstartup log to see if the client is actually able to register with the MP?

@rahuljindal-MVP 

 

Hi Rahul,

Thanks for your reply, I appreciate it.

I've just checked that log now on the Client PC and here are a few of the more recent entries in the log:

]LOG]!><time="16:14:33.812-60" date="04-05-2024" component="ClientIDManagerStartup" context="" type="1" thread="6876" file="Event.cpp:911">
<![LOG[PKI Client Certificate matching SCCM certificate selection criteria is not available.]LOG]!><time="16:14:33.827-60" date="04-05-2024" component="ClientIDManagerStartup" context="" type="2" thread="6876" file="ccmgencert.cpp:4147">
<![LOG[Registered AAD join event listener.]LOG]!><time="16:14:36.451-60" date="04-05-2024" component="ClientIDManagerStartup" context="" type="1" thread="4052" file="regtask.cpp:754">
<![LOG[Registered for AAD on-boarding notifications.]LOG]!><time="16:14:36.451-60" date="04-05-2024" component="ClientIDManagerStartup" context="" type="1" thread="4052" file="regtask.cpp:767">
<![LOG[Initializing notification listener for potential PKI issued certificate changes.]LOG]!><time="16:14:36.451-60" date="04-05-2024" component="ClientIDManagerStartup" context="" type="1" thread="4052" file="regtask.cpp:881">
<![LOG[Succesfully intialized PKI issued cert renewal listener.]LOG]!><time="16:14:36.451-60" date="04-05-2024" component="ClientIDManagerStartup" context="" type="1" thread="4052" file="regtask.cpp:923">
<![LOG[[RegTask] - Executing registration task synchronously.]LOG]!><time="16:14:36.451-60" date="04-05-2024" component="ClientIDManagerStartup" context="" type="1" thread="4052" file="regtask.cpp:1709">
<![LOG[Expected MDM_EnrollmentStatusTracking_PolicyProviders02_01.InstanceID="ConfigMgr",ParentID="./Vendor/MSFT/EnrollmentStatusTracking/DevicePreparation/PolicyProviders" instance is not found.]LOG]!><time="16:14:36.624-60" date="04-05-2024" component="ClientIDManagerStartup" context="" type="2" thread="4052" file="esp.cpp:209">
<![LOG[ConfigMgr is not being tracked as ESP provider.]LOG]!><time="16:14:36.624-60" date="04-05-2024" component="ClientIDManagerStartup" context="" type="1" thread="4052" file="esp.cpp:335">
<![LOG[RegTask: Failed to refresh MP. Error: 0x80004005]LOG]!><time="16:14:47.011-60" date="04-05-2024" component="ClientIDManagerStartup" context="" type="3" thread="4052" file="regtask.cpp:284">
<![LOG[Sleeping for 288 seconds before refreshing location services.]LOG]!><time="16:14:48.037-60" date="04-05-2024" component="ClientIDManagerStartup" context="" type="1" thread="4052" file="regtask.cpp:229">
<![LOG[RegTask: Failed to refresh MP. Error: 0x80004005]LOG]!><time="16:19:46.543-60" date="04-05-2024" component="ClientIDManagerStartup" context="" type="3" thread="4052" file="regtask.cpp:284">

 

This then continues pretty much every 5 minutes up to as recent as now:

 

<![LOG[RegTask: Failed to refresh MP. Error: 0x80004005]LOG]!><time="22:00:57.450-60" date="04-05-2024" component="ClientIDManagerStartup" context="" type="3" thread="4052" file="regtask.cpp:284">
<![LOG[Sleeping for 222 seconds before refreshing location services.]LOG]!><time="22:02:04.395-60" date="04-05-2024" component="ClientIDManagerStartup" context="" type="1" thread="4052" file="regtask.cpp:229">
<![LOG[RegTask: Failed to refresh MP. Error: 0x80004005]LOG]!><time="22:06:11.508-60" date="04-05-2024" component="ClientIDManagerStartup" context="" type="3" thread="4052" file="regtask.cpp:284">
<![LOG[Sleeping for 217 seconds before refreshing location services.]LOG]!><time="22:07:23.488-60" date="04-05-2024" component="ClientIDManagerStartup" context="" type="1" thread="4052" file="regtask.cpp:229">
<![LOG[RegTask: Failed to refresh MP. Error: 0x80004005]LOG]!><time="22:11:21.645-60" date="04-05-2024" component="ClientIDManagerStartup" context="" type="3" thread="4052" file="regtask.cpp:284">
<![LOG[Sleeping for 219 seconds before refreshing location services.]LOG]!><time="22:12:31.644-60" date="04-05-2024" component="ClientIDManagerStartup" context="" type="1" thread="4052" file="regtask.cpp:229">
<![LOG[RegTask: Failed to refresh MP. Error: 0x80004005]LOG]!><time="22:16:28.581-60" date="04-05-2024" component="ClientIDManagerStartup" context="" type="3" thread="4052" file="regtask.cpp:284">
<![LOG[Sleeping for 209 seconds before refreshing location services.]LOG]!><time="22:17:48.635-60" date="04-05-2024" component="ClientIDManagerStartup" context="" type="1" thread="4052" file="regtask.cpp:229">
<![LOG[RegTask: Failed to refresh MP. Error: 0x80004005]LOG]!><time="22:21:39.610-60" date="04-05-2024" component="ClientIDManagerStartup" context="" type="3" thread="4052" file="regtask.cpp:284">
<![LOG[Sleeping for 225 seconds before refreshing location services.]LOG]!><time="22:22:43.617-60" date="04-05-2024" component="ClientIDManagerStartup" context="" type="1" thread="4052" file="regtask.cpp:229">

 

 

Does this give you anything to advise on?

So it appears from the log that the client is not receiving mp information. This can most certainly be related to boundaries as Garth pointed out. Also, what are the command line parameters are you using while installing the agent through the TS?
Your screenshot clearly shows up subnets, not ip ranges. What exactly is the ip address and subnet mask of the device? What do the logs say about boundaries?

@Garth-MVP 

Hey Garth,

 

Sorry you are right yes, it is IP Subnets specifying the Boundaries. (it was a long day!)

 

The IP / Subnet of the device in question is:

 

IP: 192.168.121.100
Subnet mask: 255.255.252.0


Which log(s) should I check with regards to the boundaries?


@rahuljindal-MVP 

 

Hi Rahul

 

The command line parameters while installing the agent are:

 

CCMSetup.exe SMSSITECODE=AUTO MP=SCCM1.ourdomainname.network

again only ip ranges will be 100% correct. Again exactly what is the ip address and its subnet mask? All the logs are here. https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/hierarchy/log-files

@Garth-MVP 

 

The IP / Subnet of the device in question is:

 

IP: 192.168.121.100
Subnet mask: 255.255.252.0

 

 

Which logs referenced on the link you've provided do I need to check in regards to Boundaries?

 

Thanks

 

 

Sorry, I miss read the ip address in your previous post. To be honest it is the subnet mask that is throwing me off, I have not seen one so big is forever. Are you truly sure that is the subnet mask and not 255.255.255.252 or 255.255.255.0?

It is absolutely important to know for sure.

As for the list the doc site tell you what each log is used for.



@Garth-MVP 

Yes, the subnet of 255.255.252.0 is correct.

 

I should have mentioned, that it is just Windows 11 (23H2) PCs that I am trying to install the Client to.

 

I have noticed today that I have (via command line) been able to install the client to an already pre-existing Windows 11 (23H2) PC on the network that reports nicely to SCCM and I'm able to Remote Control the same etc. So wondered if it could be related to some Windows Update on the Client that is blocking the communications of the SCCM client?
I feel I have ruled this out now however as I have started with a base install today of Windows 11 23H2 and joined it to the domain and immediately attempted to install the SCCM client. This appears to have been successful, but again it doesn't appear to be able to communicate with the SCCM server.

 

It is just any new PCs that I provision that I seemingly am able to install the Client, it just cannot communicate with the SCCM server. 

I say that the Client is installed successfully because the ccmsetup.log reports:
<![LOG[CcmSetup is exiting with return code 0]LOG]!>

It should also be noted that even though the above is logged in the ccmsetup.log, the "Software Center" app is not visible in the Start Menu either.

 

Is there any reason why the server would be provisioned with a secondary IP Address?

Primary IP is: 192.168.120.11, but then it has a Secondary IP of: 172.16.120.11 ?

They are both pingable from any PC, but obviously the above results in 2 entries to DNS, which  (clutching at straws) I wondered if it could have an impact on any new installations of the SCCM client?

 

Thanks

 

Just to add to this as well...

I've also just noticed, I am able to install the Client via the SCCM Console to the Windows 11 PC that was pre-existing (I un-installed via command line first)

If I try the same on the new Windows 11 PC that I've provisioned, it doesn't install and doesn't even invoke the ccmsetup.exe if I watch the processes in Task Manager.
The Exit 0 means the install was successful and if you look at the client on the device you will see the ConfigMgr applet within the control panel.

Did you change your boundaries to IP ranges only?
I do not see the ConfigMgr applet in Control Panel.

I haven't changed the boundaries as I thought this may be the wrong path, as it has always previously worked with Subnets (as proven today by installing to the pre-existing PC) and I didn't want to cause any adverse effects?
IP Ranges are the only boundary type that will be 100% correct. All others relay on external details. No it will not have any adverse effect.

Review the setup log again as exit 0 means it was successfully installed.
It always has been <![LOG[CcmSetup is exiting with return code 0]LOG]!> Garth.

It seems that there is some sort of issue with communicating with the server / MP.

@Garth-MVP 

I'm beginning to think this could be linked to something to do with Certificates?

Here is some of the log from the ClientIDManagerStartup.log on a Client that is working ok:

 

<![LOG[[----- STARTUP -----]]LOG]!><time="17:04:49.111-60" date="04-08-2024" component="ClientIDManagerStartup" context="" type="1" thread="20236" file="ccmidstore.cpp:21">
<![LOG[Machine: DEVPC186XJ03]LOG]!><time="17:04:49.142-60" date="04-08-2024" component="ClientIDManagerStartup" context="" type="1" thread="20236" file="ccmid.cpp:1440">
<![LOG[OS Version: 10.0.22631.0]LOG]!><time="17:04:49.142-60" date="04-08-2024" component="ClientIDManagerStartup" context="" type="1" thread="20236" file="ccmid.cpp:1444">
<![LOG[SCCM Client Version: 5.00.9122.1018]LOG]!><time="17:04:49.142-60" date="04-08-2024" component="ClientIDManagerStartup" context="" type="1" thread="20236" file="ccmid.cpp:1448">
<![LOG[TPM is available.]LOG]!><time="17:04:49.346-60" date="04-08-2024" component="ClientIDManagerStartup" context="" type="1" thread="20236" file="KSPUtils.cpp:1545">
<![LOG[Retrieved key 'ConfigMgrPrimaryKey' from provider Microsoft Platform Crypto Provider]LOG]!><time="17:04:49.346-60" date="04-08-2024" component="ClientIDManagerStartup" context="" type="1" thread="20236" file="KSPUtils.cpp:531">
<![LOG[Key 'ConfigMgrMigrationKey' not found, 0x80090016.]LOG]!><time="17:04:49.346-60" date="04-08-2024" component="ClientIDManagerStartup" context="" type="1" thread="20236" file="KSPUtils.cpp:527">
<![LOG[Deleted Certificate ID from registry successfully]LOG]!><time="17:04:49.346-60" date="04-08-2024" component="ClientIDManagerStartup" context="" type="1" thread="20236" file="ccmgencert.cpp:4052">
<![LOG[HTTPS is enforced for Client. The current state is 1087.]LOG]!><time="17:04:49.361-60" date="04-08-2024" component="ClientIDManagerStartup" context="" type="1" thread="20236" file="CcmUtilLib.cpp:556">
<![LOG[Begin searching client certificates based on Certificate Issuers]LOG]!><time="17:04:49.361-60" date="04-08-2024" component="ClientIDManagerStartup" context="" type="1" thread="20236" file="CcmCert.cpp:4999">
<![LOG[Certificate Issuer 1 [CN=ourdomain-CGDC1-CA; DC=ourdomain; DC=network]]LOG]!><time="17:04:49.361-60" date="04-08-2024" component="ClientIDManagerStartup" context="" type="1" thread="20236" file="CcmCert.cpp:5015">
<![LOG[Based on Certificate Issuer 'CN=ourdomain-CGDC1-CA, DC=ourdomain, DC=network' found Certificate [Thumbprint BCD37C2085AF177A546E3E60614C46A94C58615B] issued to 'DEVPC186XJ03.ourdomain.network']LOG]!><time="17:04:49.376-60" date="04-08-2024" component="ClientIDManagerStartup" context="" type="1" thread="20236" file="CcmCert.cpp:4937">
<![LOG[Begin validation of Certificate [Thumbprint BCD37C2085AF177A546E3E60614C46A94C58615B] issued to 'DEVPC186XJ03.ourdomain.network']LOG]!><time="17:04:49.376-60" date="04-08-2024" component="ClientIDManagerStartup" context="" type="1" thread="20236" file="CcmCert.cpp:1777">
<![LOG[Completed validation of Certificate [Thumbprint BCD37C2085AF177A546E3E60614C46A94C58615B] issued to 'DEVPC186XJ03.ourdomain.network']LOG]!><time="17:04:49.392-60" date="04-08-2024" component="ClientIDManagerStartup" context="" type="1" thread="20236" file="CcmCert.cpp:1954">
<![LOG[Skipping Certificate [Thumbprint 9F4A303BA2CA3FB2C3757861B661CDD176054FAC] issued to 'localhost' as root is '']LOG]!><time="17:04:49.392-60" date="04-08-2024" component="ClientIDManagerStartup" context="" type="1" thread="20236" file="CcmCert.cpp:4957">
<![LOG[Completed searching client certificates based on Certificate Issuers]LOG]!><time="17:04:49.392-60" date="04-08-2024" component="ClientIDManagerStartup" context="" type="1" thread="20236" file="CcmCert.cpp:5079">
<![LOG[Begin to select client certificate]LOG]!><time="17:04:49.392-60" date="04-08-2024" component="ClientIDManagerStartup" context="" type="1" thread="20236" file="CcmCert.cpp:5266">
<![LOG[Begin validation of Certificate [Thumbprint BCD37C2085AF177A546E3E60614C46A94C58615B] issued to 'DEVPC186XJ03.ourdomain.network']LOG]!><time="17:04:49.392-60" date="04-08-2024" component="ClientIDManagerStartup" context="" type="1" thread="20236" file="CcmCert.cpp:1777">
<![LOG[Completed validation of Certificate [Thumbprint BCD37C2085AF177A546E3E60614C46A94C58615B] issued to 'DEVPC186XJ03.ourdomain.network']LOG]!><time="17:04:49.392-60" date="04-08-2024" component="ClientIDManagerStartup" context="" type="1" thread="20236" file="CcmCert.cpp:1954">
<![LOG[>>> Client selected the PKI Certificate [Thumbprint BCD37C2085AF177A546E3E60614C46A94C58615B] issued to 'DEVPC186XJ03.ourdomain.network']LOG]!><time="17:04:49.392-60" date="04-08-2024" component="ClientIDManagerStartup" context="" type="1" thread="20236" file="CcmCert.cpp:5413">
<![LOG[Raising pending event:


And here is some of the same log from a Client that isn't  working :

 

<![LOG[[----- STARTUP -----]]LOG]!><time="10:57:37.666-60" date="04-09-2024" component="ClientIDManagerStartup" context="" type="1" thread="13296" file="ccmidstore.cpp:21">
<![LOG[Machine: CGPCJN3GXP2]LOG]!><time="10:57:37.713-60" date="04-09-2024" component="ClientIDManagerStartup" context="" type="1" thread="13296" file="ccmid.cpp:1440">
<![LOG[OS Version: 10.0.19045.0]LOG]!><time="10:57:37.713-60" date="04-09-2024" component="ClientIDManagerStartup" context="" type="1" thread="13296" file="ccmid.cpp:1444">
<![LOG[SCCM Client Version: 5.00.9122.1018]LOG]!><time="10:57:37.713-60" date="04-09-2024" component="ClientIDManagerStartup" context="" type="1" thread="13296" file="ccmid.cpp:1448">
<![LOG[Client is set to use HTTPS when available. The current state is 1216.]LOG]!><time="10:57:37.713-60" date="04-09-2024" component="ClientIDManagerStartup" context="" type="1" thread="13296" file="CcmUtilLib.cpp:565">
<![LOG[Registered AAD join event listener.]LOG]!><time="10:57:40.350-60" date="04-09-2024" component="ClientIDManagerStartup" context="" type="1" thread="6212" file="regtask.cpp:754">
<![LOG[Registered for AAD on-boarding notifications.]LOG]!><time="10:57:40.350-60" date="04-09-2024" component="ClientIDManagerStartup" context="" type="1" thread="6212" file="regtask.cpp:767">
<![LOG[[RegTask] - Executing registration task synchronously.]LOG]!><time="10:57:40.366-60" date="04-09-2024" component="ClientIDManagerStartup" context="" type="1" thread="6212" file="regtask.cpp:1709">
<![LOG[Read SMBIOS (encoded): 39004D003500350038004B003300]LOG]!><time="10:57:40.428-60" date="04-09-2024" component="ClientIDManagerStartup" context="" type="1" thread="6212" file="smbiosident.cpp:118">
<![LOG[Evaluated SMBIOS (encoded): 39004D003500350038004B003300]LOG]!><time="10:57:40.428-60" date="04-09-2024" component="ClientIDManagerStartup" context="" type="1" thread="6212" file="smbiosident.cpp:184">
<![LOG[No SMBIOS Changed]LOG]!><time="10:57:40.428-60" date="04-09-2024" component="ClientIDManagerStartup" context="" type="1" thread="6212" file="smbiosident.cpp:65">
<![LOG[SMBIOS unchanged]LOG]!><time="10:57:40.428-60" date="04-09-2024" component="ClientIDManagerStartup" context="" type="1" thread="6212" file="ccmid.cpp:686">
<![LOG[SID unchanged]LOG]!><time="10:57:40.428-60" date="04-09-2024" component="ClientIDManagerStartup" context="" type="1" thread="6212" file="ccmid.cpp:703">
<![LOG[HWID unchanged]LOG]!><time="10:57:41.493-60" date="04-09-2024" component="ClientIDManagerStartup" context="" type="1" thread="6212" file="ccmid.cpp:720">
<![LOG[RegTask: Failed to refresh MP. Error: 0x80004005]LOG]!><time="10:58:18.034-60" date="04-09-2024" component="ClientIDManagerStartup" context="" type="3" thread="6212" file="regtask.cpp:284">
<![LOG[Sleeping for 262 seconds before refreshing location services.]LOG]!><time="10:58:19.039-60" date="04-09-2024" component="ClientIDManagerStartup" context="" type="1" thread="6212" file="regtask.cpp:229">
<![LOG[RegTask: Failed to refresh MP. Error: 0x80004005]LOG]!><time="11:03:17.563-60" date="04-09-2024" component="ClientIDManagerStartup" context="" type="3" thread="6212" file="regtask.cpp:284">
<![LOG[Sleeping for 261 seconds before refreshing location services.]LOG]!><time="11:03:19.568-60" date="04-09-2024" component="ClientIDManagerStartup" context="" type="1" thread="6212" file="regtask.cpp:229">
<![LOG[RegTask: Failed to refresh MP. Error: 0x80004005]LOG]!><time="11:08:17.368-60" date="04-09-2024" component="ClientIDManagerStartup" context="" type="3" thread="6212" file="regtask.cpp:284">
<![LOG[Sleeping for 260 seconds before refreshing location services.]LOG]!><time="11:08:20.383-60" date="04-09-2024" component="ClientIDManagerStartup" context="" type="1" thread="6212" file="regtask.cpp:229">

 

 

Does this give any more information in what to check next?

That looks like a good place to start.