Note: The above formula is based on conservative assumptions to account for potential spikes in the number of clients contacting the server during the approval window.Using this technique, it is estimated that between 10 SUS client machines will get the Windows XP SP2 update per day.You may monitor the SUS server using performance counters or the Task Manager and increase the length of the approval windows if you determine the load on your SUS server is not high.

updating ms windows xp-69updating ms windows xp-89updating ms windows xp-24

This technique relies on the SUS administrator to approve and then un-approve the Windows XP SP2 update on the SUS server on a daily basis, until the number of Windows XP systems that have not received the SP2 update is less than 2000.

Because the update is only approved for a limited time each day, only a subset of the SUS clients contacting the server on a given day will see the update marked as ‘approved’ and will attempt to download the update.

It is also recommended that you plan your Windows XP SP2 deployment so it doesn’t overlap with the deployment of the monthly security updates from Microsoft (released on the 2nd Tuesday of each month) to eliminate the need to factor in the impact of the deployment of these updates on server load and therefore on the lengths of the approval windows for the Windows XP SP2 deployment.

The following are the pros and cons of using this technique: Pros: This option allows limiting the maximum bandwidth that may be used for SUS by setting the appropriate values for the maximum number of concurrent connections and the maximum bandwidth the IIS server allocates to servicing SUS requests.

Introduction Key benefits of using SUS to deploy Windows XP SP2 Situation overview Factors to consider when using SUS to deploy Windows XP SP2 Overall recommendations Summary Windows XP Service Pack 2 (SP2) contains major security improvements designed to provide better protection against hackers, viruses, and worms.

Windows XP SP2 also improves the manageability of the security features in Windows XP and provides more and better information to help users make decisions that may potentially affect their security and privacy.

Note: Limiting the load on the SUS server or the network via the options described here will result in it taking longer for all the Windows XP systems to be updated, because the bottleneck is the server load.

The guidance provided below for each option is based on the same server load assumption, so it should take approximately the same length of time to deploy Windows XP SP2 irrespective of the option implemented.

If your SUS server machines is running additional services or the available network capacity is less than the server network card capacity, you will need to adjust this guidance to reflect your situation.

There are essentially three options, depending on the number of Windows XP systems to be updated using your SUS server (if you have one or a few SUS servers) and the topology of your SUS implementation (if you have many SUS servers): For the first (no action necessary) option, it is recommended that the SUS administrator monitor the server load when the update is first approved and for the first hour of the work day or first work shift after the Windows XP SP2 update has been approved.

The following section provides guidance to prevent this situation from occurring.