Export (0) Print
Expand All

Windows Server 2003 Service Pack 1 Installation and Deployment Guide

Updated: June 8, 2005

Applies To: Windows Server 2003 R2

Introduction to Service Pack 1 (SP1)

Before You Deploy SP1

Planning Your Deployment

The Standalone Installation

The Integrated Installation

Command-Line Options for Installing SP1

Uninstalling SP1

Symbols for Debugging Service Packs

Additional Resources

Introduction to Service Pack 1 (SP1)

This guide explains how you can:

  • Deploy Microsoft® Windows Server™ 2003 Service Pack 1 (SP1) to multiple computers that are already running the Windows Server 2003 operating systems. If you have only one server to update, you can see the Readme for Windows Server 2003 Service Pack 1 (on the Microsoft TechCenter Web site) instead.

  • Integrate SP1 with Windows Server 2003 for deploying to multiple computers running an earlier version of Windows® or with no operating system installed.

  • Uninstall SP1 from computers.

This guide does not explain:

noteNote
You cannot install SP1 on any x64-based versions of Windows Server 2003. For more information about these versions, see Windows Server 2003 x64 on the Microsoft Web site.

  • How to deploy SP1 by using Software Update Services (SUS)

    For details about using SUS, see Windows Server System on the Microsoft Web site.

Before You Deploy SP1

Before you deploy SP1, you should review the information about the service pack on the Microsoft TechCenter Web site so that you can:

  • Understand what functionality and security technologies SP1 includes and how you can implement them in your environment.

  • Find out how to plan, prepare, test, and troubleshoot your SP1 deployment.

  • Read other essential installation information, and check minimum hard disk requirements in the Readme for Windows Server 2003 Service Pack 1 (on the Microsoft TechCenter Web site).

List of updates

For information about updates and fixes included in SP1, see article 824721, "Windows Server 2003 Service Pack 1 List of Updates," in the Microsoft Knowledge Base.

Release notes

Before you install SP1, see article 889101, "Release Notes for Windows Server 2003 Service Pack 1," in the Microsoft Knowledge Base.

Files and programs in SP1

You can obtain installation files to deploy SP1 to multiple computers from either the SP1 CD or the Microsoft Download Center.

For 32-bit versions of Windows Server 2003 (which run on x86-based computers), the SP1 installation file is named WindowsServer2003-KB889101-SP1-x86-LLL.exe, where LLL is the language version of SP1. For example, ENU represents the English-language version.

For Itanium-based versions of Windows Server 2003, the SP1 installation file is named WindowsServer2003-KB889101-SP1-ia64-LLL.exe.

You can update Itanium-based versions with SP1 for only English, German, Japanese, and French locales.

The instructions and examples throughout this document use the name of the installation file for 32-bit versions (unless a particular difference between 32-bit and Itanium-based installations must be called out).

Contents of the SP1 CDs

For each language version, two CDs are available to update Windows Server 2003 operating systems with SP1: one for 32-bit versions of Windows Server 2003 and one for Itanium-based versions. The CD for Itanium-based versions is labeled as such.

Each SP1 CD contains the following files:

  • A service pack installation file

  • The Deploy.cab file. This is a compressed file that contains a collection of tools and accompanying online Help. (See Deploy.chm and Ref.chm when you expand Deploy.cab.) It is located on the SP1 CD in the \Support\Tools folder. Deploy.cab is not automatically loaded when you install SP1.

  • The Support.cab file. This is a compressed file that also contains a collection of tools and online Help. It is located in the \Support\Tools folder. Technical support personnel and network administrators can use the updated support tools in this file to manage networks and troubleshoot problems. Support.cab is not automatically loaded when you install SP1.

Download Center

You can update multiple servers by downloading SP1 installation files from the Microsoft Download Center. You can download installation files for 32-bit versions or Itanium-based versions of Windows Server 2003.

Because downloading SP1 installation files takes a substantial amount of time, we recommend that you save the file on your computer. This way, if you must restart the installation or reinstall SP1, you will not need to download the file again. Because the installation file is very large, if your computer has more than one hard disk, you should save the file on a disk other than your system disk.

Planning Your Deployment

To ensure a successful deployment, you should review the information presented in Before You Deploy SP1.

