PENDING sccm inactive client status

[hamid.azeez]

hello fellow techs, hope you can assist with some guidance here.
i upgraded my sccm to build 2211 couple weeks ago and have noticed all my clients in sccm are now in "inactive" state. up until the upgrade, all was working fine. i have not made any change other than the upgrade.
i have reviewed the clientlocation.log, clientidmanagerstartup.log. based on the error messages in the clientlocation log, i am not able to resolve.
it talks about cert - valid until the end of 2023
i have confirmed my boundaries and groups and reference are all set correctly.
untill the client and attempt reinstall, both fails manual or via console push. from console push install, i can see the ccmsetup folder gets dropped on the test client and also see the ccmsetup process in task manager. on reviewing the ccmsetup log:
i see: no valid source or MP - is this not set in the boundary group - references? if not, where can i validate this?

is their anything else you may suggest i can try/review to find this root cause?
i realize there are many posts here with the same inactive topic, none seems to help in my scenario.

many thanks in advance,
Hamid.

 

[Youssef Saad]

Hello Hamid,

If all your devices don't communicate with your ConfigMgr environnement after the upgrade, I would suggest to you to start the troubleshooting from your ConfigMgr site server and then continue from the client side.
As a first step, in your CM console, take a look in the Monitoring node > System Status > Site Status & Component Status.

Do you have any errors or warnings there?

 

[hamid.azeez]

hi Youssef, thank you so much for your response and your guidance. so i reviewed the components here and noticed some errors in one of the component. after reviewing the log details. my WSUS wasn't syncing. i was able to resolved by restarting the wsuspool by following this URL: https://www.prajwaldesai.com/sccm-wsus-sync-fails-with-http-503-errors/

although, this does not provided me with any solution to my initial issue with INACTIVE client status.

this was the only major error reported in this section.
Please let me know if there any other ideas i can try. in the meantime, i will keeping digging into logs.

thanks.