Forum Discussion
SCCM Client showing as "No" or "Not Installed"
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.
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