Back to CTS-NET Support Page

Customizing Microsoft NT 40 Workstation Setup

You can customize the installation of Windows NT Workstation that you distribute to your users. The customization can be as simple as specifying which features in the retail product you want to use. Or, you can include applications or additional files, such as corporate-specific help files, along with the installation of Windows NT Workstation. You can even tailor the customized setup so that different computers get different configurations. And with Unattended Setup, you can supply answers to all the prompts the user would normally need to respond to during setup. Even the computername and username for each computer can be supplied via Unattended Setup.

This chapter is loosely organized according to the features you are most likely to need to implement, and the order in which you would perform the tasks. It does not parallel the order of the setup process.

Overview of the Setup Process

The key to deploying Windows NT Workstation is the winnt or winnt32 command. These commands use a network connection to access the installation files, which are in one central location. This central location is called the distribution sharepoint. The winnt command is used to install Windows NT Workstation on a computer currently running a 16-bit Windows operating system, such as Windows 3.1 or Windows for Workgroups 3.1, or MS-DOS, or Windows 95. The winnt32 command is used to upgrade from an earlier version of Windows NT Workstation. Either of these commands can be issued either directly from the keyboard, or as a line in a .BAT file, or via Systems Management Server.

When you use the winnt or winnt32 command, all the files needed to complete the installation are copied over the network to a temporary directory. Then Setup continues as it would if you were performing the installation from a local drive, going through first text mode setup, and then GUI mode setup.

In text mode setup, all the files required for installation are copied from the temporary directory into the installation directory on the hard disk of the target computer. After text mode setup is complete, GUI mode begins. In GUI mode, the user is presented with a Graphical User Interface (GUI), and is prompted for information used to customize the setup. For example, the user may be given the opportunity to choose components to install. During GUI mode Setup, computer-specific information such as the computername and username are supplied.

The winnt and winnt32 Commands

Before using the winnt or winnt32 command, there must be a network connection between the computer being upgraded (the destination computer) and the distribution sharepoint. If the destination computer is already using networking software, the connection can be made in the usual way. If the computer is not yet running networking software, you can use a Network Installation Startup Disk to start the computer and make the network connection. See "Network Installation Startup Disks," later in this chapter, for information on creating and using a Network Installation Startup Disk.

The winnt or winnt32 command is run from the destination computer. The command can be typed from the keyboard, or run from a batch file, or included in the Network Installation Startup Disk, or issued via Systems Management Server.

The syntax of the winnt command is as follows:

winnt [/s:sourcepath] [/i:inf_file] [/t:drive_letter] [/x] [/b] [/o[x]] [/u:answer_file] [/udf:id, [UDF_file]]

and the syntax of the winnt32 command is as follows:

winnt32 [/s:sourcepath] [/i:inf_file] [/t:drive_letter] [/x] [/b] [/o[x]] [/u:answer_file] [/udf:id, [UDF_file]]

where

/s:sourcepath

/i:inf_file

/t:drive_letter

/x

/b

/o

/ox

/u:answer_file

/udf:id [,UDF_file]

Computers running an earlier version of Windows NT Workstation can upgrade to Windows NT Workstation 4.0 using the winnt32 command. These computers do not need a Network Installation Startup Disk, because they can connect to the network using the built-in networking features of Windows NT Workstation. The options for winnt32 are the same as those for winnt.

Options for Customizing Setup

The tools for customizing setup include the following:

Answer files (UNATTEND.TXT)

Answer files are text files that provide the answers to some or all of the prompts that the end user would otherwise need to respond to during Setup. The answer file is specified with the /u option to the winnt or winnt32 command.

The simplest use of this feature is to specify in the answer file those features of the Windows NT Workstation retail product that you want included in the installation. However, you can also use the answer file display company information during GUI-mode setup, to specify a keyboard layout, to join a domain or workgroup, and to install device drivers, protocols, or network adapters.

