Terminology Used in This Guide
Contents of the Service Pack 4 CD
Web Site Information for This Service Pack
Updates Included in This Service Pack
Identifying Deployment Tools and Files
Determining Your Deployment Options
Testing the Deployment in Your Environment
Evaluating Application Compatibility Modes
Removing Visible Entry Points for Windows 2000 Components (Optional)
Removing Visible Entry Points During Unattended Setup
Removing Visible Entry Points During Sysprep
Installing Service Pack 4 for Windows 2000
Installing the Debugging Symbol Files for Service Pack 4
Removing a Service Pack Deployed by Using Group Policy
About This Guide |
Back to Top |
This guide provides instructions for administrators who want to install Service Pack 4 (SP4) for Microsoft® Windows® 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server, or Windows 2000 with Server Appliance Kit. The guide includes technical details, procedures, and recommendations for installing the service pack on multiple computers in a small business or a corporate environment.
This guide also provides information about the most common scenarios for installing the service pack either as a standalone installation or as an installation that is integrated 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.
If you are a Windows 2000 Datacenter Server customer, contact your OEM for information on how to deploy service packs on your computers.
This guide assumes that you have a working knowledge of Windows 2000 and service pack installations. Although this guide provides some basic operating system information, it is not a replacement for either the Windows 2000 documentation or formal training. Rather, it is intended to complement these sources of information.
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 guide.
The Microsoft Windows 2000 Service Pack 4 Web site provides links from which you can install SP4. It also provides links to other documents and information about SP4, including a list of known issues, release notes for SP4, and updated versions of this guide. You can find this information under Learn More on the Windows 2000 Service Pack 4 Web site.
This guide includes the following main sections:
This section provides an introduction to SP4. It also describes additional resources that you can use to plan your service pack deployment.
This section identifies the important steps for planning your service pack deployment. It includes information about installation methods, deployment tools and files, Windows versions that you can update to SP4 or upgrade to Windows 2000 with SP4, and methods you can use to test the deployment in your environment.
This section explains how to remove visible entry points (such as shortcuts and menu entries) for Microsoft Internet Explorer, Outlook® Express, or Windows Media® Player, either during unattended Setup for Windows 2000 or while running Sysprep for Windows 2000.
You can perform either a standalone installation of SP4, in which only the service pack is installed, or an integrated installation, in which Windows 2000 and SP4 are installed together.
This section explains how to perform a standalone installation of the service pack and includes step-by-step instructions for the following scenarios:
This section explains how to create an integrated installation and then install Windows 2000 together with the service pack. This section provides step-by-step instructions for the following scenarios:
Note
For details about the combination installation (installing hotfixes with Windows 2000, the service pack, or both), see the Microsoft Windows 2000 Hotfix Installation and Deployment Guide.
This table in this section provides definitions for a few specialized terms that are used in this guide. The terms are specific to service pack installations, Windows 2000, or both. It is important that you understand these terms before you proceed.
| 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 SP4). You can also create an integrated version of Windows 2000 operating system files with SP4. |
For additional information about Windows 2000 and SP4, see the following resources:
About This Service Pack |
Back to Top |
This service pack is a collection of updates to Windows 2000. SP4 is a recommended update because it includes fixes that can improve how some programs run with Windows 2000.
This section provides information about the following topics:
The SP4 CD includes the following:
W2ksp4.exe is a self-extracting compressed file. You can extract all of the files that W2ksp4.exe contains. You can then use the Command-Line Options for W2ksp4.exe and Update.exe to specify the type of installation you want.
For example, you can extract all of the files to a shared network folder and then use Update.exe (also included on the Service Pack 4 CD) to update individual computers.
If you run W2ksp4.exe without command-line options, all of the SP4 files will be installed on the local computer, which is the default installation location.
The Service Pack 4 CD also contains the following documents and tools for advanced users and administrators:
For more information about 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 about how to use them, and additional information about performing an unattended Setup.
For more information about the Windows 2000 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 812809, "Service Pack 4 Adds Updates to Several Windows 2000 Support Tools," in the Microsoft Knowledge Base.
Note
If you are a Windows 2000 Datacenter Server customer, contact your original equipment manufacturer (OEM) for updated support tools.
All files and programs included on the Service Pack 4 CD are also available on the Web. To view a list of fixes included in the service pack, see the Microsoft Windows 2000 Service Pack 4 Web site. The list includes the files affected by SP4, known issues, and general release notes for the service pack. You can find this information under Learn More on the Web site.
There are also two installation options available from the Web site: the Express installation and the Network installation. Both installations provide you with the same software. For administrators installing SP4 on multiple computers, the Network installation is the best option.
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 Microsoft Windows 2000 Service Pack 4 Web site. The remaining files that 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 must be updated, the download time is significantly reduced.
This is self-extracting package contains all of the files that are required for any computer running Windows 2000 to update to SP4. This installation option downloads all of the SP4 files to your computer from the Microsoft Windows 2000 Service Pack 4 Web site. This option is designed 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 update to SP4, Microsoft provides extensive documentation about the service pack. You will find the current list of fixes and general release note items (for example, space requirements for installing SP4) under Learn More on the Microsoft Windows 2000 Service Pack 4 Web site.
The service pack is a collection of updates for Windows 2000. These updates address the following areas of functionality:
This section describes the functionality included in SP4.
After you have installed the service pack, it is not necessary to reinstall it if you add a device or software to your computer. For example, Windows 2000 includes a file named Driver.cab that contains all of the files potentially installed by Plug and Play–class installers. Setup and other components use this file to install the drivers for new devices (for example, a PCMCIA adapter or a Universal Serial Bus keyboard) without requiring access either to the Windows 2000 CD or to installation files on 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 Sp4.cab. This file contains only updated versions of drivers that exist in the original Driver.cab file from Windows 2000. In addition to the Sp4.cab file, the Update.exe program installs Drvindex.inf, which points to Sp4.cab for all of the updated drivers and 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 Microsoft Windows NT 4.0 and then reinstall it there, you must reinstall the service pack after you reinstall TCP/IP. This reinstallation 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.
For more information about this, see article 274215, "Not Necessary to Reinstall Windows 2000 Service Packs After System State Changes," in the Microsoft Knowledge Base.
If you 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 guide.
The Update.exe program creates a log file named Svcpack.log in systemroot. This log file contains the following information:
Beginning with Service Pack 2 for Windows 2000 (SP2), 128-bit encryption is supported as the default standard, and installing SP2, SP3, or SP4 automatically updates your computer from 56-bit encryption if it has not been updated already. For more information about support for 128-bit encryption in the service pack, see the documents under Learn More on the Windows 2000 Service Pack 3 Web site and the page titled "128-bit Encryption Becomes the Default in Windows 2000 Service Pack 2 (SP2)" on the Microsoft Windows 2000 Web site.
For information about Kerberos support in SP4, see article 235529 "Kerberos Support on Windows 2000–Based Server Clusters," in the Microsoft Knowledge Base.
Note
Removing SP4 does not cause your computer to revert to 56-bit encryption. You can remove SP4 at any time, but your computer will retain support for 128-bit encryption unless you reformat the hard drive and reinstall Windows 2000 or Windows 2000 with SP1.
To deploy the service pack, you can run W2ksp4.exe, which extracts the installation files for SP4. Update.exe then 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 W2ksp4.exe and Update.exe programs support. You can include one or more options that you want to use when you type the command to extract files from W2ksp4.exe. The options are passed to Update.exe. They dictate the specifics of the installation process. The options do not affect the way the files are extracted, however.
All of the options listed in the following table use a forward slash (/), but you can use a hyphen (-) instead. 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 during the installation process. |
| /Q | Uses quiet mode, which is the same as unattended mode except that the user interface is hidden. If you use this option, no prompts will appear during the installation process. |
| /F | Forces other applications to close when the computer restarts after the installation. |
| /N | Does not back up files for removing the service pack. |
| /O | Overwrites OEM files without prompting. |
| /Z | Does not restart the computer after the installation is completed. |
| /L | Lists installed hotfixes. |
| /S:foldername | Combines Windows 2000 with SP4 in a shared distribution folder for an integrated installation. |
| /D:foldername | Backs up files into the specified folder. |
You can use these options to install the service pack as follows:
W2ksp4.exe /U
When you use /U, all of the default options are used during the service pack installation. This installation does not prompt you for any input, but it displays a progress bar throughout the installation process.
W2ksp4.exe /Q
This option installs SP4 the same way it does for an unattended installation. However, neither the progress bar nor any errors that might occur appear during this installation.
W2ksp4.exe /F
After the installation is completed, you must close all applications and then restart 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 except /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).
W2ksp4.exe /N
If you specify this option, the files that are required to remove the service pack will not be backed up during the installation. No entry will be created in Add/Remove Programs for removing the service pack later. Although this option can help save disk space, it prevents you from being able to remove the service pack later, even from the command line.
You can use this option in conjunction with other command-line options except /S (used for integrated installation mode) and /L (used to list installed hotfixes).
W2ksp4.exe /O
W2ksp4.exe /Z
Use this option if you want to install hotfixes after installing the service pack and therefore do not want your computer to restart automatically after the service pack is installed. You can use this option in conjunction with other command-line options except /S (used for integrated installation mode) and /L (used to list installed hotfixes). After you have installed the hotfixes, restart the computer immediately to complete the service pack installation process.
W2ksp4.exe /L
Use this option if you want to display all of the hotfixes that are installed on the computer. This option is not designed for use with any other options.
Qfecheck.exe
For more information about the Qfecheck.exe program, see the following:
w2ksp4.exe /S:foldername
If you want to deploy Windows 2000 with SP4 as an integrated installation, you can use this option to build an integrated shared network folder that contains files for Windows 2000 and SP4. You can use this shared folder to save time by installing Windows 2000 and the service pack together. For information on how to deploy Windows 2000 with SP4 as an integrated installation (sometimes called "slipstreaming"), see Scenario 1: Installing Windows 2000 Integrated with the Service Pack later in this guide.
w2ksp4.exe /D:foldername
If you back up files but do not specify a folder, the files will be backed up to the default location:
$ntservicepackuninstall$
The following table identifies additional command-line options that only the W2ksp4.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 W2ksp4.exe. |
| /U /X:foldername | Extracts service pack files to the specified folder without starting Update.exe or prompting you. |
Planning Your Deployment |
Back to Top |
To help ensure that your deployment of the service pack is successful, you should prepare for your deployment by first assessing the updates and enhancements contained in the service pack. You should then determine how those changes would affect your organization. After this assessment, complete these other important planning tasks:
The following sections describe these planning 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 guide is an important tool for designing, planning, and developing your deployment of Windows 2000 and its service packs. This guide can help you understand what is involved in planning your deployment at both a project-management level and a feature level. It provides 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 information that can help you deploy Windows 2000.
The service pack supports the following types of installation:
After you determine which type of installation best suits your organization, review the corresponding scenario in the Installing Service Pack 4 for Windows 2000 section later in this guide to determine the deployment tools and files that your installation requires.
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 type of installation 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 software distribution feature of SMS version 2.0, you can automatically update 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 your users are not logged on.
Note
SMS provides tools for upgrading computers that have other versions of Windows installed (including Windows NT 4.0), but it does not provide tools for installing operating systems on computers that have no operating system already installed.
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 computers that are running Windows 2000. You can use Windows Installer to manage program installation, modification, repair, and removal. Windows Installer facilitates consistent deployment, which enables you to manage shared resources, customize installation processes, make decisions about application usage, and solve configuration problems.
Windows 2000 includes Windows Installer version 1.1. Installing SP3 or SP4 automatically updates Windows Installer to version 2.0, which you can also download from the Download Center on the Microsoft Web site.
Note
After you install Windows Installer version 2.0, you cannot revert to version 1.1, even if you remove the service pack.
For integrated installations only, the Unattend.txt answer file identifies how Windows 2000 Setup should interact with the distribution folders and files that you create. It also provides information about your preinstallation requirements. In addition, the answer file also provides Setup with all of the information that the end user is prompted to provide during a typical Windows 2000 installation. 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) in Deploy.cab in the \Support\Tools folder of the Service Pack 4 CD.
For information about automating your installation, see the Windows 2000 Server Resource Kit Deployment Planning Guide, which is included in the Support.cab file in the \Support\Tools folder of the Service Pack 4 CD.
The Windows 2000 Resource Kit CD provides additional deployment and preinstallation tools that you can use to customize certain parts of the user interface. For example, you can use the Microsoft System Preparation Tool (Sysprep.exe) to perform legal imaging, disk duplication, the automation of mini-setup, 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, you should consider the following installation types and the versions of Windows they support:
To start the service pack installation, you can either double-click the W2ksp4.exe icon, or you can use a command-line option to extract the contents of W2ksp4.exe and then run Update.exe.
To perform an integrated installation, you run Windows 2000 Setup (Winnt.exe or Winnt32.exe) from an i386 shared distribution folder that you previously updated with SP4. This update is performed by using the /S option (see The Integrated Installation earlier in this guide) with W2ksp4.exe or Update.exe.
The following table shows which versions of Windows are and are not supported for each of these two types of installations.
| Windows version | Supported for standalone installations of SP4 | Supported for integrated installations of SP4 |
|---|---|---|
| Microsoft Windows 95 | No | Yes |
| Windows 98 | No | Yes |
| Windows 98 Second Edition | No | Yes |
| Windows NT 3.51 | No | Yes |
| Windows NT 4.0 | No | Yes |
| Windows Millennium Edition | No | No |
| Windows 2000 Professional | 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 which 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 that is required to install SP4 on a particular version of Windows 2000, see article 813432, "Release Notes for Windows 2000 Service Pack 4," in the Microsoft Knowledge Base .
Although Microsoft has a high degree of confidence in this service pack, it is not possible to test all possible hardware configurations and line-of-business (LOB) applications that might be present in all environments. We therefore 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 exhibit problems after the computers on which they are running are upgraded from Windows 95 or Windows NT 4.0 to Windows 2000 might function better if they are started in an application compatibility environment.
Windows 2000 uses 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 279792, "HOW TO: Enable Application Compatibility-Mode Technology in Windows 2000 SP2 and SP3," in the Microsoft Knowledge Base. Although this article was written for SP2 and SP3, it applies to SP4 as well.
Removing Visible Entry Points for Windows 2000 Components (Optional) |
Back to Top |
This section explains how to remove visible entry points (such as shortcuts and menu entries) for Internet Explorer, Outlook® Express, or Windows Media® Player, either during unattended Setup for Windows 2000 (using Winnt.exe or Winnt32.exe), or while running Sysprep for Windows 2000.
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 or Off.
| On | Installs the item. |
| Off | Does not install the item. |
To remove visible entry points for Internet Explorer, Outlook Express, or Windows Media Player from Windows 2000 during unattended Setup, perform the following procedure.
To remove visible entry points for Internet Explorer, Outlook Express, or Windows Media Player
The following sample code shows how to modify the [Components] section of the Unattend.txt file to remove visible entry points:
[Components]
IEAccess = Off
OEAccess = Off
WMPOCM = OffTo remove visible entry points for Internet Explorer, Outlook Express, or Windows Media Player from Windows 2000 after you have already installed the operating system, perform the following procedure.
To remove visible entry points for Internet Explorer, Outlook Express, or Windows Media Player
[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 /I:%windir% \inf\sysoc.inf /U:%systemdrive%\sysprep\unattend.txt /X /Q /R /C
Installing Service Pack 4 for
|
Back to Top |
The following sections provide instructions for installing SP4. You can either update computers that are already running Windows 2000 by performing a standalone installation of SP4, or you can install Windows 2000 and the service pack together by performing an integrated installation.
For either type of installation, administrative logon credentials are required. To install the service pack locally or over a network, you must be logged on as a member of the Administrators group on that computer.
During a standalone 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 how to complete a standalone installation for each of the following scenarios:
Important
If it becomes necessary to replace a system file because it has become corrupted or for some other reason, you must have the service pack source files in order to do so.
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 standalone installation scenarios described in this guide focus on the use of shared distribution folders on networks, which is the most common distribution medium for this audience.
Your particular installation requirements will determine which of the standalone installation scenarios presented in this section you should use.
When you use this method, you set up a shared distribution folder on a network so that users can update their computers from a central point and store their system backup files locally.
You can do this by starting the W2ksp4.exe program and specifying the options you want. You can also create logon scripts for users, which will ensure that they can update their computers to SP4 when they next use their computers.
Note
In the following procedure, Drive represents the drive letter of the network or computer where your distribution folder is located.
To install the service pack
For example, to create a distribution folder named SP4, type the following at the command prompt:
mkdir Drive:\W2KSP4
This is important because if real-time virus checkers are running, they can cause problems with the installation.
\\servername\W2KSP4\W2ksp4.exe
You can include command-line options as needed. For example, if you want to install hotfixes immediately after installing SP4, and therefore do not want your computer to restart automatically after SP4 is installed, specify the /Z option in the installation command.
Important
SP4 will not be fully operational until you restart your computer.
This scenario explains how to prepare a shared distribution folder on a network and then install the service pack from that folder. Doing this enables you to store service pack source files in the shared distribution folder rather than on local computers.
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; this method is not suitable for updating laptop computers.
You must use a shared distribution folder that was created specifically for SP4. Do not reuse a folder that was set up for a previous service pack. Shared distribution folders for service pack source files must be permanent to ensure that all of the files that a computer might need to replace are available.
It can be useful to use command-line options to extract the files from W2ksp4.exe if you want to use the distribution folder to contain the service pack source files. This saves disk space on local computers because the installation points 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 must restore a file that has been corrupted or tampered with, or when an optional component is configured.
For more information about moving the shared distribution folder, see article 271484, "Files and Folders Are Added to Your System After Service Pack Is Installed," in the Microsoft Knowledge Base.
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, see article 174799, "How to Install Service Packs in a Cluster," in the Microsoft Knowledge Base before you install the service pack. If Microsoft SQL ServerTM is installed on the server cluster, see article 239473, "FIX:70rebind.exe for Windows 2000 and MDAC Upgrades on Clustered SQL Server 7.0 Servers," in the Microsoft Knowledge Base.
For information about Kerberos support in SP4, see article 235529, "Kerberos Support on Windows 2000-Based Server Clusters," in the Microsoft Knowledge Base. This article was written for SP3, but it also applies to SP4.
Note
In the following procedure, Drive represents the drive letter of the network or computer where your distribution folder is located.
To install the service pack
For example, to create a distribution folder named W2KSP4, type the following at the command prompt:
mkdir Drive:\W2KSP4
Drive:\w2ksp4.exe /x:Drive:\W2KSP4
This is important because if real-time virus checkers are running, they can cause problems with the installation.
For example, to install the service pack from a distribution folder named SP4, you would use the following command:
\\servername\W2KSP4\i386\update\update.exe
Important
SP4 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 Microsoft Systems Management Server (SMS). This installation method installs the service pack on SMS client computers that are already running Windows 2000.
Important
To perform this type of installation, you must have SMS 2.0 with Service Pack 2, Service Pack 3, or Service Pack 4 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. In addition, 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 Systems Management Server 2.0 Administrator’s Guide. For specific information about software distribution, see Chapter 12, "Distributing Software," in that guide.
For information about using SMS securely, see the security documentation on the Microsoft Systems Management Server Web site, including the white paper, "SMS Security Essentials," on the Microsoft Web site.
A sample package definition file for Windows 2000 SP4 (W2ksp4.sms) is provided in the \Support\Tools folder on the Service Pack 4 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 create the package, you can modify it in the same way that 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. You can choose the command-line options you want to use to install the package. For example, the package definition for the service pack includes programs you can use to install the service pack with or without user input.
To create the SMS package
To create a package on a site
The Create Package From Definition Wizard appears.
To check and modify the options that control the execution of your program, click the Requirements, Environment, and Advanced tabs, and then click OK to finish.
Note
For more information about the options that are available on the Requirements, Environment, and Advanced tabs, see the Systems Management Server 2.0 Administrator’s Guide.
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.
Important
Distribution points must have sufficient disk space for the SMS package. For instructions on how to use the SMS Administrator console to determine the amount of disk space available on distribution points, see the Systems Management Server 2.0 Administrator’s Guide.
To distribute the SMS package to the distribution points
The New Distribution Points Wizard appears.
Note
All of the distribution points for all sites are listed, so you can specify all of the distribution points now. Specify a distribution point for every site that has clients on which you want to install SP4.
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
The Distribute Software Wizard appears.
SMS clients refresh the list of advertised programs on a configurable polling interval. The default interval is one hour.
After a client receives the service pack advertisement, if the advertisement is not assigned (not mandatory), it appears for selection by users in the Advertised Programs Wizard in Control Panel. If the advertisement is assigned, (mandatory) it runs on the specified schedule.
In the console tree, under Site Database, click Advertisements to see the advertisement you created. Click the advertisement you created if you want to make changes to any of the settings.
Note
For more information about creating a collection, see the Systems Management Server 2.0 Administrator’s Guide.
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.
Note
If you plan to deploy the service pack by using the Group Policy snap-in, you should follow the instructions given in article 302430, "HOW TO: Assign Software to a Specific Group By Using a Group Policy," in the Microsoft Knowledge Base.
This section assumes that you have a basic understanding of Windows Installer, as well as a working knowledge of Group Policy and the Microsoft Active Directory® directory service. For more information about Windows Installer, Group Policy, or Active Directory, see the Microsoft Windows 2000 Server Resource Kit (deploy.chm), which is included in the file Support.cab file in the \Support\Tools folder on the service pack CD.
The Windows Installer package file (Update.msi) contains all of the information that Windows Installer requires to install or remove the service pack and to run Setup. This package file describes the relationships among service pack 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 deploy SP4 to the computers that are running Windows 2000 in your organization. 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 users start their computers. Users do not choose to install the service pack. Only a network administrator or someone who is logged on to a local computer as a member of the Administrators group on that computer can remove the assigned software.
Important
We recommend that you use W2Ksp4.exe when deploying SP4 from the command prompt. If you use Update.msi to distribute service packs, you must use only a computer-based (machine-assigned) GPO. The use of user-based Group Policy deployments with Update.msi is not supported. For more information, see article 278503, "Best Practices for Using Update.msi to deploy Service Packs," in the Microsoft Knowledge Base.
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, see article 305134, "4-Digit Number Is Listed After the Windows Service Pack Entry in the Add Remove Programs Tool," in the Microsoft Knowledge Base.
If the service pack installation is not completed because of a power outage, a shutdown by a user, or for some other reason, you must reinstall the GPO on the computers involved. To determine whether the service pack installation completed successfully, run Winver.exe. You can then view details about the Windows version and any service packs that are running on your computer. If the service pack has not deployed, open the Group Policy snap-in, and then open the Group Policy object (GPO). Click the package, click Action, click All Tasks, and then click Redeploy Applications.
We do not recommend removing earlier service packs from your computer before you install a new one. However, if 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 updated to SP3 because SP4 is now available), you can do so by performing the following procedure, "To remove earlier service packs."
For information about removing service packs that were deployed by using 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 use Group Policy to assign the service pack to computers, you must do the following:
Each of these procedures is explained in detail in the remainder of this section.
Important
If you have 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 guide.
Note
For the following procedure, Drive represents the drive letter 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 SP4, type the following:
mkdir Drive:\W2KSP4
You must set the appropriate permissions to share your distribution folder so that users have only Read and Execute permissions, and members of the Administrators group have full-control access to the folder.
Drive:\SP4\W2ksp4.exe /X
and then press ENTER.To create a Group Policy for SP4 deployments
The Active Directory Users and Computers snap-in includes tools for Group Policy and software installation and maintenance. You can use this snap-in 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. You can also 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 almost identical to the space requirements for Windows 2000. For information on these requirements, see article 813432, "Release Notes for Windows 2000 Service Pack 4, " in the Microsoft Knowledge Base.
Scenario 1 in this section explains how to use Update.exe to create an integrated installation. It also explains 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 guide 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 as part of 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.
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.
To use the Setup Manager Wizard (Setupmgr.exe) to install Windows 2000 integrated with SP4, you must first have an integrated Windows 2000 with Service Pack 4 CD, or you must create a shared distribution folder on the network, as explained in the following procedure.
Important
Do not create an installation of Windows 2000 integrated with a service pack in a shared distribution folder if users are still using a previously installed integrated version in the same shared folder.
Note
In the following procedure, Drive represents the drive letter of the network or computer where your distribution folder is located.
To create an integrated installation of Windows 2000 and the service pack
For example, to create a distribution folder named W2000\i386, type the following:
mkdir Drive:\W2000\i386
Ensure that 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 product CD in the CD-ROM drive (D:) to the distribution folder named W2000\i386, you would type the following:
xcopy /E D:\i386 Drive:\W2000\i386
w2ksp4.exe /S:Drive:\W2000
For a list of command-line options, see Command-Line Options for W2ksp4.exe and Update.exe earlier in this guide.
For more information about how to do this, you can view Help by entering the following the command from the deployment folder:
\i386\winnt32.exe /?
For more detailed information, see the Winnt32.exe command syntax topic in the Microsoft Windows 2000 Professional Resource Kit.
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 write the files from the distribution folder to a CD. 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. This section does not provide details on how to set up RIS, however. Rather, it focuses on adding a new image (Windows 2000 integrated with service pack) to an existing RIS server. For more information about RIS, see the "Step-by-Step Guide to Remote OS Installation” on the Microsoft Web site.
Remote OS Installation supports two types of operating system images: CD-based images and Remote Installation Preparation (RIPrep) images. The CD-based option is similar to setting up a client operating system directly from the Windows 2000 product CD, but in this case, the source files reside on a RIS server. You can use a RIPrep image to configure a client computer (with Remote OS Installation and any preinstalled programs and tools) exactly how you want it, and then copy that image for installation on client computers that are connected to the network. To store a RIPrep–based image on a server, at least one CD-based image must also be stored on the same RIS server.
After you install RIS on a server, perform the following steps to add an image of Windows 2000 integrated with the service pack to that server.
To copy Windows 2000 integrated with SP4 to a RIS server
To perform this procedure, you must have a CD-based image of Windows 2000 Professional or Windows 2000 Server with SP4 on your RIS server. (See the preceding section, "Adding a Service Pack 4 Integrated CD-Based Image to a RIS Server.")
To update existing RIPrep images
Note
You cannot use the /S option with Update.exe to integrate SP4 directly into an existing CD-based image or RIPrep image.
Installing the Debugging Symbol Files for Service Pack 4 |
Back to Top |
The debugging symbol files are recommended for system administrators and other advanced users who diagnose Windows 2000 system problems.
To use the SP4 debugging symbols successfully, you must have the Windows 2000 symbols installed on your computer before you install the SP4 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 SP4, double-click the following file:
\support\debug\symbols\i386\symbols_sp.exe
During the installation, the SP4 debugging symbol files overwrite any existing files in the symbol installation folder.
You can also download symbols from the "How To Get Symbols" page on the Microsoft Debugging Tools Web site. This page also contains information about the Microsoft Symbol Server, from which you can 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.
Note
It is not necessary for you to install the debugging symbols for your computer to operate properly.
Removing the Service Pack |
Back to Top |
This section provides information about how to remove the service pack from your computer. If you want to remove the service pack, you can restore your computer to its previous state.
Important
If you want to remove a service pack that was installed through an integrated installation, you must first reformat the hard drive. You can then perform a clean installation of Windows 2000 that is not integrated with SP4. If you want to revert to Windows 2000 with SP3, after you reformat your hard drive, you can perform an integrated installation of Windows 2000 with SP3.
When you run the Update.exe program to install the service pack, a subfolder named $ntservicepackuninstall$ is created in your systemroot folder.
If you installed the service pack using a scenario from The Standalone Installation section, you can remove it by using either the command prompt or Add/Remove Programs in Control Panel.
Important
If you install any applications or services that require the service pack, removing the service pack can adversely affect those programs.
If you turned off the automatic backup option for Update.exe, you cannot remove the service pack unless you reformat the hard drive and perform a clean installation of Windows 2000.
If you install Internet Explorer after you install the service pack, the service pack will not appear in Add/Remove Programs. If you want to be able to use Add/Remove Programs to remove the service pack, you must install Internet Explorer before you install the service pack.
To remove the service pack by using Add/Remove Programs
Important
If you choose to remove SP4, a dialog box appears that lists the applications you have installed since you updated your computer to SP4. If you continue to remove SP4, 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 the Group Policy snap-in. Only the network administrator or a user who is logged on as a member of the Administrators group on the local computer 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 probably 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 uses Update.msi to remove the service pack, the only way to reinstall it on the computers involved is to either deploy a newer version of it, or manually reinstall the recently removed service pack, either from the service pack CD or from a shared network folder.
For more information, see article 315141, "'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 |
If you have SP3 or SP4 installed, you can automatically receive critical Windows 2000 fixes as soon as they become available. For information about using this option, see the Microsoft Windows 2000 Service Pack 3 Installation and Deployment Guide under Learn More on the Windows 2000 Service Pack 3 Web site.
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.
© 2003 Microsoft Corporation. All rights reserved.
Microsoft, Windows, Windows NT, Outlook, Windows Media, and Active Directory 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.