After you have reviewed this information, you must complete the following set of planning tasks:

  • Choose an installation method.

  • Remove all prerelease versions of SP1 from your servers.

  • Determine whether you want to disable antivirus software during installations from the CD.

  • Identify the deployment tools and files.

  • Determine update and upgrade options.

  • Check space requirements.

  • Test and troubleshoot the deployment in your environment.

  • Review the post-installation information near the end of this guide.

For detailed information about deployment-planning tasks and strategies, see the Windows Server 2003 Deployment Guide (on the Microsoft TechCenter Web site). This information can help you get started, including describing how to create a deployment plan and how to run a pilot project.

Choosing an installation method

You can either:

  • Deploy SP1 on a network to multiple servers that are already running Windows Server 2003. (Standalone Installation)

  • Integrate a Windows Server 2003 operating system with SP1, and then install the operating system and SP1 together on multiple servers using one procedure. This type of installation is also known as "slipstreaming." You can either install an integrated version on a server that does not have an operating system, or you can use the integrated version to upgrade computers that are running previous versions of Windows to Windows Server 2003 with SP1 (following the same path you would use to upgrade those computers to Windows Server 2003).

  • Follow the instructions in the Windows Server 2003 Service Pack 1 Installing and Deploying Updates (on the Microsoft TechCenter Web site) to combine SP1 with an installation of Windows Server 2003, with other updates, or with both the operating system and other updates, and then install them together using one procedure.

You can perform a standalone or integrated installation from a shared distribution folder on a network. Even if you decide to do this, we recommend storing SP1 source files locally.

If you want to save disk space, you can extract the files from the service pack installation file. With this method, Windows accesses the distribution folder whenever it requires a service pack file, such as when Windows File Protection must restore a corrupted file or when an optional component is being configured. This step saves disk space on local computers because, if source files for the service pack are required, the installation will point to the distribution folder for the folder called ServicePackFiles instead of creating this folder locally.

ImportantImportant
Because the service pack source files are stored remotely on the network, this installation method is suitable only for computers that are permanently connected to the network. For example, this method is not suitable for updating laptop computers.

You must use a shared distribution folder that was created specifically for SP1. Do not reuse a folder that was set up for a previous service pack. Shared distribution folders for service pack source files must be permanent to ensure that all of the files that a computer might need to replace are available.

For more information about moving the shared distribution folder, see article 271484, "Files and Folders Are Added to Your System After Service Pack Is Installed," in the Microsoft Knowledge Base.

Removing prerelease versions of SP1

Unless you have a supplemental support agreement with Microsoft, you must uninstall any prerelease versions of SP1 before you proceed. Microsoft does not support installing this version over the release candidate or beta versions of SP1.

Antivirus software and installing the service pack

ImportantImportant
Antivirus software is a critical part of keeping a computer secure. But the time that it takes for the software to scan files on your system can add significantly to the time required to install the service pack: as much as an hour or more on slower systems. Disabling your antivirus software before you install the service pack eliminates this extra installation time. If you disable your antivirus software before you install the service pack, be sure that you understand the risks involved, and be sure to enable the antivirus software after you install the service pack.

Checking space requirements

Check the system requirements for installing SP1 in the article 892807, "Hard Disk Space Requirements for Windows Server 2003 Service Pack 1" in the Microsoft Knowledge Base.

Overview of the deployment tools and files

After you select your installation method, review the corresponding scenario in The Standalone Installation or The Integrated Installation later in this guide. This section will help you identify the tools and files that you need for your deployment.

Depending on your environment, you might need one or more of the following deployment tools and files:

  • Microsoft Windows Installer

    Windows Installer is a Windows component that standardizes and simplifies how you install and manage software programs (such as the service pack) on multiple computers. You can use this installation service to manage the installation, modification, repair, and removal of programs. Because Windows Installer facilitates consistency in your deployments, it enables you to manage shared resources, customize installation processes, make decisions about application usage, and resolve configuration problems.

  • The Unattend.txt answer file (for integrated installations only)

    The Unattend.txt answer file identifies how Windows Server 2003 Setup interacts with the distribution folders and files that you create and provides information about your preinstallation requirements. This answer file also supplies Setup with all of the information that you are prompted to provide during a typical Windows Server 2003 installation.

    You can create or modify the Unattend.txt file by using either a text editor or Setup Manager. Make sure that only the system administrator has Write access to this file.

    For more information, see the Unattend.txt topic in the Microsoft Windows Preinstallation Reference Help (Ref.chm) in Deploy.cab in the \Support\Tools folder on your SP1 CD.

  • Microsoft Systems Management Server

    Microsoft Systems Management Server (SMS) provides a variety of tools to help you deploy the service pack in your organization. With SMS 2003, you can automatically update servers in your organization with the new service pack.

    You can allow administrators to run the service pack installation whenever they like, or you can schedule the service pack installation to run at a specific time.

The following resources provide more detailed information about specific deployment tools and files.

  • Windows Server 2003 Deployment Kit (on the Microsoft TechCenter Web site).

  • Article 892778, "Updated System Preparation tool for Windows Server 2003 Service Pack 1," in the Microsoft Knowledge Base.

  • The Microsoft Windows Corporate Deployment Tools User's Guide (Deploy.chm) and the Microsoft Windows Preinstallation Reference Help (Ref.chm) in Deploy.cab in the \Support\Tools folder on your CD.

  • The Windows Support Tools Help (Suptools.chm) in Support.cab in the \Support\Tools folder on your CD. This Help file describes the support tools and gives examples of how to use them.

  • The Release Notes (Readme.htm) for Windows Support Tools for Microsoft Windows Server 2003, which is located in the \Support\Tools folder on your CD.

  • Article 892777, “Windows Server 2003 Service Pack 1 Support Tools,” in the Microsoft Knowledge Base.

Testing the deployment in your computing environment

Although Microsoft has a high degree of confidence in SP1, it is not possible to test all hardware configurations and applications that might be present in all environments where you might install SP1.

We therefore recommend that you test the service pack in your computing environment before you deploy it to all of your servers.

Testing the service pack can include the steps described in following procedure, but might need to include more steps, depending on your environment.

To test the service pack in your environment

  1. Your test environment should include a cross-section of the types of computers on which you want to deploy the service pack. Make sure that the test computers are equipped with the software and the hardware devices that are typically used in your organization.

  2. Install the service pack on each test computer just as you would in the environment where you plan to use the service pack. Make sure that you complete each of the following tasks as appropriate for your environment:

    • Update test computers that are running Windows Server 2003 to Windows Server 2003 with SP1.

    • Upgrade test computers that are running Windows NT Server 4.0 and Windows 2000 Server to Windows Server 2003 with SP1.

    • Install Windows Server 2003 with SP1 onto test computers that have no other operating system installed (that is, perform a "clean installation").

  3. Verify that the software and hardware continue to work as expected for a variety of scenarios.

If you are installing Windows Server 2003 for the first time in your organization, you might want to set up a pilot group to test your deployment and verify whether it works in your environment as expected.

The Standalone Installation

During the standalone installation, the service pack is installed on a computer that is already running Windows Server 2003. When you run the Update.exe program to install SP1, it installs the updated system files and makes the necessary registry changes. After the computer is restarted and the post-boot processes have completed, the installation is complete, and the operating system runs with an updated file set.

This section describes four scenarios for installing the service pack.

  • Scenario 1: Installing the service pack so that computers use local source files for the service pack (recommended)

  • Scenario 2: Installing the service pack so that computers share remote source files for the service pack

  • Scenario 3: Using Systems Management Server (SMS) to install the service pack

  • Scenario 4: Using Windows Installer and Group Policy to install the service pack

ImportantImportant
If a system file on a computer becomes corrupted or must be replaced for some other reason, you must have the source files for that service pack to replace that system file.

You can distribute the service pack through several types of media, including CD-ROMs, shared folders on networks, and Web downloads. Because this guide is intended for corporate audiences, it focuses on using shared distribution folders on networks, which is the most common distribution medium for this audience.

Svcpack.log file creation

When you run a standalone installation, the Update.exe program creates a log file named Svcpack.log in systemroot. This log file contains the following information:

  • The command line that initiated the Update.exe program.

  • A list of the files that the Update.exe program copied to your computer.

  • Error messages if any errors were encountered.

  • The command-line options that were used to install the service pack.

Scenario 1: Installing the service pack so that computers use local source files for the service pack (recommended)

By using this method, you can set up a shared distribution folder on a network for the service pack installation file. (The 32-bit version of this file is called WindowsServer2003-KB889101-SP1-x86-LLL.exe.) If you set up a shared distribution method, you can run the service pack installation from a central location and then store source files for the service pack locally.

To install SP1 from a shared folder, copy the service pack installation file to the folder from which you want to install SP1. You can download the SP1 installation file from the Microsoft Download Center, or you can copy it from the SP1 CD:

  • WindowsServer2003-KB889101-SP1-x86-LLL.exe.

  • WindowsServer2003-KB889101-SP1-ia64-LLL.exe.

When you run WindowsServer2003-KB889101-SP1-x86-LLL.exe, the updated system files are extracted to the local machine. By default, Update.exe then automatically installs the updated system files and makes the necessary changes in the registry. After the computer is restarted, the installation is complete, and Windows Server 2003 runs with an updated file set.

Unless you have a supplementary support agreement with Microsoft, you must uninstall any prerelease versions of SP1 before you proceed. Microsoft does not support the installation of this version over the release candidate or beta versions of SP1.

noteNote
In the following procedure, Drive: represents the drive letter of the network or computer where your distribution folder is located.

To update servers by installing SP1 from a shared folder so that computers use local source files for the service pack (recommended)

  1. Connect to the network or computer on which you want to create the distribution folder.

  2. In the shared folder on the network, create a distribution folder for the service pack.

    For example:

    To install SP1 for a Windows Server 2003 operating system, create a distribution folder named WS2003SP1 by typing the following:

    mkdir Drive:\WS2003SP1

    (In the example, Drive: represents the drive where you want to place the distribution folder.)

  3. Copy WindowsServer2003-KB889101-SP1-x86-LLL.exe from the SP1 CD or download it from the Microsoft Download Center into the distribution folder.

  4. To verify that you have assigned appropriate permissions to users who are installing the service pack, do the following:

    1. Navigate to the appropriate folder, right-click it, and then click Properties.

    2. Click the Sharing tab, and then click Share This Folder.

    3. In Share Name, type a name for the folder.

    4. Click Permissions, and then assign permissions that allow users to install the service pack from this folder.

    5. If you are using an NTFS file system partition, click the Security tab, confirm that the permissions listed there do not conflict with those on the Sharing tab, and then click OK.

  5. To install the service pack from the distribution folder (in this example, the folder is named WS2003SP1), at the command prompt, type the following:

    \\ServerName\WS2003SP1\WindowsServer2003-KB889101-SP1-x86-LLL.exe

    You can include command-line options as needed. For example, if you want to install updates immediately after you install SP1, specify the /Z option in the installation command. This option prevents your computer from restarting automatically after SP1 is installed.

  6. Follow the instructions in the Setup Wizard.

  7. After the installation is complete, do one of the following:

    • If you do not want to install additional updates right after the service pack installation, restart the computer immediately.

    • If you want to install additional updates, install them before you restart your computer. If you use this approach, SP1 and the updates will become fully operational at the same time.

  8. After you restart the computer, restart the antivirus software if you disabled it.

ImportantImportant
SP1 will not be fully operational until you restart your computer.

# Scenario 2: Installing the service pack so that computers share remote source files for the service pack

Use this method to set up a shared distribution folder on a network, and then install the service pack from the shared folder onto computers that are already running Windows Server 2003.

With this method, source files for the service pack are stored in the shared distribution folder rather than on local computers.

ImportantImportant
Because the source files for the service pack are stored remotely on the network, this method is suitable only for computers that are permanently connected to the network. For example, this method is not suitable for updating laptop computers.

You must use a shared distribution folder that was created specifically for SP1. Do not reuse a folder that was set up for a previous service pack. Shared distribution folders for service pack source files must be permanent to ensure that all of the files that a computer might need to replace are available.

If you want the installation to use source files from the distribution folder, you must first extract them from the installation file. This method saves disk space on local computers because, if source files for the service pack are required, the installation will point to the distribution folder for the folder called ServicePackFiles instead of creating this folder locally. The ServicePackFiles folder is needed whenever the operating system requires a service pack file, such as when Windows File Protection must restore a corrupted file, or when an optional component is being configured.

For more information about moving the shared distribution folder, see article 271484, "Files and Folders Are Added to Your System After Service Pack Is Installed," in the Microsoft Knowledge Base.

noteNote
In the following procedure, Drive: represents the drive letter of the network or computer where your distribution folder is located.

To install the service pack so that computers share remote source files for the service pack

  1. Connect to the network or computer on which you want to create the distribution folder.

  2. In the shared folder on the network, create a distribution folder for the service pack. For example, to create a distribution folder named WS2003SP1, type the following at the command prompt:

    mkdir Drive:\WS2003SP1

  3. To extract files to the shared distribution folder, type the following at the command prompt:

    WindowsServer2003-KB889101-SP1-x86-LLL.exe /X:Path

    where Path is the location of the shared distribution folder.

    If you use /U (for unattended), no confirmation dialog box appears after the files have been extracted.

  4. For each computer that you plan to update, back up the files and close programs before you continue (unless you plan to force programs to close during the installation).

  5. To install the service pack from the shared distribution folder, run Update.exe instead of the installation file (for example, WindowsServer2003-KB889101-SP1-x86-LLL.exe). For example, to install the service pack from a distribution folder named WS2003SP1, type the following at the command prompt:

    Drive:\WS2003SP1\i386\Update\Update.exe.

    You can use the same command-line options for Update.exe as you would for the installation file.

  6. The installation continues as described in Scenario 1 earlier in this section.

We recommend that you restart the computer immediately to complete the installation after Update.exe has completed.

If you want to install updates, critical updates, or security updates, see the Guide for Installing and Deploying Updates for Microsoft Windows Server 2003 Service Pack 1 (on the Microsoft TechCenter Web site).

If you disabled your antivirus software, enable it again after you restart the computer.

ImportantImportant
SP1 will not be fully installed until you restart your computer.

# Scenario 3: Using SMS to install the service pack

This scenario explains how to use Microsoft Systems Management Server (SMS) to install the service pack from a shared distribution folder on a network. This installation method installs the service pack on SMS servers that are already running Windows Server 2003.

This scenario assumes that you have an understanding of SMS and a working knowledge of software distribution.

ImportantImportant
To perform this type of installation, your computer must be running SMS 2.0 with Service Pack 5, SMS 2003, or SMS 2003 with Service Pack 1.

To use SMS to install the service pack

  1. Create the SMS package by importing the package definition file for the service pack. In the package, provide the path to the source files for the service pack.

  2. Distribute the SMS package to the distribution points.

  3. Create the advertisement to notify SMS servers that the service pack is available.

For details about deploying SP1 using SMS, see article 894712, "How to install Windows Server 2003 Service Pack 1 (SP1) by using Systems Management Server," in the Microsoft Knowledge Base.

# Scenario 4: Using Windows Installer and Group Policy to install the service pack

This scenario explains how to use Windows Installer to install the service pack from a shared distribution folder on a network. This method installs the service pack on servers that are already running Windows Server 2003.

To use this method, you should have a thorough understanding of Windows Installer and a working knowledge of Group Policy and Active Directory. For more information about Windows Installer, Group Policy, and Active Directory, see the Windows Server 2003 Deployment Guide (on the Microsoft TechCenter Web site).

# Using Windows Installer

The Windows Installer package file (Update.msi) contains all of the information that Windows Installer requires to install or remove the service pack and to run Setup.

This package file describes the relationships between service pack components and resources. It also contains an installation database from which you can view a summary (known as a summary information stream) of the properties that the installation program uses. To view this summary, right-click the installation database, and then click Properties.

You must use the machine-assigned distribution method with Update.msi. No other methods are available.

ImportantImportant
We recommend that you use the installation file WindowsServer2003-KB889101-SP1-x86-LLL.exe or WindowsServer2003-KB889101-SP1-ia64-LLL.exe when deploying SP1 at the command prompt. (LLL represents the language code; for example, ENU represents English). If you use Update.msi to distribute service packs, you must use a server-based (machine-assigned) Group Policy object (GPO) only. User-based Group Policy deployments are not supported with Update.msi. For more information, see article 278503, "Best Practices for Using Update.msi to Deploy Service Packs," in the Microsoft Knowledge Base.

To upgrade servers to SP1, you must join them to the same domain as the server where the Windows Installer (MSI) file resides. After you assign the package, Windows Installer automatically installs the service pack the next time that the server is started (as long as it is connected to the network).

noteNote
Only a network administrator or someone who is logged on to a local server as an administrator can remove the assigned software.

# Assigning Service Pack 1 to Servers

The procedure in this section explains how to assign the service pack to servers that are managed by a GPO. For your installation, you might want to associate the GPO with a new Active Directory container.

