This article provides tips for avoiding configurations that experience poor performance because of design or configuration limitations in WSUS. Although WSUS can support , clients per server , clients when you use Configuration Manager , we don't recommend approaching this limit. Instead, consider using a configuration of servers sharing the same SQL Server database. This way you have safety in numbers.
If one server goes down, it won't immediately spoil your weekend because no client can update while you must be updated against the latest zero-day exploit. A scan storm can occur when many clients change WSUS servers and the servers don't share a database. WSUS tracks activity in the database, so that both know what has changed since a client last scanned and will only send metadata that's updated since then.
If clients change to a different WSUS server that uses a different database, they must do a full scan. A full scan can cause large metadata transfers. Transfers of greater than 1 GB per client may occur in these scenarios, especially if the WSUS server isn't maintained correctly. It can generate enough load to cause errors when clients communicate with a WSUS instance. And clients retry repeatedly in this case. Sharing a database means when a client switches to another WSUS instance that uses the same DB, the scan penalty isn't incurred.
The load increases aren't the large penalty you pay for switching databases. Configuration Manager, because it includes compliance checking, requests scans with criteria that will return all updates that are in any status except declined. The metadata returned will usually be less than when the scan is initiated by Configuration Manager. The Update Agent does cache the data, and the next scan requests will return the data from the client cache.
WSUS implements an internal cache that retrieves the update metadata from the database. This operation is expensive and very memory intensive. When the pool recycles, the cache is removed and must be rebuilt. It isn't a large problem when clients are undergoing delta scans. But if you end up in a scan storm scenario, the pool will recycle constantly.
Although it typically takes less than 15 minutes to run, it might take much longer on some computers. Even if the progress bar seems to stop, the scan is still running, so don't select Cancel.
To manually fix corruption errors that the tool detects but can't be fixed, see How to fix errors that are found in the CheckSUR log file. You can also try to directly download the update package from Microsoft Update Catalog , and then install the update package manually. For example, you may have problems when you try to install updates from Windows Update.
In this situation, you can download the update package and try to install the update manually. To do this, follow these steps:. In the search box, input the update number that you want to download. In this example, input Then, select Search. Find the update that applies to your operating system appropriately in the search results, and then select Add to add the update to your basket. Select Browse to choose a location for the update you are downloading, and then select Continue.
Select Close after the download process is done. Then, you can find a folder that contains the update package in the location that you specified. If the Windows update or service pack installed successfully, you are finished. If the problem is not fixed, or if System Update Readiness Tool cannot find the cause, contact us for more help.
When the System Update Readiness tool detects incorrect manifests, Cabinets, or registry data, it may replace the incorrect data with a corrected version. The System Update Readiness tool creates a log file that captures any issues that the tool found or fixed. Was this information helpful? Yes No. Thank you! Any more feedback? The more you tell us the more we can help. Can you help us improve? Resolved my issue. Clear instructions. Easy to follow. No jargon. Pictures helped.
Didn't match my screen. Incorrect instructions. Too technical. Not enough information. Not enough pictures. Any additional feedback? Submit feedback. Thank you for your feedback!
0コメント