Showing posts with label Patching. Show all posts
Showing posts with label Patching. Show all posts

Saturday, 8 September 2018

SCCM client log and troubleshooting for patching

* SCCM is a beast in itself. It's client has so many components that even if 1 Component is not working,it can cause issues
* Log files are the heart of troubleshooting for SCCM.You have to know which log file to read in which order for effective troubleshooting
* All SCCM log files are in location C:\Windowds\ccm\logs folder
* For patching issues follow the following order for troubleshooting.
*First step is to see whether patches are getting download to the client. The patches once downloaded are stored in ccmcache folder.
*This folder is in C:\windows\ccmcache
*If patches are not downloaded  in this folder then you have problem with client not able to download the patches from WSUS server.
*  You should immediately look for log called wuahandler.log
*Look for errors in this log most likely you will see error connecting to WSUS server.
* Generally the easiest troubleshooting step I do if I see this error only on few clients is to uninstall and reinstall the client from the
* Mostly this should resolve if there is client issue. . I suggest doing the install from SCCM console and choose the location for the source to I still from site location.

Wednesday, 22 April 2015

SCOM Data access Service and Config Service failing to start after recent SCCM Patching

SCOM Data access Service and Config Service failing to start after recent SCCM Patching

  • After recent SCCM patching window where the SCOM servers got patched, i got a call from support team that the SCOM Data access service (SDK service) and Config Service are not starting.
  • Further investigation revealed that a particular patch KB2677070 was causing the issue as it was trying to access the intenet to check on revoked trusted certificates.
  • As most corporate enviorment internet is blocked from prouction servers this started faining can caused the service not to start.
  • After uninstall the patch and reboot the server, the services started without any issue.
  • Another solution is that you have go to th registry
  • HKLM\Software\Policies\Microsoft\SystemCertificates
  • Right-click AuthRoot, select New, and then click DWORD.
  • Type DisableRootAutoUpdate, and then press Enter.
  • Right-click DisableRootAutoUpdate, and then click Modify.
  • In the Value data box, type 1, and then click OK.