Top 10 Tips for Optimizing WSUS Performance and Reliability

Introduction: (0:00)
History Lesson on the Start of WSUS Issues from Meghan Stewart: (0:36)
Q&A’s with Meghan Stewart: (9:45)
Background on Optimizing WSUS Performance and Reliability: (12:51)
SQL Memory: (15:33)
How to Adjust SQL Memory: (16:18)
Creating Custom Indexes:(17:39)
How to Create Custom Indexes Manually: (20:06)
Running Re-Indexing of the Database: (24:19)
Decline Unneeded Update: (29:56)
First Time Sync Without Updates Declined: (31:27)
Large Metadata Updates – General WSUS Update Maintenance: (32:03)
Reviewing Categories/Products Enabled in the Software Update Point: (38:49)
Example of what Timeouts Look Like When Custom Indexes are Not Created: (41:22)
Creating Custom Indexes to improve Timeouts: (42:53)
IIS Configuration: (47:17)
SQL Server Profiler: (50:42)
Q&A’s with Justin and Cody: (54:44)
Wrap-Up: (55:40)

[saiiiiiii]

30:00 let's say I have 600 non-declined updates in total and 2 WSUS target groups (Windows Clients and Windows Servers), each group needing 300 of these updates. Does it make a difference if I approve the updates for both target groups or will the Client just scan for updates that'll match the software it has installed anyway? Or should I just approve target group matching updates?