An unattended installation relies on one of two Setup
programs: a 16-bit Setup program called Winnt.exe, or a 32-bit Setup program
called Winnt32.exe. You can run Winnt.exe on a computer that is running MS-DOS,
Windows 3.1, or Windows for Workgroups. You can run Winnt32.exe on a
computer that is running Windows 95, Windows 98,
Windows Millennium Edition, Windows NT, Windows 2000, Windows XP,
and the Windows Server 2003 414l111e family.Winnt.exe and Winnt32.exe can be found
on a Windows XP Professional or Windows Server 2003 414l111e product CD. For a
worksheet to assist you in recording Setup options for each of your unattended
installations, see "Unattended Installation
Worksheet" (ACIUI_1.doc) on the Windows
Server 2003 Deployment Kit companion CD (or see "Unattended Installation Worksheet"
on the Web at https://www.microsoft.com/reskit).
You can start Setup by using the Winnt.exe command line tool from MS-DOS, Windows for Workgroups, or Windows 3.1. Winnt.exe has the following syntax:
winnt [/s:[sourcepath]] [/t:[tempdrive]] [/u:[answer_file]] [/udf:id [,UDB_file]] [/r:folder] [/rx:folder] [/e:command] [/a]
Use the following parameter descriptions to determine which parameters to use for your unattended installation. For a worksheet to assist you in recording these parameters, see "Unattended Installation Worksheet" (ACIUI_1.doc) on the Windows Server 2003 414l111e Deployment Kit companion CD (or see "Unattended Installation Worksheet" on the Web at https://www.microsoft.com/reskit).
Specifies the source location of the Windows operating system files. The location must be a full path of the form drive_letter path_to_folder or \\server\path_to_shared_folder. The default is the current folder. Use this parameter if you are using a distribution share.
Directs Setup to place temporary files on the specified drive and to install Windows on that drive. If you do not specify a location, Setup attempts to locate a drive for you.
Performs an unattended installation with an answer file. The answer file provides answers to some or all of the prompts that the end user normally responds to during setup. If you use /u, you must also use /s.
Indicates an identifier (id) that Setup uses to specify how a uniqueness database file (.udf) modifies an answer file (see /u). The .udf file overrides values in the answer file, and the identifier determines which values in the .udf file are used. If no .udf file is specified, Setup prompts the user to insert a disk that contains the .udf file.
Specifies an optional folder to create during setup. For example, you might create a folder named Drivers on the C drive, and then copy device driver files to the folder after the installation completes. The folder remains after Setup finishes.
Specifies an optional folder to create and to copy the contents of another folder to during setup. The folder is deleted after the Setup program stops running. For example, you might create a folder named Scripts on the C drive, and then copy scripts that you want to run during the installation to that folder. After the installation completes, the scripts and the folder are deleted.
This parameter specifies a command to run after the GUI mode stage of Setup.
This parameter enables accessibility options.
You cannot use Winnt.exe to perform an upgrade. You can perform only clean installations when you use Winnt.exe. In addition, you must use the 8.3 naming convention to name all of the files and folders in your distribution share. To adhere to the 8.3 naming convention, you cannot have more than 8 characters before the decimal point, and you must have a three-character extension after the decimal point. You need to use a $$Rename.txt file to convert 8.3 file names to long file names during setup. For more information about renaming files and folders during setup, see "Designing a Distribution Share" earlier in this chapter.
For more information about Winnt.exe parameters, see "Winnt.exe Command Line Options" in the Microsoft Windows Corporate Deployment Tools User's Guide (Deploy.chm). Deploy.chm is included in the Deploy.cab file in the Support folder on the Windows Server 2003 414l111e operating system CD.
You can start Setup by using the Winnt32.exe command line tool from Windows 95, Windows 98, Windows Millennium Edition, Windows NT 4.0, Windows 2000, Windows XP Professional, and the Windows Server 2003 family. You cannot run Winnt32.exe on an Itanium-based computer from the extensible firmware interface (EFI), and no Winnt32.efi is available.
Winnt32.exe has the following syntax:
winnt32 [/checkupgradeonly] [/cmd:command_line] [/cmdcons] [/copydir:\folder_name] [/copysource:folder_name] [/debug[level] [filename]] [/dudisable] [/duprepare:pathname] [/dushare:pathname] [/emsport:] [/emsbaudrate:baudrate] [/m:folder_name] [/makelocalsource] [/noreboot] [/s:sourcepath] [/syspart:drive_letter ] [/tempdrive:drive_letter ] [/udf:id [,UDB_file]] [/unattend[num] [answer_file]]
Use the following parameter descriptions to determine which parameters to use for your unattended installation. For a worksheet to assist you in recording these parameters, see "Unattended Installation Worksheet" (ACIUI_1.doc) on the Windows Server 2003 414l111e Deployment Kit companion CD (or see "Unattended Installation Worksheet" on the Web at https://www.microsoft.com/reskit).
Checks your computer for upgrade and installation compatibility with Windows XP Professional and Windows Server 2003 414l111e .
If you use this option with /unattend, no user input is required. Otherwise, the results are displayed, and you can save them with a specified file name. The default file name is Upgrade.txt in the systemroot folder.
Instructs Setup to execute a specific command before beginning the final stage of the setup process. This occurs after your computer has restarted and after the Setup program has collected the necessary configuration information, but before the setup process finishes.
Installs the Recovery Console as a startup option on a functioning x86-based computer. The Recovery Console is a command-line interface from which you can perform tasks such as starting and stopping services and accessing the local drive (including drives formatted with NTFS). You can use the Recovery Console only after Setup finishes.
Creates one or more folders in the folder where the Windows files are installed.
Creates one or more temporary folders in the folder where the Windows files are installed.
Creates a debug log at the level specified, for example, /debug4:Debug.log. The default log file is %SYSTEMROOT%\Winnt32.log, and the default debug level is 2. The log levels are: 0, representing severe errors; 1, representing errors; 2, representing warnings; 3 representing information; and 4, representing detailed information for debugging. Each level includes the levels under it.
Prevents Dynamic Update from running. Without Dynamic Update, Setup runs only with the original Setup files. This option disables Dynamic Update even if you set DUDisable equal to No in the [Unattended] section of your answer file.
Prepares a distribution share so that it can be used with Dynamic Update files downloaded from the Windows Update Web site. This distribution share can then be used for installing Windows for multiple clients.
Specifies a distribution share on which you previously downloaded Dynamic Update files (updated files for use with Setup) from the Windows Update Web site, and on which you previously ran /duprepare:pathname. When run on a client, specifies that the client installation uses the updated files on the distribution share specified in pathname.
Enables or disables Emergency Management Services during setup and after a member of the Windows Server 2003 414l111e family of operating systems has been installed. With Emergency Management Services, you can remotely manage a server in emergency situations that normally require a local keyboard, mouse, and monitor, such as when the network is unavailable or the server does not function properly. Emergency Management Services has specific hardware requirements, and is available only for products in the Windows Server 2003 family. For more information about Emergency Management Services, see "Planning for Remote Server Management" in Planning Server Deployments of this kit.
For x86-based computers, this parameter specifies the baud rate for Emergency Management Services. (The option is not applicable for Itanium-based computers.) Must be used with /emsport:com1 or /emsport:com2 or else /emsbaudrate is ignored.
Specifies that Setup copies replacement files from an alternative location. Instructs Setup to look in the alternative location first, and, if files are present, to use them instead of the files from the default location.
Instructs Setup to copy all installation source files to your local hard disk. Use /makelocalsource when installing from a CD to provide installation files when the CD is not available later in the installation.
Instructs Setup not to restart the computer after the file-copy stage of Setup finishes, so that you can execute another command.
Specifies the location of the Windows files. To simultaneously copy files from multiple servers, type the /s:sourcepath option multiple times (up to a maximum of eight).
On an x86-based computer, this parameter specifies that you can copy Setup startup files to a hard disk, mark the disk as active, and then install the disk onto another computer. When you start the computer onto which you have installed the disk, it automatically starts with the next phase of Setup. You must always use the /tempdrive parameter with the /syspart parameter.
You can start Winnt32.exe with the /syspart option on an x86-based computer running Windows NT 4.0, Windows 2000, or Windows XP Professional. The computer cannot be running Windows 95, Windows 98, or Windows Millennium Edition.
Directs Setup to place temporary files on the specified partition. For a new installation, Windows is installed on the specified partition. For an upgrade, the /tempdrive option affects the placement of temporary files only; the operating system is upgraded in the partition from which you run Winnt32.exe.
Indicates an identifier (id) that Setup uses to specify how a uniqueness database file (.udf) modifies an answer file (see the /unattend option).
If you start from the Windows Server 2003 414l111e operating system CD and run an unattended setup, you cannot use the /udf command-line option for Winnt32.exe.
Upgrades your previous version of Windows 98,
Windows Millennium Edition, Windows NT 4.0, or
Windows 2000 in unattended mode (without user input). Setup downloads the
Dynamic Update files from Windows Update and includes these files in the
installation.
All user settings are taken from the previous installation, so no user
intervention is required during setup.
Performs a fresh installation of Windows in unattended mode using the specified answer file. Setup downloads the Dynamic Update files from the Windows Update Web site and includes these files in the installation. The specified answer_file provides Setup with your custom specifications.
For more information about Winnt32.exe parameters, see "Winnt32.exe Command Line Options" in the Microsoft Windows Corporate Deployment Tools User's Guide (Deploy.chm). Deploy.chm is included in the Deploy.cab file in the Support folder on the Windows Server 2003 414l111e operating system CD.
|
