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
TheStandaloneInstallation
TheIntegrated Installation
Command-Line Options for Installing SP1
Uninstalling SP1
Symbols for Debugging Service Packs
Additional Resources
Introduction to Service Pack 1 (SP1)
This guideexplains how you can:
Deploy Microsoft® Windows Server™ 2003 Service Pack 1 (SP1) to multiple computers thatarealready running
the Windows Server 2003 operating systems. If you have only oneserver to update,you can seethe Readmefor
Windows Server 2003 Service Pack 1 (on the MicrosoftTechCenter Web site) instead.
Integrate SP1 with Windows Server 2003 for deploying to multiplecomputers running an earlier version of
Windows® or with no operating system installed.
Uninstall SP1 from computers.
This guide does notexplain:
How to combine SP1 with other updates for Windows Server 2003.For information about how to do this, see
Microsoft Windows Server 2003 Service Pack 1 Installing and Deploying Updates (on the MicrosoftTechCenter Web
site).
New SP1 functionality.For important information about functional changes to SP1 thatyou should understand before
you deploy SP1, review theinformation thatapplies to your setup on the MicrosoftTechCenter Web site.
Note
You cannot install SP1 on any x64-based versions of Windows Server 2003.For moreinformation about theseversions, 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
Beforeyou deploy SP1,you should review theinformation about theservice pack on the MicrosoftTechCenter Web siteso 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 troubleshootyour SP1 deployment.
Read other essential installation information,and check minimum hard disk requirements in the Readmefor Windows
Server 2003 Service Pack 1 (on the MicrosoftTechCenter Web site).
List of updates
For information about updates and fixes included in SP1, seearticle 824721, “Windows Server 2003 Service Pack 1 List of
Updates,” in the Microsoft Knowledge Base.
Release notes
Beforeyou install SP1, seearticle 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 multiplecomputers from either theSP1 CD or the Microsoft Download
Center.
For 32-bitversions of Windows Server 2003 (which run on x86-based computers), theSP1 installation fileis named
WindowsServer2003-KB889101-SP1-x86-LLL.exe, whereLLL is thelanguageversion ofSP1.For example,ENU represents the
English-languageversion.
For Itanium-based versions of Windows Server 2003, theSP1 installation fileis named WindowsServer2003-KB889101-SP1-
ia64-LLL.exe.
You can updateItanium-based versions with SP1 for only English, German, Japanese,and French locales.
Theinstructions and examples throughout this document usethe name of theinstallation filefor 32-bitversions (unless a
particular difference between 32-bitand Itanium-based installations must becalled out).
Contents of the SP1 CDs
For each languageversion, two CDs areavailableto update Windows Server 2003 operating systems with SP1: onefor 32-bit
versions of Windows Server 2003 and onefor Itanium-based versions.The CD for Itanium-based versions is labeled as such.
Each SP1 CD contains thefollowing files:
A service pack installation file
The Deploy.cab file.This is a compressed filethat contains a collection of tools and accompanying online Help. (See
Deploy.chm and Ref.chm when you expand Deploy.cab.) It is located on theSP1 CD in the\Support\Tools folder.
Deploy.cab is notautomatically loaded when you install SP1.
TheSupport.cab file.This is a compressed filethatalso contains a collection of tools and online Help. It is located in the
\Support\Tools folder.Technical support personnel and network administrators can usethe updated support tools in this
fileto manage networks and troubleshoot problems.Support.cab is notautomatically loaded when you install SP1.
Download Center
You can update multipleservers by downloading SP1 installation files from the Microsoft Download Center. You can download
installation files for 32-bitversions or Itanium-based versions of Windows Server 2003.
Because downloading SP1 installation files takes a substantial amount of time, werecommend thatyou savethefile on your
computer.This way, if you must restart theinstallation or reinstall SP1,you will not need to download thefileagain. Because
theinstallation fileis very large, if your computer has morethan one hard disk,you should savethefile on a disk other than
your system disk.
Planning Your Deployment
To ensurea successful deployment,you should review theinformation presented in Before You Deploy SP1.
After you havereviewed this information,you must completethefollowing set of planning tasks:
Choosean installation method.
Removeall prereleaseversions ofSP1 from your servers.
Determine whether you want to disableantivirus software during installations from the CD.
Identify the deployment tools and files.
Determine updateand upgrade options.
Check spacerequirements.
Testand troubleshoot the deployment in your environment.
Review the post-installation information near theend of this guide.
For detailed information about deployment-planning tasks and strategies, seethe Windows Server 2003 Deployment Guide
(on the MicrosoftTechCenter Web site).This information can help you get started, including describing how to createa
deployment plan and how to run a pilot project.
Choosing an installation method
You can either:
Deploy SP1 on a network to multipleservers thatarealready running Windows Server 2003. (StandaloneInstallation)
Integratea Windows Server 2003 operating system with SP1,and then install the operating system and SP1 together on
multipleservers 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 havean operating system, or you can usetheintegrated version to upgrade
computers thatarerunning previous versions of Windows to Windows Server 2003 with SP1 (following thesame path
you would useto upgradethosecomputers to Windows Server 2003).
Follow theinstructions in the Windows Server 2003 Service Pack 1 Installing and Deploying Updates (on the Microsoft
TechCenter Web site) to combineSP1 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 decideto
do this, werecommend storing SP1 sourcefiles locally.
If you want to save disk space,you can extract thefiles from theservice 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 restorea
corrupted file or when an optional component is being configured.This step saves disk space on local computers because, if
sourcefiles for theservice pack arerequired, theinstallation will point to the distribution folder for thefolder called
ServicePackFiles instead of creating this folder locally.
Important
Becausetheservice pack sourcefiles arestored remotely on the network, this installation method is suitable only for
computers thatare permanently connected to the network.For example, this method is not suitablefor updating laptop
computers.
You must usea shared distribution folder that was created specifically for SP1. Do not reusea folder that was set up for a
previous service pack.Shared distribution folders for service pack sourcefiles must be permanent to ensurethatall of the
files thata computer might need to replaceareavailable.
For moreinformation about moving theshared distribution folder, seearticle 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 havea supplemental supportagreement with Microsoft,you must uninstall any prereleaseversions ofSP1 before
you proceed. Microsoft does not support installing this version over thereleasecandidate or beta versions ofSP1.
Antivirus software and installing the service pack
Important
Antivirus softwareis a critical part of keeping a computer secure. But thetimethat it takes for thesoftwareto scan files on
your system can add significantly to thetimerequired to install theservice pack:as much as an hour or more on slower
systems. Disabling your antivirus software beforeyou install theservice pack eliminates this extra installation time. If you
disableyour antivirus software beforeyou install theservice pack, besurethatyou understand therisks involved,and be
sureto enabletheantivirus softwareafter you install theservice pack.
Checking space requirements
Check thesystem requirements for installing SP1 in thearticle 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 selectyour installation method, review thecorresponding scenario in TheStandaloneInstallation or TheIntegrated
Installation later in this guide.This section will help you identify thetools and files thatyou need for your deployment.
Depending on your environment,you might need one or more of thefollowing deployment tools and files:
Microsoft Windows Installer
Windows Installer is a Windows component that standardizes and simplifies how you install and managesoftware
programs (such as theservice pack) on multiplecomputers. You can usethis installation serviceto managethe
installation, modification, repair,and removal of programs. Because Windows Installer facilitates consistency in your
deployments, itenables you to manageshared resources,customizeinstallation processes, make decisions about
application usage,and resolveconfiguration problems.
The Unattend.txt answer file (for integrated installations only)
The Unattend.txtanswer fileidentifies how Windows Server 2003 Setup interacts with the distribution folders and files
thatyou createand provides information aboutyour preinstallation requirements.This answer filealso supplies Setup
with all of theinformation thatyou are prompted to provide during a typical Windows Server 2003 installation.
You can create or modify the Unattend.txt file by using either a texteditor or Setup Manager. Makesurethat only the
system administrator has Writeaccess to this file.
For moreinformation, seethe 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
MicrosoftSystems ManagementServer (SMS) provides a variety of tools to help you deploy theservice pack in your
organization.With SMS 2003,you can automatically updateservers in your organization with the new service pack.
You can allow administrators to run theservice pack installation whenever they like, or you can scheduletheservice pack
installation to run ata specific time.
Thefollowing resources provide more detailed information about specific deployment tools and files.
Windows Server 2003 Deployment Kit (on the MicrosoftTechCenter Web site).
Article 892778, “Updated System Preparation tool for Windows Server 2003 Service Pack 1,” in the Microsoft Knowledge
Base.
The Microsoft Windows Corporate DeploymentTools 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 SupportTools Help (Suptools.chm) in Support.cab in the\Support\Tools folder on your CD.This Help file
describes thesupport tools and gives examples of how to usethem.
The Release Notes (Readme.htm) for Windows SupportTools for Microsoft Windows Server 2003, which is located in the
\Support\Tools folder on your CD.
Article 892777, “Windows Server 2003 Service Pack 1 SupportTools,” in the Microsoft Knowledge Base.
Testing the deployment in your computing environment
Although Microsoft has a high degree of confidencein SP1, it is not possibleto testall hardwareconfigurations and
applications that might be present in all environments whereyou might install SP1.
Wethereforerecommend thatyou test theservice pack in your computing environment beforeyou deploy it to all of your
servers.
Testing theservice pack can includethesteps described in following procedure, but might need to include moresteps,
depending on your environment.
To test the service pack in your environment
1. Your testenvironment should includea cross-section of thetypes of computers on which you want to deploy theservice
pack. Makesurethat thetest computers areequipped with thesoftwareand the hardware devices thataretypically used
in your organization.
2. Install theservice pack on each test computer justas you would in theenvironment whereyou plan to usetheservice
pack. Makesurethatyou completeeach of thefollowing tasks as appropriatefor your environment:
Updatetest computers thatarerunning Windows Server 2003 to Windows Server 2003 with SP1.
Upgradetest computers thatarerunning Windows NTServer 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 thesoftwareand hardwarecontinueto work as expected for a variety of scenarios.
If you areinstalling Windows Server 2003 for thefirst timein your organization,you might want to set up a pilot group to test
your deploymentand verify whether it works in your environmentas expected.
The Standalone Installation
During thestandaloneinstallation, theservice 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 thecomputer is restarted and the post-boot processes havecompleted, theinstallation is complete,and the
operating system runs with an updated fileset.
This section describes four scenarios for installing theservice pack.
Scenario 1: Installing theservice pack so that computers uselocal sourcefiles for theservice pack (recommended)
Scenario 2: Installing theservice pack so that computers shareremotesourcefiles for theservice pack
Scenario 3: Using Systems ManagementServer (SMS) to install theservice pack
Scenario 4: Using Windows Installer and Group Policy to install theservice pack
Important
If a system file on a computer becomes corrupted or must bereplaced for some other reason,you must havethesourcefiles
for that service pack to replacethat system file.
You can distributetheservice pack through several types of media, including CD-ROMs, shared folders on networks,and Web
downloads. Becausethis guideis intended for corporateaudiences, 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 standaloneinstallation, the Update.exe program creates a log file named Svcpack.log in systemroot.This log
filecontains thefollowing information:
Thecommand linethat initiated the Update.exe program.
A list of thefiles that the Update.exe program copied to your computer.
Error messages if any errors wereencountered.
Thecommand-line options that were used to install theservice 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 theservice pack installation file. (The 32-bit
version of this fileis called WindowsServer2003-KB889101-SP1-x86-LLL.exe.) If you set up a shared distribution method,you
can run theservice pack installation from a central location and then storesourcefiles for theservice pack locally.
To install SP1 from a shared folder,copy theservice pack installation fileto thefolder from which you want to install SP1. You
can download theSP1 installation filefrom the Microsoft Download Center, or you can copy it from theSP1 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 areextracted to thelocal machine.
By default, Update.exethen automatically installs the updated system files and makes the necessary changes in theregistry.
After thecomputer is restarted, theinstallation is complete,and Windows Server 2003 runs with an updated fileset.
Unless you havea supplementary supportagreement with Microsoft,you must uninstall any prereleaseversions ofSP1 before
you proceed. Microsoft does not support theinstallation of this version over thereleasecandidate or beta versions ofSP1.
Note
In thefollowing procedure, Drive: represents the driveletter of the network or computer whereyour 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 createthe distribution folder.
2. In theshared folder on the network,createa distribution folder for theservice pack.
For example:
To install SP1 for a Windows Server 2003 operating system,createa distribution folder named WS2003SP1 by typing
thefollowing:
mkdir Drive:\WS2003SP1
(In theexample, Drive: represents the drive whereyou want to placethe distribution folder.)
3. Copy WindowsServer2003-KB889101-SP1-x86-LLL.exefrom theSP1 CD or download it from the Microsoft Download
Center into the distribution folder.
4. To verify thatyou haveassigned appropriate permissions to users who areinstalling theservice pack, do thefollowing:
a. Navigateto theappropriatefolder, right-click it,and then click Properties.
b. Click the Sharing tab,and then click Share This Folder.
c. In Share Name, typea namefor thefolder.
d. Click Permissions,and then assign permissions thatallow users to install theservice pack from this folder.
e. If you are using an NTFS filesystem 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 theservice pack from the distribution folder (in this example, thefolder is named WS2003SP1),at the
command prompt, typethefollowing:
\\ServerName\WS2003SP1\WindowsServer2003-KB889101-SP1-x86-LLL.exe
You can includecommand-line options as needed.For example, if you want to install updates immediately after you
install SP1, specify the/Z option in theinstallation command.This option prevents your computer from restarting
automatically after SP1 is installed.
6. Follow theinstructions in theSetup Wizard.
7. After theinstallation is complete, do one of thefollowing:
If you do not want to install additional updates rightafter theservice pack installation, restart thecomputer
immediately.
If you want to install additional updates, install them beforeyou restartyour computer. If you usethis approach,
SP1 and the updates will becomefully operational at thesametime.
8. After you restart thecomputer, restart theantivirus softwareif you disabled it.
Important
SP1 will not befully operational until you restartyour computer.
# Scenario 2: Installing the service pack so that computers share remote source files for the service pack
Usethis method to set up a shared distribution folder on a network,and then install theservice pack from theshared folder
onto computers thatarealready running Windows Server 2003.
With this method, sourcefiles for theservice pack arestored in theshared distribution folder rather than on local computers.
Important
Becausethesourcefiles for theservice pack arestored remotely on the network, this method is suitable only for computers
thatare permanently connected to the network.For example, this method is not suitablefor updating laptop computers.
You must usea shared distribution folder that was created specifically for SP1. Do not reusea folder that was set up for a
previous service pack.Shared distribution folders for service pack sourcefiles must be permanent to ensurethatall of thefiles
thata computer might need to replaceareavailable.
If you want theinstallation to usesourcefiles from the distribution folder,you must firstextract them from theinstallation file.
This method saves disk space on local computers because, if sourcefiles for theservice pack arerequired, theinstallation will
point to the distribution folder for thefolder called ServicePackFiles instead of creating this folder locally.TheServicePackFiles
folder is needed whenever the operating system requires a service pack file, such as when Windows File Protection must
restorea corrupted file, or when an optional component is being configured.
For moreinformation about moving theshared distribution folder, seearticle 271484, “Files and Folders Are Added to Your
System After Service Pack Is Installed,” in the Microsoft Knowledge Base.
Note
In thefollowing procedure, Drive: represents the driveletter of the network or computer whereyour 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 createthe distribution folder.
2. In theshared folder on the network,createa distribution folder for theservice pack.For example, to createa distribution
folder named WS2003SP1, typethefollowing at thecommand prompt:
mkdir Drive:\WS2003SP1
3. To extract files to theshared distribution folder, typethefollowing at thecommand prompt:
WindowsServer2003-KB889101-SP1-x86-LLL.exe /X:Path
where Path is thelocation of theshared distribution folder.
If you use/U (for unattended), no confirmation dialog boxappears after thefiles have been extracted.
4. For each computer thatyou plan to update, back up thefiles and close programs beforeyou continue(unless you plan to
force programs to close during theinstallation).
5. To install theservice pack from theshared distribution folder, run Update.exeinstead of theinstallation file(for example,
WindowsServer2003-KB889101-SP1-x86-LLL.exe).For example, to install theservice pack from a distribution folder
named WS2003SP1, typethefollowing at thecommand prompt:
Drive:\WS2003SP1\i386\Update\Update.exe.
You can usethesamecommand-line options for Update.exeas you would for theinstallation file.
6. Theinstallation continues as described in Scenario 1 earlier in this section.
Werecommend thatyou restart thecomputer immediately to completetheinstallation after Update.exe has completed.
If you want to install updates,critical updates, or security updates, seethe Guidefor Installing and Deploying Updates for
Microsoft Windows Server 2003 Service Pack 1 (on the MicrosoftTechCenter Web site).
If you disabled your antivirus software,enableitagain after you restart thecomputer.
Important
SP1 will not befully installed until you restartyour computer.
# Scenario 3: Using SMS to install the service pack
This scenario explains how to use MicrosoftSystems ManagementServer (SMS) to install theservice pack from a shared
distribution folder on a network.This installation method installs theservice pack on SMS servers thatarealready running
Windows Server 2003.
This scenario assumes thatyou havean understanding ofSMS and a working knowledge of software distribution.
Important
To perform this type of installation,your computer must berunning 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. CreatetheSMS package by importing the package definition filefor theservice pack. In the package, providethe path to
thesourcefiles for theservice pack.
2. DistributetheSMS packageto the distribution points.
3. Createtheadvertisement to notify SMS servers that theservice pack is available.
For details about deploying SP1 using SMS, seearticle 894712, “How to install Windows Server 2003 Service Pack 1 (SP1) by
using Systems ManagementServer,” 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 theservice pack from a shared distribution folder on a network.
This method installs theservice pack on servers thatarealready running Windows Server 2003.
To usethis method,you should havea thorough understanding of Windows Installer and a working knowledge of Group
Policy and Active Directory.For moreinformation about Windows Installer, Group Policy,and Active Directory, seethe
Windows Server 2003 Deployment Guide(on the MicrosoftTechCenter Web site).
# Using Windows Installer
The Windows Installer packagefile(Update.msi) contains all of theinformation that Windows Installer requires to install or
removetheservice pack and to run Setup.
This packagefile describes therelationships between service pack components and resources. Italso contains an installation
databasefrom 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 theinstallation database,and then click Properties.
You must usethe machine-assigned distribution method with Update.msi. No other methods areavailable.
Important
Werecommend thatyou usetheinstallation file WindowsServer2003-KB889101-SP1-x86-LLL.exe or WindowsServer2003-
KB889101-SP1-ia64-LLL.exe when deploying SP1 at thecommand prompt. (LLL represents thelanguagecode; for example,
ENU represents English). If you use Update.msi to distributeservice packs,you must usea server-based (machine-assigned)
Group Policy object (GPO) only. User-based Group Policy deployments are not supported with Update.msi.For more
information, seearticle 278503, “Best Practices for Using Update.msi to Deploy Service Packs,” in the Microsoft Knowledge
Base.
To upgradeservers to SP1,you must join them to thesame domain as theserver wherethe Windows Installer (MSI) file
resides. After you assign the package,Windows Installer automatically installs theservice pack the next timethat theserver is
started (as long as it is connected to the network).
Note
Only a network administrator or someone who is logged on to a local server as an administrator can removetheassigned
software.
# Assigning Service Pack 1 to Servers
The procedurein this section explains how to assign theservice pack to servers thatare managed by a GPO.For your
installation,you might want to associatethe GPO with a new Active Directory container.
To use Group Policy to assign the service pack
1. Createa shared network distribution folder.
2. Createa GPO for SP1 deployments.
3. Deploy theSP1 Update.msi from theshared distribution folder as machine-assigned. Do not deploy itas a user
deployment.
When theservers arerestarted, they are updated to SP1.
Important
Check the properties of each server to ensurethat the update has completed. You might need to restarteach server
morethan onceto completethe update.
For general information about how to apply your software deployment policy to users who are outsidethe boundaries of
organization units, seearticle 324750 “How To Assign Softwareto aSpecific Group By Using a Group Policy in the
Windows Server 2003 Family,” in the Microsoft Knowledge Base.
The Integrated Installation
You should perform theintegrated installation of Windows Server 2003 with SP1 on computers that do not havean operating
system or thatarerunning an earlier version of Windows, such as Windows 2000. You would usethis method if you already
purchased Windows Server 2003 and want to apply theservice pack and the operating system at thesametime.
When you perform an integrated installation,you install the operating system and theservice pack simultaneously.This means
thatyou do not need to perform separateinstallations of the operating system and theservice pack.
To perform an integrated installation, first usethe/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 theintegrated installation
process,Windows Server 2003 Setup installs the operating system with theservice pack already applied.
The path thatyou useto upgrade previous versions of Windows to Windows Server 2003 with SP1 is thesame path you
would useto upgradeto Windows Server 2003.
To completethe procedurefor integrating Windows Server 2003 with SP1,you must usea computer that is already running a
Windows Server 2003 or Windows XP operating system.
Note
In thefollowing procedure, Drive: represents the driveletter of the network or computer whereyour distribution folder is
located.
Spslpsrm.log file creation
The Update.exe program creates a log file, named Spslpsrm.log, for integrated installations.This log fileis created in
systemrootand contains thefollowing information:
Thecommand linethat initiated the Update.exe program.
A list of thefiles that the Update.exe program copied to your computer.
Error messages if any errors wereencountered.
Thecommand-line options that were used to install theservice 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 createthe distribution folder.
2. In theshared folder on the network,createa distribution folder for the Windows Server 2003 installation files.
For example:
To install SP1 with a 32-bitversion of Windows Server 2003,createa distribution folder named WS2003\x86 by
typing thefollowing:
mkdir Drive:\WS2003\x86
To install SP1 with a 64-bitversion of Windows Server 2003,createa distribution folder named WS2003\64bit by
typing thefollowing:
mkdir Drive:\WS2003\64bit
Important
Ensurethat only system administrators havefull access to this folder. Other users should have only Read and
Execute permissions.
3. To verify thatyou haveassigned appropriate permissions to users who areinstalling theservice pack, do thefollowing:
a. Navigateto theappropriatefolder, right-click it,and then click Properties.
b. Click the Sharing tab,and then click Share This Folder.
c. In Share Name, typea namefor thefolder.
d. Click Permissions,and then assign permissions thatallow users to install theservice pack from this folder.
e. If you are using an NTFS filesystem 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. Insertyour Windows Server 2003 product CD or DVD into the CD-ROM drive,and then copy thecontents of the CD to
the distribution folder thatyou created in step 2.
For example, to copy theinstallation files and folders from the Windows Server 2003 product CD in the CD-ROM drive
(D:) to the distribution folder named WS2003\x86 on theE: drive,you would typethefollowing:
xcopy /E D:\ E:\WS2003\x86
5. Removethe product media from the CD-ROM drive,and then insert theSP1 CD. Besureto usethecorrectSP1 CD (for
either 32-bit or Itanium-based versions of Windows Server 2003).
6. Do one of thefollowing:
To apply thesourcefiles for theservice pack to theinstallation files for a 32-bitversion of Windows Server 2003 in
thefolder named WS2003\x86, typethefollowing:
WindowsServer2003-KB889101-SP1-x86-LLL.exe /integrate:Drive:\WS2003\x86
To apply thesourcefiles for theservice pack to theinstallation files for an Itanium-based version of Windows
Server 2003 in thefolder named WS2003\64bit, typethefollowing:
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 areextracted and then applied to the operating system files to updateyour shared distribution folder.
You can either usethefiles from this network shared folder to makea CD (32-bitversions only) to upgradeyour servers,
or you can customizeSetup for Windows Server 2003 as necessary.For moreinformation about how to customize
Setup,you can view Help by entering thefollowing command from theshared distribution folder:
\i386\winnt32.exe /?
8. You can now deploy Windows Server 2003 with SP1 to your computers from theshared distribution folder in either
attended or unattended Setup mode. During thestandard installation process,Setup for Windows Server 2003
(Winnt.exe or Winnt32.exe) installs the updated operating system with theservice pack already applied.
Important
When you run thecommand given in Step 6, the Update.exe program automatically creates aSvcpack.log filein systemroot
on thecomputer that is running the Update.exe program. If you plan to update morethan one operating system from this
computer, renametheSvcpack.log fileafter you updateeach version.This step ensures thatyou do not overwritethecurrent
log file when you updateadditional operating systems.
Scenario 2: Using RIS to install Windows Server 2003 integrated with the service pack
This section explains how to use RemoteInstallation Services (RIS) to install Windows Server 2003 operating systems
integrated with theservice pack. However, this section does notexplain how to set up RIS.For moreinformation about RIS, see
RemoteInstallation Services (on the MicrosoftTechCenter 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 thesourcefiles reside on a RIS server. You can createa RIPrep imagefrom a server that is running Windows
Server 2003 with SP1 and that is configured with applications and settings thatyou specify. You can then deploy this imageto
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 thefollowing 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. Createan integrated installation of Windows Server 2003 with SP1.For moreinformation, seeScenario 1: Creating an
installation of Windows Server 2003 integrated with theservice pack earlier in this guide.
2. To createan image,click Start,click Run,and then typethefollowing:
risetup.exe -add
3. The RemoteInstallation Services Setup Wizard appears.Follow theinstructions in the wizard.When theInstallation
Source Files Location page prompts you for theimagesource,enter the path to theshared folder that contains the
integrated installation thatyou created in Step 1.
4. A boxappears showing the progress of theinstallation. After the RISetup imageis complete,you can install theimage on
each server as described in RemoteInstallation Services (on the MicrosoftTechCenter Web site).
Updating existing RIPrep images to SP1
If you want to add additional programs or settings to your integrated installation image,you must havea CD–based image of
Windows Server 2003 with SP1 on your RIS server. (For moreinformation, seethe preceding section, Adding a CD-based
imagefor 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 theadditional programs and settings thatyou want to includein theimage.
3. Run RIPrep to createan image on the RIS server.
For instructions on how to run RIPrep on RIS servers running Windows Server 2003, see RemoteInstallation Services
and Automating and Customizing Installations (on the MicrosoftTechCenter Web site).
4. You can now deploy your RIPrep imageto other servers.For details about how to perform this task, see Remote
Installation Services (on the MicrosoftTechCenter Web site).
Note
You cannot usethe/integrate option to integrateSP1 directly into an existing CD-based image or a RIPrep image.
Command-Line Options for Installing SP1
You can definethe way SP1 is installed by typing one or more of thefollowing command-line options when you run the
installation file(for example,WindowsServer2003-KB889101-SP1-x86-LLL.exe) or Update.exe. You can precedethe options
with either a forward slash (/) or a hyphen (-).The options are not case-sensitive.
Commandline
option
Description
/?
or
/Help
Displays help text.
/D:
FolderName
Back up to a specified folder thefiles thatarerequired to removetheservice pack.
If you back up files but do not specify a folder, the default location is:
$ntservicepackuninstall$
Any location thatyou specify must be on thelocal drive.
/ER Enables extended return codes that return a detailed error messageif the updateinstallation fails.For more
information, seethe white paper,The PackageInstaller (Formerly Called Update.exe) for Microsoft Windows
Operating Systems and Windows Components, on the Microsoft Web site.
/F After theinstallation is complete,you must closeall open applications beforeyou restart thecomputer.This
option forces applications to close without saving files. You can usethis option with other command-line
options,except /integrate, /L,and /Z.
/Forcerestart Restarts thecomputer after the updateinstallation is complete.This option follows standard shutdown
behavior. It does not forceapplications to close.
/integrate:
Path
Integrates this software updateinto the path thatyou specify. Besureto providetheabsolute 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 notappear in Add or Remove Programs if you
usethis option.
/O Overwrites OEM files without prompting.
/Q
or
/Quiet
Uses quiet mode.Shows no user interface during SP1 installation.This is thesameas unattended mode,except
that the user interfaceis hidden. No prompts will appear during theinstallation process.
/U
or
/Passive
Uses unattended Setup modeand defaultSP1 options. Requires no user interaction during theinstallation of
the updates and shows only critical errors and a progress bar.
/Z
or
/Norestart
Does not restart thecomputer after theinstallation is completed.
Command-Line Options for Installing the Service Pack Only
Thefollowing tableidentifies additional command-line options that only theinstallation program for theservice pack supports.
Commandline
option
Description
/X Extracts service pack files without starting Update.exe. You are prompted to providethe path for thefolder in
which you want theextracted service pack installation files to be placed.
/U /X:
FolderName
Extracts service pack files and places them in theFolderName folder without prompting and without starting
Update.exe.
Important
SP1 will not befully functional until you restartyour computer.
Qfecheck.exe
For moreinformation about the Qfecheck.exe program, seethefollowing articles in the Microsoft Knowledge Base:
282784: “Qfecheck.exe Verifies theInstallation of Windows 2000 and Windows XP Updates”
304864: “Qfecheck HotfixTool Reports False Need to Reinstall Freshly Installed Updates”
Although thesearticles 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 thecommand prompt to remove
SP1 atany timeand restoreyour computer to its previous state.
You can uninstall SP1 only if it was installed as an updateto an existing operating system. You cannot removeSP1 if you
installed itas part of an integrated installation. In this case,you must uninstall theentire operating system together with SP1.
To remove SP1 using a command prompt
1. Open a command promptand type:
%systemroot%\$NtServicePackUninstall$\spuninst\
2. Type Spuninst.exe /Option. Replace Option with any of the options in thefollowing table.
3. Press ENTER to continue,and then follow theinstructions thatappear on your screen.
Option Description
/U Removes theservice pack in unattended mode. If you usethis option, only critical error prompts appear whileyou
uninstall SP1.
/Q Removes SP1 in quiet mode, which is thesameas unattended modeexcept that the user interfaceis hidden. If you use
this option, no prompts appear whileyou uninstall SP1.
/Z Does not restart thecomputer after you uninstall SP1.
/F Forces other applications to close when thecomputer restarts after you uninstall SP1.
Important
If you chooseto removeSP1,a dialog box displays a list of theapplications thatyou installed after you installed SP1. If you
continueto removeSP1, theseapplications might not work correctly.
Multiple descriptions of someapplications mightappear instead of a single generic description. You should ignorethese
additional descriptions.
Symbols for Debugging Service Packs
If you area system administrator (someone who diagnoses problems on computers thatarerunning Windows Server 2003),
werecommend thatyou download thesymbol 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 thesymbols for debugging
Windows Server 2003 from the download page on theInternet,and then you mustadd symbols for debugging SP1 to the
samefolder.For moreinformation, see Debugging Tools for Windows — Overview at the Microsoft Web site.
You can download symbols for debugging SP1 from one of thefollowing locations:
From the Download Windows Symbol Packages page on the Microsoft Web site.
On demand from theInternetSymbol Server.For moreinformation about using theInternetSymbol Server, see
Debugging Tools and Symbols: Getting Started on the Microsoft Web site.
TheEnglish version of the Windows Server 2003 Service Pack 1 CD, which includes thesymbols package.The package
(Symbols.exe) is in the\Support\Symbols folder on theservice pack CD.Thesymbols packageis included only on the
English version of theservice pack CD, but this packageis language-independentand can be downloaded for debugging
any Windows Server 2003 locale.
Note
When you install SP1, thecurrentversions of thesymbol files overwriteany previous versions thatarein thesymbol
installation folder.
Additional Resources
For information about Windows Server 2003 and SP1, seethe MicrosoftTechCenter Web site.
The Microsoft Knowledge Base provides updated information about the Windows Server 2003 operating systems,SP1,
and other Microsoft products.
For the most up-to-dateinformation about supported hardware, seethe hardwarecompatibility information at the
Windows Server Catalog Web site.
To obtain the most recent product updates, seethe Windows Update Web site.