SCCM Weird Issue

[Guest Guest]

Hi,

 

Has anyone experienced this issue before in the picture below?

 

Never seen this before.

 

Anyone know how to fix this?

 

[chris11256]

I have this on newly imaged computers before they run policy cycles. If it's an existing PC it might be worth trying an SCCM client reinstall via the console.

[Guest Guest]

This is on a brand new AD domain though?

[Katy]

That happens when the client hasn't managed to talk to the server yet.

Try clicking on each of the two items and clicking Run Now, then wait a while. Maybe give it a reboot too.

 

Last time I had this issue it was because the client wasn't approved in Config Manager - typically when you set it to pull in Active Directory computer accounts, it's set to auto-approve, possible it's not? Right clicking on the device in the CM console should be obvious if it's not approved.

 

Otherwise if it is approved but not syncing, give it a reboot and make sure all the relevant services have started on the server and client.

[Sheridan]

I've seen this once or twice, but usually with a couple more options showing. If a reboot didn't fix it I uninstalled and reinstalled the client which worked fine afterwards