Scenario 3: Installing the service pack by using SMS
Scenario 4: Installing the service pack by using Windows Installer and Group Policy
Scenario 1: Installing Windows 2000 integrated with the service pack
Scenario 2: Using RIS to install Windows 2000 integrated with the service pack
About This Guide |
Back to Top |
This guide provides instructions for administrators installing Service Pack 3 (SP3) for Windows 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server, and Windows 2000 with Server Appliance Kit. This guide includes information for advanced users, technical details, procedures, and recommendations for successfully installing the service pack on multiple computers in a small business or corporate environment.
This document focuses on the key scenarios for installing the service pack either alone or with Windows 2000.
Note
If you want to install the service pack in combination with Windows 2000 hotfixes, see the Microsoft Windows 2000 Hotfix Installation and Deployment Guide.
This guide assumes a working knowledge of Windows 2000 and service pack installations. Although some basic operating system information is included in the document, this is not a replacement for either the Windows 2000 documentation or formal training. Rather, it is intended to complement these sources of information.
In particular, you should use this guide in conjunction with the Microsoft Windows 2000 Professional Resource Kit and the Microsoft Windows 2000 Server Resource Kit. For more information about these technical resources, see For More Information later in this document.
The Windows 2000 Service Pack 3 Web site provides a list of known issues and release notes pertaining to SP3, and any updated versions of this guide will be included on the Web site. You will find all of this information under Learn More on the site.
This guide includes the following main sections:
You can read this section to become familiar with the service pack. This section also provides information about additional resource material that can help you plan your service pack deployment.
This section identifies the important steps for planning your service pack deployment. You can read about the installation methods, the deployment tools and files, the versions of Windows supported by the service pack, and the methods for testing the deployment in your environment.
This section explains how to remove Microsoft Internet Explorer, Microsoft Outlook® Express, or Windows Media® Player visible entry points (such as shortcuts and menu entries) either during unattended Setup for Windows 2000 or while running Sysprep for Windows 2000.
You can install SP3 separately as an update or integrate it with Windows 2000 before installing the two together.
The Update Installation
This section explains how to perform an update installation of the service pack. This type of installation entails installing SP3 separately as a standalone application in Windows 2000. Procedures provide step-by-step instructions for the following update installation scenarios:
The Integrated Installation
This section explains how to create an integrated installation and install Windows 2000 combined with the service pack. Procedures provide step-by-step instructions for the following integrated installation scenarios:
Note
For details about the combination installation (installing hotfixes with Windows 2000), see the Microsoft Windows 2000 Hotfix Installation and Deployment Guide.
Before you get started, it's important to understand a few specialized terms that are used in this installation and deployment guide.
The following table provides definitions of terms used in this guide that are specific to service pack installations or Windows 2000, or both.
| Term | Definition |
|---|---|
| systemroot | The "root" directory of the Windows installation on the computer's hard disk. For example, on most computers, systemroot is C:\Winnt. |
| systemdrive | The drive where the operating system is installed. For example, on most computers, the systemdrive is C:\. |
| integrated | Describes the version of the service pack that comes bundled with the operating system (for example, Windows 2000), which results in a unified operating system that is marketed as such (for example, Windows 2000 with SP3). You can also create an integrated version of Windows 2000 operating system files with SP3. |
For additional information about Windows 2000 and this service pack, see the following resources:
What is the Service Pack? |
Back to Top |
This service pack is a collection of updates to Windows 2000. To help you learn more about the service pack, this section discusses the following topics:
Important
This service pack is not a required upgrade; however, some applications might not run correctly unless SP3 is installed.
The Service Pack 3 CD includes the following items:
W2ksp3.exe is a self-extracting compressed file. You can extract all of the files that W2ksp3.exe contains and proceed by using command-line options to determine the type of installation. For example, you can extract all of the files to a shared network folder and then use Update.exe (included on the Service Pack 3 CD) to upgrade individual computers.
If you run W2ksp3.exe without command-line options, all of the SP3 files will be installed on the local computer, which is the default installation location.
The Service Pack 3 CD also contains the following documents and tools for advanced users and administrators:
For more information on the deployment tools, see the Help file "Windows 2000 Resource Kit Deployment Tools" (Deptool.chm), which is included in Deploy.cab. This Help file provides a list of tools, instructions for how to use them, and additional information about performing an unattended setup.
For more information on the support tools, see the Help file "Windows 2000 Support Tools" (W2rksupp.chm), which is included in Support.cab. This Help file provides descriptions of the support tools and examples of how they are used. You can find additional information about these tools in article Q322271, "Service Pack 3 Adds Updates to Several Windows 2000 Support Tools," in the Microsoft Knowledge Base.
Important
All files and programs included on the Service Pack 3 CD are also available on the Web. On the Windows 2000 Service Pack 3 Web site, you can view a list of fixes included in the service pack. The list includes the files affected by SP3, known issues, and general release notes for the service pack.
There are also two installation options available from this Web site, as described in the following paragraphs. Note that both of these installations provide you with the exact same software.
This installation package includes only the files required to start the installation and connect to a download server: the information (.inf) file, the version (.ver) file, and a URL that points to the download server on the Windows 2000 Service Pack 3 Web site. The remaining files you need are identified and downloaded when you link to the download server. Because the Express installation detects the service pack files that are already installed on your computer and installs only those files that need to be updated, the download time is significantly reduced.
This is a full self-extractable package that contains all of the files required for a service pack installation. This installation option downloads all of the SP3 files to your computer from the Windows 2000 Service Pack 3 Web site. This is ideal for administrators who want to set up a shared network folder for deploying the service pack on multiple computers.
To help you decide whether to upgrade to this service pack, Microsoft provides extensive documentation about the service pack updates. You will find the current list of fixes and general release note items (for example, space requirements for installing SP3) on the Windows 2000 Service Pack 3 Web site.
The service pack is a collection of updates for Windows 2000. These updates address the following aspects of Windows 2000:
SP3 includes the features listed and described in the following paragraphs.
After you have installed the service pack, you do not need to reinstall it if you add a device or new software to your computer. For example, Windows 2000 includes a file named Driver.cab, which contains all of the files potentially installed by Plug and Play (PnP)-class installers. Setup and other components use this file to install the drivers for new devices (for example, a PCMCIA card or a USB keyboard) without requiring access to the Windows 2000 CD or the network.
The service pack does not update the Driver.cab file itself; instead, the Update.exe program installs an additional driver .cab file named Sp3.cab. This file contains only updated versions of drivers that exist in the original Windows 2000 Driver.cab file. In addition to the Sp3.cab file, the Update.exe program installs a new Drvindex.inf that points to Sp3.cab for all of the updated drivers and also points to Driver.cab for all of the remaining drivers.
Update.exe installs a Layout.inf file. Layout.inf ensures that the correct software is installed and that all updates are made automatically to Windows 2000 when you remove services from or add services to your computer. For example, if you remove TCP/IP from Windows NT® 4.0 and then reinstall it there, you must reinstall the service pack after you reinstall TCP/IP. This is unnecessary in Windows 2000. The Layout.inf file is updated automatically to determine which files must be installed from the original Windows 2000 CD or from the service pack and, if necessary, the file prompts the CD or the service pack for the appropriate media.
For more information about this, see article Q274215, "Not Necessary to Reinstall Windows 2000 Service Packs After System State Changes," in the Microsoft Knowledge Base.
You can integrate the service pack with a Windows 2000 installation. You do not need to perform separate installations of Windows 2000 and the service pack. For more information about this installation method, see The Integrated Installation later in this document.
The Update.exe program creates a log file in systemroot named Svcpack.log. This log file contains the following information:
Beginning with Service Pack 2, high encryption (128-bit) is supported as the default standard, and installing Service Pack 2 or later automatically upgrades your computer from standard encryption (56-bit) if it hasn't been upgraded already. High-encryption support is intended to improve the security of stored data and online transactions, as well as any other content you share over networks or the Internet, and to bring your computer on par with the current worldwide encryption standard.
For more information about support for 128-bit encryption in the service pack, see the bulletin on the Microsoft Windows 2000 Web site about 128-bit encryption being the default level. High encryption support is included for all Windows 2000 encryption-based services, including Kerberos, Protected Storage, RAS, RPC, SSL/TLS, CryptoAPI, Terminal Services RDP, and IPSec.
For information about Kerberos support in SP3, see the article Q235529 "Kerberos support on Windows 2000 Server Clusters," in the Microsoft Knowledge Base.
Important
Removing SP3 does not cause your computer to revert to 56-bit encryption. You can remove SP3 at any time, but your computer will retain high-encryption support. After SP3 is installed, the Protected Store will not be upgraded to 128-bit encryption. Microsoft has released a patch and tool to upgrade the Protected Store. To download the patch and the tool, see Microsoft Security Bulletin MS00-032. The FAQ for this security bulletin provides more information about Protected Store, the patch, and the tool.
To deploy the service pack, you can run the W2ksp3.exe, which extracts the contents. After this, Update.exe runs automatically to install the service pack. You can define the way these steps are completed by using the options explained in this section.
The following table describes the command-line options that both the Update.exe and W2ksp3.exe programs support. You include the options you want to use when you enter the command to extract files from W2ksp3.exe. The options are passed to Update.exe and dictate the specifics of the installation process; they do not, however, affect the way the files are extracted. All of the options listed in the table include a forward slash (/), but you can use a hyphen (-) instead, if you prefer. The options work the same way with either symbol.
| Command-line option | Description |
|---|---|
| /U | Uses unattended Setup mode. If you use this option, only critical error prompts will appear on-screen during the installation process. |
| /Q | Uses quiet mode (the same as unattended mode, but with the user interface hidden from view). If you use this option, no prompts will appear on-screen during the installation process. |
| /F | Forces other applications to close at shutdown. |
| /N | Does not back up files for removing the service pack. |
| /O | This option is not currently available. |
| /Z | Does not restart the computer after the installation is completed. |
| /L | Lists installed hotfixes. |
| /S:folder_name | Uses integrated installation mode—to a distribution server location. (This option is not currently available for W2ksp3.exe.) |
You can use these options to install the service pack as follows:
W2ksp3.exe /U
Use this option to install the service pack using all the default options. The installation will not prompt you for any input, but the installation progress bar in the user interface will be displayed throughout the installation process.
W2ksp3.exe /Q
Use this option to install SP3 the same way as described for the unattended installation. However, neither the progress bar in the user interface nor any errors that might occur will be displayed during installation.
W2ksp3.exe /F
After the installation is completed, you must close all open applications before restarting the computer. To force applications to close without saving files, use the /F option. You can use this option in conjunction with other command-line options, with the exception of /S (used for integrated installation mode), /L (used to list installed hotfixes), and /Z (used to prevent the restart from automatically occurring after the installation)
W2ksp3.exe /N
If you select this option, the files needed to remove the service pack will not be backed up during the installation. This can help save disk space but also means that you will not be able to remove the service pack at a later date. If you use this option, the Add/Remove program entry is not added for removing the service pack at some point in the future, and you will not be able to remove the service pack from the command line either.
You can use this option in conjunction with other command-line options, with the exception of /S (used for slipstreaming only) and /L (used for installing hotfixes).
W2ksp3.exe /Z
If you want to install hotfixes after installing the service pack and thus do not want your computer to restart automatically after the service pack installation is complete, use this option. You can use this option in conjunction with other command-line options, with the exception of /S and /L. After you have installed the hotfixes, be sure to restart the computer immediately to complete the service pack installation process.
W2ksp3.exe /L
If you want to display all of the hotfixes that are currently installed on the computer, use this option. This option is not designed for use with any other command-line options.
Qfecheck.exe
For more information about the Qfecheck.exe program, see the following articles in the Microsoft Knowledge Base:
Update.exe /s:<FolderName>
If you want to deploy Windows 2000 with SP3 as an integrated installation, you can use this option to build an integrated shared network folder that contains files for Windows 2000 and SP3. You can use this "slipstreamed" shared folder to install both Windows 2000 and the service pack together by using the integrated installation, thus saving time. For information on how to create and install the slipstreamed shared network folder, see Scenario 1: Installing Windows 2000 Integrated with the Service Pack later in this document.
The following table identifies additional command-line options that only the W2ksp3.exe program supports.
| Command-line option | Description |
|---|---|
| /X | Extracts service pack files without starting Update.exe.
You are prompted to provide the path for the folder to which you want to extract W2ksp3.exe. |
| /U /X:folder_name | Extracts service pack files to the <folder_name> folder without prompting you and without starting Update.exe. |
Planning the Deployment |
Back to Top |
To ensure a successful deployment of the service pack, prepare for your deployment by assessing the updates and enhancements contained in the service pack and determining how they affect your organization. After you have assessed deploying the service pack in your organization, complete these important planning tasks:
The following sections describe these tasks. For a complete list of and detailed information about deployment planning tasks and strategies, see the Microsoft Windows 2000 Server Resource Kit Deployment Planning Guide. This planning guide is an important tool to use as you design, plan, and develop your deployment of Windows 2000 as well as Windows 2000 service packs. The guide can help you gain insight into planning your deployment on both a project management level and a feature level. It addresses planning information that can help you get started, such as how to create a deployment plan and how to run a pilot project. It also provides important technical discussions that can help you deploy Windows 2000.
The service pack supports the following installation methods:
For more information about the update and integrated installation methods, see these sections later in this document:
After you select your installation method , review the corresponding scenario in the Installing Service Pack 3 for Windows 2000 section later in this document to determine the necessary deployment tools and files.
This section provides a brief overview of common deployment tools and files. For more detailed information about a specific deployment tool or file, see the Microsoft Windows 2000 Server Resource Kit Deployment Planning Guide.
Depending on the scenario you choose, you might need one or more of the following deployment tools and files:
Microsoft Systems Management Server (SMS) provides a variety of tools to help you deploy the service pack in your organization. With the SMS version 2.0 software distribution feature, you can automatically upgrade all of the SMS client computers in your organization with the new service pack. You can allow your users to run the service pack installation whenever they like, or you can schedule the service pack installation to run at a specific time. You can also schedule it to run on SMS client computers at a time when the users are not logged on.
Note
SMS provides tools for upgrading your current computers, but not for the installation of new computers that do not have an operating system already installed. Upgrades from other versions of Windows (including Windows NT 4.0) are possible with SMS.
Windows Installer is a Windows 2000 component that standardizes and simplifies the way you install and manage software programs (such as the service pack) on multiple computers. This system-resident installation service enables you to manage the installation, modification, repair, and removal of programs. Windows Installer facilitates consistent deployment, enabling you to manage shared resources, customize installation processes, make decisions about application usage, and resolve configuration problems.
Windows 2000 includes Windows Installer version 1.1. Installing SP3 automatically updates Windows Installer to version 2.0, which is also available independently from the microsoft.com Download Center Web site.
Note that after updating Windows Installer to version 2.0, you cannot remove it or roll it back to version 1.1, even if you remove the service pack.
Note
After you install a Windows 2000 service pack by using the Update.msi file, the service pack entry in Add/Remove Programs in Control Panel has a trailing 4-digit number in brackets (the language code). For more information on this issue, view article Q305134, "4-Digit Number Is Listed After the Windows Service Pack Entry in the Add Remove Programs Tool," in the Microsoft Knowledge Base.
For integrated installations only, the Unattend.txt answer file identifies how Windows 2000 Setup should interact with the distribution folders and files you create, and it supplies information about your preinstallation requirements. The answer file also supplies Setup with all of the information that the end user is prompted to provide during a typical Windows 2000 installation. For example, the Unattend.txt file contains a "FullName" entry in the [UserData] section. This entry instructs Windows 2000 Setup to prompt the user to provide a full name. You can create or modify the Unattend.txt file by using either a text editor or Setup Manager.
Important
Make sure that only the network administrator has write access to this file. For more information, see the Microsoft Windows 2000 Guide to Unattended Setup (Unattend.doc).
You can find information about automating your installation in the Windows 2000 Server Resource Kit Deployment Planning Guide included in the Support.cab file on the service pack CD.
The Cmdlines.txt file contains a list of the commands that run during Windows 2000 graphical user interface (GUI)-mode Setup. These commands can, for example, run an application setup command or another executable file. You can create the Cmdlines.txt file by using either a text editor (such as Notepad) or Setup Manager.
The Windows 2000 Resource Kit CD provides additional deployment and preinstallation tools that allow you to customize certain parts of the user interface and to provide information about your unique computer features and support programs. For example, the Microsoft System Preparation Tool (Sysprep.exe) enables you to perform legal imaging, disk duplication, automation of minisetup, and auditing.
Updated versions of these deployment and preinstallation tools are available from the Windows 2000 Downloads Web site.
Before you deploy the service pack in your organization, consider the upgrade paths supported by update and integrated installations:
You start the service pack installation either by double-clicking the W2ksp3.exe icon or by running Update.exe after extracting the contents of W2ksp3.exe by using a command-line option.
You run Windows 2000 Setup (Winnt.exe or Winnt32.exe) from an i386 shared distribution folder that was previously updated with SP3 by using the /S option (see The Integrated Installation earlier in this document).
The following table shows which Windows versions are and are not supported for these two types of SP3 installations.
| Windows version | Supported for update installations of Service Pack 3 | Supported for integrated installations of Service Pack 3 |
|---|---|---|
| Windows 95 | No | Yes |
| Windows 98 | No | Yes |
| Windows 98SE | No | Yes |
| Windows NT 3.51 | No | Yes |
| Windows NT 4.0 | No | Yes |
| Windows Millennium Edition | No | No |
| Windows 2000 Pro | Yes | No |
| Windows 2000 Server | Yes | No |
| Windows 2000 Advanced Server | Yes | No |
| Windows 2000 with Server Appliance Kit | Yes | No |
Disk space requirements vary according to the version of Windows 2000 you are installing: Windows 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server, or Windows 2000 with Server Appliance Kit. For specific information about the space you will need to install SP3 on a given version of Windows 2000, see the Readme file on the service pack CD.
Although Microsoft has a high degree of confidence in this service pack, we cannot test all possible hardware configurations and line-of-business (LOB) applications that might be present in all environments. Instead, we recommend that you test the service pack in your environment before you deploy it to all of your users.
Testing the service pack in your environment can include, but is not limited to, the following procedure.
To test the service pack in your environment
If you are installing Windows 2000 for the first time in your company or a particular division of your company, you might want to set up a pilot group to help test your deployment and verify that it works in your environment as expected.
For more information about planning for, testing, and deploying Windows 2000 in your environment, see the Windows 2000 Server Deployment and Planning Guide.
Compatibility modes provide an environment for applications that were designed to run on Windows 95, Windows 98, or Windows NT 4.0 Service Pack 5. These modes resolve several of the most common issues that prevent older applications from working correctly on Windows 2000. Applications that experience problems after the computer they are running on are upgraded from Windows 95 or Windows NT 4.0 to Windows 2000 might function better if they are started in one of these application compatibility environments.
Windows 2000 uses the compatibility modes to ensure compatibility with many popular applications. However, advanced users can also use this technology to provide solutions for their own applications. For more information on compatibility modes and how to use them, see article Q279792, "HOW TO: Enable Application Compatibility-Mode Technology in Windows 2000 Service Pack 2," in the Microsoft Knowledge Base. Note that although this article was written for SP2, it applies to SP3 as well.
SP3 includes significant enhancements and updates for Windows 2000 application-compatibility issues, including support for the Application Compatibility Toolkit, which you will find on the MSDN Application Compatibility Web site.
Compatibility modes are required primarily for user applications rather than for server applications. Because of this, compatibility updates are supplied with Windows 2000 Professional only. Windows 2000 Server and Windows 2000 Advanced Server users can install these compatibility updates from the Windows 2000 Compatibility Updates Web site.
Removing Visible Entry Points for Windows 2000 Components |
Back to Top |
This section explains how to remove Microsoft Internet Explorer, Outlook Express, or Windows Media Player visible entry points (such as shortcuts and menu entries) either during unattended Setup for Windows 2000 (using W2ksp3.exe or Update.exe) or while running Sysprep for Windows 2000. Note that the two procedures in this section do not remove any actual Windows code; they remove only the visible entry points for the individual components that you specify.
Each entry listed in the [Components] section in the Unattend.txt file uses the same two values: On and Off. For each item, select On to install it, or select Off not to install it.
To remove Internet Explorer, Outlook Express, or Windows Media Player visible entry points from Windows 2000 during unattended Setup, perform the following procedure.
To remove visible entry points during unattended Setup
[Components]
IEAccess = Off
OEAccess = Off
WMPOCM = OffTo remove Internet Explorer, Outlook Express, or Windows Media Player visible entry points from Windows 2000 after you have already installed the operating system, perform the following procedure.
To remove visible entry points during Sysprep
[Components]
IEAccess = Off
OEAccess = Off
WMPOCM = OffYou can use the same Unattend.txt file described in the preceding section (Removing Visible Entry Points During Unattended Setup), or you can use a separate file that contains only the [Components] section.
[GuiRunOnce]
sysocmgr /U:unattend.txt /Q /R /C /X
Installing Service Pack 3 for Windows 2000 |
Back to Top |
The following sections provide instructions for installing SP3. You can either update computers already running Windows 2000 or complete an integrated installation by installing Windows 2000 and the service pack together.
For either type of installation, administrative logon credentials are required. To install the service pack on a given computer or over a network, you must be logged on as an administrator.
During the update installation, the service pack is installed on a computer that is already running Windows 2000. When you run the Update.exe program, it automatically installs the updated system files and makes the necessary registry changes. After the computer is restarted, the installation is complete and Windows 2000 runs with an updated file set.
This section describes the steps involved in the following update installation scenarios:
Important
If a system file on a computer becomes corrupted or needs replacing for some other reason, you will need the service pack source files to replace that system file.
This service pack supports several types of distribution media, including CD-ROMs, shared folders on networks, and Web downloads. Because this guide is intended for corporate audiences, the update installation scenarios described in this document focus on the use of shared distribution folders on networks, which is the most common distribution medium for this audience.
Depending on your installation requirements, you can choose from the various update scenarios presented in this section.
Note
In all of the following procedures, "E:\" represents the drive name of the network or computer where your distribution folder is located.
This method enables you to set up a shared distribution folder on a network so that users can upgrade their computers from a central point and store their system backup files locally.
You can do this by starting the W2ksp3.exe program (setting whatever options you want to use). You can also create logon scripts for users, which will ensure that they can upgrade to SP3 when they next use their computers.
To install the service pack
For example, to create a distribution folder named SP3, type the following at the command prompt:
mkdir E:\SP3
This is an important first step, because real-time virus checkers could cause problems with the installation if they are running.
E:\SP3\W2ksp3.exe
You can include command-line options as needed. For example, if you want to install hotfixes immediately after installing SP3 and thus don't your computer to restart automatically at the completion of the SP3 installation, include the /Z option in the installation command.
If you want to install hotfixes, see the hotfix installation and deployment guide. You can restart the computer later so that SP3 and the hotfixes become fully operational at the same time.
Important
SP3 will not be fully operational until you restart your computer.
This scenario explains how to prepare a shared distribution folder on a network and install the service pack from it. Doing this enables you to store service pack source files in the shared distribution folder rather than on local computers. Note that the update installation method installs the service pack on computers that are already running Windows 2000.
Important
Because the service pack source files are kept 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 upgrading laptops.
You must use a shared distribution folder that was created specifically for SP3. 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 a computer might need to replace are available.
Extracting the files from W2ksp3.exe by using command line options can be useful if you want to use the distribution folder as the folder that contains the service pack source files. This saves disk space on local computers, as the installation would point to the distribution folder for ServicePackFiles rather than creating this folder locally. The ServicePackFiles folder is needed whenever Windows 2000 requires a service pack file, such as when Windows File Protection needs to restore a corrupted or tampered-with file or when an optional component is configured.
If you move the shared distribution folder, see article Q271484, "Files and Folders Are Added to Your System After Service Pack Is Installed," in the Microsoft Knowledge Base for more information.
If you are installing the service pack on a server cluster, you must first pause the node and move all groups running on it to another node. For complete instructions before installing the service pack, see article Q174799, "How to Install Service Packs in a Cluster," in the Microsoft Knowledge Base. If SQL Server is installed on the server cluster, see article Q239473, "PRB:70rebind.exe for Windows 2000 and MDAC Upgrades on Clustered SQL Server 7.0 Servers," in the Knowledge Base before installing the service pack.
For information about Kerberos support in SP3, see article Q235529, "Kerberos support on Windows 2000 Server Clusters," in the Microsoft Knowledge Base.
To install the service pack
This is an important first step, because real-time virus checkers could cause problems with the installation if they are running.
mkdir E:\SP3
W2ksp3.exe -x
You are then prompted to enter the path to the distribution folder you have created. Enter the full path to this folder — for example, E:\SP3 — to automatically extract the service pack files to that path.
If you have extracted the files first, use Update.exe. For example, to install the service pack from a distribution folder named SP3, type the following at the command prompt:
E:\SP3\i386\Update\Update.exe
If you did not extract the files first, use W2ksp3.exe. For example, to install the service pack from a distribution folder names SP3, type the following at the command prompt:
E:\SP3\W2ksp3.exe
After the installation is complete, restart the computer right away unless you want to install hotfixes immediately after the service pack installation.
If you want to install hotfixes, see the hotfix installation and deployment guide. You can restart the computer later so that SP3 and the hotfixes become fully operational at the same time.
Important
SP3 will not be fully operational until you restart your computer.
This scenario explains how to install the service pack from a shared distribution folder on a network by using SMS. This update installation method installs the service pack on SMS client computers that are already running Windows 2000.
Important
To do this type of installation, you must have SMS 2.0 with SP2 installed on your computer.
To install the service pack by using SMS
This scenario assumes that you have an understanding of SMS as well as a working knowledge of software distribution. Also, this section assumes that your SMS infrastructure is in place or that you will put an SMS infrastructure in place before you deploy the service pack. For more information about SMS, see the SMS 2.0 Administrator's Guide. For specific information about software distribution, see Chapter 12, "Distributing Software," in the SMS 2.0 Administrator's Guide.
For information about using SMS securely, see the security documentation on the Microsoft Systems Management Server Web site, including the "SMS Security Essentials" white paper.
A sample package definition file for Windows 2000 SP3 (W2ksp3.sms) is provided in the \Support\Tools folder on the service pack CD.
The first step in distributing software through SMS is to create the SMS package, which contains the files and instructions that direct the software distribution process. When you create the SMS package, you set up the location of the package source files (where SMS obtains the files) and the package definition file (.sms or .pdf) for distributing the service pack.
A package definition file is a specially formatted file that contains all of the information necessary to create the SMS package. If you import this file, SMS immediately creates the package. After you use a package definition file to create a package, you can modify it the same way you would modify any other SMS package.
Each predefined SMS package also contains SMS programs, which are command lines that run on each targeted computer to control the execution of the package. Each program is a different combination of options that you create for installing the package. For example, the package definition for the service pack includes programs to install the service pack with or without user input. These SMS programs must be compatible with the installation files for the package.
To create the SMS package
For example, to create a source files folder named SP3, type the following:
mkdir E:\SP3
For example, to copy the service pack executable files from the service pack CD in the CD-ROM drive (D:) to the SP3 source files folder, type the following:
xcopy D:\ E:\SP3 /e
Important
If you download a service pack from the Windows 2000 Service Pack 3 Web site, you must extract the compressed program file before you can copy it to the source files folder.
After you create the SMS package for the service pack, you can distribute the package to your distribution points. Distribution points are shared network folders from which SMS copies the package source files so that client computers can access these files.
To distribute the SMS package to the distribution points
Note
All of the distribution points for all sites are listed, so you can select all of the distribution points now. Be sure to specify a distribution point for every site that has clients that need SP3.
Note
Distribution points must have sufficient disk space for the SMS package. For instructions for using the SMS Administrator console to check the amount of disk space available on distribution points, see the SMS 2.0 Administrator's Guide.
After you distribute the SMS package to the distribution points, you can create the advertisement that offers the package to the SMS clients.
To create the advertisement
Note
For more information about creating a collection, see the SMS 2.0 Administrator's Guide.
The Distribute Software Wizard appears.
SMS clients refresh the list of advertised programs on a configurable polling interval; to the default interval is 60 minutes. After the service pack advertisement is received on a client, it appears (for selection by users) in the Advertised Programs Wizard in Control Panel, or, if the advertisement is assigned (mandatory), it runs on the specified schedule.
This scenario explains how to install the service pack from a shared distribution folder on a network by using Windows Installer. This installation method installs the service pack on computers that are already running Windows 2000.
This section assumes that you have a basic understanding of Windows Installer, as well as a working knowledge of Group Policy and Active Directory™. For more information about Windows Installer, Group Policy, or Active Directory, see the Microsoft Windows 2000 Professional Resource Kit or the Microsoft Windows 2000 Server Resource Kit (included in the Support.cab file on the service pack CD.
Note
If you plan to deploy the service pack using Group Policy, you are advised to follow the instructions given in article Q302430, "HOW TO: Assign Software to a Specific Group By Using a Group Policy," in the Microsoft Knowledge Base.
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 the Setup user interface. This package file describes the relationships among service pack features, components, and resources. The package file also contains an installation database, a summary information stream, and data streams for various parts of the service pack installation.
You can use the Software Installation and Maintenance feature in Windows 2000, which uses Windows Installer and the Update.msi file to create a Windows Installer package that installs the service pack. The Software Installation and Maintenance feature uses a Group Policy object (GPO) to deploy the package (on networked computers) within Active Directory containers, such as sites, domains, and organizational units that are associated with the GPO.
After you assign the package, Windows Installer installs the service pack automatically when the users start their computers. The users do not choose to install the service pack. Note that only a network administrator or someone who is logged on to a local computer as an administrator can remove the assigned software.
Important
Microsoft recommends that you use W2ksp3.exe when deploying Windows 2000 SP3 by using the command prompt. If you use Update.msi to distribute service packs, implement the distribution by using a computer-based GPO only. Microsoft does not support the use of user-based Group Policy deployments with Update.msi. User-based Group Policy deployments apply on a per-user basis. The installation of a service pack applies to the entire system. For more information, see article Q278503, "Best Practices for Using Windows 2000 Update.msi Package for Service Pack 1 Installation," in the Microsoft Knowledge Base.
Microsoft requires that you use the machine assigned distribution method when using Update.msi. There are no other methods available.
If the service pack installation does not get completed because of a power outage, a shutdown by a user, or some other reason, you must reinstall the GPO on the computers involved. You can determine whether the service pack installation was completed successfully by doing either of the following:
To work around an issue caused by the installation not being completed successfully, move the computers out of the scope of the service pack deployment to another organizational unit, restart the computers, move them back to the organizational unit that has the service pack deployed, and then restart the computers a second time. This redeploys the service pack to the client computers. You can use Active Directory Users and Computers to move the computers from one organizational unit to another.
Microsoft does not recommend removing earlier service packs from your computer before you install a new one. However, when you want to prevent the automatic installation of an earlier service pack on computers added to your organizational unit (for example, to prevent computers from being upgraded to Service Pack 2, because SP3 is now available), you can do so by performing the following procedure.
For information about removing service packs that were deployed with Group Policy, see Removing a Service Pack Deployed by Using Group Policy later in this guide.
To remove an earlier service pack
This procedure explains how to assign the service pack to computers managed by a GPO. For your installation, you might want to associate the GPO with a different Active Directory container. To assign the service pack to computers by using Group Policy, you must do the following:
Each of these procedures is explained in detail in the remainder of this section.
Note
If you used Add/Remove Programs to remove a service pack that was deployed by using the Update.msi program, you cannot automatically deploy it again by using Group Policy. For more information, see Removing a Service Pack Deployed by Using Group Policy later in this document.
Note
For the following procedure, "E:\" represents the drive of the network or computer where your distribution folder is located.
To create a shared network distribution folder
For example, to create a distribution folder named SP3, type the following:
mkdir E:\SP3
You must set the appropriate permissions to share your distribution folder so that users have read and execute access only and administrators have full-control access to the folder.
To create a group policy for SP3 deployments
The Active Directory Users and Computers snap-in includes tools for Group Policy and software installation and maintenance. You can use these snap-ins to assign the service pack to computers in an organizational unit. For more information, see the Microsoft Windows 2000 Server Resource Kit or the Microsoft Windows 2000 Professional Resource Kit.
To apply the group policy and deploy the service pack to the client computers
You can apply the service pack directly to the Windows 2000 installation files and complete an integrated installation by using a shared distribution folder on a network. It is also possible to create a CD to complete the installation after you have integrated the files.
Because the integrated installation replaces individual files, the space requirements for this installation type are practically identical to the space requirements for Windows 2000. For information on these requirements, see the Readme.doc file on the Windows 2000 CD.
The following scenario explains how to use Update.exe to build the integrated installation and how to run Windows 2000 Setup (Winnt32.exe) to install Windows 2000 with the service pack already applied.
Because this guide is intended for corporate audiences, the integrated scenario described in this document focuses on the use of shared distribution folders on networks, which is the most common distribution medium for this audience.
Important
You cannot remove a service pack that you installed together with Windows 2000 in an integrated installation.
This section describes the installation steps for the following integrated installation scenarios:
Depending on your installation requirements, you can choose from these two integrated installation scenarios, which are described in detail in the following sections.
Note
In the following procedures, "E:\" represents the drive name of the network or computer where your distribution folder is located.
This scenario explains how to create an integrated installation of Windows 2000 and the service pack in a shared distribution folder on a network. The integrated process installs the service pack during Windows 2000 Setup. To complete this procedure, you must use a computer that is running Windows 2000.
Note that to use the Setup Manager Wizard (setupmgr.exe) to install Windows 2000 integrated with SP3, you must first have an integrated Windows 2000 Service Pack 3 CD or create a shared distribution folder on the network, as explained in the following procedure.
Important
Do not update Windows 2000 integrated with a service pack in a shared distribution folder if there are users who are still using a previously installed integrated version in the same shared folder.
To create an integrated installation of Windows 2000 and the service pack
For example, to create a distribution folder named Win2000\i386, type the following:
mkdir E:\Win2000\i386
Ensure only the system administrator has full access to this folder. Other users should have only read and execute permissions.
For example, to copy the installation files and folders from the Windows 2000 CD in the CD-ROM drive (D:) to the distribution folder named Win2000\i386, type the following:
xcopy D:\i386 E:\Win2000\i386 /e
For example, to extract the service pack files located in the CD-ROM drive (D:) to your computer's hard disk (C:) in a folder called <SampleFolder>, type the following:
D:\W2ksp3.exe /x
In the Choose Directory For Extracted Files box, type C:\<SampleFolder>.
C:\<SampleFolder>\i386\Update\Update.exe -s:E:\Win2000
For a list of command-line options, see Command-Line Options for W2ksp3.exe and Update.exe earlier in this document.
You can now deploy Windows 2000 to your users' computers from the shared distribution folder in either attended or unattended Setup mode. Alternatively, you can burn a CD containing the files from the distribution folder. During the standard installation process, Windows 2000 Setup (Winnt.exe or Winnt32.exe) installs the updated operating system with the service pack already applied.
Important
When you run the Update.exe program as described earlier for an integrated installation, a Svcpack.log file is created automatically in systemroot on the computer that is running the Update.exe program. If you plan to update more than one version of Windows 2000 on this computer, rename the Svcpack.log file after you update each version. This ensures that you do not overwrite the current log file when you update additional versions of Windows 2000.
This scenario explains how to use Remote Installation Services (RIS) to install Windows 2000 integrated with the service pack. However, this section does not provide details on how to set up RIS. For more information about RIS, see the Step-by-Step Guide to Remote OS Installation.
There are two types of operating system images supported by Remote OS Installation: CD-based images and Remote Installation Preparation (RIPrep) images. The CD-based option is similar to setting up a client's operating system directly from the Windows 2000 CD, but in this case, the source files reside on a RIS server. The RIPrep image enables an administrator to configure a client computer exactly how he or she wants it and then make a copy of that image for installation on client computers connected to the network.
After you complete the installation of RIS on the server, perform the following steps to add an image of Windows 2000 integrated with the service pack to your RIS server.
To copy Windows 2000 integrated with SP3 to your RIS server
To perform this procedure, you must have an SP3 CD-based image of Windows 2000 Professional or Windows 2000 Server on your RIS server (see the preceding section, "Adding a Service Pack 3 Integrated CD-Based Image to a RIS Server").
To update existing RIPrep images
Note
You cannot use the /S option to integrate SP3 directly into an existing CD-based image or RIPrep image.
Installing the Service Pack 3 Debugging Symbol Files |
Back to Top |
The debugging symbol files are recommended for system administrators and other advanced users who will be diagnosing Windows 2000 system problems.
To use the SP3 debugging symbols successfully, you must have the Windows 2000 symbols installed on your computer before you install the SP3 symbols. If you do not already have these symbol files, you can download them from the How To Get Symbols page on the Microsoft Debugging Tools Web site.
To install the debugging symbol files for SP3, click here. During the installation, the SP3 debugging symbol files are copied over any existing versions of the debugging symbol files in the symbol installation folder.
Note
You do not need to have debugging symbols installed for your computer to operate properly.
You can also download symbols from How to Get Symbols page on the Microsoft Debugging Tools Web site. This page also contains information about the Microsoft Symbol Server, which enables you to download symbols on demand during a debugging session. For more information and to obtain the most current version of the debugging tools for Windows, see the Microsoft Debugging Tools Web site.
Removing the Service Pack |
Back to Top |
This section discusses the process of removing the service pack from your computer. If you want to remove the service pack, it is possible to restore your computer to its previous state. However, you cannot remove a service pack that was installed by means of an integrated installation.
When you run the Update.exe program to install the service pack, a subfolder named $ntservicepackuninstall$ is created in your systemroot folder.
You can remove the service pack either by using the command prompt or by using Add/Remove Programs in Control Panel.
Important
To remove the service pack by using Add/Remove Programs
Important
If you choose to remove SP3, a dialog box appears, listing the applications you installed since you upgraded to SP3. If you continue with the removal, these applications might not work correctly.
To remove the service pack by using the command prompt
When you use Add/Remove Programs to remove a service pack that was deployed by using the Update.msi program, you cannot automatically deploy it again by using Group Policy. Only the network administrator or a user who is logged on as an administrator is authorized to remove a service pack.
Update.msi is designed this way because a network administrator is likely to remove a service pack for good reason and does not want users who are connected to the network to have the service pack automatically reinstalled the next time they start their computers. After an administrator removes the service pack by using Update.msi, the only way to reinstall it on the computers involved would be to either deploy a newer version of it or manually reinstall the recently removed service pack from the service pack CD or from a shared network folder.
For more information, see article Q315141, "Nothing to Do" Error Message When You Try to Remove Service Pack from Add/Remove Programs," in the Microsoft Knowledge Base.
Automatic Updates for Windows 2000 |
Back to Top |
SP3 installs the Automatic Updates feature so that you can automatically receive critical Windows 2000 fixes as soon as they become available. If you choose to enable Automatic Updates, whenever your computer is online and Windows 2000 updates become available, a "balloon" message is displayed in the status area. A link is provided so that you can go straight to the updates you need.
You can configure your computer to receive these notifications if you are logged on as an administrator. Use Control Panel to select the options you want. If Automatic Updates is not configured within 24 hours after the service pack is installed, the network administrator or whoever is logged on locally as an administrator will be prompted to configure it. Automatic Updates will not download any updates until someone has configured it to do so.
Network administrators can configure Automatic Updates by using Group Policy.
To configure Automatic Updates by using Group Policy
The Configure Automatic Updates policy is now displayed on your screen. This policy dictates whether a given computer will receive security updates and other important downloads through the Windows Automatic Updates feature. Using this policy, you can specify whether or not Automatic Updates is enabled.
When Windows 2000 finds updates that apply to this computer, an icon appears in the status area, along with a message that the updates are ready to be downloaded. Clicking the icon or the message will display the option you use to select the updates you want to download. Windows 2000 then downloads the selected updates in the background. When the download is complete, the icon appears in the status area again, along with a message that the updates are ready to be installed. Clicking the icon or the message will display the option you use to select the updates you want to install.
Windows 2000 finds updates that apply to your computer and downloads these updates in the background (the user is not notified or interrupted during this process). When the download is complete, the icon appears in the status area, along with a message that the updates are ready to be installed. Clicking the icon or the message will display the option you use to select the updates you want to install.
Specify the schedule by using the options in the Group Policy Settings dialog box. If there is no schedule specified, the default schedule for all installations is every day at 3:00 A.M. If any of the updates require that your computer be restarted to complete the installation, Windows 2000 will restart the computer automatically. (If a user is logged on to the computer when Windows 2000 is ready to restart it, the user will be notified of this and given the option to delay the restart.)
If you select option 4, you can set a recurring schedule. If there is no schedule specified, all updates be downloaded and installed every day at 3:00 A.M.
You can also select either the Disabled or Not Configured option:
Copyright |
Back to Top |
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 2002 Microsoft Corporation. All rights reserved.
Microsoft, Active Directory, Outlook, Windows, Windows Media, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
This product contains graphics filter software; this software is based in part on the work of the Independent JPEG Group.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.