Installing Windows 2000 with Hotfixes

This scenario explains how to create a combination installation of Windows 2000 integrated with SP3 and post-SP3 hotfixes in a shared distribution folder on a network. You do not need to perform separate installations of either Windows 2000 or the Windows 2000 hotfixes.

Important

An attempt to slipstream an SP3 hotfix into an integrated SP3 shared distribution folder might cause Windows 2000 to stop working (because of the SP3.cat file getting overwritten and SP3 files becoming untrusted). For more information on this issue, see article Q290074, "Slipstreaming Earlier Fixes Into an Integrated Installation Share Breaks the Share," in the Microsoft Knowledge Base.

Important

                     This process installs the Windows 2000 hotfixes during Windows 2000 Setup.

                     Because Windows 2000 Setup requires the 8.3 naming convention for all files and folders in the distribution folder, you must change the hotfix file names (from Q######_XXX_YYY_ZZZ_LL to Q######).

Preparing for the Installation

Before you run Windows 2000 Setup to deploy the installation of Windows 2000 and the Windows 2000 hotfixes across a network, you must copy the Windows 2000 and Windows 2000 hotfix installation files to a shared distribution folder and complete the following tasks.

If you are an OEM and plan to install any additional OEM files (for example, device driver, application, or component files) on the destination computers, create a \$1 subfolder within the \$OEM$ subfolder. The \$1 subfolder maps to systemdrive, the destination drive for the Windows 2000 installation.

Note

In the following procedure, "E:\" represents the drive name of the network or computer where your distribution folder is located.

To install Windows 2000 integrated with SP3 and Windows 2000 hotfixes

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

2.     Create an \i386 distribution folder by typing the following (using the appropriate drive name):

mkdir E:\i386

3.     Use the command-line utility xcopy to copy the files and subfolders from the Windows 2000 integrated SP3 installation CD to the E:\i386 folder. For example, if D: is your CD-ROM drive, type the following:

xcopy /e /i /v d:\i386 e:\i386

4.     Edit E:\i386\dosnet.inf to add svcpack to the [OptionalSrcDirs] section as follows:

[OptionalSrcDirs]
uniproc
svcpack

5.     Create an E:\i386\svcpack folder. For example, to create a \svcpack subfolder within the \i386 folder, type the following:

mkdir E:\i386\svcpack

6.     Copy the hotfix executable program (Q######_XXX_YYY_ZZZ_LL.exe) to the E:\i386\svcpack folder by using the 8.3 naming format (Q######.exe), where ###### represents the actual hotfix number.

If you are deploying multiple hotfixes, rename all of the hotfix package files.

7.     Expand the hotfix to a unique temporary location. For example, to expand the files to the sample folder, type the following:

E:\i386\svcpack\Q###### /sE:\samplefolder

8.     Copy the catalog files (.cat) and hotfix binary files (such as .exe, .dll, .sys) as follows:

a.    Copy Q######.cat to E:\i386\svcpack folder. If multiple hotfixes are to be deployed together, make sure that you copy all catalog files from each of the hotfixes to be deployed. Each hotfix has a unique catalog file that you must copy in the format Q######.cat.

b.    If any binary files exist in multiple packages, keep only the file with the highest version number.

c.    Delete any binary files to be replaced in the \i386 folder (usually you can identify the file name by an underscore at the end in the shared folder).

d.    Copy the hotfix binary files and any subfolders for the hotfix to the \i386 folder.

For example, \i386\uniproc\* files in the hotfix need to be copied to the \i386\uniproc folder of the shared installation folder. There is no need to copy Update.exe, update.inf, spmsg.dll, spcustom.dll, spuninst.exe, update.ver, or symbols files.

9.    Note

10. Step 8 can be cumbersome if you are installing multiple hotfixes. This step is necessary only if the hotfixes contain updated system files that are required to start the computer to GUI mode or to prevent a virus attack during upgrade.

11. Delete the E:\i386\svcpack.in_ file.

12. Create a new svcpack.inf file at E:\i386\svcpack.inf, with the following content:

[Version]
Signature="$Windows NT$"

MajorVersion=5

MinorVersion=0

BuildNumber=2195

[SetupData]
CatalogSubDir="\i386\svcpack"

[ProductCatalogsToInstall]
Q######.cat

[SetupHotfixesToRun]
Q######.exe /switches (the recommended switches for hotfixes are /q /n /z)

Important

If you will be deploying multiple hotfixes together, add an entry for each hotfix under [SetupHotfixesToRun] (as shown following this paragraph), and then add the Qchain.exe file to make sure that the correct files get replaced after the installation. You must also copy Qchain.exe to the svcpack folder. The following lines are a sample of the [SetupHotfixesToRun] section for an installation in which multiple hotfixes are installed.

[ProductCatalogsToInstall]
Q123456.cat

Q123478.cat

Q123490.cat

[SetupHotfixesToRun]
Q123456.exe /switches (the recommended switches for hotfixes are /q /n /z)

Q123478.exe /switches (the recommended switches for hotfixes are /q /n /z)

Q123490.exe /switches (the recommended switches for hotfixes are /q /n /z)

13. If you will be installing multiple hotfixes, copy Qchain.exe to the E:\i386\svcpack folder.

You can find Qchain.exe on the Microsoft Web site.