A sample answer file, UNATTEND.TXT, is included on the Windows NT Workstation 4.0 product CD. Using this file as a template, you can create one or more answer files to customize your installation of Windows NT Workstation. See Appendix ___, "Options Available Through Answer Files and UDFs," for a discussion of the sections and syntax you can use in your answer files.

Uniqueness Database Files (UDFs)

Uniqueness Database Files (UDFs) are an extension of the answer file functionality. A UDF has a structure similar to that of an answer file. However, the UDF begins with an additional section in which uniqueness IDs are specified and mapped to sections in the UDF. If a uniqueness ID is specified in the winnt or winnt32 command, any values specified in the sections associated with that uniqueness ID override the values in the same-named sections in the answer file.

You can specify numerous alternatives in a single UDF — even one for each computer in your organization.

The $OEM$\OEMFILES Directory

To install components, files, or applications that are not included with the Windows NT Workstation retail product, the required files must be added to subdirectories of the $OEM$\OEMFILES directory on the distribution sharepoint.

Hardware-dependent files that are loaded during text mode setup are placed in subdirectories of $OEM$\OEMFILES\TEXTMODE. Create one directory for each device.

System files that replace or supplement the system files included with the retail product are placed in subdirectories of $OEM$\OEMFILES\$$WINNT.

Files for network components, such as protocols, adapters, or network services, are placed in subdirectories of $OEM$\OEMFILES\NETWORK. Create one directory for each component.

Files for applications that support a scripted (silent) installation, and any other files you want to copy to the destination computers, are placed in subdirectories of $OEM$\OEMFILES\$$ROOT. To include in your installation of Windows NT Workstation applications that must be installed interactively, use the sysdiff utility.

The sysdiff Utility

To pre-install applications that do not support a scripted installation, you must use the sysdiff utility. You can also use sysdiff to install other applications.

To use sysdiff, you first create a snapshot of a reference system. Then you install the applications you want to distribute. After you’ve installed the applications, you create difference file. The information in the difference file includes all the binary files for the applications, as well as the initialization file settings and registry settings for the applications.

A command in $OEM$\OEMFILES\CMDLINES.TXT file is used to apply the difference file to new installations of Windows NT Workstation. Or, the difference file can be applied to a computer that is already running Windows NT Workstation 4.0 by issuing the same command from the command line.

Because the difference file includes all the files and all the initialization and registry settings for the applications, it can be a very large package, depending on the number and complexity of the applications you have added. Applying such a large package can add considerably to the time required for setup. As an alternative, you can create an information file (INF) from the difference file, which contains registry and initialization file directives only. The command that creates the INF also creates a directory tree, within the $OEM$\OEMFILES directory structure, that contains all the files contained in the difference file package. These files are then copied along with other files required by setup during the early phases of setup, and are in place when the INF is invoked from the $OEM$\OEMFILES\CMDLINES.TXT file.

Adding Applications

You can install any number of applications along with Windows NT Workstation, using the procedure that follows.

To use unattended setup to distribute applications with the Windows NT Workstation installation

The Sysdiff Utility

The Sysdiff utility is used in several steps:

If you want to distribute computers or hard disks that are ready for GUI-mode setup, use the winnt /u or winnt32 /u command to install the your customized version of Windows NT Workstation, including the difference file — but stop the process after text mode Setup is complete by turning off the computer. Then duplicate the hard disk, using the xcopy command. The duplicated disks will include all the information copied during text mode, including the contents of the $OEM$ directory and its subdirectories. These directories will be deleted, along with other temporary directories used by Setup, after GUI mode setup is completed. GUI mode setup proceeds the first time the computer is turned on.

The sysdiff process is shown in the following illustration:

<<Art goes here. Show three computers: the first is used to (1) install the retail product, (2) sysdiff /snap, (3) install applications, (4) sysdiff /diff. The second computer is the server used as a distribution sharepoint. Show the difference file, and sysdiff.exe copied to the sharepoint. Show also the other distribution files on the sharepoint. The third computer uses sysdiff /apply (either through an answer file or from the command line) to copy the settings and files required for the applications installed on the first computer after the /snap and before the /diff.). This computer is then either taken through the entire setup process or (perhaps showing another computer for this option) it is stopped at the end of text mode setup and the hard disk is duplicated.>>

To create the snapshot file

To create the difference file

To apply the difference file

To create an INF

Run the following command:

Because the INF file is copied during text mode Setup, it should be placed in the $OEM$\OEMFILES\TEXTMODE directory and listed in the TXTSETUP.OEM file in that directory. On x86 machines, TXTSETUP.OEM and all files listed in it must also be listed in the [OEMBootFiles] section of the answer file.

To invoke the INF

To dump the contents of a difference file

Use the command,

sysdiff /dump difference_file dump_file

A text file with the name specified in the dump_file parameter is created that contains information regarding the contents of the difference file.

SYSDIFF.INF

When sysdiff is run, it looks for a file called SYSDIFF.INF in the directory containing SYSDIFF.EXE. This file contains information used by sysdiff to exclude certain files and registry entries from snapshots or difference files. The SYSDIFF.INF file can be customized but it is highly recommended that at least a basic one be used when performing the sysdiff /snap and sysdiff /diff commands. Otherwise, sysdiff will attempt to include files such as PAGEFILE.SYS, which will almost certainly cause sysdiff to fail.

Example SYSDIFF.INF File

[Version]
;
; This section is required, as it identifies the file as
; a Win4-style INF. Just leave this section as-is.
;
Signature = $chicago$