To use Group Policy to assign the service pack

  1. Create a shared network distribution folder.

  2. Create a GPO for SP1 deployments.

  3. Deploy the SP1 Update.msi from the shared distribution folder as machine-assigned. Do not deploy it as a user deployment.

    When the servers are restarted, they are updated to SP1.

    ImportantImportant
    Check the properties of each server to ensure that the update has completed. You might need to restart each server more than once to complete the update.

    For general information about how to apply your software deployment policy to users who are outside the boundaries of organization units, see article 324750 "How To Assign Software to a Specific Group By Using a Group Policy in the Windows Server 2003 Family," in the Microsoft Knowledge Base.

The Integrated Installation

You should perform the integrated installation of Windows Server 2003 with SP1 on computers that do not have an operating system or that are running an earlier version of Windows, such as Windows 2000. You would use this method if you already purchased Windows Server 2003 and want to apply the service pack and the operating system at the same time.

When you perform an integrated installation, you install the operating system and the service pack simultaneously. This means that you do not need to perform separate installations of the operating system and the service pack.

To perform an integrated installation, first use the /integrate option to update Windows Server 2003 with SP1 installation files in a shared distribution folder. After you do this, run Windows Server 2003 Setup. During the integrated installation process, Windows Server 2003 Setup installs the operating system with the service pack already applied.

The path that you use to upgrade previous versions of Windows to Windows Server 2003 with SP1 is the same path you would use to upgrade to Windows Server 2003.

To complete the procedure for integrating Windows Server 2003 with SP1, you must use a computer that is already running a Windows Server 2003 or Windows XP operating system.

noteNote
In the following procedure, Drive: represents the drive letter of the network or computer where your distribution folder is located.

Spslpsrm.log file creation

The Update.exe program creates a log file, named Spslpsrm.log, for integrated installations. This log file is created in systemroot and contains the following information:

  • The command line that initiated the Update.exe program.

  • A list of the files that the Update.exe program copied to your computer.

  • Error messages if any errors were encountered.

  • The command-line options that were used to install the service pack.

Scenario 1: To create an integrated installation of the service pack with Windows Server 2003

  1. Connect to the network or computer on which you want to create the distribution folder.

  2. In the shared folder on the network, create a distribution folder for the Windows Server 2003 installation files.

    For example:

    • To install SP1 with a 32-bit version of Windows Server 2003, create a distribution folder named WS2003\x86 by typing the following:

      mkdir Drive:\WS2003\x86

    • To install SP1 with a 64-bit version of Windows Server 2003, create a distribution folder named WS2003\64bit by typing the following:

      mkdir Drive:\WS2003\64bit

      ImportantImportant
      Ensure that only system administrators have full access to this folder. Other users should have only Read and Execute permissions.

  3. To verify that you have assigned appropriate permissions to users who are installing the service pack, do the following:

    1. Navigate to the appropriate folder, right-click it, and then click Properties.

    2. Click the Sharing tab, and then click Share This Folder.

    3. In Share Name, type a name for the folder.

    4. Click Permissions, and then assign permissions that allow users to install the service pack from this folder.

    5. If you are using an NTFS file system partition, click the Security tab, confirm that the permissions listed there do not conflict with those on the Sharing tab, and then click OK.

  4. Insert your Windows Server 2003 product CD or DVD into the CD-ROM drive, and then copy the contents of the CD to the distribution folder that you created in step 2.

    For example, to copy the installation files and folders from the Windows Server 2003 product CD in the CD-ROM drive (D:) to the distribution folder named WS2003\x86 on the E: drive, you would type the following:

    xcopy /E D:\ E:\WS2003\x86

  5. Remove the product media from the CD-ROM drive, and then insert the SP1 CD. Be sure to use the correct SP1 CD (for either 32-bit or Itanium-based versions of Windows Server 2003).

  6. Do one of the following:

    • To apply the source files for the service pack to the installation files for a 32-bit version of Windows Server 2003 in the folder named WS2003\x86, type the following:

      WindowsServer2003-KB889101-SP1-x86-LLL.exe /integrate:Drive:\WS2003\x86

    • To apply the source files for the service pack to the installation files for an Itanium-based version of Windows Server 2003 in the folder named WS2003\64bit, type the following:

      WindowsServer2003-KB889101-SP1-ia64-LLL.exe /integrate:Drive:\WS2003\64bit

    For a list of additional command-line options, see Command-Line Options for Installing SP1.

  7. Service pack files are extracted and then applied to the operating system files to update your shared distribution folder. You can either use the files from this network shared folder to make a CD (32-bit versions only) to upgrade your servers, or you can customize Setup for Windows Server 2003 as necessary. For more information about how to customize Setup, you can view Help by entering the following command from the shared distribution folder:

    \i386\winnt32.exe /?

  8. You can now deploy Windows Server 2003 with SP1 to your computers from the shared distribution folder in either attended or unattended Setup mode. During the standard installation process, Setup for Windows Server 2003 (Winnt.exe or Winnt32.exe) installs the updated operating system with the service pack already applied.

ImportantImportant
When you run the command given in Step 6, the Update.exe program automatically creates a Svcpack.log file in systemroot on the computer that is running the Update.exe program. If you plan to update more than one operating system from this computer, rename the Svcpack.log file after you update each version. This step ensures that you do not overwrite the current log file when you update additional operating systems.

Scenario 2: Using RIS to install Windows Server 2003 integrated with the service pack

This section explains how to use Remote Installation Services (RIS) to install Windows Server 2003 operating systems integrated with the service pack. However, this section does not explain how to set up RIS. For more information about RIS, see Remote Installation Services (on the Microsoft TechCenter Web site).

Types of RIS images

RIS supports two types of operating system images: CD-based images (images created by using RISetup) and Remote Installation Preparation (RIPrep) images.

Using the CD-based option is similar to setting up a server operating system directly from the Windows Server 2003 product CD, except that the source files reside on a RIS server. You can create a RIPrep image from a server that is running Windows Server 2003 with SP1 and that is configured with applications and settings that you specify. You can then deploy this image to other similar servers connected to the network.

Adding a CD-based image for an operating system that is integrated with a service pack to a RIS server

After you install RIS, perform the following steps to add an image of Windows Server 2003 with SP1 to your RIS server.

To copy Windows Server 2003 with SP1 to your RIS server

  1. Create an integrated installation of Windows Server 2003 with SP1. For more information, see Scenario 1: Creating an installation of Windows Server 2003 integrated with the service pack earlier in this guide.

  2. To create an image, click Start, click Run, and then type the following:

    risetup.exe -add

  3. The Remote Installation Services Setup Wizard appears. Follow the instructions in the wizard. When the Installation Source Files Location page prompts you for the image source, enter the path to the shared folder that contains the integrated installation that you created in Step 1.

  4. A box appears showing the progress of the installation. After the RISetup image is complete, you can install the image on each server as described in Remote Installation Services (on the Microsoft TechCenter Web site).

Updating existing RIPrep images to SP1

If you want to add additional programs or settings to your integrated installation image, you must have a CD–based image of Windows Server 2003 with SP1 on your RIS server. (For more information, see the preceding section, Adding a CD-based image for an operating system that is integrated with a service pack to a RIS server.)

To update existing RIPrep images

  1. Use RIS to install the RISetup image on your computer.

  2. Add the additional programs and settings that you want to include in the image.

  3. Run RIPrep to create an image on the RIS server.

    For instructions on how to run RIPrep on RIS servers running Windows Server 2003, see Remote Installation Services and Automating and Customizing Installations (on the Microsoft TechCenter Web site).

  4. You can now deploy your RIPrep image to other servers. For details about how to perform this task, see Remote Installation Services (on the Microsoft TechCenter Web site).

noteNote
You cannot use the /integrate option to integrate SP1 directly into an existing CD-based image or a RIPrep image.

Command-Line Options for Installing SP1

You can define the way SP1 is installed by typing one or more of the following command-line options when you run the installation file (for example, WindowsServer2003-KB889101-SP1-x86-LLL.exe) or Update.exe. You can precede the options with either a forward slash (/) or a hyphen (-). The options are not case-sensitive.

 

Command-line option Description

/?

or

/Help

Displays help text.

/D: FolderName

Back up to a specified folder the files that are required to remove the service pack.

If you back up files but do not specify a folder, the default location is:

$ntservicepackuninstall$

Any location that you specify must be on the local drive.

/ER

Enables extended return codes that return a detailed error message if the update installation fails. For more information, see the white paper, The Package Installer (Formerly Called Update.exe) for Microsoft Windows Operating Systems and Windows Components, on the Microsoft Web site.

/F

After the installation is complete, you must close all open applications before you restart the computer. This option forces applications to close without saving files. You can use this option with other command-line options, except /integrate, /L, and /Z.

/Forcerestart

Restarts the computer after the update installation is complete. This option follows standard shutdown behavior. It does not force applications to close.

/integrate: Path

Integrates this software update into the path that you specify. Be sure to provide the absolute path to the installation files for your operating system.

/L

Lists installed updates.

/N

We do not recommend this option.

Does not back up files for removing SP1. An entry for SP1 does not appear in Add or Remove Programs if you use this option.

/O

Overwrites OEM files without prompting.

/Q

or

/Quiet

Uses quiet mode. Shows no user interface during SP1 installation. This is the same as unattended mode, except that the user interface is hidden. No prompts will appear during the installation process.

/U

or

/Passive

Uses unattended Setup mode and default SP1 options. Requires no user interaction during the installation of the updates and shows only critical errors and a progress bar.

/Z

or

/Norestart

Does not restart the computer after the installation is completed.

Command-Line Options for Installing the Service Pack Only

The following table identifies additional command-line options that only the installation program for the service pack supports.

 

Command-line option Description

/X

Extracts service pack files without starting Update.exe. You are prompted to provide the path for the folder in which you want the extracted service pack installation files to be placed.

/U /X: FolderName

Extracts service pack files and places them in the FolderName folder without prompting and without starting Update.exe.

ImportantImportant
SP1 will not be fully functional until you restart your computer.

Qfecheck.exe

For more information about the Qfecheck.exe program, see the following articles in the Microsoft Knowledge Base:

  • 282784: "Qfecheck.exe Verifies the Installation of Windows 2000 and Windows XP Updates"

  • 304864: "Qfecheck Hotfix Tool Reports False Need to Reinstall Freshly Installed Updates"

Although these articles were written for other Windows operating systems, they also apply to updates for Windows Server 2003.

Uninstalling SP1

If you created backup files when you installed SP1, you can use Add or Remove Programs or the command prompt to remove SP1 at any time and restore your computer to its previous state.

You can uninstall SP1 only if it was installed as an update to an existing operating system. You cannot remove SP1 if you installed it as part of an integrated installation. In this case, you must uninstall the entire operating system together with SP1.

To remove SP1 using a command prompt

  1. Open a command prompt and type:

    %systemroot%\$NtServicePackUninstall$\spuninst\

  2. Type Spuninst.exe /Option. Replace Option with any of the options in the following table.

  3. Press ENTER to continue, and then follow the instructions that appear on your screen.

 

Option Description

/U

Removes the service pack in unattended mode. If you use this option, only critical error prompts appear while you uninstall SP1.

/Q

Removes SP1 in quiet mode, which is the same as unattended mode except that the user interface is hidden. If you use this option, no prompts appear while you uninstall SP1.

/Z

Does not restart the computer after you uninstall SP1.

/F

Forces other applications to close when the computer restarts after you uninstall SP1.

ImportantImportant
If you choose to remove SP1, a dialog box displays a list of the applications that you installed after you installed SP1. If you continue to remove SP1, these applications might not work correctly.

Multiple descriptions of some applications might appear instead of a single generic description. You should ignore these additional descriptions.

Symbols for Debugging Service Packs

If you are a system administrator (someone who diagnoses problems on computers that are running Windows Server 2003), we recommend that you download the symbol files for debugging service packs. However, you do not need to install these files for your computer to run properly.

If you want to debug Windows Server 2003 with SP1, you must first download and install the symbols for debugging Windows Server 2003 from the download page on the Internet, and then you must add symbols for debugging SP1 to the same folder. For more information, see Debugging Tools for Windows — Overview at the Microsoft Web site.

You can download symbols for debugging SP1 from one of the following locations:

  • From the Download Windows Symbol Packages page on the Microsoft Web site.

  • On demand from the Internet Symbol Server. For more information about using the Internet Symbol Server, see Debugging Tools and Symbols: Getting Started on the Microsoft Web site.

  • The English version of the Windows Server 2003 Service Pack 1 CD, which includes the symbols package. The package (Symbols.exe) is in the \Support\Symbols folder on the service pack CD. The symbols package is included only on the English version of the service pack CD, but this package is language-independent and can be downloaded for debugging any Windows Server 2003 locale.

noteNote
When you install SP1, the current versions of the symbol files overwrite any previous versions that are in the symbol installation folder.

Additional Resources

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft