After you create a distribution folder, customize the installation by creating answer file(s) and adding devices, device drivers, applications, Help files, support information, and other components. Depending on what you want to customize, use Setup Manager to perform either or both of the following tasks:
Add entries in the answer file to provide specific instructions to be carried out by Setup during installation.
Populate the distribution folder by adding files, programs, and applications.
The tools you can use to customize Windows XP Professional depend on your choice of methods to install the operating system.
Table 2-4 shows the customization tools that are covered in the Using Windows XP Professional Customization Tools section.
Table 2-4: Customization Tools
Tool
Installation Method
Description
Unattended Installation (Winnt32.exe)
Unattend.txt
Supplies an answer file that you can either modify or use as is.
Setup Manager
Use to create and modify answer files and distribution folders.
System Preparation (Sysprep.exe) tool
Sysprep.inf
Supplies an answer file that you can either modify or use as is.
Sysprep Factory Mode
Use to customize the Setup for the destination computer.
MiniSetup Wizard
Displays a configurable collection of Setup screens to gather information that has not been preconfigured in the answer file. Use Setup Manager (setupmgr.exe) to preconfigure the MiniSetup Wizard screens or Windows Welcome (Msoobe.exe). Oobe is an acronym for out-of-box experience.
MiniSetup starts the first time a computer starts from a disk that has been duplicated using Sysprep.
Setup Manager
Use to create and modify answer files, distribution folders, and the MiniSetup Wizard.
Remote Installation Services (RIS)
RIS template answer file (Ristndrd.sif)
Supplies an answer file that you can either modify or use as is.
RIS Client Installation Wizard
Provides basic functionality for installing client computers.
Setup Manager
Use to create and modify answer files and distribution folders.
Manually create an answer file
Notepad or other text editor
Use to create a new answer file or to modify an existing one.
You can customize features and components in Windows XP Professional. The examples provided at the end of this section demonstrate the following:
Adding hardware devices, including storage devices, Plug and Play devices, and hardware abstraction layers (HALs). When adding hardware devices to the distribution folder and specifying the devices in the answer file, consider mass storage devices such as Small Computer Systems Interface (SCSI) hard drives. Windows XP Professional Setup detects and installs most hardware devices automatically. However, to install a SCSI device that is not supported by Windows XP Professional, you must add the device drivers for that SCSI device and its Txtsetup.oem file to the distribution folder (in the $OEM$\Textmode folder). To access that SCSI controller during text mode, the [MassStorageDrivers] section of the answer file must be modified with the appropriate device driver entries.
Note
Ensure that hardware on the destination computer meets the minimum requirements listed in Planning Deployments in this book. Also to ensure that the individual components are compatible with Windows XP Professional, see the Hardware Compatibility List link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources
Setting passwords for local user accounts. You can also force all users or certain users to change their passwords when they log on after an upgrade from Windows 98, or Windows Me.
Setting options for language and multilingual support, and setting key descriptions for other regional and language options, such as language-specific keyboard layouts.
Setting time zones.
Specifying display settings to ensure that Setup automatically detects a computer s display resolution.
Specifying file system settings to automatically convert FAT16 and FAT 32 file systems to NTFS during installation.
Using the $$Rename.txt file to automatically convert short file names to long file names.
Adding applications during the GUI-mode phase of Setup using Cmdlines.txt.
Adding applications when the user logs on for the first time using [GuiRunOnce].
Using batch files and packaging applications to be used with the Windows Installer service.
You can customize many Windows XP Professional features after installation, such as wallpaper, screen saver settings, Active Desktop, custom toolbars and taskbars, and new Start and Programs menu options. For more information about post-installation customization, see Managing Desktops in this book.
Using Windows XP Professional Customization Tools
Use Setup Manager (setupmgr.exe) to create answer files or use a simple text editor (such as Notepad) to manually create them.
You can use a network connection to a RIS server to download one or more operating system images (including Windows XP Professional). If you use a RIS server to download an operating system image, RIS provides answer file templates and a Client Installation Wizard (CIW).
You can use Sysprep to distribute operating system images using removable media. Sysprep provides an answer file (Sysprep.inf) that you can customize.
Customizing Unattended Installations
An answer file or setup script is a text file that follows a specific format and syntax and contains all of the information Setup must have to automate and customize an installation. The Setup program uses this customized script to provide values for all of the settings that are required during installation.
Typically, the answer file for Winnt32.exe is named Unattend.txt; however, you can use any valid file name (for example, Sales.txt, Test.txt, and Support.txt). You must use the /Unattend parameter and the correct file name when you run Setup from the command line (for example, /Unattend:filename.txt). By using descriptive names to differentiate different versions of an answer file, you can build and maintain a variety of unique answer files for the workgroups within your organization.
The answer file provides Setup with the necessary information to enable interaction with the distribution folders and files that you have created.
Creating an Answer File by Using Setup Manager
You can use Setup Manager to create an answer file for an unattended installation, an automated installation using Sysprep, or an automated installation using RIS. Setup Manager is available on the Windows XP Professional operating system CD in the Deploy.cab file of the \Support\Tools folder. Setup Manager helps you create and modify an answer file by providing prompts for the information that is required and then creating the answer file. Setup Manager can create a new answer file, import an existing answer file for modification, or create a new answer file based on the configuration of the computer on which it is running.
Table 2-5 lists the parameters that you can configure with Setup Manager. The parameters are listed in the order in which they are presented. After you configure the parameters, Setup Manager generates the results as answer file keys.
Table 2-5: Setup Manager Parameters
Parameter
Description
Set user interaction
Sets the level of user interaction that is appropriate during the setup process. For example, you can select Provide defaults to display the configurable values supplied in the answer file, or Fully automated to create a setup process that does not prompt the user to review or supply configuration values.
Set default user information
Specifies an organization or user name.
Define computer names
When you enter multiple names during the setup process, Setup Manager automatically generates the Uniqueness Database File (UDF) that is required to add those unique names to each computer during setup. If the administrator imports names from a text file, Setup Manager converts each name to a Uniqueness Database File. The administrator can also set an option to generate unique computer names.
Set an administrator password
Setup Manager can encrypt the administrator password in the Unattend.txt answer file. This prevents the password from being readable if the answer file is viewed in a text editor. Setup Manager can also be set to prompt the user for the administrator password during setup. If the Administrator Password box is left blank, you can use the AutoLogon feature to log on to the client computer as an administrator. To disable AutoLogon, type a value in the Administrator Password box when you run Setup Manager.
Display settings
You can automatically set the display color depth, screen area, and refresh frequency display settings.
Configure network settings
Any custom network-setting option that can be configured from the desktop can be configured remotely using Setup Manager. The interface for setting network settings in Setup Manager is the same interface that the user sees on their desktop. Using Setup Manager, you can also add computers to a domain or workgroup, or automatically create accounts in the domain.
Set time zone and regional options
Sets the correct time zone using the same property sheet that a user would access to change the time zone locally. Specifies regional and language options such as date, time, numbers, character sets, and keyboard layout.
Set Internet Explorer settings
Performs the basic setup for Internet connections, such as connecting to proxy servers. If your organization wants to customize the browser, the administrator can use Setup Manager to access the customization tool that is part of the Internet Explorer Administration Kit (IEAK), available from http://www.microsoft.com/
Set telephony settings
Sets telephony properties, such as area codes and dialing rules.
Add Cmdlines.txt files
Files used to install additional components, such as applications. For example, the administrator can add the command line to run Microsoft Office setup by including the command line for Office setup in the Cmdlines.txt file.
Create an installation folder
Uses the default installation folder, \\Windows, to generate a unique folder during setup or to set a custom folder.
Install printers
Sets up multiple printers as part of the installation process.
Add commands to the Run Once section
Sets up commands that run automatically the first time a user logs on. These might include running an application setup program or changing security settings.
Run commands at the end of setup
Specifies commands that run at the end of the setup process and before users log onto the system, such as starting an application setup file.
Copy additional files
Specifies additional files to be copied to the user s desktop, such as device driver libraries, and their location.
Create a distribution folder
Creates a distribution folder on the network that includes the required Windows XP Professional source files. You can also add files that you want to copy or supply additional device drivers for use with Windows XP Professional.
Setup Manager cannot perform the following functions:
Specify system components, such as Internet Information Services.
Create Txtsetup.oem files.
Create subfolders in the distribution folder.
To copy Setup Manager from the Windows XP Professional CD
In the \Support\Tools folder, double-click the Deploy.cab file.
Copy Setupmgr.exe to a folder on the hard disk.
To run Setup Manager
Double-click Setupmgr.exe. The Setup Manager Wizard helps you create an answer file and a distribution folder.
Example of an Unattend.txt Answer File
Listing 2-1 displays a typical Unattend.txt answer file. This file automates the installation or upgrade of Windows, enabling the Setup program to run without requiring user input. Comments within the answer file describe most sections, keys, and values.
Listing 2-1: Example of an Unattend.txt Answer File
[GuiUnattended] ; Set the TimeZone. For example, to set the TimeZone for the ; Pacific Northwest, use a value of "004." Be sure to use the ; numeric value that represents your own time zone. To look up ; a numeric value, see the Deploy.chm file on the Windows XP Professional CD. ; The Deploy.cab file is in the \Support\Tools folder. TimeZone = "YourTimeZone" OemSkipWelcome = 1 ; The OemSkipRegional key allows Unattended Installation to skip ; RegionalSettings when the final location of the computer is unknown. OemSkipRegional = 1
[UserData] ; Tip: Avoid using spaces in the ComputerName value. ComputerName = "YourComputerName" ; To ensure a fully unattended installation, you must provide a value ; for the ProductKey key. ProductKey = "Your product key"
[LicenseFilePrintData] ; This section is used for server installs. AutoMode = "PerServer" AutoUsers = "50"
[Components] ; This section contains keys for installing the components of ; Windows XP Professional. A value of On installs the component, and a ; value of Off prevents the component from being installed. iis_common = On iis_inetmgr = Off iis_www = Off iis_ftp = Off iis_doc = Off iis_smtp = On ; The Fp_extensions key installs Front Page Server Extensions. Fp_extensions = On ; If you set the TSEnabled key to On, Terminal Services is installed on ; a current version of Windows Server. TSEnabled = On ; If you set the TSClients key to On, the files required to create ; Terminal Services client disks are installed. If you set this key ; to On, you must also set the TSEnabled key to On. TSClients = On Indexsrv_system = On Accessopt = On Calc = On Charmap = On Chat = Off Clipbook = On Deskpaper = On Dialer = On Freecell = Off Hypertrm = On Media_clips = On Media_utopia = On Minesweeper = Off Mousepoint = Off Mplay = On Mswordpad = On Paint = On Pinball = Off Rec = On Solitaire = Off Templates = On Vol = On
[TapiLocation] CountryCode = "1" Dialing = Pulse ; Indicates the area code for your telephone. This value must ; be a 3-digit number. AreaCode = "Your telephone area code" LongDistanceAccess = 9
[NetOptionalComponents] ; Section contains a list of optional network components to install. Snmp = Off Lpdsvc = Off Simptcp = Off
[Branding] ; This section brands Microsoft Internet Explorer with custom ; properties from the Unattended answer file. BrandIEUsingUnattended = Yes
[URL] ; This section contains custom URL settings for Microsoft ; Internet Explorer. If these settings are not present, the ; default settings are used. Specifies the URL for the ; browser s default home page. For example, you might use the ; following: Home_Page = www.microsoft.com. Home_Page = YourHomePageURL ; Specifies the URL for the default search page. For example, you might ; use the following: Search Page = www.msn.com Search_Page = YourSearchPageURL ; Specifies a shortcut name in the link folder of Favorites. ; For example, you might use the following: Quick_Link_1_Name = ; "Microsoft Product Support Services" Quick_Link_1_Name = "Your Quick Link Name" ; Specifies a shortcut URL in the link folder of Favorites. For example, ; you might use this: Quick_Link_1 = http://support.microsoft.com/. Quick_Link_1 = YourQuickLinkURL
[Proxy] ; This section contains custom proxy settings for Microsoft ; Internet Explorer. If these settings are not present, the default ; settings are used. If proxysrv:80 is not accurate for your ; configuration, be sure to replace the proxy server and port number ; with your own values. HTTP_Proxy_Server = proxysrv:80 Use_Same_Proxy = 1
Customizing Sysprep Installations
This section provides information about the components of Sysprep 2.0, including:
The Sysprep.inf File
The MiniSetup Wizard
Factory Mode
Audit Boot Mode
Reseal Mode
The -msoobe parameter (Windows Welcome)
Using Sysprep.inf
Listing 2-2 displays an example of a Sysprep.inf answer file. If you are running Sysprep with the -mini parameter, you can use the Sysprep.inf answer file to automate the MiniSetup process. It uses the same .inf file syntax and key names (for supported keys) as Unattend.txt. Place the Sysprep.inf file in the %SystemDrive%\Sysprep folder or on a floppy disk. If you use a floppy disk, insert it into the floppy disk drive after the Windows startup screen appears. Note that if you do not include Sysprep.inf when running Sysprep, the MiniSetup Wizard requires user input at each customization screen.
If you provided a Sysprep.inf file on the reference computer and want to individually change Sysprep.inf on each destination computer, use the floppy disk method.
Listing 2-2: Sample Sysprep.inf Answer File
[Unattended] ; Prompt the user to accept the EULA. OemSkipEula = No ;Use Sysprep s default and regenerate the page file for the system ;to accommodate potential differences in available RAM. KeepPageFile = 0 ;Provide the location for additional language support files that ;might be required in a global organization. InstallFilesPath = c:\Sysprep\i386
[GuiUnattended] ;Set the time zone. TimesZone = 20 ;Skip the Welcome screen when the system starts. OemSkipWelcome = 1 ;Do not skip the Regional and Language Options dialog box so that users can ;indicate which options apply to them. OemSkipRegional = 0
[Identification] ;Join the computer to the domain ITDOMAIN. JoinDomain = ITDOMAIN
[Networking]
For more information about answer file keys and values, see the Deploy.chm in the Deploy.cab file on the Windows XP Professional operating system CD. The Deploy.cab file is in the \Support\Tools folder.
Using MiniSetup
If you are running Sysprep with the -mini parameter, the MiniSetup Wizard appears the first time a computer starts from a disk that was duplicated by using Sysprep. The MiniSetup Wizard gathers information that is required to customize the destination computer. If you do not use Sysprep.inf or if you leave some sections of the file blank, the MiniSetup Wizard displays screens to collect the required information that has not already been provided. The displayed screens can include:
Welcome to Windows XP Professional Setup Wizard.
End-User License Agreement (EULA).
Regional and Language Options.
User name and company.
Product key. This screen is always displayed unless you prepopulate the system preparation procedure with product key information.
Computer name and administrator password.
Telephony application programming interface (TAPI) settings screen. This screen is only displayed if a modem or a new modem device exists on the computer.
Date and time settings.
Networking settings.
Workgroup or computer domain.
For more information about bypassing these screens, see Table 2-6.
Note
Because Setup detects optimal settings for display devices, you no longer see the Display Settings screen when Setup or the MiniSetup Wizard is running. You can specify the settings in the [Display] section either in the answer file that is used for your reference computer or in the Sysprep.inf file used for your destination computer. If settings in the [Display] section are in the answer file that is used for your reference computer, Sysprep retains those settings unless Sysprep.inf contains different settings or unless a video adapter or monitor is detected that requires settings different from those of the reference computer.
Table 2-6: Parameters in Sysprep.inf for Bypassing the MiniSetup Wizard
Parameter
Section, Key, and Value
Set regional options
[RegionalSettings]
LanguageGroup = 15,7,1
SystemLocale = 00000409
UserLocale = 00000409
InputLocale = 0409:00000409
[GuiUnattended]
OemSkipRegional = 1
Define user name and company
[UserData]
FullName = User Name
OrgName = Organization Name
Define computer name and administrator password
[UserData]
ComputerName = W2B32054
[GuiUnattended]
AdminPassword =
Set TAPI settings
[TapiLocation]
AreaCode = 425
Set network settings
[Networking]
Set server licensing (Windows server only)
[LicenseFilePrintData]
AutoMode = PerServer
AutoUsers = 5
Define time zone selection
[GuiUnattended]
TimeZone = Index
If you use the [RegionalSettings] section to add additional language support, make sure the language files are available. Also, make sure the C:\Sysprep\i386\Lang folder contains the files in the \i386\Lang folder on the Windows XP Professional CD. In addition, make sure the following entries appear in the Sysprep.inf file:
[Unattended] InstallFilesPath = "C:\Sysprep\i386"
Using Sysprep Factory Mode
You can use Sysprep Factory Mode, sysprep -factory, to preconfigure installation options and reduce the number of displayed MiniSetup or Windows Welcome (Msoobe.exe) screens. Factory Mode enables you to prepopulate information in the [Factory] section header of the Sysprep answer file, WinBom.ini. You can prepopulate information, such as address, time zone, existing ISP, and locale. You can also use Factory Mode to update other .ini or answer files, such as Sysprep.inf, OOBEinfo.ini, or .isp and .ins files.
Factory Mode enables you to add additional device drivers and applications to the image after the computer restarts when you are running Sysprep.exe. You typically run Sysprep.exe as the final step in the preinstallation process to prepare the computer for delivery. When restarted, the computer displays the MiniSetup or Windows Welcome screens. By clicking the Factory button on the OEM Reset Reminder dialog box, or by running Sysprep -factory from the command line (using the -factory parameter), the computer restarts in a network-enabled state without starting MiniSetup or Windows Welcome. In this state, Factory.exe processes WinBom.ini and performs the following tasks:
Copies device drivers from a network source to the computer.
Starts Plug and Play enumeration.
Copies applications from a network source to the computer.
Adds customer data.
In this state, the computer can be audited. When complete, run Sysprep with the - reseal parameter to prepare it for delivery.
When you use Factory Mode with disk-imaging (or cloning) software, you can reduce the number of required images. You can create a reference computer image with a minimal set of device drivers, and then copy the image to the destination computers. For any destination computer that requires additional device drivers, you can run Factory Mode to update the installed image with the required drivers.
Table 2-7 lists the sections in a WinBom.ini file.
Table 2-7: WinBom.ini Sections
Section
Description
[ComputerSettings]
Configures end-user settings on the destination computer.
[Factory]
Includes entries for performing a factory installation of Windows XP Professional.
[NetCards]
Includes entries for configuring the network adapter on the destination computer if a network connection is required.
[OEMLink]
Adds a graphic and text to the Start menu to provide end users with easy access to an OEM s .htm file.
[OEMRun]
Runs external applications and command shell scripts while the Sysprep -factory command is running. Commands are processed asynchronously. Each application runs in the order listed in this section, but the application does not wait for a previous application to finish before it runs. These executable files or command shell scripts are the last processing performed by the Sysprep -factory command.
[OEMRunOnce]
Includes entries for controlling the running of external applications and command shell scripts during the running of the Sysprep -factory command.
[Section_name]
Preinstalls an application as specified in the [OEMRunOnce] section.
[PnPDriverUpdate]
Includes entries for updating device drivers on the installed image prior to installing the drivers with Plug and Play.
[PnPDrivers]
Lists the updated device drivers to be copied on to the computer.
[Shell]
Customizes the appearance of the Windows desktop and Start menu.
[SetupHomenet]
Sets up a firewall on a computer that uses a preconfigured Internet connection.
[StartMenuMFUlist]
Prepopulates the Most Frequently Used programs list on the Start menu with shortcuts to preinstalled applications.
[UpdateSystem]
Updates any of the computer s files or registry entries.
[UserAccounts]
Includes entries for controlling the creation of user identities on the destination computer.
[UserDefined]
Creates a user-defined section that can contain branding information or any other data for other processes.
Using Sysprep Audit Boot Mode
To test and verify installations, you can use Audit Boot Mode to quickly restart the computer before you are ready to use Reseal Mode. You can invoke Audit Boot Mode by clicking the Audit Boot button in the OEM Reset Reminder dialog box.
Using Sysprep Reseal Mode
When you have made modifications in Factory Mode, you can use Reseal Mode to prepare the computer for delivery. When the computer restarts from Factory Mode, you can invoke Reseal Mode by clicking the Reseal button on the OEM Reset Reminder dialog box, or by running Sysprep -reseal from the command line (using the -reseal parameter). To display the Windows Welcome screens on the first restart after you reseal the image, use the -msoobe parameter.
Customizing RIS Installations
Remote Installation Services (RIS) is a tool that enables you to perform a clean installation of a pre-configured image of a supported operating system on a client computer. You can use RIS to install the operating system over a network connection on a computer that supports the Pre-Boot eXecution Environment (PXE). You can also use RIS with the Remote Boot Floppy Generator (Rbfg.exe) to create a remote boot disk that can be used with a variety of supported PCI-based network adapters.
Using RIS Answer Files
The Remote Installation Services answer file guides the installation of the operating system. When you install RIS on a computer running a current version of Windows 2000 Server and then run Risetup.exe, a standard answer file is created and named Ristndrd.sif. You can modify this RIS answer file to perform an installation with minimal or no user intervention and place the computer account object in the domain in which the RIS server resides. Ristndrd.sif also contains the description that is displayed during the CIW when the user at the client computer selects an operating system image to install.
Listing 2-3 displays an example of a RIS answer file, Ristndrd.sif.
[OSChooser] Description = "Microsoft Windows XP Professional" Help = "Automatically installs Windows Professional without prompting the user for input." LaunchFile = "%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com" ImageType = Flat Version = "5.1"
Customizing the RIS Client Installation Wizard
After you install RIS on a computer that is running a current version of Windows 2000 Server, you have access to a default set of Client Installation Wizard (CIW) screens, which provide basic functionality for installing clients. You can modify the CIW screens to meet the needs of your organization. The files are simple text files (with an .osc extension) that are in the OSCML format. CIW screens are also referred to as Operating System Chooser (OSC) screens. They have the .osc file name extension and are modeled on the HTML 2.0 format.
Note
The CIW screens are modeled on HTML 2.0; they are not a subset of the HTML 2.0 specification.
OSCML does not support Microsoft Visual Basic Scripting Edition, Microsoft JScript, or Java.
Table 2-8 describes the screens that are displayed when a user logs on to the client computer during a RIS installation of the operating system.
After the summary screen appears, the user exits the Client Installation Wizard and proceeds to the automated installation process. The automated installation process is similar to installing the operating system from a CD, but instead of accessing the installation media locally, the client computer accesses operating system files that are stored remotely on a RIS server. Depending on the speed of your network and the load on the RIS server, this process can be much faster than an installation from a CD-ROM drive.
Table 2-8: Client Installation Wizard Screens
Screen
Description
Logon screen (Login.osc)
Requires a user to log on. The user logs on to the network by using an existing user account, password, and domain. After the user successfully logs on, RIS uses these credentials to determine which installation options to display on the Setup Options screen. If the process is not successful and the logon account, password, or domain is not recognized, the user is prompted to log on again.
Setup Options screen (Choice.osc)
Displays installation options to the user, including:
Automatic provides the easiest operating system installation path. If there is already a computer account object in Active Directory with a Globally Unique Identifier (GUID) that matches the client computer s GUID, the existing computer account is reused. If a matching GUID is not found in Active Directory, the client computer is named based on the automatic naming format configured in the properties of the RIS server, and a new computer account is created in the location specified by the RIS server.
Custom allows users to override the automatic computer naming process, as well as the default location within Active Directory where client computer account objects are created. The Custom Setup option is similar to the automatic option, but you can use it to set up a client computer for a subsequent user (for example, to install an operating system on a client computer within the enterprise) before delivery to a user. If either the computer name or computer location is left blank on the Custom Setup screen, the automatic name or location is used.
Restart a Previous Setup Attempt restarts the operating system installation process by using the information entered during the previous attempt. If the installation process fails or network connectivity is disrupted during the initial text-mode phase of setup (before completing the file copy phase), a Restart Setup command is available for optional display to the user the next time the computer is started.
Maintenance and Troubleshooting provides access to maintenance and troubleshooting tools, such as system flash BIOS updates and computer diagnostic tools that can be used prior to operating system installation.
The degree to which this screen and its options are displayed is controlled by means of RIS Group Policy settings.
Duplicate GUID detection screen (Osauto.osc)
This screen is not displayed to users. Osauto.osc determines if a computer account object already exists in Active Directory with the same GUID as the computer running the Client Installation Wizard. If a duplicate GUID is found, DupAuto.osc is displayed. If no duplicate GUID is found, OSChoice.osc is displayed.
Error screen (Dupauto.osc)
Displayed if a duplicate GUID is found in Active Directory. Instructs the user to contact the network administrator.
Operating system choice screen (Oschoice.osc)
Displays the list of operating system images on the RIS server that are available to a user who is logged-on. If only one image is available for the user to install, that image is automatically selected and the user does not see this screen.
Caution screen (Warning.osc)
Displays a warning message that the hard disk will be formatted. The user is cautioned that an operating system will be installed on the computer, a process that requires the hard disk to be repartitioned and formatted, erasing all data currently on the disk.
Summary screen (Install.osc)
Displays information about the computer including computer name, computer GUID, and the RIS server to be used for downloading the image. Pressing any key begins the installation process.
At this point, the RIS server has created a computer account object in Active Directory for the computer and can look up the computer and its computer name and other settings if the computer is reinstalled.
If you were running the Client Installation Wizard to prestage the computer for another user, you can now shut down the computer and return it to the end user. The end user must have reset password permissions on the newly created computer account object in Active Directory.
Custom Setup screen (Custom.osc)
Prompts the user for a computer name and the Organizational Unit (OU) in which to create the computer account.
Using the Client Installation Wizard
Typically, when a remote boot-enabled client computer using RIS to install an operating system is turned on for the first time, the client computer contacts the boot server, and the user is prompted to press the F12 key on the keyboard of the client computer to initiate the download of the Client Installation Wizard (CIW). After the CIW is downloaded to the client computer, the Welcome screen appears and the user is prompted to log on to the network with an existing user account, password, and logon domain. After the logon process is established, RIS checks to see what installation options the user has access to based on the Group Policy settings that are applied to the user. The CIW displays a menu with the appropriate installation options tailored to the specific user. RIS has been configured so that a user is not presented with installation options by default. The Automatic setup option is automatically chosen.
Startrom.com
Startrom.com and Startrom.n12 are two of the RIS boot files in the \RemoteInstall\OSChooser\i386 folder of the RIS hard disk partition on a RIS server.
Startrom.n12
The default RIS boot file that can be sent in response to a client computer request to initiate the operating system installation procedure. If you use the default RIS boot file, the client computer prompts the user to press the F12 key to download the Client Installation Wizard (CIW).
The alternate RIS boot file that you can rename and use to streamline the process of initiating the installation of the operating system. If the client computer has a new, clean hard disk and if it is configured to boot from the network, use this alternate RIS boot file. The RIS server automatically starts downloading the CIW to the client computer. The client computer does not prompt the user to press the F12 key.
The \RemoteInstall\OSChooser\i386 folder is created and populated when you run Risetup.exe on a computer that is running Windows 2000 Server. The default Startrom.com file is the boot file that can be sent, in response to a client computer request, from a RIS server to a client computer. This default Startrom.com file prompts the user to press the F12 key to initiate the download of the CIW screens and to start the process of installing the operating system.
If you are installing Windows XP Professional on a new client computer that has a clean hard disk, you can use the Startrom.n12 file instead of the default Startrom.com file on the RIS server to eliminate the need to press the F12 key from the client computer. To do this, perform the following tasks from the RIS server:
In the \RemoteInstall\OSChooser\i386 folder of the hard disk partition that is used for RIS installations, change the name of the Startrom.n12 file to Startrom.com.
Change the boot order of the client computer so that it starts from the hard disk first and from PXE second.
The first time the client computer attempts to start from the hard disk, the boot process fails because the operating system is not yet installed on the hard disk. The client computer then starts from PXE without requiring a user to press the F12 key. After you successfully complete the operating system installation, subsequent restarts are performed by using the operating system that is now installed on the hard disk. It is necessary to perform step two in the preceding task because the client computer initiates a RIS installation on every restart if PXE is first in the boot order.
Creating an Answer File Manually
You can use a text editor, such as Notepad, to manually create an answer file. An answer file consists of section headers, keys, and values for those keys. Note that you do not have to specify all possible keys in the answer file if the installation does not require them. Invalid key values cause errors or faulty performance after Setup. Listing 2-4 displays an example of a manually created answer file.
isting 2-4: Example of a Manually Created Answer File
[Section1] ; Sections contain keys and corresponding values for the keys. ; Keys and values are separated by equal signs. ; Values with spaces usually require double quotes. ; Text (like this) following semi-colons are comments. Key = Value
[Section2] Key = "Value with spaces"
Winnt.sif is the answer file that is used for performing an unattended clean installation from a CD. Listing 2-5 displays an example of a fully unattended Winnt.sif answer file.
Note
When you use Winnt.exe to perform a clean installation from a bootable CD on a computer with multiple hard disks or partitions, specify the exact location of the destination hard disk or partition to which you are installing. Add AutoPartition = 1 to the [Data] section of the Winnt.sif file to specify the location.
[UserData] FullName = USERNAME OrgName = MS ComputerName = COMPUTERNAME
[Identification] JoinWorkgroup = WORKGROUP
[Networking] InstallDefaultComponents = Yes
Customizing Components and Features
This section describes the tools you can use and the procedures you can perform to manually customize the components and features of a Windows XP Professional installation. You also have the option of using Setup Manager Wizard to customize components and features for a Windows XP Professional installation.
Adding Hardware Device Support
The following topics describe how to add hardware device support to your installation:
Mass Storage Devices
Hardware Abstraction Layers
Driver Signatures
Plug and Play Devices
Mass Storage Devices
In Windows XP Professional, Plug and Play installs most hardware devices that can be loaded later in the setup process. However, mass storage devices, such as hard disk controllers, must be properly installed for full Plug and Play support to be available during the GUI mode of Setup. For this reason, the installation of mass storage devices is handled differently from the installation of other hardware devices.
To add small computer system interface (SCSI) devices during text-mode Setup (before full Plug and Play support is available), you must provide a Txtsetup.oem file that describes how Setup needs to install the particular SCSI device. For more information about Txtsetup.oem, see the Microsoft Windows XP Professional Device Driver Kit.
To install a mass storage device
In the distribution folder, create the Textmode folder in the \$OEM$ folder.
Copy the following files into the Textmode folder. These files are available from the device vendor. In the list below, replace Driver with the appropriate driver name:
Driver.sys
Driver.dll
Driver.inf
Driver.cat
Txtsetup.oem
Some drivers, such as SCSI miniport drivers, might not include a DLL file.
Note
A catalog file, for example Driver.cat, might not be required.
Most SCSI drivers do not ship with dynamic-link library files (DLLs).
Catalog files (.cat) are not used during text-mode setup.
The required files are specified in the Txtsetup.oem file. Make sure that all the files listed in Txtsetup.oem appear in the textmode directory and that the files are specified in the [OEMBootFiles] section of the Unattend.txt file.
You must also copy the driver files to the PnPdrvrs location that you specified for the OemPnPDriversPath key in the answer file. For example:
\$OEM$\$1\PnPdrvrs\Storage
You must include a catalog file, for example, Driver.cat, with the mass storage device drivers if the catalog file is listed in Txtsetup.oem. For more information about catalog files, see the Hardware Development link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources
In the answer file, create a [MassStorageDrivers] section, and include the driver entries that you want to include. If you are using two mass storage devices, one to control the hard disk, and the other to control the CD-ROM drive, a possible entry in the [MassStorageDrivers] section is shown in the following example:
Information for this section can be obtained from the Txtsetup.oem file, which is provided by the hardware manufacturer.
In the answer file, create an [OEMBootFiles] section, and include a list of the files in the $OEM$\Textmode folder. A possible entry to the [OEMBootFiles] section is shown in the following example:
Replace the word Driver with the appropriate driver name.
Warning
Only add driver entries to the [MassStorageDrivers] and [OEMBootFiles] sections for bootable mass storage devices. Do not include references to secondary mass storage devices. For secondary mass storage devices, add the drivers to the PnPdrvrs folder specified in the OEMPnPDriversPath key of the answer file.
If your mass storage device is a Plug and Play device, verify that a Hardware Identification Section and a reference to the catalog file for the driver (Driver.cat) exist in the Txtsetup.oem file. For more information, see the Driver Development Kits link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources
In the Txtsetup.oem file, verify that a section named [HardwareIds.Scsi.yyyyy] exists. If not, create it by using the following format:
[HardwareIds.scsi. yyyyy] id = "xxxxx" , "yyyyy"
In the preceding example, xxxxx is the device identifier and yyyyy is the device service name. For the Symc810 driver, which has a device ID of PCI\VEN_1000&DEV_0001, you can create the section shown in the following example:
[HardwareIds.scsi.symc810] id = "PCI\VEN_1000&DEV_0001" , "symc810"
Hardware Abstraction Layers
To specify Hardware Abstraction Layers (HALs) for installation, you must have a Txtsetup.oem file and the HAL files that are provided by the vendor. Use the same Txtsetup.oem file if you are installing mass storage device drivers. Only one Txtsetup.oem file can be used; therefore, if you have to install HALs and mass storage device drivers, combine the entries into one file.
To use third-party drivers, you must make appropriate changes to the answer file. For more information about answer file syntax, see the Deploy.chm in the Deploy.cab file on the Windows XP Professional operating system CD. The Deploy.cab file is in the \Support\Tools folder.
To install a HAL
If you have not already done so, create a Textmode folder in the \$OEM$ folder.
Copy the files that you receive from the device vendor to the Textmode folder.
In the answer file, edit the [Unattended] section for the HAL, and add any drivers that you want to install. A possible entry for the ComputerType key is shown in the following example:
[Unattended] ComputerType = "HALDescription", OEM
You can obtain information about the HALDescription from the [Computer] section of the Txtsetup.oem file, which is provided by the hardware manufacturer.
In the answer file, create an [OEMBootFiles] section, and enter the names of the files in the \$OEM$\Textmode folder.
Driver Signatures
Before using updated drivers, verify that they are signed correctly. If drivers are not correctly signed, they might not be installed. To verify that drivers are correctly signed, contact the vendor.
In the answer file, the DriverSigningPolicy key in the [Unattended] section specifies how nonsigned drivers are processed during installation.
Warning
Microsoft strongly advises against using DriverSigningPolicy = Ignore unless you have fully tested the device driver in your environment and are sure that it works correctly. Using unsigned drivers increases the risk of device driver problems that can affect the performance or stability of your computer.
If you are using DriverSigningPolicy = Ignore and you attempt to install a newer, unsigned copy of a driver that is protected by Windows XP Professional, the policy level is automatically updated to Warn.
For more information about driver signing policy, see the Deploy.chm in the Deploy.cab file on the Windows XP Professional operating system CD. The Deploy.cab file is in the \Support\Tools folder.
Plug and Play Devices
Windows XP Professional automatically installs most Plug and Play device drivers; however, you need to can easily add Plug and Play device drivers if necessary. When you are creating your reference installation image, check the Windows XP Professional product CD to determine if the drivers for the Plug and Play devices you are installing are listed. You can add Plug and Play device drivers that are not included on the Windows XP Professional operating system CD by performing the procedures in this section. This method works for all Plug and Play device drivers. You can also use this method to update existing Plug and Play device drivers.
The following procedures illustrate how you can add Plug and Play to these installation methods:
Unattended Installation
Sysprep images
Risetup images
To add Plug and Play device drivers to an Unattended Installation
In the \$OEM$ folder of the distribution folder, create subfolders for any special Plug and Play drivers and their .inf files, as shown in the following example:
$OEM$\$1\PnPDrvrs
Copy the driver files for the devices into the folders created in the previous step.
In the answer file, edit the [Unattended] key for Plug and Play and add the path to the list of Plug and Play search drives, as shown in the following example:
[Unattended] OEMPnPDriversPath = "PnPDrvrs"
The folders must contain all of the files that are required to install the specific devices: drivers, catalog, and .inf files. You can store multiple devices.
Directories are not traversed; therefore, if you have files in both \Pnpdrivers\Video and in \Pnpdrivers\Audio, they both need to be explicitly named in the OemPnPDriversPath key.
When Setup searches .inf files for Plug and Play IDs during GUI-mode Setup, Setup also looks in the paths noted in the OemPnPDriversPath along with the standard default path of %windir%\Inf. The %windir%\Inf path is listed first in the search order, but if you have a device that is supported by more than one .inf file (Windows XP Professional might include a driver that offers generic functionality), Setup continues to search all paths specified in the OemPnPDriversPath entry. Even though it might find multiple matches, Plug and Play uses the .inf file that has the best match and then installs the associated device driver to support the device.
To maintain the folders to accommodate future device drivers, create subfolders for potential device drivers. By dividing the folders into subfolders, you can store device driver files by device type rather than storing all device driver files in a single folder. Suggested subfolders include Audio, Modem, Net, Print, Storage, Video, and Other. Creating an Other folder gives you the flexibility to store new hardware devices that are not currently known.
For example, if the PnPDrvs folder contains the Audio, Modem, and Net folders, the answer file must contain the statement shown in the following example:
Adding Plug and Play devices before performing disk duplication with Sysprep
When a client computer that has been duplicated with Sysprep starts for the first time, the installer detects all non Industry Standard Architecture ISA hardware. If a hardware device is found for which there are no device drivers in the default Drivers.cab, the installer checks the location specified in OemPnPDriversPath. If the device drivers are not in this location, then the user is prompted for the location of the device drivers.
To improve the user experience and reduce computer startup time during the first boot, you can install additional Plug and Play device drivers before running Sysprep. If you determine that you want these OEM-supplied device drivers to be available for Windows XP Professional reinstallation, copy the OEM-supplied device driver files directly onto the hard disk before you perform the installation procedure. During MiniSetup, the installer ignores the OemPnPDriversPath information, and attempts to install these device drivers directly from their original locations on the hard disk.
To add Plug and Play devices to a Sysprep Image
Create a folder called Sysprep on the %SystemDrive% folder.
On the root of the same volume, create a folder structure to hold the drivers, as shown in the following example:
\Drivers \NIC \VIDEO \Sysprep \Windows
Copy the driver files for the devices into the folders created in the previous step. The folders must contain all of the files that are required to install the specific devices: driver, catalog, and .inf files.
In the Sysprep.inf answer file, edit the [Unattended] key for Plug and Play, adding the path to the list of Plug and Play search drives. You can list multiple paths in this key by separating them with a semicolon, as shown in the following example:
If you do not want the OEM-supplied device drivers to remain on the volume after MiniSetup is complete, place the folder structure (that you created in the Sysprep folder) in the root volume. Adjust the OemPnPDriversPath key in the Sysprep.inf answer file to reflect this change. The Sysprep folder is automatically removed after Setup is complete. This automatic removal process also removes all of the subfolders that are subordinate to the Sysprep folder. To ensure that OEM-supplied device drivers are available if Windows XP Professional reinstallation is required, do not remove any of the OEM-supplied device drivers from the root volume.
When you run Sysprep.exe, any Plug and Play devices (including those found using the driver .inf files) are automatically installed during MiniSetup on the destination computers. You do not need to specify the -PnP command-line parameter unless there are existing (ISA) devices on the destination computers.
To add Plug and Play devices to a Risetup image
Warning
To deploy Windows XP images from Windows 2000 RIS Servers, you must install the Windows 2000 Remote Installation Services update. For more information about the Windows 2000 Remote Installation Services update, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources Search the Microsoft Knowledge Base using the keywords Risetup.exe, RIS Servers, and Windows XP Images.
Create a folder structure similar to the structure shown in the following example:
Make sure that the \$oem$ folder is at the same level as the \i386 folder.
Copy the device driver files for the devices into their respective folders. Use the folder structure that you created in the previous step.
In the Ristndrd.sif answer file, change the value of the OemPreinstall key in the [Unattended] section from No to Yes, and add the paths to the list of Plug and Play search drivers. You can list multiple paths by using semicolons to separate the path names, as shown in the following example:
Save the Ristndrd.sif file in the \RemoteInstall\Setup\%language%\Images\%risetup_image_name%\i386\Templates folder.
Note
If one of the OEM-supplied drivers is for a network adapter, the RIS server must have this driver available when booting into text-mode Setup.
Copy the network adapter driver and the associated .inf file to the \RemoteInstall\Setup\%language%\Images\%flat_image_name%\i386 directory.
If the device driver that you are adding is an updated version of a driver that is already in this directory, you must delete the associated .pnf file from the \RemoteInstall\Setup\%language%\Images\%flat_image_name%\i386 directory.
Stop and restart the Boot Information Negotiation Layer (BINL) service on all RIS servers on which you copied the drivers. This step is required for these changes to take effect.
Customizing Regional and Language Options
You can customize the [RegionalSettings] section of your answer file to specify the regional and language options listed in Table 2-9
To use this section of your answer file, you must add, as a minimum, the /copysource:lang parameter to Winnt32.exe or the /rx:lang parameter to Winnt.exe. This enables you to copy the appropriate language files to the hard disk. For example, to copy Korean settings while installing a U.S. version of Windows XP Professional, you can specify /copysource:lang\kor if starting from Winnt32.exe.
Table 2-9 describes the keys in the [RegionalSettings] section of the answer file. To ensure that Setup completes without prompting for regional option information, do not provide keys or values for the [RegionalSettings] section when specifying OemPreinstall = Yes. Set OEMSkipRegional = 1 in the [GuiUnattended] section of the answer file.
Table 2-9: Keys in the [RegionalSettings] Section
Key
Description
InputLocale
Specifies the input locale and keyboard layout combinations to be installed on the computer. The first keyboard layout specified is the default layout for the installation. The specified combinations must be supported by one of the language groups defined by using either the LanguageGroup key or the default language group for the language version of Windows XP Professional being installed. If an available language group does not support the combination specified, the default combination is used for the installation. This key is ignored if the Language key is specified.
Language
Specifies the language and locale to be installed on the computer. This language must be supported by one of the language groups specified by using the LanguageGroup key. If an available language group does not support the locale, the default language for the Windows XP Professional version being installed is used.
If this value is specified, the SystemLocale, UserLocale, and InputLocale keys are ignored.
LanguageGroup
Specifies the supported language group to be installed on the computer. If this key is specified, it provides default settings for SystemLocale, InputLocale, and UserLocale keys.
For a list of the supported language group IDs, see the Deploy.chm in the Deploy.cab file on the Windows XP Professional operating system CD. The Deploy.cab file is in the \Support\Tools folder.
SystemLocale
Enables localized applications to run and displays menus and dialog boxes in the local language.
UserLocale
Controls the settings for numbers, time, currency, and dates.
A list of valid locales and their language groups is available at the Global Software Development Web site at http://www.microsoft.com/
Note
The LANG folder is automatically copied into Windows XP Professional images on a RIS server; however, the LANG folder must be manually copied into Windows 2000 images. The LANG folder must exist within images to enable locale changes.
To use [RegionalSettings] for multilingual support during MiniSetup
Create a folder named \i386 under \$OEM$\$1\Sysprep\ in the distribution folder.
To copy files from the \i386 folder of the Windows XP Professional operating system CD to the \i386 folder in the Sysprep folder, type the following at the command prompt:
You can also use Setup Manager to add the necessary files and folders to the \i386 folder. However, any settings specified here are not kept if Sysprep is run on the computer.
In Sysprep.inf, add the InstallFilesPath key to the [Unattended] section, as shown in the following example:
InstallFilesPath = %systemdrive%\Sysprep\i386
For more information about the InstallFilesPath key, see the Deploy.chm in the Deploy.cab file, which is on the Windows XP Professional operating system CD. The Deploy.cab file is in the \Support\Tools folder.
If you specify a regional setting in the image, you must also specify the same setting in the Sysprep.inf file. In addition, you must copy the correct file to the \Sysprep\i386 folder.
The \i386 folder and its contents are only required if the end user needs language support from one of the language groups provided in that folder. The \i386 folder is deleted after MiniSetup runs on the end user s computer. If you perform an audit or if a reseller further customizes the computer, you must recreate \Sysprep\i386 and then rerun Sysprep.exe before the image is installed to allow the end user to specify the necessary regional and language options.
Presetting Time Zones
You can specify the time zone of the computers in your organization by using the TimeZone key in the [GuiUnattended] section of your answer file or the Sysprep.inf file. If the TimeZone key is not present, the user is prompted for a time zone specification during setup.
To preset time zones
In the [GuiUnattended] section of your answer file, add the statement shown in the following example:
[GuiUnattended] TimeZone = "Index"
In the preceding example, Index specifies the time zone of the reference computer. Unless the TimeZone key is specifically set in the RIS answer file, client computers that are installed with RIS use the same time zone setting as the RIS server.
For a list of valid TimeZone indexes, see the Deploy.chm in the Deploy.cab file on the Windows XP Professional operating system CD. The Deploy.cab file is in the \Support\Tools folder.
Detecting Video Mode for Computer Displays
You can customize the [Display] section of the answer file to ensure that Setup automatically detects a computer s display resolution. Specify the optimal settings (you must know the valid settings) for the keys listed in Table 2-10. If the settings that you specify are not valid, Setup finds the closest match to the selected settings, which might not be optimal.
Table 2-10: Keys in the [Display] Section
Keys
Description
BitsPerPel
Specifies the valid bits per pixel for the graphics device being installed. For example, a value of 8 implies 256 colors; a value of 16 implies 65,536 colors.
Vrefresh
Specifies a valid refresh rate for the graphics device being installed.
Xresolution
Specifies a valid x resolution for the graphics device being installed.
Yresolution
Specifies a valid y resolution for the graphics device being installed.
To ensure the video mode is properly detected by Setup
Check that the computer BIOS supports the set of Video ACPI extensions.
Check that the drivers for the video cards and displays are included in the \$1\PnPdrvrs path.
In the [Unattended] section of the answer file, set the OemPnPDriversPath key to the \$1\PnPdrvrs path.
In the [Display] section of the answer file, set the optimal settings for your computer.
To determine whether the hardware components in your organization are compatible with Windows XP Professional, see the Hardware Compatibility List link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources
Automatically Converting FAT32 to NTFS
When upgrading, you can customize the [Unattended] section of your answer file to convert FAT32 file systems automatically to NTFS.
To automatically convert FAT32 partitions to NTFS
In the [Unattended] section of your answer file, add the statement shown in the following example:
[Unattended] FileSystem = ConvertNTFS
When the FileSystem key is specified, Setup automatically converts your drive just before the GUI mode of Setup starts. You must add the FileSystem = ConvertNTFS entry to the [Unattended] section if the ExtendOEMPartition entry appears in the [Unattended] section of the answer file.
For more information about the differences between the NTFS, FAT16, and FAT32 file systems, see File Systems in this book.
Converting Short File Names to Long File Names ($$rename.txt)
If you are starting Setup from MS-DOS, you can convert short file names to long names by creating a file called $$Rename.txt and putting that file in the folder of the distribution folder that also contains the files that you want to convert. If you are starting Setup from any other operating system, they are converted automatically.
Setup uses the list of files that you specify in $$Rename.txt to convert short names to long names during the installation process. Each folder that contains a file, or files, that you want to convert must also contain a $$Rename.txt file.
The $$Rename.txt file changes short file names to long file names during Setup. $$Rename.txt lists all of the files in a particular folder that must be renamed. Each folder that contains short file names to be renamed must contain its own version of $$Rename.txt.
To convert short file names to long file names
Create a $$rename.txt file by using the sections, keys, and values shown in the following example:
Table 2-11 describes the variables in the preceding example.
Table 2-11: Converting Short File Names to Long File Names
Section or Key
Description
[Section_name_x]
This section name indicates the path to the folder that contains the files. A section does not have to be named, or it can have a backslash (\) as a name, which indicates that the section contains the names of the files or folders that are in the root directory of the drive.
Short_name_x
This key is the short name of the file or folder within the folder indicated by the section name. The short name must not be enclosed in quotation marks.
Long_name_x
This key Is the long name of the file or folder. This name must be enclosed in quotation marks if it contains spaces or commas.
Tip
If you are using MS-DOS to start the installation, and your MS-DOS-based tools cannot copy folders with path names longer than 64 characters, use short file names for the folders and then use $$Rename.txt to rename them later.
Adding Applications
Use any of the following methods to add applications to your installation:
Cmdlines.txt to add applications during the GUI mode of Setup.
Customized answer files. For example, customize the [GuiRunOnce] section of the answer file to install applications when the user logs on for the first time.
Application installation programs.
Batch files.
Windows Installer.
Using Cmdlines.txt
The Cmdlines.txt file contains the commands that GUI mode runs when installing optional components, such as applications that must be installed immediately after Windows XP Professional installation. If you plan to use Cmdlines.txt, place it in the $OEM$ folder of the distribution folder. If you are using Sysprep, place Cmdlines.txt in the $OEM$\$1\Sysprep\$oem$ folder.
Use Cmdlines.txt under the following circumstances:
You are installing from the \$OEM$ folder of the distribution folder.
The application that you are installing:
Does not configure itself for multiple users (for example, Microsoft Office 95).
Is designed to be installed by one user and to replicate user-specific information.
The section and keys for Cmdlines.txt is shown in the following example:
Command_1, Command_2, and Command_x refer to the commands that you want to run (and the order in which you want to run them) when GUI mode calls Cmdlines.txt. Note that all commands must be within quotation marks.
When you use Cmdlines.txt, be aware of the following:
When the commands in Cmdlines.txt are carried out during setup, there is no logged-on user and there is no guaranteed network connectivity. Therefore, user-specific information is written to the default user registry, and all users receive that information.
Cmdlines.txt requires that you place the files that you must have to run an application or tool in directories that you can access during the setup process. This means that the files must be on the hard disk.
Warning
Applications that can be installed by using Windows Installer cannot be added by using Cmdlines.txt.
To specify a Cmdlines.txt file during the MiniSetup portion of Sysprep
Create a Sysprep.inf file to be used by Sysprep. This is a requirement and cannot by bypassed. The Sysprep.inf file must be named Sysprep.inf and must be located in the Sysprep folder on the root of the volume that contains the folder %systemroot%.
Place the following statement in the [Unattended] section of the Sysprep.inf file:
InstallFilesPath = drive:\path
In the preceding example, path is any folder you want to use. It is recommended that you use drive as the volume containing the %systemroot% folder.
Create the folder drive:\path. You can use any folder name, but it must match the location that you specified in Sysprep.inf.
In the drive:\path folder, create a folder named $oem$, and then place the Cmdlines.txt file in this folder. This file is processed at the end of MiniSetup, before saving any settings.
Using the [GuiRunOnce] Section of the Answer File
The [GuiRunOnce] section of the answer file contains a list of commands that run the first time a user logs on to the computer after Setup has run. To configure the application installation program so that it starts automatically, you can add the statement shown in the following example to the [GuiRunOnce] section of the answer file:
If you plan to use the [GuiRunOnce] section to initiate an installation, consider the following additional factors:
If an application forces a restart, determine how to suppress the restart.
This is important because any time the system restarts, all previous entries in the [GuiRunOnce] section are lost. If the system restarts before completing entries previously listed in the [GuiRunOnce] section, the remaining items are not run. If there is no way within the application to suppress a restart, you can try to repackage the application into a Windows Installer package. Third-party products are available to provide this functionality.
Windows XP Professional contains Iexpress.exe. You can use Iexpress.exe to package .inf files into executable files. These executable files can then be included in either Cmdlines.txt or [GUIRunOnce].
Warning
If you are adding an application to multiple localized language versions of Windows XP Professional, it is recommended that you test the repackaged application on the localized versions to ensure that the files are copied to the correct locations and the required registry entries are written appropriately.
If an application requires a Windows Explorer shell to install, the [GuiRunOnce] section does not work because the shell is not loaded when the Run and RunOnce commands are carried out.
Check with the application vendor to determine if there is an update that you can download that enables the application to install. If not, repackage the application as a Windows Installer package or use another means of distribution.
Applications that use the same type of installation mechanism might not run correctly if you do not use a-wait parameter.
This can happen when an application installation is running and starts another process. When Setup is still running, initiating another process and closing an active process might cause the next routine listed in the RunOnce registry entries to start. Because more than one instance of the installation mechanism is running, the second application usually fails.
Using Application Installation Programs
The preferred method for adding an application is to use the installation routine supplied with the application. You can do this if the application that you are adding can run in quiet mode (without user intervention) by using a -q or -s parameter. These parameters vary depending on how the application is written. For a list of parameters supported by the installation mechanism, see the application documentation.
To initiate the unattended installation of an application by using the application s installation program, you can add text to the [GuiRunOnce] section of the answer file that is similar to the statement shown in the following example:
path to setup\Setup.exe /q
Setup parameters vary depending on how the application is written. For example, the -l parameter included in some applications is useful when you want to create a log file to monitor the installation. Some applications have commands that can prevent them from automatically restarting. These commands are useful in helping to control application installations with a minimal number of restarts.
Make sure that you check with the application vendor for information, instructions, tools, and best practices information before you install any application.
Warning
You must meet the licensing requirements for any application that you install, regardless of how you install it.
Using a Batch File to Control How Multiple Applications Are Installed
To control how multiple applications are installed, create a batch file that contains the individual installation commands and uses the Start command with the /wait parameter. This method ensures that your applications install sequentially and that each application is fully installed before the next application begins its installation routine. The batch file is then run from the [GuiRunOnce] section.
The following procedure explains how to create the batch file, install the application, and remove all references to the batch file after the installation is complete.
To install applications by using a batch file
Create a batch file that uses the following syntax:
Table 2-12 describes the syntax that is used in the preceding example.
Table 2-12: Batch File Parameters
File or Parameter
Description
AppSetupProgram
Specifies the path and file name for the application setup program, for example, D:\Setup.exe.
AppSetupProgramParameters
Specifies any available quiet-mode parameters for the setup program that you have specified.
Copy the batch file to the distribution folders or another location to which you have access during setup.
Using File name.bat as the name of the batch file, include an entry in the [GuiRunOnce] section of the answer file to run the batch file as shown in the following example. This example is based on the assumption that the batch file was copied to the Sysprep folder on the local hard disk. However, the batch file can be in any location that is accessible to Setup during an installation.
In the preceding example, path-n\Command-n.exe and %systemdrive%\sysprep\sysprep.exe -quiet are fully qualified paths to additional applications, tool installations, or configuration tools. They can also be paths to batch files. These paths must be available during setup.
Using Windows Installer Service
Windows Installer Service is a Windows XP Professional component that standardizes the way applications are installed on multiple computers.
When you install applications without using Windows Installer Service, every application must have its own setup executable file or script. Each application has to ensure that the proper installation rules (for example, rules for creating file versions) are followed. This is because the application setup was not an integral part of the operating system development; therefore, no central reference for installation rules exists.
Windows Installer Service implements all the Setup rules for the operating system. To follow these rules, applications must be described in a standard format known as a Windows Installer package. The data file containing the format information is known as the Windows Installer package file and has an .msi file name extension. Windows Installer Service uses the Windows Installer package file to install the application.
The package file is a database format that is optimized for installation performance. Generally, this file describes the relationships among features, components, and resources for a specific product.
The Windows Installer package file is typically located in the root folder of the Windows XP Professional operating system CD or network image, alongside the product files. The product files can exist as compressed files known as cabinet (.cab) files. Each product has its own package file. During installation, Windows Installer Service opens the package file for the product and uses the information inside the Windows Installer package to determine which installation operations must be performed for that product.
Setting Passwords
When upgrading from Windows 98 or Windows Me, you can customize your answer files to set passwords for all local user accounts and force all users or specific users to change their passwords when they first log on. You can also set passwords for the local Administrator account.
Table 2-13 describes the types of passwords that you can set in an answer file.
Table 2-13: Types of Passwords That You Can Set in an Answer File
Section
Key
Description
[GuiUnattended]
AdminPassword
Automatically sets the password for the local Administrator account. If the AdminPassword key is used in a Sysprep.inf file, the original password on the computer must be set to null. Otherwise, any AdminPassword value in the answer file is ignored.
[Win9xUpg]
DefaultPassword
Automatically sets a password for all local accounts created when you are upgrading from Windows 98 or Windows Me.
[Win9xUpg]
ForcePasswordChange
Forces users for all local accounts to change their passwords when they log on for the first time after upgrading from Windows 98 or Windows Me.
[Win9xUpg]
UserPassword
Forces specific users to change their passwords on their local accounts when they log on for the first time after upgrading from Windows 98 or Windows Me to Windows XP Professional.
Sets user passwords for local accounts after an upgrade from Windows 98 or Windows Me to Windows XP Professional.
If the answer file does not contain a UserPassword key and a DefaultPassword key, a password is generated for each migrated local user account. When users log on for the first time, they are required to change their password.
Prompting the User for the Administrator Password
The administrator password is set to null by default. You can customize your answer file to prompt the user for an administrator password during installation.
Locate the following entry in the [Unattended] section of the answer file:
[Unattended] UnattendMode = FullUnattended
If the UnattendMode key is set to FullUnattended, as shown in the preceding example, do not edit the answer file as described in the following procedure. This combination of answer file settings generates an error.
To prompt for an administrator password
Locate the following entry in the [GuiUnattended] section of your answer file:
[GuiUnattended] AdminPassword = "*"
Edit the entry to read:
[GuiUnattended] AdminPassword = ""
This enables the user to type the local administrator password in GUI-mode Setup.
To optionally put Setup in read-only mode and prevent users from changing fields (other than the Administrator password) during Setup, add the following line to the [Unattended] section of the answer file:
[Unattended] UnattendMode = "ReadOnly"
This enables the user to type only the local administrator password in GUI-mode Setup.
An alternative to the preceding procedure is to use Setup Manager to create the answer file and supply an administrator password. When you use Setup Manager, you can encrypt the password in the answer file so that users cannot read it.
For more information about using the RIS Client Installation Wizard to prompt users for the administrator password, see Customizing RIS Installations earlier in this chapter.
Setting Passwords on Local Accounts
For upgrades, you can customize your answer file to set all local account passwords to a default value.
To set passwords on all local accounts
In your answer file, add the following entry in the [Win9xUpg] section:
[Win9xUpg] DefaultPassword = "password"
In the preceding example, password is the default password that you want to set for all local users.
Note
If a local account must be created for a user without a UserPassword entry and no DefaultPassword is specified, Setup creates a random password. After the first restart, the user is prompted to change the password.
For Windows 98 upgrades, you can customize your answer file to create passwords for specific local accounts. Because Windows 98 and Windows Me passwords cannot be migrated during the upgrade, Setup must create passwords for local accounts during the upgrade process. By using the DefaultPassword key, the administrator can predetermine those passwords for specific users. If a local account needs to be created for a user without a preset value for the UserPassword entry and no value is specified for DefaultPassword, Setup generates a random password.
To create passwords for specific local accounts when you are upgrading from Windows 98 or Windows Me
In the answer file, add the following entry in the [Win9xUpg] section:
Forcing All Users to Change Local Account Passwords When Upgrading from Windows 98 or Windows Me
You can customize your answer file to require all users to change their passwords on their local accounts when they log on for the first time. When a user logs on for the first time, he or she is notified that his or her current password has expired and that a new password must be supplied.
To force users to change their password after upgrading from Windows 98 or Windows Me
In the answer file, add the following entry in the [Win9xUpg] section:
