ActivateProxy = Proxy

Note

• If your network uses Web Proxy Auto-Discovery (WPAD), you may not need to set the proxy explicitly.

Attempts to activate this installation of Windows XP during unattended Setup through an existing Internet connection on the computer.

Requires the end user to activate Windows XP either through an Internet connection or by telephone.

AutoActivate = Yes

Important

• Always requires a Product Key.
• The Product Key that 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 use Winnt.exe to install Windows, you must set UnattendSwitch to 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.

HAL_description [, Retail | OEM]

Informs Setup that the HAL to install is part of Windows XP or Windows Server 2003 family.

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 Unattend.txt file.

ComputerType = "OEM HAL", OEM
ComputerType = "Advanced Configuration and Power Interface (ACPI) PC", Retail

The HAL_description string identifies the Hardware Abstraction Layer (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).

Does not create a dump file.

Complete Memory Dump: Records the entire contents of system memory to %SYSTEMROOTt%\Memory.dmp when the system stops unexpectedly. If you choose this option, you must have a paging file on the boot volume large enough to hold all of the physical random access memory (RAM) plus 1 megabyte (MB).

Kernel Memory Dump: Records only kernel memory to %SYSTEMROOTt%\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.

Small Memory Dump (64K): Records the smallest set of useful information that can help identify the problem to %SYSTEMROOTt%\Mini.dmp. This option 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.

CrashDumpSetting = 0

Disables loading virtual OEM devices during Setup.

Does not disable loading virtual OEM devices during Setup.

DisableVirtualOemDevices = Yes

During attended Setup, you can disable loading of virtual OEM devices by pressing F4 at the prompt to press the F6 key.

Instructs Setup not to connect to the Windows Update site.

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 CD-ROM.

DUDisable = No

DUDisable is equivalent to the command:

winnt32 /unattend /dudisable

Setup disables dynamic updates by default so corporate administrators can more easily standardize on a known set of Windows system components.

Specifies the location for all downloaded Dynamic Update .cab files.

DUShare = "%SYSTEMDRIVE%\DU_Cabs"

Stops the Windows Update process when an error is detected.

Does not stop the Windows Update process when an error is detected.

DUStopOnError = Yes

Setup does not install the unsigned device driver.

Setup stops the installation and prompts the end user for input before accepting the unsigned device driver.

Setup continues despite the unsigned driver.

DriverSigningPolicy = Block

Important

• Microsoft strongly advises against using 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 DriverSigningPolicy = Ignore and you attempt to install a newer, unsigned copy of a driver that distributed with Windows XP or the Windows Server 2003 family, 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.

For more information, see:

• Windows Hardware and Driver Central Web site (http://www.microsoft.com/whdc/)
• Driver Signing for Windows (http://www.microsoft.com/whdc/hwdev/driver/digitsign.mspx)

For more information about driver ranking and how Setup chooses the correct driver, see the Microsoft Device Development Kit (http://www.microsoft.com/ddk/).

Setup does not extend the partition.

Setup extends the partition to fill out the hard disk.

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.

ExtendOemPartition = 1000

ExtendOemPartition automatically leaves the last cylinder on the hard disk free to allow dynamic disk support.

Important

• You can extend only NTFS file system partitions.
• When you use ExtendOEMPartition in Sysprep.inf for imaged computers, the destination computerÆs hard disk must be the same size or larger than the hard disk of the original master installation.
• 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 text-mode Setup by setting the FileSystem entry in the [Unattended] section of Unattend.txt to ConvertNTFS. FileSystem is not a valid entry in Sysprep.inf. However, the hard drive performs better if you use Convert with Oformat and/or Cvtarea instead of the FileSystem entry. For more information, see the Legacy Methods section of NTFS Preinstallation and Windows XP.

You can also use the ExtendPartition entry in the [ComputerSettings] section of Winbom.ini to extend the partition using the Factory tool.

%SYSTEMDRIVE%\Sysprep\Factory.exe runs on first boot.

%SYSTEMDRIVE%\Sysprep\Factory.exe does not run on first boot. (Default)

FactoryMode = Yes

Converts the primary partition to NTFS.

FileSystem = ConvertNTFS

For the Windows XP and Windows Server 2003 family of 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 text-mode Setup by setting the FileSystem entry equal to ConvertNTFS. However, the hard drive performs better if you use Convert with Oformat and/or Cvtarea instead of using the FileSystem entry. For more information, see the Legacy Methods section of NTFS Preinstallation and Windows XP.

Note

• If you plan to use ExtendOemPartition during Setup, the file system must be NTFS.
• FileSystem is not a valid entry in Sysprep.inf.

Installs the most appropriate HAL for the new operating system.

Keeps the HAL from the previous operating system.

ForceHALDetection = Yes

Important

• If ForceHALDetection=Yes during an upgrade, Setup may lose some user-specified hardware settings.
• If ForceHALDetection=No during an upgrade, Setup preserves user-specified hardware settings.

Enables hibernation.

Disables hibernation.

Hibernation = Yes

Notes

• To keep the size of your image file as small as possible, you may 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 random access memory (RAM) on the computer. Before beginning hibernation mode, verify that the amount of free disk space on your computer hard 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, 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.

  For more information on the PAE Kernel, see the Microsoft Driver Development Kit (DDK), which you can order from the Microsoft DDK Web site (http://www.microsoft.com/ddk/). You can also read the DDK documentation in the MSDN Library (http://msdn.microsoft.com/library/): Select Windows Development, then Driver Development Kit.

KeyboardLayout = Us

This entry must match one of the right-hand strings (in quotation marks) in the [Keyboard Layout] section of TxtSetup.sif.

Upgrades a previous version of Windows. Only these additional Unattend.txt entries are processed: ProductKey, AutoActivate, DUDisable, DUShare, and DUStopOnError

Does not upgrade a previous version of Windows.

NTUpgrade = Yes

Note

To upgrade from Windows 98 or Windows Millennium Edition, use the Win9xUpgrade entry.

Set NTUpgrade = Yes to upgrade the previous Windows installation. If OemPreinstall is Yes, do not set NTUpgrade equal to Yes.

This entry upgrades your previous version of Windows XP, Windows Server 2003 family, Windows 2000, Windows NT 4.0, or Windows NT 3.51. Setup takes all user settings from the previous installation, and does not require end-user intervention.

The following table provides a comprehensive list of valid upgrade scenarios.

* You can upgrade from Windows NT 4.0 Terminal Server Edition or Windows 2000 Application Server mode to Windows Server 2003 family, but Setup will warn you that it does not support Terminal Service Application mode.

OemFilesPath = "%SYSTEMDRIVE%\OEM_Files"

For more information about the \$OEM$ folder, if you are a computer manufacturer, see the Microsoft Windows XP OEM Preinstallation Kit (OPK) User Guide. Otherwise, see the Microsoft Windows 2000 Server Deployment Guide.

OemPnPDriversPath = MyFolder1;MyFolder2

OEMPreinstall = Yes

For example, if you have a folder called \Drivers with subfolders called \Audio and \Net, specify OemPnPDriversPath = drivers\audio;drivers\net in the Unattend.txt file. Setup adds:

• %SYSTEMDRIVE% to each of the folder names
• the path for each subfolder to the Plug and Play device search path.

Important

• The length of the OemPnPDriversPath entry in Unattend.txt 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 Unattend.txt, be sure that the folders are available during GUI-mode Setup or the end user first-run experience. The easiest way to do this is to place the Plug and Play drivers in the \$OEM$\$1 folder. To prevent end 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 end user for the location of the drivers during the first boot of the machine, 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.

Setup copies the subfolders and files contained in the \platform\$oem$ folder.

Setup does not copy these files.

OemPreinstall = Yes

Note

• If OemPreinstall = Yes, do not set NTUpgrade to Yes.
• If OemPreinstall = Yes, unattended Setup automatically stops at the Welcome page. To avoid this pause in your factory environment, set OEMSkipWelcome to 1. Do not distribute any computer with OEMSkipWelcome = 1. Instead, set OEMSkipWelcome to 0 in the Sysprep.inf file you use before delivering the computer to the customer.

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 end user on whose behalf you install Windows has agreed to the license agreement.

Implies that the person performing the installation and the end user have not read and agreed to the license agreement.

OemSkipEula = No

Important

• You must not use this entry to remove the Microsoft® End-User License Agreement screen because end users must see and accept it. Use Sysprep to ensure that end users see the EULA when the computer starts for the first time.

Overwrites the files if found.

Does not overwrite the files if found.

OverwriteOemFilesOnUpgrade = Yes

Deletes all partitions on the first drive and reformats the drive with NTFS.

Does not delete partitions or reformat the drive.

Repartition = Yes

Important

• Repartition is valid only when performing an unattended Setup by starting the computer from the Windows product CD.

Setup generates a unique folder name for the installation.

Setup installs to the specified folder.

TargetPath = *

The path must use 8.3 file names. be Do not include the drive letter in target_path. If you want to specify the target drive, you must use the /tempdrive command-line switch when you run Winnt32.exe.

Specifies that answers in the answer file are defaults. Unlike UnattendMode = ProvideDefault, Setup does not display the user interface to end 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 end user can modify any of the answers on the displayed page.

Use UnattendMode = DefaultHide in deployment scenarios where an administrator might want only end users to provide the administrator password on the computer. This behavior is the default if you do not specify unattended mode.

Specifies a fully unattended GUI-mode Setup. If you do not specify a required Setup answer in the answer file, Setup generates an error.

During an attended Setup, improperly signed hardware drivers generate a warning dialog box. If UnattendMode = FullUnattended, then Setup does not install hardware drivers unless they are properly signed.

Use UnattendMode = FullUnattended in deployment scenarios where you require a complete unattended installation.

Specifies an attended GUI-mode section of Setup. When specified, the end user must answer all questions in the GUI-mode portion of Setup before Setup finishes.

Use UnattendMode = GuiAttended in preinstallation scenarios when you want to automate only text-mode Setup.

Specifies default answers in the answer file. In this case, Setup displays these default answers to the end user, who can change them if they are not appropriate.

Use UnattendMode = ProvideDefault 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).

Specifies read-only answers in the answer file if the Windows Setup pages containing these answers appear to the end user. Like UnattendMode = ProvideDefault, no user interface appears if the answer file contains all the answers on a page. Unlike UnattendMode = DefaultHide, however, the end user can specify only new answers on a displayed page.

Use UnattendMode = ReadOnly in scenarios where an administrator wants to force specific answers on one page but not others.

UnattendMode = FullUnattended

Instructs Setup to skip Windows Welcome.

Instructs Setup not to skip Windows Welcome.

UnattendSwitch = Yes

Note

• UnattendSwitch is not the same as the UnattendedInstall entry in the [Data] section of the answer file. UnattendSwitch controls Windows Welcome; UnattendedInstall does not.

Delays the reboot for 15 seconds after GUI-mode Setup finishes.

Restarts immediately after GUI-mode Setup finishes.

WaitForReboot = Yes

Instructs Setup to upgrade the Windows installation, if found.

Instructs Setup not to upgrade the Windows installation, if found.

Win9xUpgrade = Yes

For more information, see [Uninstall].