Export (0) Print
Expand All

Appendix A - Answer Files and UDFs

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

When Windows NT Workstation or Windows NT Server is installed using the winnt /u:answer_file or winnt32 /u:answer_file command, the options specified in the answer file (Unattend.txt) are applied to the installation. If the /udf:uniqueness_database_file option is also specified on the winnt or winnt32 command line, the entries in the specified uniqueness database file (UDF) are also applied, overriding entries in the answer file.

For information on editing and using answer files and UDFs, see Chapter 2, "Customizing Setup," of the Windows NT Workstation 4.0 Resource Guide. This Appendix describes the sections and keys used in these files. Additional entries may be listed in the sample Unattend.txt file on the product compact disc.

Sections In Answer Files and UDFs

Cc749979.spacer(en-us,TechNet.10).gif Cc749979.spacer(en-us,TechNet.10).gif

Information in the answer file is divided into sections. Each section begins with the section name in square brackets, on a line by itself. Each section may contain one or more keys, with associated values. Each key is a character string, recognizable by the Setup program, that controls an element of the configuration to be installed. For example, there is a key to specify the computername, a key to specify whether the primary partition is converted to NTFS, and a key to specify the time zone for the computer.

The same sections and keys are used in the UDFs, provided they are used after text-mode setup. Information that the Setup program uses during text-mode setup can only be specified in the answer file, not in the UDF.

The sections are:

[Unattended] The keys in this section define the behavior of the Setup program during text mode setup. This section can only be specified in the answer file, not in the UDF. [OEMBootFiles] To install onto x86 computers, $OEM$\OEMFILES\TXTSETUP.OEM and all files listed in it (HALs and drivers), must be listed in this section. This section can only be specified in the answer file, not in the UDF. [MassStorageDrivers] This section is used to specify SCSI drivers. This section can only be specified in the answer file, not in the UDF. [KeyboardDrivers] This section is used to specify keyboard drivers. This section can only be specified in the answer file, not in the UDF. [PointingDeviceDrivers] This section is used to specify pointing device drivers. This section can only be specified in the answer file, not in the UDF. [OEM_Ads] This section describes a banner, logo, and background bitmap to be displayed during GUI-mode setup. [DisplayDrivers] This section is used to specify display drivers. [Display] This section is used to specify settings for video display. [DetectedMassStorage] This section is used to specify mass storage devices that Setup is to recognize, even if they are not physically present on the system at the time you perform the installation. This section can only be specified in the answer file, not in the UDF. [GuiUnattended] The keys in this section define the behavior of the Setup program during GUI mode setup. [UserData] The keys in this section specify information associated with each user or computer. [LicenseFilePrintData] This section pertains only to installations of Windows NT Server. It is used to supply information regarding the license agreement. [Network] This section is used to specify settings used for networking, such as protocols and adapters. If this section is not present, support for networking will not be installed. [Modem] This section header is used to identify whether a modem should be installed or not. It is used by RAS to install a modem if DeviceType = Modem is in the list of RAS parameters.

Some of the keys in these sections point to additional sections, which you must create and name. For example, to install protocols other than the defaults, you need to use the InstallProtocols key in the [Network] section to identify the name of the section in which the protocols are listed. You must also create and populate the section pointed to in the Install Protocols key.

Adding Specific Functionality to Your Customized Setup

Cc749979.spacer(en-us,TechNet.10).gif Cc749979.spacer(en-us,TechNet.10).gif

The keys you can add to the answer file or UDF are listed in the remainder of this Appendix, grouped according to the kind of effect they produce.

Preferred Options in the Retail Product

These options affect the choices a user can make while installing the retail version of Windows NT Workstation.

Preserving Settings of Existing Windows NT Workstation Systems

By default, Setup installs Windows NT Workstation 4.0 with the retail default settings, except where different settings are specified in the answer file and the UDFs. As an option, you can have Setup upgrade existing installations of Windows NT Workstation, with the system settings intact. 

To preserve existing settings when upgrading from an earlier version of Windows NT Workstation, add the following line to the [Unattended] section:

NtUpgrade = manual | yes | no | single

Where:

manual indicates that the user is to be prompted as to whether the existing installation is to be completely replaced, or upgraded with system settings intact. If the user chooses to replace the existing version, he or she will also be prompted to specify a directory in which to install Windows NT Workstation 4.0. If the user chooses to retain existing settings, the remainder of the settings in the answer file and in the UDF will be ignored. yes indicates that the existing installation of Windows NT Workstation is to be upgraded with system settings intact. If NtUpgrade = yes, the remainder of the settings in the answer file and in the UDF will be ignored. If multiple installations are detected, the settings in first installation detected are used. On x86-based systems, the system that is listed first in the Boot.ini file is the first installation detected. On Alpha AXP-based, MIPS-based, and PowerPC-based systems, the first installation is the first one listed in the Startup Environment. no indicates that the existing installation of Windows NT Workstation is to be completely replaced. The retail default settings will be used, except where keys in the answer file or UDF override them. This is the default option. single indicates that if only one existing installation of Windows NT Workstation is detected, it is to be upgraded with system settings intact. If multiple previous installations are detected, the user must indicate which settings are to be retained.

This key can only be specified in the answer file, not in the UDF.

Preserving Settings of Existing Windows for Workgroups 3.1 or Windows 3.1 Systems

By default, Setup installs Windows NT Workstation 4.0 with the retail default settings, except where different settings are specified in the answer file and the UDFs. As an option, you can have Setup upgrade existing installations of Windows for Workgroups 3.1 or Windows 3.1, with the system settings intact. 

To preserve existing settings when upgrading from either of these systems, add the following line to the [Unattended] section:

Win31Upgrade = yes | no

Where:

yes indicates that if an existing installation of Windows for Workgroups 3.1 or Windows 3.1 is detected, the existing settings are to be preserved. no indicates that the existing installation of Windows NT Workstation is to be completely replaced. The retail default settings will be used, except where keys in the answer file or UDF override them. This is the default option.

If any other values are supplied for the Win31Upgrade key, the user will be prompted to specify whether the settings should be retained.

This key can only be specified in the answer file, not in the UDF.

Specifying the Directory in Which to Install Windows NT Workstation

