Manually Fixing a Broken Client

Just because the client is installed doesn't mean it is working correctly. When you notice a device isn't reporting back correctly. There are a few things to look at first in your configuration manger console. Go to the client and look at the client activity if any of your scans or request are more then a week old that is a good indication the client is have an issue with either connection to the server or running these actions

Next go to log into the client and go to Control Panel > System and Security > Configuration Manager and on the actions tab and run the Machine Policy Retrieval & Evaluation Cycle, Software update Scan Cycle and the Hardware Inventory Cycle. Try to wait a few moments between each action running one right after the other can cause the client to stop one action an run another. If you get an error on any of these actions uninstall the SCCM client and reinstall it.

last on the client having the issue open powershell as an administrator and run the following

Get-WmiObject -Namespace root\ccm -Class sms_client

If you get an error or you do not get anything back reinstall the SCCM client, this means SCCMs part of WMI is not working and needs to be repaired reinstalling the client will do this.

You can do this all manually or you can use my SCCM Client Health Check login script to help automate the process.  


Popular posts from this blog

SCCM Task Sequence GUI - How to set up the TS to work with a GUI

SCCM Applications vs. SCCM Packages: Understanding the Key Differences

How to Deploy a Windows 10 Servicing update as a Application