I am setting up WSUS and am using a 2012 R2 Server. I got to the point where WSUS was syncing with Microsoft, but after approving critical updates WSUS now opens with "Error: Connection Error. Click Reset Server Node to try to connect to the server again." Clicking Reset Server Node does nothing
Here's what I found to work in a customers production environment:
1. On your WSUS Server, launch the IIS Manager
2. Open Application Pools
3. Right click 'WsusPool' and select 'Advanced Settings...'
4. When the Advanced Settings window opens up find the Recycling section near the bottom.
5. Change Private Memory Limit (KB) to a higher number that fits your server specifications or ‘0’, which means no limit, instead of the hard-coded 1258015.
Since implementing this change, WSUS has been available consistently through the console and clients checking for new updates.
Good luck!
0 comments:
Post a Comment