You can specify the directory on the destination computer in which the files for Windows NT Workstation 4.0 are to reside. To do so, add the following line to the [Unattended] section:

TargetPath = manual | * | path

Where:

manual indicates that the user is to be prompted for a directory. * indicates that the Setup program is to generate a unique directory name, and place the Windows NT Workstation 4.0 files in that directory. This is the default option. path indicates the name of the directory in which the Windows NT Workstation 4.0 files are to be placed. If the directory does not exist, it will be created.

This key can only be specified in the answer file, not in the UDF.

Replacing OEM Files with Windows NT Workstation Product Files

You can choose whether to replace older files that Setup finds on the system with files from the retail product that have the same name. By default, these files are overwritten.

To specify whether to keep the older versions of such files, add the following line to the [Unattended] section:

OverwriteOemFilesOnUpgrade = yes | no

If any Windows NT file in the existing installation has been overwritten by another application, you must set OverwriteOEMFilesOnUpgrade = yes. 

This key can only be specified in the answer file, not in the UDF.

Converting to NTFS

In general, partitions greater than 512 MB should be converted to NTFS. To specify whether to convert the primary partition to NTFS during installation, add the following line to the [Unattended] section:

FileSystem = ConvertNTFS | LeaveAlone
Specifying When to Configure Graphics Devices

By default, graphics devices are configured during Setup. However, you can specify that the graphics devices be configured the first time someone logs on to the new system. To specify when the graphics devices are to be configured, add the following line to the [Display] section:

ConfigureAtLogon = 0 | 1

If ConfigureAtLogon = 1, no specific video setting is made during setup. Instead, the user is prompted to select the screen resolution the first time the computer is started after setup.

If ConfigureAtLogon = 0, graphics configuration will be done during setup. If this option is selected, the following other preconfiguration values may be set, also in the [Display] section:

BitsPerPel = n
XResolution = number_of_pixels
YResolution = number_of_pixels
VRefresh = n
Flags = n

If an entry has a value of 0, or the entry is not present, the defaults will be applied.

Key

Default Value

BitsPerPel

8
If this is not a valid value, the lowest valid value is used.

XResolution

640
If this is not a valid value, the lowest valid value is used.

YResolution

480
If this is not a valid value, the lowest valid value is used.

VRefresh

60 Hz
If this is not a valid value, the lowest valid value is used.

Flags

Any that are available.

For example, if all of these keys are set to = 0, the video settings would be 640x480, 256 colors, 60 Hz (as long as that mode exists).

As another example, if BitsPerPel = 16 and all other values are set to 0, then the card will be configured in 640x480, 64 K colors, and 60 Hz (again, as long as that mode exists).

Normally, the user is prompted to test the video settings. For an unattended installation, you might want the settings to be stored without testing. To specify whether the settings should be stored without testing, add the following line to the [Display] section:

AutoConfirm = 0 | 1

If AutoConfirm = 0, or if it is not specified, the video settings specified elsewhere in the [Display] section are used, and the user must test the selected video mode in order to save the setting and continue with setup.

If AutoConfirm = 1, the settings are stored with no user intervention.

Additional Files and Applications

This section describes keys you can add to the answer file or UDF to add your own files or information to the retail version of Windows NT Workstation.

Displaying Your Company Information During Setup

To specify your own advertising or information during GUI Mode Setup, the following section must exist:

[OEM_Ads]
Banner = text
Logo = file_name{, n]
Bitmap = file_name{, n]

The value of the Banner key is the text string to be displayed as a banner in the upper left of the screen during GUI Mode Setup. The text must contain the substring "Windows NT Workstation" or "Windows NT Server" in order to be displayed. To create a multi-line banner, insert an asterisk (*) where a line break is to appear. If the Banner key is empty or does not contain the "Windows NT Workstation" or "Windows NT Server" substring, the Windows NT retail banner will be displayed.

The value of the Logo key is the filename of a bitmap to be displayed in the upper right corner of the screen during GUI Mode Setup. If your bitmap is referenced in a dynamic link library (DLL), you can specify the name of the DLL followed by the resource ID. The DLL must be in $OEM$\Oemfiles, and the resource ID must be supplied in base-10 format. If only a file name is specified, it must be the name of a .bmp file in $OEM$\Oemfiles that contains the bitmap.

If the Logo key is not specified, or its value is empty, or it specifies a non-existent bitmap, then the Windows NT retail bitmap will be displayed.

The value of the Bitmap key is the name of a bitmap that is to be tiled as a background during end-user setup.

If your bitmap is referenced in a dynamic link library (DLL), you can specify the name of the DLL followed by the resource ID. The DLL must be in $OEM$\Oemfiles, and the resource ID must be supplied in base-10 format. If only a file name is specified, it must be the name of a .bmp file in $OEM$\Oemfiles that contains the bitmap.

If the Bitmap key is not specified, or its value is empty, or it specifies a non-existent bitmap, then the Windows NT retail bitmap will be displayed.

