Systems update services

For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article. After you install this update, you may have to restart your system. NET Framework 3. NET Framework 2. Target platforms: Windows 8. Description: ComponentUpdate: A security issue has been identified in a Microsoft software product that could affect your system.

Description: Install this update to resolve issues in Windows. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article for more information.

After you install this item, you may have to restart your computer. For more information about the Software Update Services and Windows Server Update Services changes that occurred before January 11, , go to the following Microsoft websites to check the content for each year:.

Windows Internet Explorer. NET More Need more help? Expand your skills. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy. You can use WSUS to fully manage the distribution of updates that are released through Microsoft Update to computers on your network. This topic provides an overview of this server role and more information about how to deploy and maintain WSUS.

A WSUS server provides features that you can use to manage and distribute updates through a management console. The WSUS server that acts as an update source is called an upstream server. As an administrator, you can determine - based on network security and configuration - how many other WSUS servers connect directly to Microsoft Update. Update management is the process of controlling the deployment and maintenance of interim software releases into production environments. It helps you maintain operational efficiency, overcome security vulnerabilities, and maintain the stability of your production environment.

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.