;
; General notes for file/dir exclusion sections:
;
; *: refers to all drives.
; ?: refers to the drive with the system on it.
; :: is substituted with %systemroot%
;
; Lines that are not in valid format (such as those that
; don't start with *:\, ?:\, ::, or <x>:\) are ignored.
;

[ExcludeDrives]
;
; By default, all valid local hard drives are scanned from the root during
; snapshots and diffs. This section can be used to exclude entire drives.
; The first character on each line is the drive letter of a hard drive to exclude.
;

[ExcludeDirectoryTrees]
;
; By default, all directories on a drive are scanned during snapshots/diffs.
; This section allows entire directory trees to be excluded.
; Each line is a fully-qualified path of a tree to be excluded -- the directory
; and all of its subtrees are excluded from the snapshot or diff.
;
*:\recycled
*:\recycler

[ExcludeSingleDirectories]
;
; Each line is a fully-qualified path of a directory to be
; excluded. The directory's subdirs are NOT excluded.
;
::\system32\config

[ExcludeFiles]
;
; By default, all files in all directories are included in snapshots/diffs.
; This section allows exclusion of individual files.
; Each line is a fully-qualified path of a file to be excluded.
; If it does not start with x:\ then we assume it's a filename part
; for a file to be excluded whereever it is found.
;
*:\pagefile.sys
ntuser.dat
ntuser.dat.log

[IncludeFilesInDir]
;
; Each line in here is a fully qualified path of a directory
; whose files are all to be included in a diff (marked as
; added/changed). Use this if you want to include files in the diff
; that might not have actually been changed.
;

[ExcludeRegistryTrees]
;
; By default, all registry keys in HKEY_LOCAL_MACHINE\System,
; HKEY_LOCAL_MACHINE\Software, and HKEY_CURRENT_USER are scanned during
; snapshots and diffs. This section allows exclusion of entire registry subkeys.
; Each line indicates a registry key and subkeys to be excluded.
; The first field is one of HKLM or HKCU
; The second field is the subkey, which must NOT start with a \.
;
HKLM,SYSTEM\ControlSet001
HKLM,SYSTEM\ControlSet002
HKLM,SYSTEM\ControlSet003
HKLM,SYSTEM\ControlSet004
HKLM,SYSTEM\ControlSet005
HKLM,SYSTEM\ControlSet006
HKLM,SYSTEM\ControlSet007
HKLM,SYSTEM\ControlSet008
HKLM,SYSTEM\ControlSet009

[ExcludeRegistryKeys]
;
; Each line indicates a single registry key to be excluded.
; Subkeys of this key are not excluded.
;
; The first field is one of HKLM or HKCU
; The second field is the subkey, which must NOT start with a \.
;
HKCU,Software\Microsoft\Windows\CurrentVersion\Explorer\RunMRU

[ExcludeRegistryValues]
;
; Each line indicates a registry value entry to be excluded.
;
; The first field is one of HKLM or HKCU.
; The second field is the subkey, which must NOT start with \.
; The third field is the value entry name.
;

Unattended Setup

In unattended setup, the Setup program is run over a network using the winnt or winnt32 command with the /u option. The /u option is used to specify an answer file. This file provides the answers to some or all of the prompts that the end user would otherwise need to respond to during Setup. In addition, entries in the answer file can direct Setup to install additional components, such as applications or other files that you have added to subdirectories of $OEM$ on your distribution share.

Answer Files (UNATTEND.TXT)

You can make different unattended answer files for the various setup configurations used in your organization, then customize them with UDFs as needed. For example, you make one answer file for each geographic location, or for each division. To tailor the information to individual users, create a UDF with a section for each user or computer that specifies the user name and computer name. Each user can then receive a tailored installation by specifying both the answer file and the UDF in the winnt or winnt32 command.

Answer files and UDFs are text files with specific section names and keys. For a description of these sections and keys, and the customizations you can perform through these files, see Appendix ___, "Options Available Through Answer Files and UDFs."

If you are using Microsoft Systems Management Server (SMS) to manage computer resources in your organization, you can use package definition files (PDFs) to install or upgrade Windows NT. See the Microsoft Systems Management Server documentation for information on using PDFs to install operating systems.

Creating an Unattended Answer File

You can create one or more unattended answer files for your organization by editing a copy of the UNATTEND.TXT included with the Windows NT Workstation 4.0 Resource Kit. Use any text editor to modify the file, and save the modified copy as a text file. The modified UNATTEND.TXT can be given any legal filename.

The options available in answer files and UDFs are documented in Appendix ___, "Options Available Through Answer Files and UDFs."

Tailoring the Installation With Uniqueness Database Files

When you are deploying a complete, unattended installation of Windows NT Workstation to numerous computers, some of the information you need to supply via answer files, such as the computername, must be unique to each computer. With Windows NT Workstation 4.0, you can use a single answer file for the information that applies to all users, and one or more Uniqueness Database Files (UDFs) to supply information that is specific to a single computer or a small group of computers.

Uniqueness Database Files (UDFs) are used to provide replacements for sections of the answer file, or supply additional section. The replacement sections are specified in a text file similar to the answer file. This file is indexed via strings called uniqueness IDs.

The uniqueness database file is used to specify a set of sections that should be merged into the answer file at the start of GUI Setup. This merging takes place before any affected components actually read the internal representation of the answer file. Thus this entire mechanism is totally transparent.

For a discussion of the sections and keys used in answer files and UDFs, see Appendix ___, "Options Available Through Answer Files and UDFs."

Creating the UDF

The first section of the UDF is the [UniqueIds] section. This section lists all uniqueness ids that are supported by this database. The left hand side is a uniqueness ID. The uniqueness ID can be any string but must not contain the star (*), space, comma, or equals character. The right hand side is a list of sections, each of which should match the name of a section in the answer file. The format is as follows:

[UniqueIds]
id1 = section1,section2
id2 = section1,section2
id3 = section1,section3,section4

For example, if you were using computernames for the uniqueness IDs, this section might look like this:

[UniqueIds]
janeayer = UserData,Unattended
emilybr = UserData,Unattended
jconrad = UserData,KeyboardDrivers, PointingDeviceDrivers

Following the [UniqueIds] section are the sections referenced in [UniqueIds]. These section names can take either of two forms: they can be exactly like the section name in the answer file (for example, [Unattended]). Or, the section name can be preceded with the uniqueness ID and a colon (for example, [janeayer:UserData]). This allows you to create specialized replacement sections for each computer name.

If both a general section (such as [Unattended]) and an ID-specific section (such as [jconrad:Unattended]) is available, Setup will use the section for the uniqueness ID specified in the winnt or winnt32 command line.

The sections in the UDF can contain any keys and values that the same-named sections could contain in the answer file. During setup, each key specified in a referenced section overrides the value for the same key in the answer file. Values are substituted as follows:

Specifying a UDF During Installation

To specify a uniqueness ID during setup, the user must run the winnt or winnt32 command with the following parameter:

/UDF:ID[,database_filename]

Where

ID

database_filename

If both the uniqueness ID and the filename of the UDF are specified, the UDF is copied to the local drive during text-mode Setup, and is used during GUI Setup without user intervention. The UDF can have any legal filename.

If only the uniqueness ID is specified on the winnt or winnt32 command line, Setup requires a floppy disk with a UDF file named $UNIQUE$UDF. This disk must be prepared by the administrator and made available to the user in advance. The user is prompted for this disk during GUI mode setup.

In either case, if the supplied UDF is corrupt or if Setup cannot locate the specified uniqueness ID in it, the user is prompted to insert a floppy with the fixed UDF, or Cancel. If the user chooses Cancel, the values in the answer file will be used. These might not be appropriate for the computer.

The $OEM$\OEMFILES Directory and Its Subdirectories

To install components, files, or applications that are not included with the Windows NT Workstation retail product, the required files must be added to subdirectories of the $OEM$\OEMFILES directory on the distribution sharepoint.

The $OEM$\OEMFILES directory includes the following subdirectories:

The $OEM$\OEMFILES\CMDLINES.TXT File

The commands to install files located in the subdirectories of $OEM$\OEMFILES are listed them in a text file named CMDLINES.TXT and placed in the $OEM$\OEMFILES directory of the distribution sharepoint.

The $OEM$\OEMFILES\TEXTMODE Directory

The $OEM$\OEMFILES\TEXTMODE directory contains all files that that the Setup Loader needs to load, and that Text Mode Setup needs to copy to the target computer, so that the system can boot into GUI setup.

If you are installing HALs, SCSI, keyboard, video, or pointer device drivers that are not included with Windows NT Workstation 4.0 retail version, this directory should also contain a standard TXTSETUP.OEM file. This file contains pointers to all the files required by the Setup Loader and Text Mode Setup to load and install these components. On x86 machines, TXTSETUP.OEM and all files listed in it (HALs and drivers), must also be listed in the [OEMBootFiles] section of the answer file.

The $OEM$\OEMFILES\$$WINNT Directory

This directory contains system files (either new files or replacements to files included in the retail product) that need to be copied to the various subdirectories the Windows NT system directory. Maintain the directory structure used in the retail product. In each subdirectory, place the files that need to be copied to the corresponding system directory on the destination computer. If some of the files use long filenames, add the file $$RENAME.TXT. This file lists all files that have long names, and their corresponding short names.

The $OEM$\OEMFILES\NETWORK Directory

This directory contains only subdirectories. Each subdirectory will contain the files for a particular network component (network cards, network services, and network protocol). Files in this directory will be used by the network setup module.

The $OEM$\OEMFILES\$$ROOT Directory

Subdirectories of the $OEM$\OEMFILES\$$ROOT directory on the distribution sharepoint contain the files for applications that you want to install along with Windows NT Workstation. These applications must support a scripted (silent) installation; to include applications that require interactive installation, use the sysdiff utility.

Create a subdirectory of $OEM$\OEMFILES\$$ROOT for each logical drive on the destination computer to which files will be copied. Then create and populate subdirectories for the directories to be added to that drive.

Setup uses commands specified in the $OEM$\OEMFILES\CMDLINES.TXT file to install applications or copy files that are available in subdirectories of $OEM$\OEMFILES\$$ROOT on the distribution sharepoint. You can use these commands to invoke a Win95-style INF file, run the sysdiff command, or perform any other action.

For example, to install MS Office on the C: drive, in the \MSOffice directory, place the files in $OEM$\OEMFILES\$$ROOT\C\MSOffice. Then specify the command to install the application in the $OEM$\OEMFILES\CMDLINES.TXT file.

You can also place files that you only want copied (not "installed") in subdirectories of $OEM$\OEMFILES\$$ROOT. For example, if you have written help files that cover policies and procedures used in your organization, you can place them in a subdirectory of $OEM$\OEMFILES\$$ROOT. Then use a command in the $OEM$\OEMFILES\CMDLINES.TXT file to copy them to the destination computers.

Network Installation Startup Disks

To deploy Windows NT Workstation to computers that are not currently running networking software, you need to provide some way for them to connect to the distribution sharepoint and begin the installation process. This is done with a Network Installation Startup Disk.

A Network Installation Startup Disk is a bootable MS-DOS system disk that contains just enough network client software to connect to the distribution server. A winnt command line in the AUTOEXEC.BAT file on the disk then install Windows NT Workstation over the network.

This disk can be used to do additional tasks, by adding lines to the AUTOEXEC.BAT file on the disk. For example, a series of Network Installation Startup Disks can be produced for an entire division or organization, with each disk specifying a different uniqueness id in a common UDF. The end users can simply insert the disk in drive a:, turn on the computer, and walk away, returning to a completed custom installation of Windows NT Workstation.

Creating a Network Installation Startup Disk

Before you create a Network Installation Startup Disk, you need to determine the following:

To create a Network Installation Startup Disk

Using the Network Installation Startup Disk

Once the answer files, along with any UDFs or other customization files, are available on the distribution sharepoint, your technicians or end users can use the Network Installation Startup Disk to install Windows NT Workstation over the network.

To use the Network Installation Startup Disk

For more information, see the guidelines for Computers Running MS-DOS Network Client in Chapter 4, "Deployment on Existing Client-Server Networks."

Troubleshooting

If the computer displays an error message saying that "the specified shared directory cannot be found," make sure that the directory containing the Windows NT installation files is indeed shared on the Windows NT Server computer.

The NetBEUI protocol can only be used in a LAN or a setup staging area because NetBEUI does not support traffic across routers. Both IPX and TCP/IP can be used in a WAN with Setup Manager and CPS. However, not all companies route IPX so you may need to create boot floppies with TCP/IP for use in a WAN environment.

If the computer displays an error message about lack of memory, modify the CONFIG.SYS file on the network installation startup disk to use extended memory. For example, EMM386.EXE and HIMEM.SYS provide extended memory for MS-DOS 5.0 and later. If you do not have extended memory, use the NetBEUI or IPX protocols instead of TCP/IP.

Creating .INF Files

Device information (INF) files provide information used by the Windows NT Workstation Setup program to install software that supports a given hardware device. INF files may also be created to permit scripted installations of applications.

Some Windows NT Workstation 4.0 .INF files use the same format as Windows 95 .INF files. Other .INF files use the format used in earlier versions of Windows NT Workstation. See the Windows 95 Resource Kit for a discussion of Windows 95-style INFs.

Remainder of this section to be written.

Special Issues: Dual Boot Computers

In the deployment lab, you might want to set up some computers to run either Windows NT Workstation 3.51 or Windows NT Workstation 4.0, with the choice of operating system to be made during system startup. This is referred to as dual booting. The following considerations apply in this case: