Hunt SCCM Issues Down

1     This problem may occur if Windows Update or Microsoft Update cannot read the update manifest. Soluion To resolve this problem, rename the Spupdsvc.exe file, and then try to install the updates again. To do this, follow these steps: Click Start, and then click Run. Copy the following text, paste it into the Run box, and then click OK or press ENTER: Cmd /c ren %WinDir%\System32\Spupdsvc.exe Spupdsvc.old Try to install the updates again. If you still cannot install the updates, see the "References" section for information about how to contact Windows Update support or Microsoft Update support.

Solution 1. Restart the console, log out and log back in 2. Check in the  Smsprov.log file  for SQL related Errors 3. Reboot the SCCM Server 4. Try Increasing the tempdb size from 10MB to 100MB 5. Check with the SQL Team for to see  DDL Auditing is turned on 6. See if the last collection value of CollectionsID and NextCollectionID are in series If value of CollectionsID in collections table is 101, and the value of NextCollectionID in nextids table is should be102. Select * From Collections Select * from Nextids. 7. Check the smsprov.log. Point no. 5. is mostly causing the issue because the DBA Team sometimes enables DDL Auditing without informing..

Solution Verify that a heartbeat has occurred on the client by reviewing the inventoryagent.log. This log is located in the %windir%\System32\ccm\logs folder. You must locate the Inventory: Action=Discovery ReportType=Full string. You can use the Advanced Client Spy utility to view the status of discovery data. This utility is part of Configuration Manager Toolkit.  In the discovery record properties, you can view the discovery method that reported the discovery, and the last time that the discovery process ran. You can review the record to determine whether the issue is a failure to run a discovery property. If the data that is provided by Heartbeat Discovery is current, this issue may occur because of a client assignment issue on the SMS Advanced Client computer. If the correct Heartbeat Discovery data is not present, a communication problem may exist between the client, the management point, the site, and the site database. 

Causes:-- Normally windows update center will download available updates and have them installed and maintain a record for the same so that the same update is not repeated again, however if there is some issue with the Windows Update Center itself, it would either fail to download the updates or would fail to maintain a record of the installed updates. Generally on a user’s computer, the Windows Update center is being disabled. Due to lack of permissions to download files from the internet, it’s the SCCM Windows Update service that executes and installs these updates on the machines and if for any reason a user’s computer is having any issue with corrupted files or any other, these updates status may not be reaching to SCCM Compliance and as a result shows up as a required update in the machine. Even if the update is installed, the SCCM Compliance wouldn’t have a record for its installation which is why it would constantly popup and repeat the same update as a required upd

Remove SCCM Child Primary Site- Step by Step... CEN - Primary Central Site PRI - Child Primary Site SEC - Secondary Site Here is the procedure how to remove  PRI  SCCM Child Primary Site from its  CEN  SCCM Parent Site. All steps have to be performed from the Central Site  Server except the last one. First step is to login to the Central Site Server and to delete   PRI   child site address from SCCM console. Next step is to execute Preinst.exe which is located in C:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\00000409 folder: Execute  Preinst /dump command . It shows SCCM sites in SCCM Parent Central Site. The target is to remove   PRI   Child Primary Site. Delete jobs for PRI site:  Preinst /deljob PRI Delete PRI site:  Preinst /delSITE PRI CEN Execute again  Preinst /deljob PRI  to delete any job in meantime. Executing again  Preinst /dump  command shows that   PRI   Child Primary Site has been removed from SCCM Parent

WSUS POOL in IIS getting stopped frequently, causing scan  failures from client end     So why does the WSUS App pool crash and how to fix it? The WSUS App pool “private memory limit” setting is by default configured to 1.7 GB, the pool crashed because it couldn’t keep up. In order to fix that, people increase the memory on the Software Update Point and also configure the WSUS App pool memory limit with 8-12 GB. After that App pool should be started and let the clients flood the network for a couple of hours and everything was back to normal. So why couldn’t the WSUS App pool keep up? This is due to the larger number of updates in the catalog which continues to grow over time.  After the Patch Tuesday sync from Microsoft, clients started scanning successfully at first, but the Update catalog reached a size that increased the load on the Software Update Point. Due to the default memory limit of the app pool the server ran out of memory causing the WSUS App pool ca