For best results on VGA-based displays this bitmap should be exactly 640 x 480 pixels. On ARC computers (which don't necessarily use VGA mode during setup) other optimal sizes may be possible. If the bitmap is monochrome, it will be tinted blue when displayed (like the retail background bitmap, which is itself monochrome).

Running a Program Concurrently with Setup

To run a custom program concurrently with Setup, add the following line to the [GuiUnattended] section:

DetachedProgram = path\filename

where path and filename describe the location of the custom program. For example:

DetachedProgram = c:\mt32\mtrun.exe

To supply arguments to the custom program, add the following line to the [GuiUnattended] section:

Arguments = path\filename/argument

where path\filename indicates the path to the program and argument indicates the arguments you want to supply. For example:

Arguments = c:\mt32\scriptl.pcd/H
Using Files You Supply in the Subdirectories of $OEM$

To include files you have added to customize the application, the following line must be present in the [Unattended] section:

OemPreinstall = Yes 

A Yes value indicates that Windows NT Setup might need to install some OEM-supplied files located in subdirectories of $OEM$.

The default value is No. The default is used when the OemPreinstall key is missing. The No value implies that Setup will perform a regular unattended installation.

This key can only be specified in the answer file, not in the UDF. The keys described in the following sections are used only if OemPreinstall = Yes.

Installing Display Drivers

To install display drivers, include the following section:

[DisplayDrivers]
driver_description = Retail | OEM
.

This section is optional. If the [DisplayDrivers] section is empty or absent, Setup will install all the Windows NT retail display drivers during Text Mode Setup. During GUI Mode Setup, any drivers that fail to initialize will be disabled.

The driver_description value identifies the driver to be installed. This value must match one of the strings defined in the right-hand side of the [Display] section of Txtsetup.sif (except for the string "Standard VGA (640x480, 16 colors)" or Txtsetup.oem (for an OEM-supplied driver).

This key can only be specified in the answer file, not in the UDF. This section is valid only if OemPreinstall = Yes.

Installing SCSI Drivers

To install SCSI drivers, include the following section:

[MassStorageDrivers]
driver_description = Retail | OEM
.

This section is optional. If the [MassStorageDrivers] section is empty or absent, Setup will attempt to detect and install all known miniport drivers.

The driver_description value identifies the driver to be installed. This value must match one of the strings defined in the [SCSI] section of Txtsetup.sif or Txtsetup.oem (for an OEM-supplied driver).

This key can only be specified in the answer file, not in the UDF. This section is valid only if OemPreinstall = Yes.

Installing Keyboard Drivers

To specify keyboard drivers to be installed, include the following section:

[KeyboardDrivers]
driver_description = Retail | OEM
.

This section is optional. If the [KeyboardDrivers] section is absent or empty, Setup will detect and install a keyboard driver from the retail Windows NT product.

The driver_description value identifies the driver to be installed. This string must match one of the strings defined in the [Keyboard] section of the Txtsetup.sif or Txtsetup.oem (for an OEM-supplied driver).

This key can only be specified in the answer file, not in the UDF. This section is valid only if OemPreinstall = Yes.

Installing Pointing Device Drivers

To install pointing device drivers, include the following section

[PointingDeviceDrivers]
driver_description = Retail | OEM

This section is optional. If the [PointingDeviceDrivers] section is absent or empty, Setup will detect and install a pointing device driver from the retail Windows NT product.

The driver_description value identifies the driver to be installed. This string must match one of the strings defined in the [Mouse] section of Txtsetup.sif or Txtsetup.oem (for an OEM-supplied driver).

This key can only be specified in the answer file, not in the UDF. This section is valid only if OemPreinstall = Yes.

Networking Options

If networking is to be installed, you must include a [Network] section. If this section header is missing, network installation will be skipped. If the section is present but empty, the user will be presented with various error messages.

Specifying Manual Installation of Network Components

If you want the network components to be installed interactively during an otherwise unattended installation, include the following line in the [Network] section:

Attend = Yes

For the installation of network components to proceed without user intervention, this key must be absent.

Detecting Network Adapters

To detect network adapter cards installed on a computer, the following must be specified under the [Network] section:

DetectAdapters = adapters_section[,adapters_section]. . .

The value for the DetectAdapters key is a user-defined section name. For example, you could name a section [DetectAdaptersData] and specify it in this key. Create this section, and add to it the following keys:

DetectCount = number_of_cards_to_detect
LimitTo = inf_option [, inf_option] . . .
inf_option = parameter_section

The DetectCount key specifies the number of detection attempts Setup should make. The default is 1. If more cards than the number specified in DetectCount are present, the additional cards will not be detected.

The LimitTo key specifies a list of cards; detection will be limited to cards in that list. If this key is not present, any detectable adapters will be installed. The values can be obtained from the network-adapter INF files.

Each inf_option listed in the LimitTo key can also be listed as a key. The value of these keys will be the parameter normally associated with a network adapter. The values listed here will override detected values.

To detect and install only the first network adapter card, use following line under the [Network] section:

DetectAdapters = ""

Note that there is no space between the beginning and end quotation marks.

If neither the DetectAdapters key nor the InstallAdapters key (described under "Installing Network Adapter" later in this appendix) is present, user participation will be required. If DetectAdapters is present but contains no value, then the first adapter is detected and installed. The DetectAdapters and InstallAdapters keys can both be present.

Example
[Network]
InstallProtocols = SelectedProtocolsList

[SelectedProtocolsList]
TC = TCPIPParameters
ATALK = AppleTalkParameters
Installing Network Adapters

To install network adapters, the following key must be included in the [Network] section:

InstallAdapters = adapters_list_section[, adapters_list_section]. . .

The value for the InstallAdapters key is a user-defined section name. For example, you could name a section [InstallAdaptersList] and specify it in this key. All network adapters listed in the [InstallAdaptersList] section would then be installed. Create this section, and add to it a line for each adapter to be installed, using the following format:

inf_option = parameter_section[, oem_path]

If the InstallAdapters key and the DetectAdapters key are not present, user participation will be required.

Each inf_option key in this section defines the inf_option to be installed. The answers for the inf_option key are adapter-specific. If the adapter is an OEM-supplied card, the path can be specified.

Example
[Network]
InstallAdapters = SelectedAdaptersList

[SelectedAdaptersList]
NE2000 = NovelParameters
ELNKII = 3ComParameters
MSNETULTRA = MacrosoftNetUltraParameters, A:\

Note For network adapters, you must know and specify the necessary parameters for the cards you want to preinstall. To determine whether a card supports unattended setup, search for stf_unattended in the INFs for that card.

Installing Network Services

To install network services, the following keys should be specified under the [Network] section:

InstallServices = services_list_section[, services_list_section] . . . 

All services listed will be installed. If the InstallServices key is absent, no extra services will be installed.

The value for the InstallServices key is a user-defined section name. Create the section named by the InstallServices key, and in it list the service to be installed, using the following syntax:

inf_option = parameter_section[, oem_path]

Each inf_option key in this section defines the options to be installed. The value for this key is a user-defined section name and the OEM source path, if necessary. Create the section named by the inf_option key, and in it list the parameters to be used.

Example
[Network]
InstallServices = SelectedServicesList

[SelectedServicesList]
SFM = ServicesForMacParameters
WINS = WINServiceParameters
Installing Network Protocols

To detect network adapter cards installed on a computer, the following must be specified under the [Network] section:

InstallProtocols = protocol_list_section[, protocol_list_section] . . .

The value for the InstallProtocols key is a user-defined section name. For example, you could name a section [InstallProtocolsList] and specify it in this key. Create this section, and add to it a line for each protocol to be installed, using the following format:

inf_option = parameter_section[, oem_path]

The value on the left of the equals sign, inf_option, is the notation for the protocol, as it appears in the [Options] section of the INF file for that protocol. Protocol INFs have the filename Oemxpxx.inf, where xx refers to a particular protocol. The value on the right of the equals sign is a user-defined section name and the OEM source path, if necessary. Create the section named by the inf_option key, and in it list the parameters to be used for that protocol.

All protocols listed will be installed. If this key is not present, the default protocols will be installed and user participation might be required for Setup to continue.

Specifying the TCP/IP protocol is one case within the general topic of installing protocols, and is discussed in the section, "Installing TCP/IP."

Example
[Network]
InstallProtocols = SelectedProtocolsList

[SelectedProtocolsList]
TC = TCPIPParameters
ATALK = AppleTalkParameters
Installing NetBEUI

To install NetBEUI, it must be specified in the "protocol_list_section" section specified by the InstallProtocols key described in the [Network] section. This is described under "Installing Network Protocols" earlier in this Appendix. In the protocol_list_section, include the following line:

NBF = NetBEUI_parameters_section

The section you specify as the value for NBF must exist, but is empty since NetBEUI does not require any parameters. For example, your answer file might include the following lines:

[Network]
InstallProtocols = SelectedProtocolsList

[SelectedProtocolsList]
NBF = NetBEUI_params
TC = TCPIPParameters

[NetBEUI_params]

[TCPIPParameters]
.
.
.
Installing TCP/IP

To install TCP/IP, it must be specified in the section specified by the InstallProtocols key described in the [Network] section. This is described under "Installing Network Protocols" earlier in this Appendix. Create a separate section for the parameters, and refer to it in the section specified by the InstallProtocols key

The supported TCP/IP parameters are as follows:

DHCP = Yes | No
ScopeID = scope_ID

If you have set DHCP = No, you must also provide the following parameters. For a discussion of these parameters see Chapter 7, "Using Microsoft DHCP Servers" in the Windows NT Server Networking Guide.

IPAddress = ddd.ddd.ddd.ddd 
Subnet = ddd.ddd.ddd.ddd 
Gateway = ddd.ddd.ddd.ddd 
DNSServer = IPAddress, IPAddress, IPAddress
;Up to 3 IP addresses can be specified
WINSPrimary = IPAddress
WINSSecondary = IPAddress
DNSName = DNS_Domain_Name

Both TCP/IP and SNMP allow you to configure computers on a site basis and/or on a computer-specific basis. A site-based configuration configures each computer with identical parameters, whereas a computer-specific configuration allows a computer to have unique parameters. These two configurations can be mixed together. The generic or site-specific parameters are processed first. If computer-specific parameters exist, they are overlaid on the site-specific ones.

Example: TCP/IP without DHCP
[Network]
InstallProtocols = SelectedProtocolsList

[SelectedProtocolsList]
TC = TCPIPParameters

[TCPIPParameters]

DHCP = NO
IPAddress = 192.9.1.1 
Subnet = 255.0.0.0
Gateway = 111.1.1.1
DNSServer = 192.9.1.7, 192.9.1.8, 192.9.1.9
WINSPrimary = 111.2.2.2
WINSSecondary = 111.3.3.3
DNSName = microsoft.com
ScopeID = This_is_the_scope_id
Example: TCP/IP with DHCP, and adding DNS and WINS parameters
[Network]
InstallProtocols = SelectedProtocolsList

[SelectedProtocolsList]
TC = TCPIPParameters

[TCPIPParameters]

DHCP = YES
DNSServer = 192.9.1.7, 192.9.1.8, 192.9.1.9
WINSPrimary = 111.2.2.2
DNSName = microsoft.com
ScopeID = This_is_the_scope_id
Installing the SNMP Service

To install the Simple Network Management Protocol (SNMP) service, it must be specified in the section that you create and that you specify in the InstallServices key. The InstallServices key is described under "Installing Network Services" earlier in this Appendix. On the line that specifies the protocol, you name the section (also created by you) that contains the parameters for the protocol. This is illustrated in the example at the end of this section.

The supported parameters are as follows:

Accept_CommunityName = Name1, Name2, Name3 ;maximum of 3 names
Send_Authentication = Yes | No
Any_Host = Yes | No
Limit_Host = host1, host2, host3 ;limit to 3 hosts
Community_Name = name
Traps = IPaddress | IPXaddress ;maximum of 3 addresses
Contact_Name = name ;limit to 1 name
Location = location_name ;limit to 1 name
Service = Physical, Applications, Datalink, Internet, EndToEnd 
; Any combination is valid

For a discussion of these parameters, see Chapter 11, "Using SNMP for Network Management" in the Windows NT Server Networking Guide.

If a parameter is an IP address, all four octets must be specified in dotted decimal notation only.

Both TCP/IP and SNMP allow you to configure computers on a site basis and/or on a computer-specific basis. A site-based configuration configures each computer with identical parameters, whereas a computer-specific configuration allows a computer to have unique parameters. These two configurations can be mixed together. The generic or site-specific parameters are processed first. If computer-specific parameters exist, they are overlaid on the site-specific ones.

Example
[Network]
InstallServices = SelectedServicesList

[SelectedServicesList]
SNMP = SNMPParameters

[SNMPParameters]
Accept_CommunityName = MicrosoftCommunity
Send_Authentication = YES
Any_Host = NO 
Limit_Host = HostSystem 

Community_Name = MyCommunity
Traps = 1234567890AB, 192.001.001, 3456123456

Contact_Name = NT_Administration
Location = Building_26
Service = Physical, Datalink, Internet
Installing NWLNKIPX

To install NWLNKIPX, it must be specified in the "protocol_list_section" section specified by the InstallProtocols key described in the [Network] section. This is described under "Installing Network Protocols" earlier in this Appendix. In the protocol_list_section, include the following line:

NWLNKIPX = NetBEUI_parameters_section

The section you specify as the value for NWLNKIPX must exist, but is empty since NWLNKIPX does not require any parameters. For example, your answer file might include the following lines:

[Network]
InstallProtocols = SelectedProtocolsList

[SelectedProtocolsList]
NWLNKIPX = NWLNKIPX _params
TC = TCPIPParameters

[NWLNKIPX _params]

[TCPIPParameters]
.
.
.
Installing Client Service for NetWare (NWWKSTA option)

To install Client Service for NetWare, it must be specified in the section specified by the InstallServices key (the InstallServices key is included in the [Network] section). To the section specified by the InstallServices key, add the following line:

NWWKSTA = NetWareClientParametersSection

You can assign any name for the NetWareClientParametersSection. Create a section with that name and specify the NetWare client parameters that you want to use in that section. The recognized parameters are as follows:

DefaultLocation = server_location
DefaultScriptOptions = 0 | 1 | 3

DefaultLocation identifies the default logon server for the NetWare client. The DefaultScriptOptions key specifies the default action to take with scripts, and can be assigned any of the following values:

0

Do not run a script

1

Run NW 3.x level scripts only

3

Run NW 3.x or NW 4.x scripts

Example
[Network]
InstallServices = SelectedServicesList

[SelectedServicesList]
NWWKSTA = ClientNetwareParameters

[ClientNetwareParameters]
DefaultLocation = NWServer
DefaultScriptOptions = 0
Installing Remote Access Service (RAS)

To install Remote Access Service (RAS), include the following line in the section you defined with the InstallServices key in the [Network] section:

RAS = RAS_parameters_section

where RAS_parameters_section is a section that you define and use to specify the following parameters:

PortSections = MYCOM1, MYCOM2, MYCOM3-25
DialoutProtocols = TCP/IP | IPX | NETBEUI | ALL> 
DialinProtocols = TCP/IP | IPX | NETBEUI | ALL 
NetBEUIClientAccess = Network | ThisComputer
TcpIpClientAccess = Network | ThisComputer 
UseDHCP = YES | NO
StaticAddressBegin = IP_address
StaticAddressEnd IP_address
ExcludeAddress = IP_address1-IP_address2
ClientCanRequestIPAddress = YES | NO
IpxClientAccess = Network | ThisComputer
AutomaticNetworkNumbers = YES | NO
NetworkNumberFrom = IPX_net_number 
AssignSameNetworkNumber = YES | NO
ClientsCanRequestIpxNodeNumber YES | NO

Defaults and restrictions are as follows:

PortSections

Any number of port section names

DialoutProtocols

ALL implies all installed protocols

DialinProtocols

ALL implies all installed protocols

NetBEUIClientAccess

Default is Network

TcpIpClientAccess

Default is Network

UseDHCP

Default is YES

StaticAddressBegin

Required if UseDHCP = NO

StaticAddressEnd

Required if UseDHCP = NO

ExcludeAddress

One or more ranges, comma separated.
StaticAddressBegin and StaticAddressEnd should be specified.

ClientCanRequestIPAddress

Default is NO

IpxClientAccess

Default is Network

AutomaticNetworkNumbers

Default is YES

NetworkNumberFrom

1 to 0xFFFFFFFE; required if AutomaticNetworkNumbers is NO

AssignSameNetworkNumber

Default is YES

ClientsCanRequestIpxNodeNumber

Default is NO

DeviceType = Modem

 

If you have specified a "PortSection" you must create the section, which can have the following keys:

PortName = COM1 | COM2 | COM3-COM25
DeviceType = Modem
DeviceName = device_name
PortUsage = DialOut | DialIn | DialInOut

Where:

PortName indicates the names of the ports to be configured in a particular port section. DeviceType indicates the type of device RAS should install. For the current release of Windows NT Workstation, the only available device type is a modem. If DeviceType = Modem, the InstallModem key must be included in the [Modem] section. DeviceName specifies the name of the device to be installed. PortUsage defines the dialing properties for the ports being configured.

For a discussion of RAS features and parameters, see Chapter 5, "Understanding Remote Access Service" in the Networking Supplement included with the product documentation.

Example: RAS Using One Dialout Port
[Network]
InstallServices = SelectedServicesList

[SelectedServicesList]
RAS = RemoteAccessParameters

[RemoteAccessParameters]
PortSections = MYCOM1
DialoutProtocols = TCP/IP

[MYCOM1]
PortName = COM1
DeviceType = Modem
DeviceName = "Intel Fax Modem 144e"
PortUsage = DialOut
Example: RAS Using One Dialout, One Dialin and Four Dialin and Dialout Ports, With All Installed Protocols

This configuration uses default values for all protocols:

[Network]
InstallServices = SelectedServicesList

[SelectedServicesList]
RAS = RemoteAccessParameters

[RemoteAccessParameters]
PortSections = Dialin, Dialout, Dialinout
DialoutProtocols = ALL
DialinProtocols = ALL

[Dialin]
PortName = COM1
DeviceType = Modem
DeviceName = "USR Sportster V.34"
PortUsage = DialOut

[Dialout]
PortName = COM2
DeviceType = Modem
DeviceName = "USR Sportster V.34"
PortUsage = DialOut 

[Dialinout]
PortName = COM3-COM6
DeviceType = Modem
DeviceName = "USR Sportster V.34"
PortUsage = DialInOut
Example: RAS 16 Dialin Ports, With TCP/IP and DHCP Enabled
[Network]
InstallServices = SelectedServicesList

[SelectedServicesList]
RAS = RemoteAccessParameters

[RemoteAccessParameters]
PortSections = InternetPorts
DialoutProtocols = TCP/IP
DialinProtocols = TCP/IP
TcpIpClientAccess = Network
UseDHCP = YES
ClientCanRequestIPAddress = NO

[InternetPorts]
PortName = COM3-COM17
DeviceType = Modem
DeviceName = "USR Sportster V.34"
PortUsage = DialIn
Example: RAS 16 Dialin Ports, With TCP/IP and Static IP Address Pool
[Network]
InstallServices = SelectedServicesList

[SelectedServicesList]
RAS = RemoteAccessParameters

[RemoteAccessParameters]
PortSections = InternetPorts
DialoutProtocols = TCP/IP
DialinProtocols = TCP/IP
TcpIpClientAccess = Network
UseDHCP = NO
StaticAddressBegin = 101.16.1.1
StaticAddressEnd = 101.16.1.16
ClientCanRequestIPAddress = NO

[InternetPorts]
PortName = COM3-COM17
DeviceType = Modem
DeviceName = "USR Sportster V.34"
PortUsage = DialIn
Example: RAS 16 Dialin Ports, With IPX and Static IPX Address Pool
[Network]
InstallServices = SelectedServicesList

[SelectedServicesList]
RAS = RemoteAccessParameters

[RemoteAccessParameters]
PortSections = InternetPorts
DialoutProtocols = IPX
DialinProtocols = IPX
IpxClientAccess = Network
AutomaticNetworkNumbers = NO
NetworkNumberFrom = 0xa100
AssignSameNetworkNumber = NO
ClientsCanRequestIpxNodeNumber = NO

[InternetPorts]
PortName = COM3-COM17
DeviceType = Modem
DeviceName = "USR Sportster V.34"
PortUsage = DialIn

Hardware Support

This section describes keys you can add to specify what hardware is detected during setup, and what hardware support is installed.

Installing a Modem Driver For Use With RAS

If the RAS parameters include the line DeviceType = Modem, the following line must be included in the [Modem] section:

InstallModem = Modem _Parameter_Section

where Modem_Parameter_Section is a section that you create and give any name you choose. This section contains the parameters required to install the modem on a specified COM port. If the section is empty, RAS will detect modems on its pre-configured ports and install any modem it finds.

The [Modem_Parameter_Section] contains one line for each COM port on which a modem is to be installed, using the following syntax:

[Modem_Parameter_Section]
COMx = "description" [,Manufacturer, Provider]

Where:

COM x  identifies the COM port on which the modem is to be installed (for example COM1, COM2…) description must match a modem description in a Mdmxxxxx.inf file that corresponds to the modem to be installed. This string must be enclosed in quotes. Manufacturer is an optional field that identifies the manufacturer of a particular modem when description is not unique to a particular manufacturer. Provider is an optional field that identifies the provider of a particular modem when description is not unique to a particular manufacturer.

Using Hardware Detected by Setup

You can have the user confirm the hardware and mass storage devices detected by Setup, or you can specify that Setup proceed with the installation without seeking confirmation. Mass storage devices include any devices controlled by a SCSI mini port driver. For example, all CD-ROM drives, SCSI adapters, and hard drive controllers (except ATdisk, abiosdsk, and standard floppy disks) are mass storage devices.

To specify whether the user is to confirm the hardware detected, add the following line to the [Unattended] section:

ConfirmHardware = yes | no

Yes indicates that the user must confirm hardware and mass storage devices detected by the Setup program. No indicates that the Setup program should use hardware detected by the Setup program.

This key can only be specified in the answer file, not in the UDF.

Note If OEMPreinstall = yes, then the ConfirmHardware key is ignored.

Specifying Mass Storage Devices

When installing onto an x86-based computer, you can have Setup prepare the system for mass storage devices you specify, even if they are not physically present on the system at the time you perform the installation. To do so, add the section [DetectedMassStorage]. Copy the entries for the devices you want to specify from the [SCSI] section of the Txtsetup.sif file. This file is on the Setup boot floppy disks.

This section can only be specified in the answer file, not in the UDF.

If this section is present and contains entries, support for the specified devices will be included in the installation, as if the devices had actually been detected by Setup.

If this section is present and has no entries, the result is the same as if Setup detected no mass storage devices.

If this section is not present, Setup will attempt to detect the mass storage devices on the computer by loading all known miniport drivers.

Specifying a Keyboard Layout

To specify a keyboard layout, add the following line to the [Unattended] section:

KeyboardLayout = layout_description

This key is optional. If the KeyboardLayout key is not specified or is absent, Setup will detect and install a keyboard layout from the retail Windows NT Workstation product.

The layout_description value must match one of the strings in the [KeyboardLayout] section of Txtsetup.sif. 

This key can only be specified in the answer file, not in the UDF.

Per-User Settings

For a completely unattended installation, you must specify user settings in either the answer file or the UDF.

Specifying User Data

If the user's full name, the organization name, the computer name, and a product ID for the copy of Windows NT Workstation are not provided to the Setup program, the user will be prompted for them. This information can be included in an answer file, but it is generally more effective to provide it in a UDF. Indeed, the UDF functionality is designed to allow you specify a variant of the basic configuration for each user, rather than create separate answer files, one for each user, with most of the information copied in each answer file.

The section and keys are the same, whether you specify the data in an answer file or UDF. In the [UserData] section, add the following lines:

FullName = "User's full name"
OrgName = "Organization name"
ComputerName = computername
ProductId = "123-456789012345"

The ProductId key specifies the Microsoft product identification number. This must be an authentic number that will be requested by Microsoft Product Support Services if you call for technical support. Note that you must include the hyphen in the product identification number. Note also that for the FullName, OrgName, and ProductId keys, the value must be enclosed in quotation marks.

Specifying a Time Zone

If no time zone is specified, the user will be prompted to select one. To specify a time zone, add the following line to the [GuiUnattended] section:

TimeZone = "time_zone"

Where time_zone is one of the following:

(GMT) Greenwich Mean Time; Dublin, Edinburgh, London (GMT+01:00) Lisbon, Warsaw (GMT+01:00) Paris, Madrid (GMT+01:00) Berlin, Stockholm, Rome, Bern, Brussels, Vienna (GMT+02:00) Eastern Europe (GMT+01:00) Prague (GMT+02:00) Athens, Helsinki, Istanbul (GMT-03:00) Rio de Janeiro (GMT-04:00) Atlantic Time (Canada) (GMT-05:00) Eastern Time (US & Canada) (GMT-06:00) Central Time (US & Canada) (GMT-07:00) Mountain Time (US & Canada) (GMT-08:00) Pacific Time (US & Canada); Tijuana (GMT-09:00) Alaska (GMT-10:00) Hawaii (GMT-11:00) Midway Island, Samoa (GMT+12:00) Wellington (GMT+10:00) Brisbane, Melbourne, Sydney (GMT+09:30) Adelaide (GMT+09:00) Tokyo, Osaka, Sapporo, Seoul, Yakutsk (GMT+08:00) Hong Kong, Perth, Singapore, Taipei (GMT+07:00) Bangkok, Jakarta, Hanoi (GMT+05:30) Bombay, Calcutta, Madras, New Delhi, Colombo (GMT+04:00) Abu Dhabi, Muscat, Tbilisi, Kazan, Volgograd (GMT+03:30) Tehran (GMT+03:00) Baghdad, Kuwait, Nairobi, Riyadh (GMT+02:00) Israel (GMT-03:30) Newfoundland (GMT-01:00) Azores, Cape Verde Is. (GMT-02:00) Mid-Atlantic (GMT) Monrovia, Casablanca (GMT-03:00) Buenos Aires, Georgetown (GMT-04:00) Caracas, La Paz (GMT-05:00) Indiana (East) (GMT-05:00) Bogota, Lima (GMT-06:00) Saskatchewan (GMT-06:00) Mexico City, Tegucigalpa (GMT-07:00) Arizona (GMT-12:00) Enewetak, Kwajalein (GMT+12:00) Fiji, Kamchatka, Marshall Is. (GMT+11:00) Magadan, Soloman Is., New Caledonia (GMT+10:00) Hobart (GMT+10:00) Guam, Port Moresby, Vladivostok (GMT+09:30) Darwin (GMT+08:00) Beijing, Chongqing, Urumqi (GMT+06:00) Alma Ata, Dhaka (GMT+05:00) Islamabad, Karachi, Sverdlovsk, Tashkent (GMT+04:30) Kabul (GMT+02:00) Cairo (GMT+02:00) Harare, Pretoria (GMT+03:00) Moscow, St. Petersburg

For example:

TimeZone = "(GMT-08:00) Pacific Time (US & Canada); Tijuana"
Joining a Workgroup or Domain

The computer can be part of either a workgroup or a domain. If the computer is a server, a third option, domain controller, is available. The key for establishing the computer as a domain controller is described under "Windows NT Server Settings," later in this appendix.

To join a workgroup, the following key must be specified under the [Network] section:

JoinWorkgroup = workgroup_name

The workgroup_name value specifies the workgroup the computer will participate in.

To join an existing domain, specify the following under the [Network] section:

JoinDomain = domain_name

The domain_name value specifies the domain to join.

In the lab, you might also want to define user credentials (for example, Administrator) and password required to create a computer account on the domain specified. In this case you would add the following under the [Network] section:

JoinDomain = domain_name
CreateComputerAccount = [user_name_with_creation_rights
[, user_password]

The CreateComputerAccount key supplies the credentials and password to create the computer account. The user account specified in the CreateComputerAccount key must already exist in the specified domain.

The [Network] section must contain one of the keys JoinWorkgroup, JoinDomain, or InstallDC. The InstallDC key applies only to Windows NT Server, and is described under "Installing a Domain Controller."

Windows NT Server Settings

The following options apply only to installations of Windows NT Server:

Setting License Options

When installing Windows NT Server, you must specify whether the server is licensed in "per seat" or "per server" mode. If this is not specified in the answer file, Setup will prompt for the information.

To specify the license mode, add the following key to the [LicenseFilePrintData] section:

AutoMode = PerSeat | PerServer

If the AutoMode key is empty or missing, Setup prompts for the license mode.

PerSeat indicates that a client access license has been purchased for each computer that accesses the server.

PerServer indicates that client access licenses have been purchased for the server to allow a certain number of concurrent connections to the server. If AutoMode is set to PerServer, AutoUsers must also be specified, as follows:

AutoUsers = n

where n is the number of concurrent client connections that the server is licensed to support. This will be a number between 0 and 999999.

If AutoMode = PerServer and AutoUsers is missing or empty, Setup will prompt for the number of concurrent client connections that the server is licensed to support.

For information on the licensing modes, see Chapter 12, "Licensing and License Manager," in the Concepts and Planning Guide included with the Windows NT Server retail product. The chapter includes a worksheet to help you decide which licensing mode is best for your organization.

Installing A Domain Controller

When installing Windows NT Server, you can use the JoinWorkgroup or JoinDomain key in the [Network] section (as described under "Joining a Workgroup or Domain" earlier in this Appendix), or you can set the computer to be a domain controller. To establish the computer as a domain controller, add the following line to the [Network] section:

InstallDC = domain_name

If the specified domain does not exist, it will be created. This key is only valid if the server role has been set as a primary or backup domain controller and the AdvServerType key has been set accordingly.

If you are creating a backup domain controller (BDC), add the following line to the [Network] section to define the user credentials and password required to create a computer account on the domain specified:

CreateComputerAccount = [user_name_with_creation_rights
[, user_password]

The [Network] section must contain one of the keys JoinWorkgroup, JoinDomain, or InstallDC.

Example: Creating a Backup Domain Controller for the Marketing Domain
[Network]
InstallDC = Marketing
CreateComputerAccount = Administrator, FishScale

A computer account is also created for this computer, using the Administrator account and supplying the password (FishScale) for the Administrator account.

Setting the Server Role

A computer running Windows NT Server can be a standalone server, a primary domain controller (PDC), or a backup domain controller (BDC). To specify which role the computer is to have in the network, add the following line to the [GuiUnattended] section:

AdvServerType = SERVERNT | LANMANNT | LANSECNT

Where:

SERVERNT indicates that the computer will be a standalone server. LANMANNT indicates that the computer will serve as a primary domain controller (PDC). LANSECNT indicates that the computer will be a backup domain controller (BDC).

Installing the Internet Information Server (NT Server Only)

To install Internet Server on a Windows NT Server, add the following line to the [Network] section. This key is only valid for Windows NT Server, and will be ignored when installing Windows NT Workstation.

InstallInternetServer = Internet_Server_Parameter_Section
[Internet_Server_Parameter_Section]

where Internet_Server_Parameter_Section is a section that you create, and that contains parameters for installing Internet Server.

Example
[Network]
InstallInternetServer = InternetServerParameters
[InternetServerParameters]

Create a section called [INETSTP], and add some or all of the following keys, depending on the features you want to install, to that section:

InstallINETSTP= 1 | 0
InstallFTP=1 | 0
InstallWWW=1 | 0
InstallGOPHER=1 | 0
InstallADMIN=1 | 0
InstallMOSAIC=1 | 0
InstallGATEWAY=1 | 0
InstallDNS=1 | 0
InstallHELP=1 | 0
InstallSMALLPROX=1 | 0
InstallCLIENTADMIN=1 | 0
WWWRoot=c:\wwwroot
FTPRoot=c:\ftproot
GopherRoot=c:\gophroot
InstallDir=c:\inetsrv
EmailName=email_address
UseGateway=1 | 0
GatewaysList=\\gateway1 \\gateway2

Where the possible values for a key are 1 or 0; 1 means "yes" and 0 means "no." The effects of these keys are shown in the following table:

InstallINETSTP=

Specifies whether Internet Services will be installed.

InstallFTP=

Specifies whether the FTP Service will be installed.

InstallWWW=

Specifies whether the WWW Service will be installed.

InstallGOPHER=

Specifies whether the Gopher Service will be installed.

InstallADMIN=

Specifies whether the Internet Administrator Manager will be installed.

InstallMOSAIC=

Specifies whether the Internet Explorer Browser will be installed.

InstallGATEWAY=

Specifies whether the Gateway Service will be installed.

InstallDNS=

Specifies whether the DNS Service will be installed.

InstallHELP=

Specifies whether the HELP Files will be installed. (Applies to Windows NT Workstation only.)

InstallSMALLPROX=

Specifies whether the Access Gateway Proxy will be installed. (Applies to Windows NT Workstation only.)

InstallCLIENTADMIN=

Specifies whether the client administrator tools will be installed. (Applies to Windows NT Workstation only.)

WWWRoot=c:\wwwroot

Specifies the virtual root for the WWW service.

FTPRoot=c:\ftproot

Specifies the virtual root for the FTP service.

GopherRoot=c:\gophroot

Specifies the virtual root for the Gopher service.

InstallDir=c:\inetsrv

Specifies the installation directory for all components of Internet Services.

EmailName=email_name

Specifies the Internet e-mail name of the user.

UseGateway=

Specifies whether a gateway is to be used.

GatewaysList=\\gateway1 \\gateway2

Lists the gateways to be used (if UseGateway=1).

Using an Extended Partition for Text Mode Files

Cc749979.spacer(en-us,TechNet.10).gif Cc749979.spacer(en-us,TechNet.10).gif

If you are installing Windows NT Workstation on a disk larger than 2 GB, you can cause Setup to extend the partition on which the temporary files are located into any available unpartitioned space that physically follows it on the disk. These temporary files must be installed on a primary partition. The space used must be limited to 1024 cylinders. Writing beyond cylinder 1024 will cause the installation to fail.

To control whether Setup extends the partition on which the temporary files are located, add the following line to the [Unattended] section:

ExtendOemPartition = 0 | 1

Where:

0 specifies that the partition not be extended. 1 specifies that the partition is to be extended. When the value is 1, you must set FileSystem = ConvertNTFS.

Stopping Setup Before GUI Mode Begins

Cc749979.spacer(en-us,TechNet.10).gif Cc749979.spacer(en-us,TechNet.10).gif

If OEMPreinstall = Yes, the Setup program stops at the end of text mode by default, rather than continuing into GUI mode. This gives you the ability to duplicate disks with the operating system and applications pre-installed. The first time a computer is started with the duplicated disk in place, the system boots into GUI mode. The user can then be prompted for information such as username, computername, and the Workgroup or Domain that the computer is to join.

You can specify whether Setup continues into GUI mode at the end of text mode by adding the following line to the [Unattended] section:

NoWaitAfterTextMode = 0 | 1

Where:

0 specifies that Setup should stop at the end of text mode. 1 specifies that Setup should automatically reboot into GUI mode at the end of text mode.

Sample Unattend.txt File

Cc749979.spacer(en-us,TechNet.10).gif Cc749979.spacer(en-us,TechNet.10).gif

[Unattended]
Method = express
TargetPath = srv1231

[GuiUnattended]
AdvServerType = SERVERNT
; AdvServerType = LANMANNT (PDC) | LANSECNT (BDC) | SERVERNT (STANDALONE)
TimeZone = "(GMT-08:00) Pacific Time (US & Canada); Tijuana"

[UserData]
FullName = "John L. Smith"
OrgName = "Microsoft"
ComputerName = JohnSm_1 
ProductId = "123456789012345"

[LicenseFilePrintData]
AutoMode = PerSeat

[Network]
DetectAdapters = DetectParams
; InstallAdapters = AdaptersList
InstallProtocols = ProtocolsList
; InstallServices = ServicesList

; JoinWorkgroup = OurWorkGroup 

JoinDomain = NTWKSTA
CreateComputerAccount = JohnSm, FriedFrogs

; for a PDC install
; InstallDC = Our_DOMAIN

; for a BDC install
; InstallDC = Our_DOMAIN
; CreateComputerAccount = Administrator, FishScale

[DetectParams]
DetectCount = 1
LimitTo = IEEPRO, ELNKII

[AdaptersList]
IEEPRO = IntelEEProParams
ELNKII = 3ComELIIParams

[ProtocolsList]
TC = TCPIPParams
; NBF = NetBEUIParams
; NWLNKIPX = NWLinkIPXParams

[ServicesList]
RAS = RemoteAccessParameters

[IntelEEProParams]
Interrupt = 5
IoChannelReady = 4
Transceiver = 4
IoAddress = 784

; irq = 5
; i/o = 0x310
; io channel = auto
; transceiver = auto

[3ComELIIParams]
InterruptNumber = 2
IOBaseAddress = 512
Transceiver = 2
MemoryMapped = 0

; where Transceiver = 1 - External; 2 - On Board
; MemoryMapped = 1 - ON; 0 - OFF

; Optional:
; !AutoNetInterfaceType = 0 | 1 | 2 ...
; !AutoNetBusNumber = 0 | 1 | ...

[RemoteAccessParameters]
PortSections = MYCOM1
DialoutProtocols = TCP/IP

[MYCOM1]
PortName = COM1
DeviceType = Modem
DeviceName = "Intel Fax Modem 144e"

PortUsage = DialOut 

Cc749979.spacer(en-us,TechNet.10).gif

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft