Start Updating windows xp service pack 1

Updating windows xp service pack 1

The limited-time approval technique works by limiting the number of SUS clients that see the Windows XP SP2 update on the list of approved updates when they contact the SUS server on any given day while this technique is in use, thereby controlling the number of clients that are serviced per day and limiting the server load and additional network overhead (retry attempts, etc.).

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

The following guidance is provided for the minimum SUS server configuration – Intel P700 system with 512MB RAM and a 100 Mbps network card and network connection, which is dedicated to running the SUS server (no domain controller, etc.) and is on a network where the available bandwidth exceeds the bandwidth capacity of the server’s network card.

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.

Increasing the length of the approval windows will allow more clients to download Windows XP SP2 on a daily basis and reduce the time required to update all your Windows XP machines, but increasing the windows beyond a certain threshold (which will vary due to unique factors in your environment) will cause server overload and unnecessary network overhead which will result in increasing rather than decreasing the time required to update all your Windows XP machines.

Note: This configuration will allow about 2000 Windows XP systems to download and install the Windows XP SP2 update per day and will take approximately one hour for each to download, assuming there are no other connectivity bottlenecks.

This option uses the BITS 2.0 maximum bandwidth usage parameter to control the amount of bandwidth used by SUS clients when interacting with the SUS server.

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.

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.

Family Id=A7AA96E4-6E41-4F54-972C-AE66A4E4BF6C&displaylang=en Because Windows XP SP2 is a relatively large update (approximately 270 MB), SUS administrators need to consider the impact on internal network traffic and on the machine on which the SUS server is running.