When reviewing Windows Update Deployments in Configuration Manager Monitoring - Deployments, administrator discovers numerous clients showing unknown status and complaint status is not incrementing.
Troubleshooting
Start by utilizing the built in tools in the Configuration Manager Reporting:
- Navigate to Monitoring - Reporting - Reports
- Expand "Software Updates - E Troubleshooting"
- run the report "Troubleshooting 1 - Scan Errors"
- run the report "Troubleshooting 2 - Deployment Errors"
- run the report "Troubleshooting 3 - Computers Failing With Specific Scan Error"
- run the report "Troubleshooting 3 - Computers Failing With Specific Deployment Error"
- Review the reports
Possible Errors Found:
Error Code -2145107934 Hex Error Code 80244022 "Same as HTTP Status 503 - the service is temporarily overloaded"
and
Error Code -2145107940 Hex Error Code 8024401C "Same as HTTP status 408 - the server timed out waiting for the request"
these errors indicate a possible issue with the WSUS IIS Application Pool.
Resolution:
Review the WSUS IIS Application Pool in II Manager
If it is stopped, this may indicate the service is crashing due to lack of adequate resources and may need to be optimized.
- Restart the WSUSPOOL in IIS Manager
- Optimize the Service:
- IIS Manager > Application Pools > WsusPool > Advanced Settings
- make the following changes to the settings for the WSUSPool:
Queue Length: 2000 (default 1000)Idle Time-out (minutes): 0 ( default 20)Ping Enabled: False (default True)Private Memory Limit (KB): 0 (unlimited) (default 1,843,200 KB)Regular Time Interval (minutes): 0 (to prevent a recycle) (default 1740)
 |
| image source: https://docs.microsoft.com/en-us/troubleshoot/mem/configmgr/windows-server-update-services-best-practices#disable-recycling-and-configure-memory-limits |
Posts
