{"id":3141,"date":"2018-04-06T23:57:02","date_gmt":"2018-04-06T23:57:02","guid":{"rendered":"http:\/\/pariswells.com\/blog\/?p=3141"},"modified":"2023-07-17T11:41:26","modified_gmt":"2023-07-17T11:41:26","slug":"wsus-best-practices-fixing-the-wsus-content-directory-is-not-accessible-503","status":"publish","type":"post","link":"https:\/\/pariswells.com\/blog\/random\/wsus-best-practices-fixing-the-wsus-content-directory-is-not-accessible-503","title":{"rendered":"WSUS Best Practices ( Fixing The WSUS content directory is not accessible ) 503"},"content":{"rendered":"\n

Recently on adding some machines and updates to a existing WSUS server that had been stable for a whole year, I was getting the server being unresponsive , and the reset server node<\/strong> would not work<\/p>\n\n\n\n

After restarting the Windows Update Server Service , the error below would display in the event log : <\/p>\n\n\n\n

The WSUS content directory is not accessible. System.Net.WebException: The remote server returned an error: (503) Server Unavailable. at System.Net.HttpWebRequest.GetResponse() at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckContentDirWebAccess(EventLoggingType type, HealthEventLogger logger)<\/strong><\/p>\n\n\n\n

Running IISRest<\/strong> in the Command prompt brought the site back online  , however clearly this was a workaround to teh crash , Turns out you need some tweaking of the Website in IIS to stop this!<\/p>\n\n\n\n

    \n
  1. On your WSUS Server, launch the IIS Manager<\/li>\n\n\n\n
  2. Open Application Pools<\/li>\n\n\n\n
  3. Right click ‘WsusPool’ and select ‘Advanced Settings…’<\/li>\n\n\n\n
  4. To support the maximum SCCM Software Update Point clients, change ‘Queue Length’ from the default 1,000 to 25,000
    <\/a><\/li>\n\n\n\n
  5. If your server is NUMA aware, change ‘Maximum Worker Processes’ from the default 1 to 0. If you don’t know if your server is NUMA aware, leave this value default
    <\/a><\/li>\n\n\n\n
  6. Change ‘”Service Unavailable” Response Type’ from the default HttpLevel to TcpLevel<\/li>\n\n\n\n
  7. Change ‘Failure Interval (minutes) from the default 5 to 30<\/li>\n\n\n\n
  8. Change ‘Maximum Failures’ from the default 5 to 60
    <\/a><\/li>\n\n\n\n
  9. Click ‘OK’ to save the App Pool changes<\/li>\n\n\n\n
  10. From an administrative command prompt, type IISRESET<\/li>\n<\/ol>\n\n\n\n

    This is also a good Cleanup script to schedule : <\/p>\n\n\n\n

    \nhttps:\/\/community.spiceworks.com\/scripts\/show\/2998-wsus-automated-maintenance-formerly-adamj-clean-wsus\n<\/div><\/figure>\n","protected":false},"excerpt":{"rendered":"

    Recently on adding some machines and updates to a existing WSUS server that had been stable for a whole year, I was getting the server being unresponsive […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[2358,2357,2355,2356,925,923],"class_list":["post-3141","post","type-post","status-publish","format-standard","hentry","category-random","tag-2358","tag-reset-server-node","tag-the-wsus-content-directory-is-not-accessible","tag-unresponsive","tag-windows-update-services","tag-wsus"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t