Config Mgr 2012 Client Troubleshooting

 
Here is a list I'm compiling of Client troubleshooting issues and resolutions.
Idea and format taken from SCCM 2012 Client Troubleshooting

If Updates won't install
WUAHandler.log 80004005
   1. Delete C:\Windows\System32\GroupPolicy\Machine\Registry.pol
   2. Run Software Updates Deployment Evaluation Cycle

WUAHandler.log 8007000d Cause: Pointing to old update server URL
   1. Delete C:\Windows\System32\GroupPolicy\Machine\Registry.pol
   2. Run Software Updates Deployment Evaluation Cycle

WUAHandler.log 80072ee2
   1. Run Software Updates Deployment Evaluation Cycle while computer has good connectivity

WUAHandler.log 80072efe
   1. Run Software Updates Deployment Evaluation Cycle while computer has good connectivity

WUAHandler.log 80080005
   1. Reboot computer
   2. Verify WUAUSERV service is running
   3. Run Software Updates Deployment Evaluation Cycle

WUAHandler.log c80003f3
   1. Launch PowerShell
   2. Stop-Service wuauserv
   3. Remove-Item "C:\Windows\SoftwareDistribution" -Force
   4. Start-Service wuaserv
   5. Run Software Updates Deployment Evaluation Cycle
WUAHandler.log 80244022


WUAHandler.log 8024002D (-2145124307)
   1. Uninstall and Reinstall CM client


WUAHandler.log 87D00605 (-2016410107)
   1. Uninstall and Reinstall CM client


If PXE won't boot
Windows Boot Manager c0000001

Problem: Boot failure right after boot.sdi message. Error 0xc0000001. "A required device isn't connected or can't be accessed."
   1. Reduce RamDiskTFTPBlockSize but keep in 1024 increments
       HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP\RamDiskTFTPBlockSize
    Source: http://tech.cellfi.sh/journal/2013/4/28/windows-pe-sccm-pxe-boot-problems-bootsdi
    Additional Information: How Booting into a Boot Image Works

WUA Scan Failed Collection

Here is a SQL query to return all resources with a particular WUA Scan error code.
select v_R_System.ResourceID,v_R_SYSTEM.ResourceType,v_R_SYSTEM.Name0,v_R_SYSTEM.SMS_Unique_Identifier0,v_R_SYSTEM.Resource_Domain_OR_Workgr0,v_R_SYSTEM.Client0 from v_R_System inner join v_UpdateScanStatus on v_UpdateScanStatus.ResourceId = v_R_System.ResourceId where v_UpdateScanStatus.LastErrorCode = '-2147467259'



Unfortunately this doesn't really help us at all if we want to perform any kind of actions on these resources.



I found this site Creating Collections using SQL which out lines an unsupported but highly effective method for using a SQL query to drive a collections membership. Below is the specific SQL I used to get the results I wanted.



Get Collection ID SQL Query
select CollectionID from v_Collections where CollectionName = 'CollectionName'



Update Collection Rules SQL Query
Update  Collection_Rules_SQL set SQL = 'select SMS_R_SYSTEM.ItemKey,SMS_R_SYSTEM.DiscArchKey,SMS_R_SYSTEM.Name0,SMS_R_SYSTEM.SMS_Unique_Identifier0,SMS_R_SYSTEM.Resource_Domain_OR_Workgr0,SMS_R_SYSTEM.Client0 from vSMS_R_System AS SMS_R_System JOIN v_UpdateScanStatus on v_UpdateScanStatus.ResourceId = SMS_R_System.ItemKey where v_UpdateScanStatus.LastErrorCode = -2147467259' where CollectionID = 16777359