I don't know what you're talking about. If you're performing the proper maintenance for WSUS and have optimized it properly, the console does not time out, reports are quick to generate, and checking for updates from client systems are also quick.
Not only this, but I RECOMMEND enabling the Drivers category. Most people hate it because enabling the Drivers category brings in a lot of updates but they also don't know the power of WSUS Automated Maintenance (WAM): WAM can remove all drivers from your system without requiring a reinstall of WSUS allowing only NEW drivers to enter your system. Over time, the list piles up again (as it's routine for 500-1000 updates a day to come in from Drivers) as you can see on my instance with a snippet of the next version's output below:
Decline Multiple Types of Updates:
There are 107329 updates in this server's database.
There are 41 types of updates listed in the configuration, however only 22 are enabled to be declined.
Of course most of the time you shouldn't be seeing pages and pages and pages of updates because you're using the proper techniques to scope your views for the approvals process.
As my original question has not been answered, I would say this question is still open:
a) make the sproc run faster
b) make the console more tolerant of timeouts.
However, I suspect the answer is "No" to both of them. It's a design flaw in the sproc that causes it to timeout and that requires the developers to change their algorithm. And no, there isn't a magic way to increase the timeout in the console.
This is a well documented and reported flaw in WSUS - there are probably 50+ topics on the same problem:
I can tell you from experience, that when using WSUS Automated Maintenance (WAM)©, along with a properly configured WSUS Server, you don't get any timeouts using the Windows Internal Database (which is what I am using, and recommend to use). I have all classifications checked including Drivers, and my database currently has 108,369 updates in the database. WSUS is fast, responsive, doesn't time out, and I can list all unapproved drivers in the database (~98,000) in less than 40 seconds in the WSUS console in my Drivers update view, scoped to Unapproved with the status of Any. Opening Computer reports or update reports are usually open and usable in under 6 seconds. No timeouts, no reset server node.
Full disclosure, WAM is my product.
Have you tried to index the database as the below link? If not, we could try to index the database and then decline superseded updates to see whether this issue will be resolved or not.
It is a better way to reinstall the WSUS role if the above step is useless.
Sign in to comment