| Introduction | |
| Before You Begin | |
| Planning and Deploying SUS | |
| Updating Computers Using SUS | |
| Suggested Methods to Test Updates | |
| Related Information |
An important way to help keep your network secure is to install the latest operating system updates to computers running Microsoft Windows.
Software Update Services (SUS) Server 1.0 Service Pack 1 (SP1) provides a way to manage and distribute critical Windows updates, which resolve known security vulnerabilities and other stability issues in Windows.
Note: SUS Server 1.0 SP1 addresses compatibility issues that existed between Windows Small Business Server 2003 and SUS Server 1.0.
If you use SUS, you do not need to use the Windows Update Web site to manage the updates for each computer on the network. Instead, you can manage the updates on the computer running Windows Small Business Server and configure that computer to distribute the updates automatically to the client computers. The client computers do not need Internet access to receive the updates. This paper tells you how to install, configure, and use SUS Server 1.0 on your Windows Small Business Server 2003 network using the following steps:
| • | Planning and deploying SUS |
| • | Updating computers using SUS |
This paper also includes an optional section that gives suggested methods to test updates.
SUS can provide updates for computers running Windows 2000 Professional, Windows 2000 Server, Windows XP Professional, or Windows Server 2003 operating systems. If you are running another version of Windows, you can find instructions for how to update it on the Windows Downloads page on the Microsoft Web site at http://www.microsoft.com/windows/downloads/default.mspx.
If you have five or fewer computers, using SUS is not efficient. Instead, configure each client computer to download and install updates from Windows Update using Automatic Updates. For more information about Windows Update and Automatic Updates, see the Frequently Asked Questions on the Microsoft Web site at http://www.microsoft.com/athome/security/protect/update.mspx.
Note: If you have computers that are not part of the Small Business Server domain, you can update them using Automatic Updates. If you have computers running Windows XP Home Edition, you can use Automatic Updates or you can upgrade to Windows XP Professional. Windows XP Professional is designed to work with the Windows Server 2003 network environment. This adds security while also improving reliability, performance, and functionality for the local network. For information about upgrading client computers, see the Windows XP Professional Upgrade Center on the Microsoft Web site at http://www.microsoft.com/windowsxp/pro/upgrading/default.mspx.
IMPORTANT: All the step-by-step instructions included in this document were developed by using the Start menu that appears by default when you install your operating system. If you have modified your Start menu, the steps might differ slightly.
Before you deploy SUS, you must complete Windows Small Business Server 2003 Setup.
This document assumes that you have already completed Windows Small Business Server 2003 Setup, including the Connect to the Internet task on the To Do List. The To Do List appears at the end of Setup and is used to complete the configuration of Windows Small Business Server 2003. If you have not configured your Internet connection, complete the following procedure.
| • | To configure your Internet connection
|
If you are migrating from Microsoft Small Business Server 2000 and the computer is also running SUS Server 1.0 SP1, check for an update addressing this situation in the document "Migrating from Small Business Server 2000 or Windows 2000 Server to Windows Small Business Server 2003" on the Microsoft Web site at http://www.microsoft.com/downloads/details.aspx?FamilyID=fa187d1e-8218-4501-9729-222bd8ebb64c&DisplayLang=en.
Before you install SUS, you first take an inventory of the computers in your network. This will later help you decide how to deploy the updates to the computers. Then you install and configure SUS. Finally, you prepare the client computers for SUS and configure settings to deploy automatic updates.
Use the following steps to plan and deploy SUS Server 1.0 SP1:
| • | Take an inventory of the computers on your network |
| • | Install and configure SUS |
| • | Download updates for SUS |
| • | Upgrade Automatic Updates on client computers |
| • | Configure settings for Automatic Updates |
You must take an inventory of each computer on your network to determine its name and the licensed operating system it is running. You will use this information later to determine whether any computers need to be updated without using SUS and whether the Automatic Updates software on any of the computers needs to be updated to work with SUS. All Microsoft software should be licensed on the computers you intend to update.
Requirements
| • | You must be logged on as a member of the Administrators group. |
| • | To determine client computer names and operating system versions
|
| • | To determine server computer names and operating system versions
|
To work with SUS, computers running Windows 2000 need to have Service Pack 2 or later installed. If they do not, install the latest service pack on them.
| • | To install the latest service pack on computers running Windows 2000
|
You also need to determine your Windows domain name.
| • | To determine your Windows domain name
|
In the output text, you will see the following:
USERDOMAIN=yourWindowsdomain
where yourWindowsdomain is the name of your Windows domain.
Write your Windows domain name here:
You must download SUS Server 1.0 SP1, install it, and configure it on the computer running Windows Small Business Server 2003.
Requirements
| • | You must be logged on as a member of the Administrators group. |
| • | To download SUS Server 1.0 SP1
|
When the download is complete, install SUS Server 1.0 SP1.
| • | To install SUS Server 1.0 SP1
|
If you are running Microsoft Internet Security and Acceleration (ISA) Server on your computer running Windows Small Business Server, you must configure SUS to use a proxy server. This will allow SUS to connect to the Internet through the proxy server.
| • | To configure SUS to use a proxy server
|
SUS can provide updates for clients in any language or locale. You need to select the languages and locales that you support.
| • | To configure SUS to install particular languages and locales
|
The next step is to download all available updates for SUS. This helps ensure that your installation of SUS includes all the supported Windows operating systems for all the locales you selected in the previous procedure.
The amount of data that you must download is large; one locale requires approximately 600 MB. To download 600 MB of data takes approximately 125 minutes over a 640 Kbps broadband connection or 23 hours over a 56 Kbps dial-up connection. Therefore, schedule the download for a time when no business activity is taking place on your Internet connection. Also, make sure not to schedule the download for the same time as the system backup.
| • | Requirements
|
| • | To download updates for SUS
|
The Approve updates page appears. Do not approve any updates yet.
The Automatic Updates program on your client computers may need to be updated to work properly with SUS, depending on which operating system and service packs the client computer is running. Review the computer inventory list that you created earlier. If a computer is running any of the following operating systems, the Automated Updates program must be updated on it before you run SUS:
| • | Windows 2000 Professional Service Pack 2 |
| • | Windows 2000 Server Service Pack 2 |
| • | Windows XP Professional (no service pack) |
| • | Windows XP Home Edition (no service pack) |
On computers running Windows 2000 Service Pack 3 or later, Windows XP Service Pack 1 or later, or Windows Server 2003, you do not need to update the Automatic Updates program.
Requirements
| • | You must be logged on as a member of the Administrators group. |
| • | To update the Automatic Updates program
|
You must configure how and when to handle updates on your network, including when to download and install the updates. To do this, use Group Policy to configure the Basic SUS Config Group Policy object (GPO). If you choose to, you can also configure the Scheduled Install SUS Config GPO.
The Basic SUS Config GPO configures updates so that they are automatically downloaded and the user chooses when to install them. This GPO typically applies to servers on a network, but you can also use it to give the user of a client computer the option to install updates when the user chooses.
The Scheduled Install SUS Config GPO is an additional, optional GPO that configures updates so that they are automatically downloaded and installed according to a schedule you define. This GPO typically applies to client computers on a network.
Before configuring the GPO, you must determine if any computer accounts need to be moved to the proper location. If computers were added to the network without using the Add Computers wizard, computer accounts may not be located in the expected location and the GPO will not work for updating client computers.
Requirements
| • | You must be logged on as a member of the Administrators group. |
| • | To move computer accounts to the proper location
|
Next, create the Basic SUS Config GPO.
| • | To create the Basic SUS Config GPO
|
Create the Scheduled Install SUS Config GPO if you want to schedule the installation of Windows updates on your client computers. This installation schedule does not apply to server computers.
| • | To create the Scheduled Install SUS Config GPO
|
After you have configured SUS on the computer running Windows Small Business Server, you must determine which updates you will approve to be downloaded and installed on your computers. After the download and installation has occurred, you must then verify that the updates have occurred correctly. SUS downloads and installs only those updates that apply to a computer's operating system and locale. When new updates are released from Microsoft, repeat this process.
The following are the steps for updating your computers using SUS Server 1.0 SP1:
| • | Test the updates (optional) |
| • | Approve the updates |
| • | Verify that client computers are receiving updates |
| • | Install updates on server computers |
| • | Continue applying updates |
If you are concerned about compatibility issues for business applications when new Windows updates are installed, consider testing the updates before you approve them. If you elect to test the updates before approving them, see the section titled "Suggested Methods to Test Updates" later in this document.
To distribute updates to computers on your network, you must approve them.
Requirements
| • | You must be logged on as a member of the Administrators group. |
| • | To approve the updates
|
By 5:00 the next morning, each client computer should have downloaded and installed the updates that you approved and that apply to the operating system it is running. If the updates still have not appeared after approximately 48 hours, you can perform troubleshooting procedures to fix the problem.
For best results when using SUS, users should save their data, close their applications, log off, and leave their computer on at night so that updates install automatically before the users return the next morning.
Many Windows updates are specific to a particular operating system version. If a computer is not running that particular operating system or browser, the update is not downloaded or installed on it.
Note: If you did not create the Scheduled Install SUS Config follow the step called "Install Updates on Server Computers" later in this paper to install updates on all of your computers.
Requirements
| • | You must be logged on as a member of the Administrators group. |
| • | To verify that updates have been installed on a client computer
|
You should see a list of programs that are currently installed, including the updates that you approved.
If you do not see the updates and more than 48 hours have elapsed, perform the following procedures to fix the problem.
| • | To verify that a computer has received the appropriate Group Policy settings, using Resultant Set of Policy (Windows XP only)
|
If you created the Scheduled Install SUS Config GPO, the following will be displayed on a client computer:
Client Computer Group Policy Settings (with Both GPOs)
| Setting | State | GPO Name |
Configure Automatic Updates | Enabled | Scheduled Install SUS Config |
Specify intranet Microsoft Update service location | Enabled | Scheduled Install SUS Config |
Reschedule Automatic Updates scheduled installations | Enabled | Scheduled Install SUS Config |
No auto-restart for scheduled Automatic Updates installations | Disabled | Scheduled Install SUS Config |
If you did not create the Scheduled Install SUS Config GPO, the following will be displayed:
Client Computer Group Policy Settings (with One GPO)
| Setting | State | GPO Name |
Configure Automatic Updates | Enabled | Basic SUS Config |
Specify intranet Microsoft Update service location | Enabled | Basic SUS Config |
If this is not what is displayed, go back to the section called "Configure Settings for Automatic Updates" and double-check to see that the procedures were followed correctly.
If it appears that a computer has the proper Group Policy settings applied to it, but the expected updates still do not appear, you can try forcing a Group Policy update on that computer.
| • | To force a Group Policy update on a computer running Windows XP
|
| • | To force a Group Policy update on a computer running Windows 2000
The GPO will be updated from the computer running Windows Small Business Server. Check again for updates after 48 hours. If you did not create the Scheduled Install SUS Config GPO, check to see if the update icon appears in the taskbar. You may need to wait a few hours for the icon to appear. |
On your server computers (including the computer running Windows Small Business Server), install the updates manually, at a time that is convenient for you.
Requirements
| • | You must be logged on as a member of the Administrators group. |
| • | To manually install updates on a server computer
|
If you do not see this icon and more than 48 hours has elapsed, perform the following procedures to try to fix the problem.
| • | To verify that a computer has received the appropriate Group Policy settings using Resultant Set of Policy (Windows Server 2003 only)
|
Server computers should display the following information:
Server Computer Group Policy Settings
| Setting | State | GPO Name |
Configure Automatic Updates | Enabled | Basic SUS Config |
Specify intranet Microsoft Update service location | Enabled | Basic SUS Config |
If this is not what is displayed, go back to the section called "Configure Settings for Automatic Updates" and double-check to see that the procedures were followed correctly.
If it appears that a computer has the proper Group Policy settings applied to it but the expected updates do not appear, you can try forcing a Group Policy update on that computer.
| • | To force a Group Policy update on a computer running Windows Server 2003
|
| • | To force a Group Policy update on a computer running Windows 2000
|
The server that is running SUS downloads new updates automatically when they are released by Microsoft. Periodically check the SUS Administration page for new updates that you need to review for approval. To remind you that new updates are available, you can subscribe to receive update notifications on the Microsoft Web site at http://www.microsoft.com/security/default.mspx. If you subscribe, you will receive e-mail when new updates are released.
Requirements
| • | You must be logged on as a member of the Administrators group. |
| • | To update your computer
|
To test the Windows updates, consider designating one of your computers as the test computer. This computer should run your important applications and be used by a person who is technically advanced enough to help you troubleshoot the problems that might arise from the tests. You will need to designate more than one of your computers as a test computer if you have multiple operating-system versions or if you cannot find a computer that runs all your important applications. For example, if you use Windows XP and Windows 2000, you need a Windows XP test computer and a Windows 2000 test computer. You will download the updates directly from the Microsoft Windows Update Services and apply them to your test computer.
On test computers running Windows XP, use System Restore to create a restore point before testing the Windows updates. This will protect your system from potentially harmful changes because, if the updates cause problems with your applications, you can return the system to the restore point and undo the updates. On computers running versions of Windows other than Windows XP, you must manually uninstall the updates by using Add or Remove Programs in Control Panel.
Before you install updates, check with the manufacturer of any third-party applications that you use to see if they know of any compatibility issues between the application and a Windows update. If so, they may have a solution for the problem and you can avoid unnecessary testing. Do the following to check for compatibility issues:
| • | Check the manufacturer's manual. |
| • | Browse the manufacturer's Web site. Generally, compatibility issues are listed in the Support area. |
| • | Call their Support number and ask about any known compatibility issues with Windows updates. |
| • | To create a restore point on your test computer (Windows XP only)
|
Next, download any available critical updates and service packs from Microsoft Windows Update on the Microsoft Web site at http://windowsupdate.microsoft.com. You must do this on a different test computer for each version of Windows running on your network. For example, if you have Windows XP and Windows 2000 Professional, you need a Windows XP test computer and a Windows 2000 Professional test computer.
Note: Some updates cannot be removed from the operating system. The detailed description of the update will tell you which updates can not be removed.
| • | To update the test computer
|
Now test your important business applications on the test computer with the newly installed updates.
| • | To test your applications
|
If all of your applications worked as expected and you did not have any problems, continue on to the section titled, "Approve the Updates." Otherwise, remove the updates from the test computer. On a computer running Windows XP, use the system restore point that you created earlier. On a computer running Windows 2000, Windows Small Business Server 2003, or Windows Server 2003, you must remove the updates manually. If you want, you can also manually remove the updates from a computer running Windows XP.
| • | To remove updates using System Restore (Windows XP only)
|
| • | To remove the updates manually (Windows 2000, Windows Small Business Server 2003, Windows Server 2003)
|
After you have removed all the updates, verify that the test computer and the applications are performing normally.
If you have not already done so, contact the manufacturer of the application that had a compatibility issue with the Windows Updates to find out if they know of the issue and have a solution.
If they do not, determine which update is incompatible with the application and avoid installing that update.
| • | To determine which update is incompatible with an application
|
After testing is complete, note which Windows updates passed the test. These will be the updates that you approve. When you are ready to approve the updates, return the section titled, "Approve the Updates."
For advanced information about implementing SUS, see the following:
| • | "Deploying Patches with Software Update Services 1.0" in the Security Guidance Kit |
For more information about Windows Small Business Server 2003 security, see the following:
| • | "Securing Your Windows Small Business Server 2003 Network" in the Security Guidance Kit |