Windows Server 2003 Service Pack 2 Installation and Deployment Guide

Updated:February 19, 2009
Applies To:Windows Server 2003 with SP2
This guideis for system administrators who areinstalling Microsoft® Windows Server® 2003 operating systems with Service
Pack 2 (SP2). It includes technical information, procedures,and recommendations for installing SP2 on multiplecomputers in a
small business or corporateenvironment. Although this guideincludes some basic operating system information, itassumes
thatyou havea working knowledge of Windows Server 2003.
This guide does notexplain:
How to combine SP2 with other updates for Windows Server 2003.For information about how to do this, see
“Installing and Deploying Updates for Microsoft Windows Server 2003″ (http://go.microsoft.com/fwlink/?LinkID=64779).
New functionality in SP2.For important information about functional changes to SP2, see”What’s New in Windows
Server 2003 Service Pack 2” (http://go.microsoft.com/fwlink/?LinkID=62452).
How to deploy SP2 by using Windows Server Update Services (WSUS).For moreinformation, seethe WSUS Web
site(http://go.microsoft.com/fwlink/?LinkID=94242).
Obtain the installation files
You can install SP2 from theSP2 CD or from the Web.To order an SP2 CD, seethe MicrosoftTechNet Web site
(http://go.microsoft.com/fwlink/?LinkId=78087).To download theinstallation files, seethe Microsoft Download Center
(http://go.microsoft.com/fwlink/?LinkId=78088).
Because downloading SP2 installation files takes a substantial amount of time, werecommend thatyou savethefiles on your
computer.This way,you can reinstall or repair theinstallation without downloading thefileagain. You should ensurethat there
is enough disk space on your hard disk drive beforestarting the download.
Theinstallation fileis named one of thefollowing. XXX stands for thetype of operating system (for examplex86) and LLL
stands for thelanguage(for exampleENU).
WindowsServer2003-KB914961-SP2-XXX-LLL.exe
WindowsServer2003.WindowsXP-KB914961-SP2-XXX-LLL.exe
Plan your deployment
This section includes information about how to plan your SP2 deployment, including pre-deployment tasks, testing the
deployment,and additional resources.
Pre-deployment tasks
Beforeyou install SP2, do thefollowing:
Review the following documentation.
Article 914962 in the Microsoft Knowledge Basefor a list of the updates included in this service pack
(http://go.microsoft.com/fwlink/?LinkId=74380).
“Release Notes for Windows Server 2003 Service Pack 2” for a list of theknown issues with this version ofSP2
(http://go.microsoft.com/fwlink/?LinkId=74381).
“Installing and Deploying Updates for Microsoft Windows Server 2003” for information about combining this
service pack with other updates (http://go.microsoft.com/fwlink/?LinkID=64779).
Check the disc space requirements.Seearticle 926029 in the Microsoft Knowledge Base
(http://go.microsoft.com/fwlink/?LinkId=74454).
Back up your servers. Your backup should includeall data and configuration information that is necessary for that
server to function. It is important to perform a backup of configuration information for servers,especially thosethat
provide network infrastructure, such as Dynamic Host Configuration Protocol (DHCP).When you perform the backup, be
sureto includethe bootand system partitions and thesystem state. Another way to back up configuration information is
to createa backup set for Automated System Recovery.
Disconnect UPS devices. If you havean uninterruptible power supply (UPS) connected to your destination computer,
disconnect theconnecting serial cable beforerunning Setup.Setup automatically attempts to detect devices connected to
serial ports,and UPS equipment can cause problems with the detection process.
Disable your antivirus software. If you are not connected to a network or theInternetand you want to minimizethe
installation time,you can disableyour antivirus software.Thetimethat it takes for theantivirus softwareto scan each file
can add significant timeto theinstallation (an hour or more on slower computers). Besureto enabletheantivirus
softwareafter you install SP2.
Uninstall prerelease versions of SP2. Unless you havea supplementary supportagreement with Microsoft,you must
uninstall any prereleaseversions ofSP2 beforeyou proceed. Microsoft does not support upgrading to this version from
any prereleaseversion.
Close all open programs.
Testing the deployment
Werecommend thatyou testSP2 in your computing environment beforeyou deploy it to all of your servers. If you are
installing Windows Server 2003 for thefirst time,you should set up a pilot group to testyour deploymentand verify that the
deployment works as expected.For more detailed information about testing your deploymentand creating a pilot program,
seethe Windows Server 2003 Deployment Guide(http://go.microsoft.com/fwlink/?LinkId=44319).To test the deployment, do
thefollowing:
1. Createa testenvironment. Makesurethat thetest computers contain the operating systems, software,and the hardware
devices thatare used in your organization.
2. Install theservice pack on each test computer. As needed, test thefollowing scenarios:
Updatecomputers thatarerunning Windows Server 2003.
Updatecomputers thatarerunning Windows Server 2003 with SP1.
Updatecomputers thatarerunning Windows Server 2003 R2.
Upgradetest computers thatarerunning Windows NT® Server 4.0 and Windows 2000 Server.
Perform a clean installation—that is, install Windows Server 2003 with SP2 onto computers that do not havean
operating system.
3. Verify that thesoftwareand hardware perform as expected in each scenario.
Additional resources
Thefollowing resources contain detailed information that can help you plan your deployment.
Windows Server 2003 Deployment Guide(http://go.microsoft.com/fwlink/?LinkId=44319).
Article 926028 in the Microsoft Knowledge Base: “Updated System Preparation Tool for Windows Server 2003 Service
Pack 2.”This articlecontains instructions on how to usetheSysprep tool to deploy system images
(http://go.microsoft.com/fwlink/?LinkId=78090).
Deploy.cab and Support.cab.Thesearecompressed files that contain a collection of tools and online Help.Technical
support personnel and network administrators can usethese updated support tools to manage networks and
troubleshoot problems.Thesefiles arelocated on theSP2 CD in the\Support\Tools folder and on the Microsoft
Download Center.
To download Deploy.cab, search the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=78088)
for “Windows Server 2003 Service Pack 2 DeploymentTools.”
To download Support.cab, search the Microsoft Download Center (http://go.microsoft.com/fwlink/?
LinkId=78088) for “Windows Server 2003 Service Pack 2 SupportTools.”Support.cab is included in the
WindowsServer2003-KB914961-SupportTools-XXX-LLL.exefile.
Article 926027 in the Microsoft Knowledge Base: “Windows Server 2003 Service Pack 2 SupportTools”
(http://go.microsoft.com/fwlink/?LinkId=78091).
Qfecheck.exe.Qfecheck.exeis a command-linetool that gives network administrators increased ability to track and verify
installed hotfixes.For moreinformation about the Qfecheck.exe program, seearticle 282784 in the Microsoft Knowledge
Base: “Qfecheck.exe Verifies theInstallation of Windows 2000 and Windows XP Updates”
(http://go.microsoft.com/fwlink/?LinkId=44323). Although this article was written for other operating systems, italso
applies to Windows Server 2003.
Installation options
You havetwo installation options:
Standaloneinstallation. Deploys SP2 to servers thatarealready running Windows Server 2003.
Integrated installation. Integrates SP2 into Windows Server 2003,and then installs the operating system and SP2
simultaneously. You can usetheintegrated installation to upgradeservers and to perform clean installations on servers
that do not havean operating system.For moreinformation about creating an integrated version, see”Installing and
Deploying Updates with Microsoft Windows Server 2003″ (http://go.microsoft.com/fwlink/?LinkID=64779).
To perform theseinstallations, first copy theinstallation files to a network share.Then extract theSP2 sourcefiles either to
either each computer locally or to a network share(to save disk space on each computer).
When you extract thefiles to a network share, it is called a UNC install.For UNC installs,each computer uses thefiles on the
network shareto install thesoftware. UNC installs are only suitablefor computers thatare permanently connected to the
network becausetheservice pack sourcefiles arestored remotely.For example,you should not usethis method for updating
laptop computers becauseif connectivity is lost during theinstallation, thecomputer may beleft in an unusablestate. In
addition,you must usea network sharethat was created specifically for SP2 so that thesourcefiles arealways availablefor
computers. If you need to movea shared distribution folder, seearticle 271484 in the Microsoft Knowledge Base: “Files and
Folders Are Added to Your System After Service Pack Is Installed” (http://go.microsoft.com/fwlink/?LinkId=9273).
The standalone installation
In a standaloneinstallation,you install theservice pack on computers thatalready havean operating system.Theservice pack
installation is not complete until thecomputer is restarted.When you run a standaloneinstallation, Update.execreates a log file
named Svcpack.log in the %systemroot% directory.
Therearefour scenarios for installing thestandaloneservice pack:
Scenario 1: Installing SP2 using local sourcefiles
Scenario 2: Installing SP2 using sourcefiles thatarelocated on a network share
Scenario 3: Installing SP2 using Systems ManagementServer (SMS)
Scenario 4: Installing SP2 using Windows Installer (Update.msi) and Group Policy
Scenario 1: Installing SP2 using local source files
First set up a shared distribution folder for theservice pack installation file.Then to install theservice pack, savetheinstallation
files locally on each computer.
To install SP2 using installation files that are saved locally on each computer
1. Connect to the network or computer whereyou want to createthe distribution folder.
2. In theshared folder,createa distribution folder for theservice pack.For example, to createa distribution folder named
WS2003SP2, type mkdir Drive:\WS2003SP2 at thecommand prompt(Drive: represents the drive whereyou want to
storethe distribution folder).
3. Copy WindowsServer2003-KB914961-SP2-XXX-LLL.exeinto the distribution folder.
4. To verify thatyou haveassigned appropriate permissions to users who areinstalling theservice pack:
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 at thecommand prompt, typethefollowing using the desired command-line options:
\\ServerName\WS2003SP2\WindowsServer2003-KB914961-SP2-XXX-LLL.exe
6. Follow theinstructions in theSetup Wizard.
7. After theinstallation is complete, if you want to install additional updates, install them beforeyou restartyour computer.
8. Restart thecomputer and then restart theantivirus softwareif you disabled it.
Scenario 2: Installing SP2 using source files that are located on a network share
To install SP2 from the network, firstextract theinstallation files to a shared distribution folder.Then install SP2 on each
computer using thesefiles.
To install the service pack using a network share
1. Connect to the network or computer whereyou want to createthe distribution folder.
2. In theshared folder,createa distribution folder.For example, to createa distribution folder named WS2003SP2, type
mkdir Drive:\WS2003SP2 at thecommand prompt (Drive: represents the drive whereyou want to storethe distribution
folder).
3. To extract thefiles to the distribution folder, typethefollowing at thecommand prompt, where Path is thelocation of the
distribution folder:
WindowsServer2003-KB914961-SP2-XXX-LLL.exe /X:Path
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.exe.For example, to install from a distribution
folder named WS2003SP2, typethefollowing at thecommand prompt using the desired command-line options:
Drive:\WS2003SP2\i386\Update\Update.exe
6. Follow theinstructions in theSetup Wizard.
7. After Update.exe has completed, restart thecomputer to completetheinstallation.SP2 will not befully installed until you
restartyour computer.
8. If you disabled your antivirus software,enableitafter you restart thecomputer.
Scenario 3: Installing SP2 using Systems Management Server (SMS)
This scenario explains how to use MicrosoftSystems ManagementServer (SMS) to install theservice pack from a shared
folder. You can usethis method to install theservice pack on SMS servers thatarealready running Windows Server 2003.
This scenario assumes thatyou havean understanding ofSMS and a working knowledge of software distribution.For more
information about deploying SP2 using SMS, seearticle 926030 in the Microsoft Knowledge Base: “How to Install Windows
Server 2003 Service Pack 2 (SP2) by Using Systems ManagementServer” (http://go.microsoft.com/fwlink/?LinkId=78092).
To use SMS to install the service pack
1. Ensurethatyour computer is running SMS 2003 with Service Pack 1 or Service Pack 2.
2. CreatetheSMS package by importing the package definition filefor theservice pack. In the package, providethe path to
thesourcefiles for theservice pack.
3. DistributetheSMS packageto the distribution points.
4. Createtheadvertisement to notify SMS servers that theservice pack is available.
Scenario 4: Installing SP2 using Windows Installer (Update.msi) and Group Policy
This scenario explains how to install SP2 from a shared folder using the Windows Installer packagefile(Update.msi). You can
usethis method to install theservice pack on servers thatarealready running an operating system.
Update.msi contains all of therequired information to install or removetheservice pack.This file defines therelationships
between service pack binary files. Italso contains an installation database whereyou can view a summary of the properties
that theinstallation program uses.To view this summary, right-click theinstallation database,and then click Properties. You
must usethe machine-assigned distribution method with Update.msi.
Beforeyou begin, please note:
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(http://go.microsoft.com/fwlink/?LinkId=44319).
For general information about how to apply your software deployment policy to users who are outsidethe boundaries of
organization units, seearticle 324750 in the Microsoft Knowledge Base: “How To Assign Softwareto aSpecific Group By
Using a Group Policy in the Windows Server 2003 Family” (http://go.microsoft.com/fwlink/?LinkId=43972).
Werecommend thatyou usetheSP2 installation file(for example,WindowsServer2003-KB914961-SP2-XXX-LLL.exe)
when deploying SP2 at thecommand prompt. If you use Update.msi to distributeservice packs,you must usea serverbased
(“machine-assigned”) Group Policy object (GPO) only. User-based Group Policy deployments are not supported
with Update.msi.For moreinformation, seearticle 278503 in the Microsoft Knowledge Base: “Best Practices for Using
Update.msi to Deploy Service Packs” (http://go.microsoft.com/fwlink/?LinkId=28711).
#Assigning Service Pack 2 to servers using Group Policy
This procedureexplains how to assign theservice pack to servers thatare managed by a Group Policy object (GPO).For your
installation,you might want to associatethe GPO with a new Active Directory container. Only a network administrator or
someone who is logged on to a local server as an administrator can removetheassigned software.
To use Group Policy to assign SP2
1. Ensurethat theserver you want to updateis joined to thesame domain as theserver where Update.msi resides.
2. Createa shared network distribution folder.
3. Createa GPO for SP2 deployments.
4. Deploy Update.msi from theshared distribution folder as “machine-assigned.” Do not deploy itas a user deployment.
5. Restarteach server.When you restarteach server, it is updated to SP2. You should check the properties of each server to
ensurethat the update has completed. You might need to restarteach server morethan onceto completethe update.
The integrated installation
You should perform theintegrated installation if you want to install SP2 and Windows Server 2003 at thesametime.To
perform this type of installation, first usethe/integrateoption to update Windows Server 2003 with theSP2 installation files.
To do this,you need to usea computer that is already running a Windows Server 2003 or Windows XP operating system.
After you havetheintegrated version,you can run Windows Server 2003 Setup.The Update.exe program creates a log file
(named Spslpsrm.log) for integrated installations.This log fileis created in the %systemroot% directory. If you plan to update
morethan one operating system from this computer, renametheSvcpack.log fileafter you updateeach version. Otherwise
Update.exe will overwritethis file.
This section describes threescenarios for installing theintegrated installation.
Scenario 1: Creating an integrated installation
For Windows Server 2003
For Windows Server 2003 R2
Scenario 2: Using RIS to install an integrated installation
Scenario 3: Using Windows DeploymentServices to install an integrated installation
Scenario 1: Creating an integrated installation
This section contains instructions for creating integrated installations ofSP2 with Windows Server 2003 and Windows
Server 2003 R2.
For Windows Server 2003
To create an integrated installation of Windows Server 2003 with SP2
1. Connect to the network or computer whereyou want to createthe distribution folder.
2. Createtheshared folder and ensurethat only system administrators havefull access to this folder. (Other users should
have only Read and Execute permissions.)
3. In theshared folder,createa distribution folder for the Windows Server 2003 installation files.For example, to createa
distribution folder named WS2003\x86, type:
mkdir Drive:\WS2003\x86
4. To verify thatyou haveassigned appropriate permissions to users who areinstalling theservice pack:
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. Insertyour Windows Server 2003 product disc into the CD-ROM driveand copy thecontents to the distribution folder.
For example, to copy thecontents in the CD-ROM drive(D:) to the distribution folder named WS2003\x86 on theE: drive,
type:
xcopy /E D:\ E:\WS2003\x86
6. Removethe Windows Server 2003 product disc,and insert theSP2 CD.
7. Apply thesourcefiles for theservice pack to theinstallation files.For example, for a 32-bitversion of Windows
Server 2003, in thefolder named WS2003\x86, type:
WindowsServer2003-KB914961-SP2-XXX-LLL.exe /integrate:Drive:\WS2003\x86
8. Service pack files areextracted and then applied to the operating system files to updateyour shared distribution folder.
You can either usethefiles from this 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 customizeSetup,view
Help by typing i386\winnt32.exe /? at thecommand prompt in theshared distribution folder.
9. You can now deploy Windows Server 2003 with SP2 to your computers from theshared folder in either attended or
unattended Setup mode.
For Windows Server 2003 R2
This section applies only if you havethefirst release of Windows Server 2003 R2 where disc 1 contains Windows Server 2003
with Service Pack 1. If the product discs thatyou have do not specify which service pack is included, the discs contain Windows
Server 2003 with SP1. If you havethesecond release of Windows Server 2003 R2 where disc 1 contains Windows Server 2003
with SP2,you do not need to integrate disc 1 and SP2 because disc 1 already contains SP2.
To create an integrated installation of Windows Server 2003 R2 and SP2
1. Connect to the network or computer whereyou want to createthe distribution folder.
2. Createtheshared folder and ensurethat only system administrators havefull access to this folder. (Other users should
have only Read and Execute permissions.)
3. In theshared folder,createa distribution folder for the Windows Server 2003 R2 disc 1 installation files.For example, to
createa distribution folder named WS2003\x86\CD1, type:
mkdir Drive:\WS2003\x86\CD1
4. To verify thatyou haveassigned appropriate permissions to users who areinstalling theservice pack:
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. Insert disc 1 into the CD-ROM drive,and copy thecontents to the distribution folder.For example, to copy thecontents in
the CD-ROM drive(D:) to the distribution folder named WS2003\x86\CD1 on theE: drive, type:
xcopy /E D:\ E:\WS2003\x86\CD1
6. Removethe Windows Server 2003 R2 disc 1,and insert theSP2 CD.
7. Apply thesourcefiles for theservice pack to theinstallation files.For example, for a 32-bitversion of Windows
Server 2003 in thefolder named WS2003\x86\CD1, type:
WindowsServer2003-KB914961-SP2-XXX-LLL.exe /integrate:Drive:\WS2003\x86\CD1
8. Service pack files areextracted and then applied to the operating system files to updateyour shared distribution folder.
You can either usethefiles from this 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 customizeSetup,view
Help by typing i386\winnt32.exe /? at thecommand prompt in theshared distribution folder.
9. Insertyour Windows Server 2003 R2 disc 2 into the CD-ROM drive,and copy thecontents to the distribution folder.For
example, to copy thecontents in the CD-ROM drive(D:) to the distribution folder named WS2003\x86\CD2 on theE:
drive, type:
xcopy /E D:\ E:\WS2003\x86\CD2
10. Apply thesourcefiles for theservice pack to theinstallation files.For example, for a 32-bitversion of Windows
Server 2003 in thefolder named WS2003\x86\CD2, type:
WindowsServer2003-KB914961-SP2-XXX-LLL.exe /integrate:Drive:\WS2003\x86\CD2
11. You can now deploy theintegrated version of disc 1 and theinstallation files for disc 2 to your computers from the
shared folder in either attended or unattended Setup mode.
Scenario 2: Using RIS to install an integrated installation
This section explains how to use RemoteInstallation Services (RIS) to install an integrated version of Windows Server 2003
with SP2. However, this section does notexplain how to set up RIS.For moreinformation about RIS, see RemoteInstallation
Services (http://go.microsoft.com/fwlink/?LinkId=36940).
RIS supports two types of operating system images:
CD-based images (images created by using RISetup)
RemoteInstallation Preparation (RIPrep) images.
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 SP2,and you can then deploy this imageto other similar servers thatareconnected to the network.
Creating a CD-based (RISetup) image to add to a RIS server
After you install RIS, perform thefollowing steps to createtheimageand then add theimageto your RIS server.
To create an image of Windows Server 2003 with SP2 and add it to your RIS server
1. Createan integrated version of the operating system with SP2.For moreinformation, seeScenario 1.
2. To createan image,click Start,click Run,and then type:
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 version 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
(http://go.microsoft.com/fwlink/?LinkId=36940).
Creating a Remote Installation Preparation (RIPrep) image to deploy to other servers
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 SP2 on your RIS server. Notethatyou cannot usethe/integrate option to integrateSP2 directly
into an existing CD-based image or a RIPrep image.
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 (http://go.microsoft.com/fwlink/?LinkId=36940)
Automating and Customizing Installations (http://go.microsoft.com/fwlink/?LinkId=44324)
4. You can now deploy your RIPrep imageto other servers.
Scenario 3: Using Windows Deployment Services to install an integrated installation
This section explains how to use Windows DeploymentServices to install an integrated version of Windows Server 2003 with
SP2. However, this section does notexplain how to set up Windows DeploymentServices.For moreinformation, seethe
documentation that is included with thetool and the Windows DeploymentServices UpdateStep-by-Step Guide
(http://go.microsoft.com/fwlink/?LinkId=66145).
You can also deploy SP2 by using RIS functionality from a Windows DeploymentServices Server.For example, firstensurethat
theserver is in either Legacy or Mixed mode.Then follow the procedures in Scenario 2 to deploy SP2.To check the operating
modethatyou arein, run WDSUTIL/get-server /show:config.The output will contain a line with the modethatyou arein.
For example, “WDS operational mode: Mixed.”
To add an image of Windows Server 2003 with SP2 to your Windows DeploymentServices server,you must first createa .wim
install image. Install images are built from referenceinstallations of the Windows operating system and are deployed when
Windows DeploymentServices is used to install Windows. A referenceinstallation may bea standard Windows installation or
may beconfigured for a specificenvironment or use prior to creating theimage.
To create an install image
1. Createa referencecomputer that contains Windows Server 2003,SP2,and any programs and settings thatyou want to
includein theimage.
2. Download the updated deployment tools (Deploy.cab).To do this, search the Microsoft Download Center for “Windows
Server 2003 Service Pack 2 DeploymentTools” (http://go.microsoft.com/fwlink/?LinkId=78088).
3. From a command prompt on thereferencecomputer,change directories to the directory that contains the updated
version ofSysprep.exe(which is included in Deploy.cab).For moreinformation about using this tool, seearticle 926028
in the Microsoft Knowledge Base: “Updated System Preparation Tool for Windows Server 2003 Service Pack 2″
(http://go.microsoft.com/fwlink/?LinkId=78090).
4. Typesysprep.exe /reseal /reboot.
5. When thereferencecomputer reboots, press F12.
6. In Windows Boot Manager,chooseto boot to theappropriatecaptureimage.
7. On theImage Capture Wizard welcome page,click Next.
8. On theImage Capture Source page, usethe Volume to Capture drop-down menu to choosetheappropriatevolume,
and then providea nameand description for theimage. Click Next to continue.
9. On theImage Capture Destination page,click Browse and browseto thelocation whereyou want to storethe
captured image.
10. In theFilename text box, typea namefor theimage using the.WIM file nameextension,and then click Save.
11. Click Upload image to WDS server.
12. Typethe name of the Windows DeploymentServices server and click Connect.
13. If prompted for credentials, providea user nameand password for an account with sufficient privilegeto connect to the
Windows DeploymentServices server.
14. Using the drop-down Image Group menu,choosean image group in which to storetheimage.
15. Click Finish.
Command-line options
You can usethefollowing options to definethe way SP2 is installed. You can usethefollowing options through Update.exe or
when you run theinstallation file(for example, WindowsServer2003-KB914961-SP2-XXX-LLL.exe). You can precedethe
following options with a forward slash (/) or a hyphen (-).The options are not case-sensitive.
Note
You can also usethe/Log and /Verbose options.For moreinformation, see”The PackageInstaller (Formerly Called
Update.exe) for Microsoft Windows Operating Systems and Windows Components” (http://go.microsoft.com/fwlink/?
LinkId=42759).
Command-line
option
Description
/D:Path Backs up thefiles thatarerequired to removetheservice pack to Path. Any location thatyou specify must
be on thelocal drive. If you back up files but do not specify a folder, the default location is:
$ntservicepackuninstall$
/ER Enables extended codes that return a detailed error messageif the updateinstallation fails.For more
information, see”The PackageInstaller (Formerly Called Update.exe) for Microsoft Windows Operating
Systems and Windows Components” (http://go.microsoft.com/fwlink/?LinkId=42759).
/F
or
/Forceappsclose
Forces other applications to closeafter you install the update packageand beforethecomputer is restarted.
You cannot usethis option with /integrate, /L,and /Z.
/Forcerestart Restarts thecomputer after theinstallation is complete,even if a restart is not required to completethe
installation.This option does not forceapplications to close.
/Integrate:Path Integrates theSP2 sourcefiles into the path you specify. Besureto providetheabsolute path to your
operating system sourcefiles.This option is thesameas the/S option that was used by previous installers.
/L Lists installed updates.
/N
or
/Nobackup
Does not create backup files during setup.We do not recommend this option because backup files allow
you to removeSP2 in thefuture. An entry for SP2 does notappear in Add or Remove Programs if you use
this option.
/O
or
/Overwriteoem
Overwrites OEM files without prompting.
/Promptrestart If a restart is required,a dialog box notifies the user thata restart is required to completesetup. Intended for
use with /Quiet.
/Q
or
/Quiet
Uses quiet mode.This modeshows no user interface during theinstallation of the updates.This is thesame
as unattended mode,except that the user interfaceis hidden. No prompts will appear during theinstallation
process.
/U
or
/Passive
Installs theservice pack in unattended mode. Only critical error prompts and a progress bar will appear
during theinstallation. By default, the program invokes the/Warnrestart option.
/Warnrestart:
[Seconds]
If a restart is required,a dialog box notifies the user that thecomputer will restart in thespecified seconds.
The user can click Cancel or Restart Now.The default is 60 seconds.
/X
or
/Extract
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.For moreinformation, see”The
PackageInstaller (Formerly Called Update.exe) for Microsoft Windows Operating Systems and Windows
Components” (http://go.microsoft.com/fwlink/?LinkId=42759).
/Z
or
/Norestart
Does not restart thecomputer after theinstallation is complete,even if a restart is required to completethe
installation.
/?
or
/Help
Displays Help.
Uninstalling SP2
It is possibleto uninstall SP2 only if it was installed as an updateto an existing operating system. It is not possibleto remove
only SP2 if you installed itas part of an integrated installation. In addition,you can only uninstall thelast service pack thatyou
installed.For example, if you install SP1 and then you install SP2,you can only uninstall SP2.
By default, backup files arecreated during theinstallation so you can removeSP2. Unless you specified the/nobackup option
when installing SP2, then you can removeSP2 using Add or Remove Programs or thecommand prompt.
If you removeSP2,a dialog box displays a list of theapplications thatyou installed after you installed SP2. If you continue,
theseapplications might not work correctly. Multiple descriptions of someapplications mightappear instead of a single
generic description. You can ignoretheseadditional descriptions.
To remove SP2 using a command prompt
1. Open a command prompt, typethefollowing,and then press ENTER (Option can beany option listed in thefollowing
table):
%systemroot%\$NtServicePackUninstall$\spuninst\Spuninst.exe/Option
2. Follow theinstructions thatappear on your screen.
Option Description
/F
or
/Forceappsclose
Forces applications to close when thecomputer restarts.
/Q
or
/Quiet
Removes SP2 in quiet mode, which is thesameas unattended modeexcept that the user interfaceis hidden
and no prompts appear.
/U
or
/Passive
Removes theservice pack in unattended mode. Only critical error prompts appear whileSP2 is being
uninstalled.
/Z
or
/Norestart
Does not restart thecomputer after the process of uninstalling SP2 is complete.
/?
or
/Help
Displays Help.
Debugging symbols
If you want to debug the operating system, first download and install thesymbols for debugging Windows Server 2003,and
then add thesymbols for debugging SP2 to thesamefolder.When you install SP2, thecurrentversions of thesymbol files
overwriteany previous versions thatarein thesymbol installation folder.For moreinformation, see Debugging Tools for
Windows—Overview (http://go.microsoft.com/fwlink/?LinkId=30565).
You can download symbols for debugging SP2 from one of thefollowing locations:
The Download Windows Symbol Packages page on the Microsoft Web site(http://go.microsoft.com/fwlink/?
LinkID=30539).
On demand from theInternetSymbol Server.For moreinformation about using theInternetSymbol Server, see
“Debugging Tools and Symbols: Getting Started” on the Microsoft Web site(http://go.microsoft.com/fwlink/?
LinkId=30524).
TheEnglish version of theSP2 CD.This CD contains thesymbols package(Symbols.cab) in the\Support\Symbols folder.
This packageis language-independentand can be downloaded for debugging any Windows Server 2003 locale.
Additional resources
For information aboutSP2, seethe MicrosoftTechCenter Web site(http://go.microsoft.com/fwlink/?LinkId=78093).
The Microsoft Knowledge Base provides updated information about the Windows Server 2003 operating systems,SP2,
and other Microsoft products (http://go.microsoft.com/fwlink/?LinkId=4441).
For the most up-to-dateinformation about supported hardware, seethe hardwarecompatibility information at the
Windows Server Catalog Web site(http://go.microsoft.com/fwlink/?LinkId=16906).
To obtain the most recent product updates, seethe Windows Update Web site(http://go.microsoft.com/fwlink/?
LinkId=22377).