(Remote Installation Services)
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
[Unattended]
The [Unattended] section contains entries for running Setup.
This section is required in the answer file. Otherwise, Setup ignores the answer file.
Answer File Entries for the [Unattended] Section
| Entry | Description |
|---|---|
ActivateProxy |
Specifies the proxy settings to use when connecting to the Internet to activate this installation of Windows XP, if you set AutoActivate to Yes. |
AutoActivate |
Specifies whether Setup attempts to activate this installation of Windows XP automatically through an existing Internet connection. |
ComputerType |
Specifies the type of custom hardware abstraction layer (HAL) that Windows Setup Loader loads and installs in the intermediate (text-mode) stage of Setup. |
CrashDumpSetting |
Specifies the creation and type of the dump file. |
DisableVirtualOemDevices |
Specifies whether to load virtual OEM devices during the Windows setup process. |
DUDisable |
Specifies whether to connect to the Windows Update site to download updates during the Windows setup process. |
DUShare |
Specifies the location for downloaded Dynamic Update .cab files. |
DUStopOnError |
Specifies how Dynamic Update behaves when errors are encountered during download |
DriverSigningPolicy |
Specifies how to process unsigned drivers during unattended installation. |
ExtendOemPartition |
Specifies whether to extend the partition on which you install Windows. |
FactoryMode |
Specifies whether systemdrive\Sysprep\Factory.exe runs on first start. |
FileSystem |
Specifies whether to convert the primary partition to NTFS. |
ForceHALDetection |
Specifies whether the Intermediate (text-mode) stage of Setup examines the operating system and determines the most appropriate HAL to install during an upgrade. |
Hibernation |
Specifies whether to enable the hibernation option in the Power Options control panel. |
KeyboardLayout |
Specifies the type of keyboard layout to install during the intermediate (text-mode) stage of Setup. |
NtUpgrade |
Specifies whether Setup upgrades a previous version of Windows NT 3.51, Windows NT 4.0, Windows 2000, Windows XP, or Windows Server 2003. |
OemFilesPath |
Specifies the path to the \$OEM$ folder (containing OEM files) if it does not exist under the i386 folder of the distribution share point. |
OemPnPDriversPath |
Specifies the path to one or more folders that contain Plug and Play drivers not distributed in Drivers.cab on the Windows product CD. |
OemPreinstall |
Specifies whether Setup installs its files from distribution folders. |
OemSkipEula |
Specifies whether the user must accept the End-User License Agreement (EULA) included with Windows. |
OverwriteOemFilesOnUpgrade |
Specifies whether to overwrite OEM-supplied files that have the same name as Windows XP or Windows Server 2003 operating system files during an unattended upgrade. |
Repartition |
Specifies whether to delete all partitions on the first drive of the client computer and to reformat the drive with the NTFS file system. |
TargetPath |
Determines the installation folder in which you install Windows. |
UnattendMode |
Defines the unattended mode to use during the final (GUI-mode) stage of Setup. |
UnattendSwitch |
Specifies whether Setup skips Windows Welcome or Mini-Setup when preinstalling Windows XP Home Edition or Windows XP Professional by using the CD Boot method. |
WaitForReboot |
Specifies whether the computer waits 15 seconds after the final (GUI-mode) stage finishes. |
Win9xUpgrade |
Specifies whether Setup upgrades previous installations of Windows 98, Windows 98 Second Edition, or Windows Me to either Windows XP Home Edition or Windows XP Professional, as specified in the [Win9xUpg] section of the answer file. |
ActivateProxy
Specifies the proxy settings to use when connecting to the Internet to activate this installation of Windows XP, if you use the entry AutoActivate = Yes.
Syntax
ActivateProxy = section_name| Proxy
| Value | Description |
|---|---|
section_name |
Section of the answer file from which to read Proxy settings. |
Proxy |
Reads Proxy setting from the [Proxy] section of the answer file. |
Example
[Unattended]
ActivateProxy = Proxy
Comments
If section_name is Proxy, Windows Product Activation (WPA) uses the proxy settings specified in the [Proxy] section. If section_name is any other section, WPA uses the proxy settings specified in the section specified by section_name in the answer file. The entries in the [section_name] section must match the syntax specified in the [Proxy] section.
If your network uses Web Proxy Auto-Discovery (WPAD), you might not need to set the proxy explicitly.
AutoActivate
Specifies whether Setup attempts to activate this installation of Windows XP automatically through an existing Internet connection.
Syntax
AutoActivate = Yes | No
| Value | Description |
|---|---|
Yes |
Attempts to activate this installation of Windows XP during unattended installation through an existing Internet connection on the computer. |
No |
Requires the user to activate Windows XP either through an Internet connection or by phone. |
Example
[Unattended]
AutoActivate = Yes
Comments
The default value is No.
You must specify a valid product key in the ProductKey entry of the [UserData] section. If the Internet connection is through a firewall, you might need to specify the relevant proxy settings in the ActivateProxy entry.
This entry always requires a product key.
The product key you use to activate this installation using Windows Product Activation (WPA) must match the number on the Certificate of Authenticity (COA). The original equipment manufacturer (OEM) packages the COA with the retail product or affixes it to the computer case.
Standard licensing agreements specify that you can use a given product key to activate only one installation of Windows XP on one computer. WPA enforces this requirement.
If you start the unattended installation with Winnt.exe, you must use the entry UnattendSwitch = Yes.
Setting AutoActivate to Yes does not guarantee successful activation of this installation of Windows XP. For example, the activation attempt will fail if the computer cannot successfully connect to the Internet.
ComputerType
Specifies the type of custom hardware abstraction layer (HAL) that Windows Setup Loader loads and installs during the intermediate (text-mode) stage of Setup.
Syntax
ComputerType = HAL_description[, Retail | OEM]
| Value | Description |
|---|---|
HAL_description |
Identifies the HAL to install. It must match one of the strings in the [Computer] section of TxtSetup.sif (for a retail HAL) or TxtSetup.oem (for an OEM HAL). |
Retail |
Informs Setup that the HAL to install is part of Windows XP or Windows Server 2003. |
OEM |
Indicates that the HAL to load is OEM-supplied. If this is the case, you must also list the driver name in the [OEMBootFiles] section of the answer file. |
Example
[Unattended]
ComputerType = "Advanced Configuration and Power Interface (ACPI) PC", Retail
Comments
This entry is valid only when you use the entry OemPreinstall = Yes. If the ComputerType entry is not present, Setup attempts to detect the type of computer and install the appropriate retail HAL.
CrashDumpSetting
Specifies the creation and type of the dump file.
Syntax
CrashDumpSetting = 0 | 1 | 2 | 3
| Value | Description |
|---|---|
0 |
Does not create a dump file. |
1 |
Complete Memory Dump: Records the entire contents of system memory to systemroot\Memory.dmp when the system stops unexpectedly. If you choose this value, you must have a paging file on the boot volume large enough to hold all of the physical RAM plus 1 megabyte (MB). |
2 |
Kernel Memory Dump: Records only kernel memory to systemroot\Memory.dmp when the system stops unexpectedly. This speeds up the process of recording information in a log. Depending on the amount of RAM in your computer, you must have 50 MB to 800 MB available for the paging file on the boot volume. |
3 |
Small Memory Dump (64K): Records the smallest set of useful information that can help identify the problem to systemroot\Mini.dmp. This value requires a paging file of at least 2 MB on the boot volume of your computer and specifies that Setup creates a new file each time the system stops unexpectedly. |
Example
[Unattended]
CrashDumpSetting = 0
Comments
The default value is 3 for Windows XP Home Edition and Windows XP Professional. The default value is 1 for Windows Server 2003.
When the system fails, you can create a dump file that contains information useful for debugging. Dump file types vary by size. The system checks for available space on the boot volume and writes the largest possible dump file.
DisableVirtualOemDevices
Specifies whether to load virtual OEM devices during the Windows setup process.
Syntax
DisableVirtualOemDevices = Yes | No
| Value | Description |
|---|---|
Yes |
Disables loading virtual OEM devices during the Windows setup process. |
No |
Does not disable loading virtual OEM devices during the Windows setup process. |
Example
[Unattended]
DisableVirtualOemDevices = Yes
Comments
The default value is Yes for preinstallation; No otherwise.
An example of a virtual OEM device is a RAM disk that has mass storage drivers, related .inf files, and so on.
During an attended installation, you can disable loading of virtual OEM devices by pressing F4 at the prompt to press the F6 key.
DUDisable
Specifies whether to connect to the Windows Update site to download updates during the Windows setup process.
Syntax
DUDisable = Yes | No
| Value | Description |
|---|---|
Yes |
Instructs Setup not to connect to the Windows Update site. |
No |
Instructs Setup to connect to the Windows Update site to download any available Windows XP Setup updates. Setup also downloads any necessary drivers that are not on the Windows XP product CD. |
Example
[Unattended]
DUDisable = No
Comments
The default value is Yes.
This entry specifies whether Setup connects to the Windows Update site to download any available Setup updates or necessary drivers that are not on the Windows product CD.
DUDisable is equivalent to the command:
winnt32 /unattend /dudisable
Setup disables dynamic updates by default so that corporate administrators can more easily standardize on a known set of Windows system components.
DUShare
Specifies the location for downloaded Dynamic Update .cab files.
Syntax
DUShare = path_to_downloaded_cabs
| Value | Description |
|---|---|
path_to_downloaded_cabs |
Specifies the location for all downloaded Dynamic Update .cab files. |
Example
[Unattended]
DUShare = "%systemdrive%\DU_Cabs"
Comments
You must run the following command before using this entry.
winnt32 /DUPrepare:path_to_downloaded_cabs
When a path is specified, the Dynamic Update wizard page is not shown and Setup does not try to connect to Windows Update. Instead, Setup uses the Dynamic Update .cab files from this shared folder.
DUStopOnError
Specifies how Dynamic Update behaves when errors are encountered during download.
Syntax
DUStopOnError = Yes | No
| Value | Description |
|---|---|
Yes |
Stop downloading updates when an error is detected. |
No |
Keep downloading updates if an error is detected. |
Example
[Unattended]
DUStopOnError = No
Comments
The default value is Yes.
Errors include any failure in processing the updated Setup .cab files or the inability to connect to the Windows Update site.
DriverSigningPolicy
Specifies how to process unsigned drivers during unattended installation.
Syntax
DriverSigningPolicy = Block | Warn | Ignore
| Value | Description |
|---|---|
Block |
Setup does not install the unsigned device driver. |
Warn |
Setup stops the installation and prompts the user for input before accepting the unsigned device driver. |
Ignore |
Setup continues despite the unsigned driver. |
Example
[Unattended]
DriverSigningPolicy = Block
Comments
The default value is Warn.
Signed drivers have gone through the Microsoft driver testing and signing process to ensure they are compatible with Windows XP and Windows Server 2003.
Microsoft strongly advises against using the entry DriverSigningPolicy = Ignore unless you have fully tested the device driver in your environment and are sure that it works properly. Using unsigned drivers increases the risk of device driver problems that can affect the performance or stability of the computer.
If you are using the entry DriverSigningPolicy = Ignore and you attempt to install a newer, unsigned copy of a driver that is distributed with Windows XP or Windows Server 2003, Setup installs the signed Windows XP driver instead of the unsigned drivers, in accordance with the ranking process used by the operating system.
A catalog certificate (.cat) file authenticates a driver signature. Microsoft can only use the given certificate to sign drivers for a finite length of time, generally six months. However, as long as you have a digitally signed driver, the subsequent expiration date of the certificate does not affect the status of the driver. A driver signature does not expire, even after the certificate used to sign the driver has expired.
ExtendOemPartition
Specifies whether to extend the partition on which you install Windows.
Syntax
ExtendOemPartition = 0 | 1 |extra_size_in_MB
| Value | Description |
|---|---|
0 |
Setup does not extend the partition. |
1 |
Setup extends the partition to fill out the hard disk. |
extra_size_in_MB |
Setup increases the current partition size by this amount. This is useful if you want to configure more than one partition on the hard disk. |
Example
[Unattended]
ExtendOemPartition = 1000
Comments
This entry causes Setup to extend this destination partition into any available unpartitioned space that physically follows it on the disk.
ExtendOemPartition automatically leaves the last cylinder on the hard disk free to allow dynamic disk support.
Note
You can extend only NTFS file system partitions.
The partition that you want to extend must have unpartitioned space available following the partition.
If your manufacturing process requires FAT32, use the Oformat command-line tool included in the OEM Preinstallation Kit to format the hard disk so that you configure it for NTFS. Use the Convert command-line tool to convert the file system.
You can also convert the partition during the intermediate (text-mode) stage of Setup by setting the FileSystem in the [Unattended] section of the answer file to ConvertNTFS. However, the hard disk performs better if you use the Convert command-line tool instead of the FileSystem entry.
FactoryMode
Specifies whether systemdrive\Sysprep\Factory.exe runs on first start.
Syntax
FactoryMode = Yes | No
| Value | Description |
|---|---|
Yes |
Systemdrive\Sysprep\Factory.exe runs on first start. |
No |
Systemdrive \Sysprep\Factory.exe does not run on first start. |
Example
[Unattended]
FactoryMode = Yes
Comments
The default value is No.
This entry is only applicable if you are performing image-based installations with Sysprep. Use this entry when performing a clean installation of the operating system as the first step in building a master installation, which you plan to duplicate onto multiple destination computers. The entry FactoryMode = Yes will start the computer into a network-enabled state known as Factory mode, where system configuration can be done before imaging.
FileSystem
Specifies whether to convert the primary partition to NTFS.
This entry does not change the file system of the primary partition.
Syntax
FileSystem = ConvertNTFS | LeaveAlone
| Value | Description |
|---|---|
ConvertNTFS |
Converts the primary partition to NTFS. |
LeaveAlone |
Does not convert the primary partition to NTFS. |
Example
[Unattended]
FileSystem = LeaveAlone
Comments
This entry is provided for backward compatibility with the Windows 2000 unattended installation.
For the Windows XP and Windows Server 2003 operating systems, if your manufacturing processes require that you format the hard disk as FAT32, use the Oformat tool to create a FAT32 volume with clusters aligned in an optimal way for later conversion to the NTFS file system. Then use the Convert command-line tool to convert the file system to NTFS.
You can also convert the partition during the intermediate (text-mode) stage of Setup by setting the FileSystem entry equal to ConvertNTFS. However, the hard disk performs better if you use the Convert command-line tool instead of the FileSystem entry.
If you plan to use ExtendOemPartition during the Windows setup process, the file system must be NTFS.
ForceHALDetection
Specifies whether the intermediate (text-mode) stage of Setup examines the operating system and determines the most appropriate HAL to install during an upgrade.
Syntax
ForceHALDetection = Yes | No
| Value | Description |
|---|---|
Yes |
Installs the most appropriate HAL for the new operating system. |
No |
Keeps the HAL from the previous operating system. |
Example
[Unattended]
ForceHALDetection = Yes
Comments
The default value is No.
If you use the entry ForceHALDetection=Yes during an upgrade, Setup might lose some user-specified hardware settings.
If you use the entry ForceHALDetection=No during an upgrade, Setup preserves user-specified hardware settings.
Hibernation
Specifies whether to enable the hibernation option in the Power Options control panel.
Syntax
Hibernation = Yes | No
| Value | Description |
|---|---|
Yes |
Enables hibernation. |
No |
Disables hibernation. |
Example
[Unattended]
Hibernation = No
Comments
The default value is Yes.
This entry is not supported on the 64-bit versions of Windows Server 2003. This setting adds Hibernate to the Shutdown menu and creates the Hiberfil.sys file.
To keep the size of your image file as small as possible, you can delete the hibernation file (Hiberfil.sys), if it exists, from your master installation.
The Hiberfil.sys file created during hibernation mode is as large as the available RAM on the computer. Before beginning hibernation mode, verify that the amount of free disk space on your computer’s hard disk drive is greater than or equal to the amount of RAM in the computer.
Setup does not support hibernation if any driver or video card does not support Plug and Play.
For Windows Server 2003, Enterprise Edition and Windows Server 2003, Datacenter Edition, you cannot use hibernation if the computer uses Terminal Server or if the Physical Address Extension (PAE) Kernel supports 3 GB or more of memory.
KeyboardLayout
Specifies the type of keyboard layout to install during the intermediate (text-mode) stage of Setup.
Syntax
KeyboardLayout = layout_description
| Value | Description |
|---|---|
layout_description |
Keyboard layout. |
Example
[Unattended]
KeyboardLayout = US
Comments
If this entry does not exist, Setup detects and installs a keyboard layout.
This entry must match one of the right-hand strings (in quotation marks) in the [Keyboard Layout] section of TxtSetup.sif.
NtUpgrade
Specifies whether Setup upgrades a previous version of Windows NT 3.51, Windows NT 4.0, Windows 2000, Windows XP, or Windows Server 2003.
Syntax
NtUpgrade = Yes | No
| Value | Description |
|---|---|
Yes |
Upgrades a previous version of Windows. Only these entries are processed: Productkey, AutoActivate, DuDisable, DuShare, and DuStopOnError. |
No |
Does not upgrade a previous version of Windows. |
Example
[Unattended]
NtUpgrade = No
Comments
This entry is valid only for Winnt32.exe. To upgrade from Windows 98 or Windows Me, use the Win9xUpgrade entry.
Use the entry NtUpgrade = Yes to upgrade the previous Windows installation. If you use the entry OemPreinstall = Yes, do not use NtUpgrade = Yes.
This entry upgrades your previous version of Windows XP, Windows Server 2003, Windows 2000, Windows NT 4.0, or Windows NT 3.51. Setup takes all user settings from the previous installation, and does not require user intervention.
OemFilesPath
Specifies the path to the \$OEM$ folder (containing OEM files) if it does not exist under the i386 folder of the distribution share.
Syntax
OemFilesPath = path_to_$OEM$_folder
| Value | Description |
|---|---|
path_to_$OEM$_folder |
Path to OEM folder. |
Example
[Unattended]
OemFilesPath = "%systemdrive%\OEM_Files"
Comments
The path can be a UNC name. Enclose path_to_$OEM$_folder in quotation marks if it is a long file name.
OemPnPDriversPath
Specifies the path to one or more folders that contain Plug and Play drivers not distributed in Drivers.cab on the Windows product CD.
Syntax
OemPnPDriversPath = folder_1_on_system_drive[;folder_2_on_system_drive]...
| Value | Description |
|---|---|
folder_1_on_system_drive[;folder_2_on_system_drive]... |
Folder. |
Example
[Unattended]
OemPnPDriversPath = MyFolder1;MyFolder2
Comments
You must also use the entry OEMPreinstall = Yes.
The folders must contain all the files necessary to install the particular devices: catalog files, .inf files, and drivers.
For example, if you have a folder called \Drivers with subfolders called \Audio and \Net, use the entry OemPnPDriversPath = drivers\audio;drivers\net in the answer file. Setup adds:
%systemdrive% to each of the folder names
Path for each subfolder to the Plug and Play device search path.
The length of the OemPnPDriversPath entry in the answer file must not exceed 4096 characters.
You cannot use environment variables to specify the location of a folder.
Always use signed drivers. Signed drivers make the operating system more stable and significantly reduce requests for product support.
When using OemPnPDriversPath in the answer file, be sure that the folders are available during the final (GUI-mode) stage or during the first logon. The easiest way to do this is to place the Plug and Play drivers in the \$OEM$\$1 folder. To prevent users from inadvertently deleting driver folders located at the root of the drive, you can place drivers under the \$OEM$\$$ folder (for example: $OEM$\$$\PnP\Audio).
If the drivers are not in the Drivers.cab file on the computer’s hard disk or in the location specified by OemPnPDriversPath, Setup prompts the user for the location of the drivers during the first startup of the computer, before Windows Welcome or Mini-Setup.
You can also use the [PnPDrivers] section in Winbom.ini to update drivers on a previously-created image of the installed operating system.
OemPreinstall
Specifies whether Setup installs its files from distribution folders.
Syntax
OemPreinstall = Yes | No
| Value | Description |
|---|---|
Yes |
Setup copies the subfolders and files contained in the I386 \$oem$ folder. |
No |
Setup does not copy these files. |
Example
[Unattended]
OemPreinstall = Yes
Comments
If you use the entry OemPreinstall = Yes, do not use the entry NtUpgrade = Yes.
OemSkipEula
Specifies whether the user must accept the End-User License Agreement (EULA) included with Windows.
Syntax
OemSkipEula = Yes | No
| Value | Description |
|---|---|
Yes |
Does not prompt the user to accept the EULA. This setting implies that the person performing the installation has read and agreed to the contents of the license agreement included with the product. It also implies that the user on whose behalf you install Windows has agreed to the license agreement. |
No |
Prompts the user to accept the EULA. This setting implies that the person performing the installation and the user have not read and agreed to the license agreement. |
Example
[Unattended]
OemSkipEula = Yes
Comments
You must not use this entry to remove the Microsoft End-User License Agreement screen because users must see and accept it.
OverwriteOemFilesOnUpgrade
Specifies whether to overwrite OEM-supplied files that have the same name as Windows XP or Windows Server 2003 files during an unattended upgrade.
Syntax
OverwriteOemFilesOnUpgrade = Yes | No
| Value | Description |
|---|---|
Yes |
Overwrites the old files if found. |
No |
Does not overwrite the old files if found. |
Example
[Unattended]
OverwriteOemFilesOnUpgrade = No
Comments
The default value is Yes.
This entry is provided for backward compatibility with Windows 2000.
Repartition
Specifies whether to delete all partitions on the first drive of the client computer and to reformat the drive with the NTFS file system.
Syntax
Repartition = Yes | No
| Value | Description |
|---|---|
Yes |
Deletes all partitions on the first drive and reformats the drive with NTFS. |
No |
Does not delete partitions or reformat the drive. |
Example
[Unattended]
Repartition = Yes
Comments
The Repartition entry is valid only when performing an unattended installation by starting the computer from the Windows product CD.
TargetPath
Determines the installation folder in which you install Windows.
Syntax
TargetPath = * |target_path
| Value | Description |
|---|---|
* |
Setup generates a unique folder name for the installation. |
target_path |
Setup installs to the specified folder. |
Example
[Unattended]
TargetPath = *
Comments
An asterisk (*) indicates that Setup generates a unique folder name for the installation. The folder name given is usually Windows, unless that folder already exists. In that case, Setup installs into Windows.x (where x is 0, 1, ... 999) if these folders do not already exist.
The path must use 8.3 file names. Do not include the drive letter in target_path. If you want to specify the destination drive, you must use the /tempdrive command-line option when you run Winnt32.exe.
UnattendMode
Defines the unattended mode to use during the final (GUI-mode) stage of Setup.
Syntax
UnattendMode = DefaultHide | FullUnattended | GuiAttended | ProvideDefault | ReadOnly
| Value | Description |
|---|---|
DefaultHide |
Specifies that answers in the answer file are defaults. Unlike with the ProvideDefault value, Setup does not display the user interface to users if you specify in the answer file all the answers relating to a particular Setup page. If you specify only subsets of the answers on a page, the page appears with the provided answers. The user can modify any of the answers on the displayed page. Use the DefaultHide value in deployment scenarios where an administrator might want only users to provide the administrator password on the computer. This behavior is the default if you do not specify a value for the UnattendMode entry. |
FullUnattended |
Specifies a fully unattended final (GUI-mode) stage of Setup. If you do not specify a required Setup answer in the answer file, Setup generates an error. During an attended installation, improperly signed hardware drivers generate a warning dialog box. If you use the FullUnattended value, then Setup does not install hardware drivers unless they are properly signed. Use the FullUnattended value in deployment scenarios where you require a complete hands-off installation. |
GuiAttended |
Specifies an attended final (GUI-mode) stage of the installation. When specified, the user must answer all questions in the final stage of the installation before Setup finishes. Use the GuiAttended value in preinstallation scenarios when you want to automate only the intermediate (text-mode) stage of Setup. |
ProvideDefault |
Specifies default answers in the answer file. In this case, Setup displays these default answers to the user, who can change them if they are not appropriate. Use the ProvideDefault value in preinstallation scenarios where the OEM or administrator wants to give the person setting up the computer the option to change the predefined default answers (especially network options). |
ReadOnly |
Specifies read-only answers in the answer file if the Setup pages containing these answers appear to the user. Like the ProvideDefault value, no user interface appears if the answer file contains all the answers on a page. Unlike the DefaultHide value, however, the user can specify only new answers on a displayed page. Use the ReadOnly value in scenarios where an administrator wants to force specific answers on one page but not others. |
Example
[Unattended]
UnattendMode = FullUnattended
Comments
The default value is DefaultHide when you do not specify the entry. When you specify this entry, it fully automates the intermediate (text-mode) stage of Setup with or without the necessary answers.
UnattendSwitch
Specifies whether Setup skips Windows Welcome or Mini-Setup when preinstalling Windows XP Home Edition or Windows XP Professional by using the CD Boot method.
Syntax
UnattendSwitch = Yes | No
| Value | Description |
|---|---|
Yes |
Instructs Setup to skip Windows Welcome. |
No |
Instructs Setup not to skip Windows Welcome. |
Example
[Unattended]
UnattendSwitch = Yes
Comments
The default value is No.
Use UnattendSwitch only when you perform an unattended installation by using Winnt.exe, Winnt.sif, and the CD Boot method. This entry is not necessary if you use Winnt32.exe to run Setup.
UnattendSwitch is not the same as the UnattendedInstall entry in the [Data] section of the answer file. UnattendSwitch controls Windows Welcome; UnattendedInstall does not.
WaitForReboot
Specifies whether the computer waits 15 seconds after the final (GUI-mode) stage of Setup finishes.
Syntax
WaitForReboot = Yes | No
| Value | Description |
|---|---|
Yes |
Delays the restart for 15 seconds after the final stage of Setup finishes. |
No |
Restarts immediately after the final stage of Setup finishes. |
Example
[Unattended]
WaitForReboot = No
Comments
The default value is Yes.
Win9xUpgrade
Specifies whether Setup upgrades previous installations of Windows 98, Windows 98 Second Edition, or Windows Me to either Windows XP Home Edition or Windows XP Professional, as specified in the [Win9xUpg] section of the answer file.
Syntax
Win9xUpgrade = Yes | No
| Value | Description |
|---|---|
Yes |
Instructs Setup to upgrade the Windows installation, if found. |
No |
Instructs Setup not to upgrade the Windows installation, if found. |
Example
[Unattended]
Win9xUpgrade = Yes
Comments
The default value is No.
This entry is necessary only when using an answer file to upgrade an existing Windows 98-based or Windows Me-based computer to Windows XP Home Edition or Windows XP Professional. This entry is valid only when using Winnt32.exe for the installation.
For more information, see the section “[Uninstall].”