Updating windown service pack 3

03 Feb

The third set of options works by limiting the bandwidth used by the SUS implementation, thereby controlling the load on the server and the network.

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.

This is a manual but easily implemented mechanism to control the load on the SUS server and requires no additional infrastructure configuration or testing.

SUS administrators can use the following formula to calculate the amount of time for which to approve the Windows XP SP2 update on each day: TA = Amount of time (in hours) the update needs to be marked as ‘approved’ on a given day NXP = Number of Windows XP systems to get SP2 via the SUS server NDE = Number of days since SP2 was first marked as approved on the SUS server For example, if there are 12000 Windows XP systems that need to get the Windows XP SP2 update via a SUS server, the calculation would work out as follows: For day 1, the update would need to be marked as approved for 2 hours, since Note: An important consideration for using this technique is to initiate the approval about 1 hour after the work day or shift starts, so the SUS server is not impacted by the spike in clients trying to download SP2 soon after they are turned on.

These configuration options are available with IIS 5 as well as IIS 6.The IIS server will allocate the maximum bandwidth usage specified equally across the concurrent connections specified.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.For the standard SUS machine (P700, 512 MB RAM, 100 Mbps network card), set the maximum concurrent connections to 100 and the maximum bandwidth for the SUS Web site to 80 Mbps.