Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Installing Microsoft Windows 2000 and Windows 2000 Hotfixes
Article ID: 249149 - View products that this article applies to.
This article was previously published under Q249149
NoticeThis article applies to Windows 2000. Support for Windows 2000 ends on July 13, 2010. The Windows 2000 End-of-Support Solution Center
(http://support.microsoft.com/?scid=http%3a%2f%2fsupport.microsoft.com%2fwin2000)is a starting point for planning your migration strategy from Windows 2000. For more information see the Microsoft Support Lifecycle Policy
You can install Microsoft Windows 2000 and Windows 2000 hotfixes at the same time by copying the Windows 2000 installation files and hotfix executable files to a common distribution folder. These hotfix executable files are named Q6-digit number.exe, where 6-digit number is the 6-digit number assigned to the hotfix. You can then add command lines to the Cmdlines.txt file to run the hotfixes and install the hotfixes during Windows 2000 Setup. You do not need to perform separate installations of the Windows 2000 operating system or the Windows 2000 hotfixes unless you have already installed Windows 2000.
Before you run Windows 2000 Setup to install the Windows 2000 operating system and Windows 2000 hotfixes, you must complete the following preparatory steps:
Creating the Distribution FolderTo install the Windows 2000 operating system and Windows 2000 hotfixes on multiple computers over a network, you must create at least one distribution folder. A distribution folder typically resides on a server to which your destination computers or master computer can connect. You can use the same distribution folder for all computers with the same processor platform. To create a distribution folder:
Creating an Answer File by Using the Setup ManagerThe Unattend.txt answer file identifies how Windows 2000 Setup should interact with the distribution folders and files you create and it provides information about your preinstallation requirements. 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. 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 answer file by using a text editor or by using Setup Manager. The Setup Manager tool is available in the Tools folder on the Windows 2000 OPK Tools CD-ROM or in the Support\Tools\Deploy.cab file on the Windows 2000 CD-ROM. By using Setup Manager, you can add consistency to the process of creating or updating the answer file, the Cmdlines.txt file, or the distribution folder.
For information about using Setup Manager to create an Unattend.txt answer file, see the Microsoft Windows 2000 Server Resource Kit or the Microsoft Windows 2000 Professional Resource Kit. For a complete reference to answer file parameters and settings, see the Microsoft Windows 2000 Guide to Unattended Setup (Unattend.doc), which is located in the Docs\Unattend folder on the Windows 2000 OPK Tools CD-ROM or in the Support\Tools\Deploy.cab file on the Windows 2000 CD-ROM.
Adding Command Lines in the Cmdlines.txt File to Run the HotfixesThe Cmdlines.txt file contains a list of the commands that must run during Windows 2000 graphical user interface (GUI) mode Setup. These commands can (for example), run a .inf file, a program setup command, Sysdiff.exe, or another executable file.
You can create the Cmdlines.txt file by using a text editor or by using Setup Manager. The Setup Manager tool is available in the Tools folder on the Windows 2000 OPK Tools CD-ROM or in the Support\Tools\Deploy.cab file on the Windows 2000 CD-ROM.
To install the hotfixes during Windows 2000 Setup, you must add a command line for each hotfix to the Cmdlines.txt file. To add a command line for each hotfix to the Cmdlines.txt file, create a Cmdline.txt file that contains the following command line for each hotfix:
Q6-digit number /qwhere 6-digit number is the 6-digit number assigned to that hotfix. For example, to install the hotfix Q123456.exe, add the following command line to the Cmdlines.txt file:
[Commands]For information about using Setup Manager to create a Cmdlines.txt file, see the Microsoft Windows 2000 Server Resource Kit or the Microsoft Windows 2000 Professional Resource Kit. For more information about adding commands to the Cmdlines.txt file, see the Microsoft Windows 2000 OPK Distribution Guide, which is available on the Windows 2000 OPK Tools CD-ROM.
To install a Plug and Play hotfix before Plug and Play detection, you can use the "DetachedProgram=" line in the [GuiUnattended] section of the Unattend.txt file:
[GuiUnattended] DetachedProgram="c:\Q123456.exe -m"The -m switch indicates unattended mode.
NOTE: this example assumes that the Q123456 hotfix is copied to drive C by using the $OEM$\S1 folder in the I386 folder.
This is loaded before the Windows 2000 Startup Wizard is displayed and before the Windows File Protection (WFP) catalog is loaded. To register this with the WFP catalog, you must also reinstall this in either the [GuiRunOnce] section or by using the Cmdlines.txt file.
Copying the Files Necessary for the Windows 2000 InstallationYou must copy all the files needed for the Windows 2000 installation to your distribution folder. The distribution folder contains the Windows 2000 installation files, as well as any device drivers or other files that you want to install. Note that Windows 2000 Setup requires the 8.3 naming convention for all files and folders in the distribution folder. To copy the files necessary for the Windows 2000 installation:
Deploying the Windows 2000 InstallationYou can deploy the Windows 2000 and Windows 2000 hotfixes installation to your user's computers from the network distribution share. During the standard installation process, Windows 2000 Setup (Winnt.exe or Winnt32.exe in unattended mode) installs the operating system and applies the hotfixes. To deploy the installation: