Updating xp home to xp pro
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.
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.
While this is the theoretical number of clients that can be supported in a 24-hour period if only one client is in contact with the server at any given time and there is no time gap between servicing one client and the next, a couple of factors contribute to reducing this number in reality.
These include: Although clients that cannot be serviced by the SUS server because of capacity limitations will attempt to contact the server again after approximately 5 hours, this overload situation will result in slowing down the server and generating additional network overhead.
Using this technique, it is estimated that between 10 SUS client machines will get the Windows XP SP2 update per day.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.Microsoft strongly urges customers with Windows XP and Windows XP Service Pack 1-based systems to update to Windows XP SP2 as soon as possible.As a best-practice approach to implementing a managed rollout of Windows XP SP2, customers are encouraged to use a corporate update management solution such as Systems Management Server (SMS) 2003 or Software Update Services (SUS).