The following is a SCCM Client Health Checklist that I run through.
- Check event logs
- Application updates are listed in the Application log under MSIInstaller provider
- OS updates are via the setup event log
- SCCM Client info can also be in the Configuration Manager Agent Provider
- Check Windows Update Log
- If you are seeing a history of errors there, then I run the WUSledgehammer over it.
This resets the windows Update Agent and resets the local group policy file.
A few manual runs of the Software Update actions on the SCCM Client , 15 minutes apart and a full cycle should be completed successfully.
If you are seeing installations fail in he log or other errors then we have two other places to look
- If you are seeing a history of errors there, then I run the WUSledgehammer over it.
- Check the SCCM Client logs
- Yeah/nah that will take forever , you seen how many there are!
Easiest thing to do is to hit it with my other sledgehammer the SCCM one.
Biggest issue with pushing a re-install from the SCCM console and forcing an uninstall first, is that not everything is cleaned up
With this one you need to look at the script closely. I am currently limited to psexec, which does not work for Windows 10.
The basic principles of the script are:- Uninstall SCCM Client.
- Delete all 3 directories
- Install SCCM Client
- Yeah/nah that will take forever , you seen how many there are!
- Component Based Servicing Health
- OK this is a big one as this is the service that actually does the heavy lifting and what windows update calls to do the actual patch installation
- Again you can look at logs, search the internet , blah blah blah, but the easier thing to do is to run the Microsoft Update Readiness Tool over the machine for Windows 7 or the DISM command.
- Why did we not do that first! you may say… well, I am glad you asked
- often (95%) it is not the CBS
- it can take an hour or so to run (on spinning rust)
- The two sledgehammers above take 5 or 10 minutes each
- Most importantly- if you want to push it out as a package to Windows 7, you need a somewhat functioning SCCM Client and Windows Update Client!
- After those are run , if they cannot fix the errors , then you have two choices
- rebuild the machine
- Go into IT hero mode and follow https://support.microsoft.com/en-us/help/2700601/how-to-fix-errors-found-in-the-checksur-log
Hope that has been of some help!