Microsoft Windows XP Professional Resource Kit 2003
ISBN: N/A
EAN: N/A
EAN: N/A
Year: 2005
Pages: 338
Pages: 338
After you have chosen the method to install the operating system and have customized your answer file and the distribution folder with the appropriate files, you are ready to install the operating system.
The following installation methods are covered in this section:
Unattended Installations
Image-based Installations with Sysprep
Installations with RIS
Winnt32.exe and Winnt.exe are unattended installation tools that provide a convenient and flexible method for installing the operating system. In addition, Winnt32.exe does not require additional tools. This section explains how to use Winnt32.exe.
| Caution | Before upgrading to the Windows XP Professional operating system, restart the computer if you have recently upgraded any applications. |
| Note | When you run Winnt32.exe on a computer with multiple hard disks or partitions, specify the exact location of the destination hard drive or partition to which you are installing. Use the Winnt32 /tempdrive parameter to specify the destination. |
Use Winnt32.exe to run Setup on computers running Windows 98, Windows Me, Windows 2000, Windows NT Workstation 4.0, or Windows XP Professional operating systems.
| Note | Winnt32.exe is also referred to as Setup. |
To run Setup in unattended mode
At the command prompt type: winnt32 /unattend: answer_file.
When you run the Setup program, it installs Windows XP Professional in three phases: File Copy, Text mode, and GUI mode.
Setup copies the Windows XP Professional program files and any additional files that you specify from the distribution folder to the computer s hard disk.
Setup identifies the basic hardware in the computer (such as the microprocessor and motherboard type, hard disk controllers, file systems, and memory), installs the base operating system required to continue with Setup, and creates any folders that you specify.
Setup configures the computer s hardware (audio, video, and so on), configures network settings, prompts you to provide an Administrator password, and allows you to personalize the installation. If you use Sysprep, the Setup program goes through a different phase called MiniSetup.
Winnt32
[/checkupgradeonly]
[/cmd:command_line]
[/cmdcons]
[/copydir:folder_name]
[/copysource:folder_name]
[/debuglevel:file_name]
[/dudisable]
[/duprepare:pathname]
[/dushare:pathname]
[/m:folder_name]
[/makelocalsource]
[/noreboot]
[/s:sourcepath]
[/syspart:drive_letter]
[/tempdrive:drive_letter]
[/udf:ID,UDF_file]
[/unattend]
[/unattend:seconds][:answer_file]
To determine which parameters you want to use, refer to the following Winnt32.exe parameter descriptions:
Checks the current operating system for upgrade compatibility with Windows XP Professional. This is simply a verification and does not install Windows XP Professional.
Specifies a command to be carried out after the GUI mode of Setup finishes. The command occurs before Setup is complete and after Setup has restarted your computer and collected the necessary configuration information. For example, this parameter can run Cmdlines.txt, which specifies the applications to be installed immediately after Setup completes.
Adds a Recovery Console option for repairing a failed installation.
Creates a subfolder within the folder that contains the Windows XP Professional files. For example, if the source folder contains a Private_drivers folder that has modifications just for your site, you can type /copydir:private_drivers to copy that folder to your Windows XP Professional folder. You can use the /copydir parameter multiple times.
Temporarily creates a subfolder within the folder that contains the Windows XP Professional files. For example, if the source folder contains a Private_drivers folder that has modifications just for your site, type /copysource:private_drivers to have Setup copy that folder to your Windows XP Professional folder and use its files during Setup. Unlike the /copydir parameter, folders created by using /copysource are deleted when Setup finishes.
Creates a debug log at the specified level. When you use the default setting, the program creates a log file (%windir%\Winnt32.log) that has a warning level of 2. The warning levels for the log file are as follows: 0 = severe errors, 1 = errors, 2 = warnings, 3 = information, and 4 = detailed information for debugging. Each level also includes the levels below 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 DisableDynamicUpdates = No in the [Unattended] section of the Unattend.txt file. /dudisable in Winnt32.exe overrides the DisableDynamicUpdates = No setting in Unattend.txt.
Prepares an installation share to be used with Dynamic Update files downloaded from the Windows Update Web site. The installation share can then be used for installing Windows on multiple client computers.
Specifies a 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 computer, /duprepare:pathname specifies that the client installation uses the updated files on the share that is specified in pathname.
Instructs Setup to copy replacement files from an alternate location. It directs Setup to look at the alternate location first and to copy the files from that location (if they files are present) instead of from the default location.
Instructs Setup to copy all installation source files to your local hard disk. Use /makelocalsource to obtain installation files if you begin installation from a CD and the CD becomes unavailable during the installation.
Instructs Setup to not restart the computer after the file copy phase of Winnt32 is complete so you can execute another command.
Specifies the source location of the Windows XP Professional files. The default is the current folder. To copy files simultaneously from multiple servers, you can specify up to eight sources. For example:
winnt32 /s:server1 /s:server8
If you type the option multiple times, the first server specified must be available, or Setup fails.
This functionality speeds up the file copy phase of Setup to the destination computer and provides additional load balancing capability to the distribution servers from which you run Setup.
Specifies that you can copy Setup startup files to a hard disk, mark the disk as active, and install the disk in another computer. When you start that computer, Setup automatically starts at the next phase. Remember the following points when you use this parameter:
You must always use the /syspart option with the /tempdrive option.
Both /syspart and /tempdrive must point to the same partition of a secondary hard disk.
You must install Windows XP Professional on the primary partition of the secondary hard disk.
You can use the /syspart parameter only from a computer that is running Windows NT 3.51, Windows NT 4.0, Windows 2000 Professional, or Windows XP Professional. You cannot use this parameter from a computer that is running Windows 98 or Windows Me.
Directs Setup to place temporary files on the specified partition and to install Windows XP Professional on that partition. Remember the following points as you use this parameter:
You must always use the /tempdrive option with the /syspart option.
Both /tempdrive and /syspart must point to the same partition of a secondary hard disk.
You must install Windows XP Professional on the primary partition of the secondary hard disk.
Indicates an identifier that Setup uses to specify how a Uniqueness Database File (UDF) modifies an answer file. The UDF file overrides values in the answer file, and the identifier determines which values in the UDF file are used. For example, /udf:Roaming_user,Our_company.udf overrides settings specified for the identifier Roaming_user in the Our_company.udf file. If you do not specify a UDF file, Setup prompts you to insert a disk that contains the file $Unique$.udf.
Upgrades a previous version of Windows by using unattended installation mode. 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. No user intervention is required during Setup.
User passwords cannot be migrated from a Windows 98 or Windows Me installation during an upgrade to Windows XP Professional; however, if you are upgrading from Windows NT Workstation 4.0 or Windows 2000, any user accounts that were defined in the local database are available after upgrading to Windows XP Professional.
| Warning | By adding the OemSkipEula key to the [Unattended] section of the answer file, you can automate Setup to affirm that you have read and accepted the End User License Agreement (EULA) for Windows XP Professional. Before using this entry to install Windows XP Professional on behalf of an organization other than your own, you must confirm that the end user (whether an individual or a single entity) has received, read, and accepted the terms of the Windows XP Professional EULA. OEMs cannot specify this key for computers being sold to end users. |
The specified num value indicates the number of seconds between the time that Setup finishes copying the files and when Setup restarts. You can use num on any computer running Windows 98, Windows Me, Windows NT Workstation 4.0, Windows 2000, or Windows XP.
The specified answer_file provides Setup with your custom specifications.
The System Preparation tool, Sysprep.exe, is a disk-image-based deployment tool that you can use to install identical configurations on multiple computers. You can also use Sysprep to customize and automate MiniSetup and to audit computers. You can run Sysprep as many times as you want; however, if you are using a non-volume licensed version, you can only run Sysprep.exe and the MiniSetup Wizard three times on the same operating system installation. You cannot run Sysprep a fourth time. This also applies to Riprep.
On a reference computer, install the operating system and any applications that you want installed on your destination computers, and then run Sysprep. Sysprep prepares the hard disk on the reference computer for duplication to other computers. You can then run a third-party disk-imaging application. The major advantage of Sysprep installation is speed. The image can be packaged and compressed; only the files required for the specific configuration are created as part of the image. The shortened GUI-mode Setup can take five or six minutes instead of 45 to 60 minutes and prompts the user only for required and user-specified information.
Because the reference and destination computers are required to have identical HALs and ACPI support, you might be required to maintain multiple images for your environment.
| Warning | Before performing disk duplication, check with your software vendor to make sure that you are not violating the licensing agreement for installation of the software that you want to duplicate. |
The following steps describe the process of preparing a reference computer to use for disk duplication.
Table 2-14 describes the steps you must perform during the process of preparing a reference computer for disk duplication.
| Step | Description |
|---|---|
| Step 1 | Install the operating system on a computer that has hardware similar to the destination computers. While preparing the computer, do not join it to a domain, and keep the local administrative password blank. |
| Step 2 | Configure the computer. Log on as the administrator, and then install and customize Windows XP Professional and associated applications. These might include adding plug and play device drivers or productivity applications, such as Microsoft Office, business-specific applications, and other applications or settings that you want included in a common configuration for all client computers. |
| Step 3 | Validate the image. Run an audit, based on your criteria, to verify that the image configuration is correct. Remove residual information, including anything left behind from audit and event logs. |
| Step 4 | Prepare the image for duplication. When the computer is configured exactly as you want it, prepare the system for duplication. If you are running Sysprep with the -mini parameter, you can prepare the system by running Sysprep with the optional Sysprep.inf file, which is described earlier in this chapter. After Sysprep runs, the computer shuts down automatically or indicates that it is safe to shut down. |
| Step 5 | Duplicate. The computer hard disk is triggered to run Plug and Play detection, create new security identifiers (SIDs), and run the MiniSetup Wizard the next time the system is started. You can duplicate or create an image of the system by using hardware or software. The next time Windows XP Professional is started from this reference computer or from any destination computer created from this image, the system detects and reenumerates the Plug and Play devices to complete the installation and configuration on the destination computer. |
| Warning | Components that depend on the Active Directory directory service cannot be duplicated. |
Before you can use Sysprep, your computer hardware and related devices must meet the following requirements:
The reference and destination computers must have compatible HALs. For example, Advanced Programmable Interrupt Controller (APIC) based MPS (multiprocessor systems) must use the same APIC HAL. A standard HAL Programmable Interrupt Controller (PIC) based system is not compatible with either the APIC HAL or the MPS HAL.
The reference and destination computers must have identical Advanced Configuration and Power Interface (ACPI) support.
The Plug and Play devices on the reference and destination computers, such as modems, sound cards, network adapters, and video cards, do not have to be from the same manufacturer. However, the drivers for these devices must be available.
Third-party disk-imaging software or disk-duplicating hardware devices are required. These products create binary images of a computer s hard disk and either duplicate the image to another hard disk or store the image in a file on a separate disk.
The size of the hard disk on the destination computer must be at least the same size as the hard disk on the reference computer. If the destination computer has a larger hard disk, the difference is not included in the primary partition. However, you can use the ExtendOemPartition key in the Sysprep.inf file to extend the primary partition if it was formatted as NTFS.
In Windows XP Professional, Sysprep can reset Windows Product Activation a maximum of three times. When a computer running a disk image that was prepared with Sysprep is restarted, the activation timer is reset and the installation of Windows XP Professional is enabled with the full grace period for Windows Product Activation. After three resets, the activation timer is no longer reset. To prevent resets of the activation timer, run Sysprep from the command line, and include the -activated parameter and the -reseal parameter, as shown in the following example:
sysprep -activated -reseal
For more information about Windows Product Activation, see Planning Deployments in this book.
Run Sysprep.exe manually or configure Setup to run Sysprep.exe automatically by using the [GuiRunOnce] section of the answer file. Sysprep.exe and Setupcl.exe must be located in a Sysprep folder at the root of the system drive (%SystemDrive%\Sysprep\). To place the files in the correct location during an automated Setup, add these files to your distribution folders under the $OEM$\$1\Sysprep folder. For more information about this folder, see Create a Distribution Folder earlier in this chapter.
Sysprep.exe and Setupcl.exe prepare the operating system for duplication and start MiniSetup. If you are running Sysprep with the -mini parameter, you can also include the optional answer file, Sysprep.inf, in the Sysprep folder. Sysprep.inf contains default keys that you can use to provide consistent responses where they are appropriate. This limits the requirement for user input and reduces potential user errors.
In addition, you can customize the destination computer by placing the Sysprep.inf file on a floppy disk and inserting it after the Windows startup screen appears. The floppy disk is read when the Please Wait MiniSetup Wizard screen appears. When the MiniSetup Wizard successfully completes its tasks, the system restarts a final time, the Sysprep folder and all of its contents are deleted, and the system is ready for the user to log on.
The Sysprep files are defined in the following sections.
Table 2-15 describes the optional parameters for Sysprep.exe.
| Parameter | Description |
|---|---|
| quiet | Runs Sysprep without displaying the Sysprep onscreen messages. |
| nosidgen | Runs Sysprep without regenerating SIDs that are already on the system. This is useful if you do not intend to duplicate the computer on which you are running Sysprep. |
| pnp | Forces full hardware detection when the computer is restarted. Setup actively seeks new devices on the system, whether or not they are Plug and Play. Because this mode increases the time required for MiniSetup, it is only useful if the computer on which the image is being loaded contains non Plug and Play hardware that cannot be dynamically detected. |
| reboot | Automatically restarts the computer after Sysprep shuts it down. This eliminates the need to manually turn on the computer again. |
| activated | Prevents Windows Product Activation resets. If this parameter is not set, Sysprep can reset Windows Product Activation a maximum of three times. |
| factory | When you are running Sysprep.exe, enables you to add additional drivers and applications to the image after the computer restarts. |
| reseal | Enables you to reseal the image and prepare the computer for delivery after you have made modifications to the image in Factory Mode. |
| msoobe | Displays the Windows Welcome screen (Msoobe.exe) on the next restart of the computer. |
| forceshutdown | Prepares the operating system as specified by Reseal Mode, and then immediately shuts down the computer without user intervention. |
| mini | Runs MiniSetup on the next restart of the computer. |
| Note | For more information about optional parameters for Sysprep.exe, see Microsoft Windows Presinstallation Reference (Ref.chm) in the Deploy.cab file in the \Support\Tools folder on the Windows XP Professional operating system CD. You can use Windows Explorer or you can run Extract.exe to extract and view the Ref.chm file. |
Sysprep.inf is an answer file that is used to automate the MiniSetup process. It uses the same INI 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
For more information about Sysprep.inf, see Customizing Sysprep Installations earlier in this chapter. For details about answer file parameters and syntax, see the Deploy.chm in the Deploy.cab on the Windows XP Professional operating system CD. The Deploy.cab file is in the \Support\Tools folder.
Setupcl.exe regenerates new security identifiers (SIDs) for the computer.
To run Sysprep from the user interface, double-click Sysprep.exe. The System Preparation Tool dialog box appears. The System Preparation Tool dialog box enables you to perform the following functions:
Run Factory Mode to add additional drivers and applications to the Sysprep image.
Run Audit Boot mode to restart the computer before you are ready to use Reseal mode.
When you have made modifications in Factory Mode, run Reseal mode to prepare the computer for delivery.
Select the PnP flag to force full hardware detection when the computer is restarted.
Select the NoSIDGen flag to run Sysprep without regenerating SIDs that are already on the computer.
Select the MiniSetup flag to run MiniSetup the first time a computer starts from a hard disk that has been duplicated by using Sysprep.
Select the Pre-activated flag to prevent resets of Windows Product Activation.
For more information about Factory Mode and about MiniSetup flag, see Customizing Sysprep Installations earlier in this chapter.
After you install the operating system, you can use Sysprep to prepare for the transfer of the operating system to other similarly configured computers.
To run Sysprep manually, first install the operating system, configure the computer, and install any applications you want to include, then run Sysprep without using the -reboot command-line parameter. After the system shuts down, duplicate the image of the hard disk to the similarly configured computers.
If you are running Sysprep with the -mini parameter, the MiniSetup Wizard runs when users start their duplicated computers for the first time. You can preassign all or some of the Sysprep configuration parameters by using Sysprep.inf. The Sysprep folder (which contains Sysprep.exe and Setupcl.exe) is automatically deleted after MiniSetup is completed.
To prepare a Windows XP Professional installation for duplication
From the Start menu, click Run, and then type:cmd
At the command prompt, change to the root folder of drive C, and then type:
md sysprep
Insert the Windows XP Professional operating system CD into the appropriate CD-ROM drive. Open the Deploy.cab file in the \Support\Tools folder.
Copy Sysprep.exe and Setupcl.exe to the Sysprep folder.
If you are using Sysprep.inf, copy this file to the Sysprep folder. For Sysprep to function correctly, Sysprep.exe, Setupcl.exe, and Sysprep.inf must all be in the same folder.
At the command prompt, change to the Sysprep folder by typing:
cd sysprep
At the command prompt, type:
sysprep /optional_parameter
If you don t use -reboot as one of your optional parameters, click Shut Down from the Start menu when a message appears requesting that you shut down the computer. You are now ready to use a third-party disk-imaging tool to create an image of the installation.
| Note | You can add a Cmdlines.txt file to the Sysprep\i386\$oem$ folder to be processed by Setup. This file is used to run post-setup commands, including commands for application installation. For more information about Using Cmdlines.txt, see Adding Applications earlier in this chapter. |
Use a third-party disk-imaging tool to create a Windows XP Professional image. To ensure the best outcome when you are using a third-party disk-imaging tool with Windows XP Professional, make sure the tool meets all the requirements for your environment and make sure the tool can do the following:
Access NTFS partitions.
Make sure your disk-imaging tool is compatible with Windows XP. Disk-imaging tools that are designed for use with the version of NTFS supported by Windows 2000, might not be compatible with the version of NTFS supported by Windows XP.
Handle long file names.
Create packages with short file names (for server environments that cannot read long file names).
Open packages to add/remove files (such as new/updated drivers) without having to recreate the entire package.
With Sysprep, you can minimize the number of images that you need to use for preinstalling Windows XP Professional from multiprocessor (MP) to uniprocessor (UP) computers or from uniprocessor to multiprocessor computers. However, this only works for APIC or ACPI APIC computers.
| Note | More interrupts are available with APIC systems than with programmable interrupt controller (PIC) uniprocessor systems. As a result, computers with APIC HALs have faster response times, and they can support more hardware devices than computers with PIC HALs. |
You can use one of several methods to create images for installations on multiprocessor systems and deploy the images on uniprocessor systems, or to create images for installations on uniprocessor systems and deploy the images on multiprocessor systems. Each method has advantages and disadvantages, as outlined in the following sections. Choose the method that works best for you and your preinstallation environment.
Table 2-16 illustrates the compatibility of computers based on their HAL type. One image is required for each compatibility group. In this table, multiprocessor is abbreviated MP and uniprocessor is abbreviated UP.
| Compatibility | ACPI PIC | ACPI APIC UP | ACPI APIC MP | Non ACPI UP PIC | Non ACPI APIC UP | Non ACPI APIC MP |
|---|---|---|---|---|---|---|
| ACPI PIC | X | |||||
| ACPI APIC UP | X | X | ||||
| ACPI APIC MP | X | X | ||||
| Non-ACPI UP PIC | X | X | ||||
| Non ACPI APIC UP | X | X | X | |||
| Non ACPI APIC MP | X | X |
For this process, the image is created on a multiprocessor reference computer. This image can be used on other multiprocessor computers or on uniprocessor computers.
The advantage of multiprocessor to uniprocessor is that you can create a single entry in the Sysprep.inf file that then prompts Windows XP Professional to determine, after MiniSetup is complete, if a single processor or multiple processors are running. The correct kernel files are then used.
The disadvantage of multiprocessor to uniprocessor is that this process requires that, when you create the reference image, you include each of the Mp2up.inf files and other related Mp2up files in the distribution folders.
| Warning | This image can only be used in one of the following configurations depending on the HAL type you are using:
|
To create a multiprocessor to uniprocessor image
Copy the Mp2up.inf and associated Mp2up files to the location you are using for your Plug and Play device drivers in your distribution folders, for example, \$OEM$\$1\Sysprep\Hal.
In Sysprep.inf, add:
[Unattended]
UpdateUPHAL = "hwid,%SystemDrive%\Sysprep\Hal.inf"
In the preceding example, hwid is either MPS_UP or ACPI APIC_UP.
Install the operating system from the distribution folders to a multiprocessor computer.
Run Sysprep with the Sysprep.inf created in step 2.
Image the computer.
Place the image on comparable destination computers.
For this process, the image is created on a uniprocessor reference computer with an APIC HAL. This image can then be used on computers with compatible hardware and compatible HALs (either APIC UP HALs or APIC MP HALs).
The advantage of uniprocessor to multiprocessor is that you do not have to install the Mp2up files on the computer.
The disadvantage of uniprocessor to multiprocessor is that before the computers can be shipped, the Sysprep.inf file must be replaced depending on the type of computer being shipped: uniprocessor or multiprocessor.
| Warning | This image can only be used in one of the following configurations, depending on the HAL type you are using:
|
To create the uniprocessor to multiprocessor image
Install the operating system on a uniprocessor computer.
Run Sysprep.
Create the image of the computer.
In Sysprep.inf, add:
[Unattended]
UpdateHAL = "hwid,%windir%\inf\hal.inf"
In the preceding example, hwid is either MPS_MP or ACPI APIC_MP.
Place the image on comparable destination computers.
On multiprocessor computers, use the Sysprep.inf file created in step 4 to replace all previous Sysprep.inf files.
You can use any tools you normally use to manipulate files on the hard disk when creating new computers from an image.
When installing Windows XP Professional, you might find it necessary to extend the partition of the destination computer. You can use Sysprep with the appropriate entries in the answer file to extend an NTFS partition. You might want to extend an NTFS partition for the following reasons:
To create images that can be extended into larger disk partitions and take advantage of hard disks that might have greater capacity than the original hard disk on the reference computer.
To create images on smaller hard disks.
Review the following steps and choose the method that works best for you, based on the third-party tools that you are using to create an image of the operating system.
| Caution | Make sure that you do not accidentally delete the Setupapi.log and Hyberfil.sys files (if applicable) when modifying the image. These files are recreated when the MiniSetup Wizard runs on the destination computer. Deleting these files on an active system can cause the system to function improperly. |
When used in an answer file, the ExtendOemPartition key causes Setup to extend the destination partition into any available unpartitioned space that physically follows it on the hard disk.
The values for ExtendOemPartition are 0, 1, and extra size in MB
where:
0 Setup does not extend the partition.
1 Setup extends the partition to fill out the hard disk.
extra size in MB Setup increases the current partition size by this amount.
ExtendOemPartition automatically leaves the last cylinder on the hard disk free to allow dynamic disk support. ExtendOemPartition can be set to a number other than 1 to indicate a specific disk size for extending the hard disk. This is useful if more than one partition is requested on a computer.
| Warning | Only NTFS partitions can be extended. If the destination partition you plan to extend is FAT or FAT32, run convert.exe /fs:ntfs from the command line before running Sysprep. The file system is converted when the image is applied to the destination computer before the MiniSetup Wizard starts. Setup does not extend FAT16 and FAT32 partitions. ExtendOemPartition can be used with both the Unattend.txt and Sysprep.inf Setup files. When used in Sysprep.inf for imaged computers, the destination computer s hard disk must be the same size or larger than the reference computer s hard disk. To enable the extension, the partition to be extended must have contiguous unpartitioned space available. |
To extend a hard disk partition when using a third-party disk-imaging product or a hardware-imaging device that supports the version of NTFS that is used by Windows XP Professional
Create a partition on the reference computer hard disk that is just large enough to install Windows XP Professional with all the components and applications that you intend to add. This helps keep the size of the reference image file to a minimum.
If the destination partition you plan to extend is FAT or FAT32, run convert.exe /fs:ntfs from the command line before running Sysprep. The file system is converted when the image is applied to the destination computer before the MiniSetup Wizard starts.
| Note | ConvertNTFS does not work in Sysprep.inf because this is a text mode-only function and Sysprep does not go through text mode. |
In the [Unattended] section of Sysprep.inf, include the statement:
ExtendOemPartition = 1
You can also set the additional size in megabytes to extend the partition.
Install Windows XP Professional on the reference computer. Sysprep shuts down the system automatically.
Generate the image.
Place the image on the destination computer where the destination computer has the same size system partition as the reference computer.
Restart the destination computer.
When you place the reference image on a destination computer, drive C is converted to NTFS when the computer starts. The computer then restarts and starts MiniSetup. During MiniSetup, Windows extends drive C to the rest of the unpartitioned space on the hard disk. The destination computer then restarts, and the end user can log on and begin using Windows XP Professional.
The MiniSetup Wizard starts and the partition is extended.
To extend a hard disk partition when using a disk-imaging product that does not support NTFS used by Windows XP Professional
In the [Unattended] section of Sysprep.inf, include the statement:
ExtendOemPartition = 1
Or additional size in megabytes to extend the partition.
Use Cmdlines.txt to convert short file names.
Run Sysprep.
The following actions occur when you restart the destination computer:
The computer initially starts in conversion mode to convert the system partition on the destination computer to NTFS.
The computer automatically restarts.
The MiniSetup Wizard starts, and the partition is extended almost instantaneously.
Even if you don t have a network, you can still install Windows XP Professional and various applications on client computers, one computer at a time.
To install Windows XP Professional on nonnetworked computers
Choose a setup method, and then start Setup.
Add custom information and additional files.
Install applications. If you have no applications to install, skip this step.
| Warning | Each client computer must have a CD-ROM drive. |
Setup can typically be started from an MS-DOS bootable floppy disk, from a set of Windows XP Professional Setup floppy disks that you can create from the Web, or from the Windows XP Professional operating system CD. Starting from a CD is available only on computers that support the El Torito No Emulation CD boot specification. Choose from the setup methods provided later in this section.
| Note | Windows XP Professional Setup floppy disks are not provided with Windows XP Professional. To create a set of bootable floppy disks, access the Microsoft Windows Update Web site and download an application that enables you to create a set of bootable floppy disks. For more information about creating a set of bootable floppy disks, see http://www.microsoft.com/ |
To install from the Setup floppy disks
Start the computer by using the Windows XP Professional Setup floppy disks.
When Setup is complete, you can add applications and run Sysprep.
For more information about how to install applications, see Customizing the Installations earlier in this chapter.
To install from Windows 98, Windows Me, Windows NT Workstation 4.0, or Windows 2000
Start the computer.
From the Start menu, click Run, and then type:
path to distribution folder winnt32 /unattend:Unattend.txt
In the preceding path, Unattend.txt is the answer file that contains answers to installation questions that you want to automate.
When Setup is complete, you can add applications and run Sysprep to prepare for creating an image.
For instructions about how to install applications, see Adding Applications earlier in this chapter.
To install by using CD Boot
Start the computer from the Windows XP Professional operating system CD. Setup begins automatically.
When Setup displays the message that it is examining the hardware configuration, insert the floppy disk containing the Winnt.sif file.
When the floppy drive light goes off, remove the floppy disk. Setup begins copying files to the hard disk.
For more information about how to install applications, see Adding Applications earlier in this chapter.
| Note | The /udf parameter cannot be used with the CD Boot method. |
During this step, you can add customized information (such as your company s name) and components (such as custom Help files and other documentation).
To add customized information and components
Create a file called Oeminfo.ini and copy it to the %systemroot%\System32 folder. The systemroot folder is usually C:\Windows.
You can use Remote Installation Services (RIS) to install Windows XP Professional throughout an organization from remote locations. Using RIS, you can direct client computers to a RIS server and install automated, customized versions of Windows XP Professional.
RIS uses PXE/DHCP-based remote boot technology to remotely install the operating system on the client computer. The RIS server contains the operating system that can be installed on the client computer using either a Risetup or a Riprep-based image. You can contact the servers by designating the network adapter as the first in the boot order of the client computer s BIOS, or by using a remote boot disk for pre-PC98 computers. When a network boot is requested, the client computer performs the following tasks:
The client computer requests an IP address from the DHCP server.
The client computer requests the IP address of a boot server using PXE (if the boot server is not the DHCP server).
The client computer contacts the boot server and downloads the Client Installation Wizard (CIW).
When a client computer starts, it sends out a DHCP Discover packet requesting an IP address and the location of a RIS server. In this packet, the client computer also sends out its Globally Unique Identifier (GUID). If the DHCP and RIS servers are on the same computer, all of this requested information is provided in the initial reply. If DHCP and RIS are on separate computers, the client computer sends out another broadcast DHCP Discover packet to contact a RIS server after it has successfully obtained an IP address from the DHCP server.
A RIS server running on Windows 2000 Server uses the Boot Information Negotiation Layer (BINL) service to contact the Active Directory service to determine if the client computer is a known client. Known clients are computers that are pre-staged to Active Directory.
The RIS server checks the Active Directory directory service to determine which RIS server can respond to this client request. The RIS server then provides the name of the server and the file that the client computer must download to start the installation process.
After the boot process begins, the Client Installation Wizard (CIW) screens are downloaded to the client computer and the installation begins.
When the CIW runs, the user at the client computer must log on to the domain. At this point, the user can select an image to install.
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.
In addition, consider the following before you design a RIS deployment:
RIS server. A RIS server is a computer running Windows 2000 Server, containing a hard disk with at least two partitions, that has been configured with the Remote Installation Services Setup Wizard (Risetup.exe) to install and run the following services:
Boot Information Negotiation Layer (BINL) service in Windows 2000 Server
Trivial File Transfer Protocol Daemon (TFTPD)
Single Instance Storage Groveler
The Single Instance Storage (SIS) filter driver is also installed.
Remote Installation client. The remote installation client computer can be a new personal computer that has a PXE-enabled network adapter, or an older personal computer (for example, computers built prior to the PC98/99 design specification) that can install Windows XP Professional using a remote boot disk to emulate PXE for the network adapter.
Active Directory. Active Directory is a requirement for RIS. RIS setup sends a query to make sure Active Directory is running. If Active Directory is not detected on the network, RIS Setup does not continue.
Networking considerations. Consider the following factors when you are designing your RIS deployment:
The RIS server does not have to be the domain controller for the domain.
You must have DNS and DHCP servers available to service the RIS client computers on the network.
The servers that are running DNS and DHCP do not have to be members of the same domain as the RIS server.
You do not have to use Microsoft DNS and DHCP services.
Table 2-17 describes the major RIS components and the users who work with each component.
| Component | Description | User |
|---|---|---|
| Remote Installation Services Setup (Risetup.exe) | Sets up the RIS server. This component is not available in Windows XP Professional. | System administrator |
| Remote Installation Services Administrator | Configures Group Policy settings relating to RIS. This component is not available in Windows XP Professional. | System administrator |
| Remote Installation Preparation tool (Riprep.exe) | Creates operating system images and installs them on the RIS server. You can also use Riprep.exe to create application images to install applications with the operating system. Client computers using PXE boot ROMs or a Remote Boot Floppy Generator (RBFG) floppy disk can then download the image. Because the client computer initiates the download, starting from the text-mode portion of Setup, Riprep allows for differences in hardware among client computers (such as the boot device). | Desktop administrator |
| Remote Boot Floppy Generator (Rbfg.exe) | Creates the Remote Installation Services bootable floppy disk that is required to install RIS-based operating systems on client computers that do not have a PXE-enabled boot ROM. | End user |
| Client Installation Wizard (Oschooser.exe) | Selects the RIS image that the user must install. This wizard is used on the client computer. | End user with rights to create computer objects in the domain |
| Warning | To deploy Windows XP Professional Riprep-based images from Windows 2000 RIS Servers, you must install the Remote Installation Preparation tool update. For more information about the Remote Installation Preparation tool 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 Riprep.exe, Setupcl.exe, Imirror.dll, and Windows XP Images. |
The following sections discuss planning for RIS from a client perspective and explain how to use the Remote Installation Preparation tool and the Remote Installation Services boot disk.
RIS enables the administrator to configure Windows XP Professional and any applications for a single group of users, and then to apply this configuration when installing the operating system on client computers. For users, the result is a simplified and timely installation and configuration of their computer and a more rapid return to productivity if a hardware failure occurs.
Administrators have two options when using RIS:
The Risetup option. Similar to setting up a workstation directly from the Windows XP operating system CD; however, the source files reside across a network on RIS servers. Risetup images are created by using Risetup.exe, which is a server-only application.
The Riprep imaging option. Enables a network administrator to clone a standard desktop configuration, including operating system configurations and desktop customizations. After installing and configuring Windows XP Professional, its services, and any standard applications on a workstation, the network administrator runs a wizard that prepares the installation image and replicates it to available RIS servers. Remote boot enabled client computers can then request a local installation of the image from the RIS servers over the network.
When a network service boot is requested, DHCP provides an IP address for the client computer, and the client computer can then download the Client Installation Wizard. At this point, the wizard prompts the user to log on, and, depending on the user s credentials or security group membership, displays a menu that offers appropriate customized unattended operating system installation options. The network administrator uses Group Policy settings to determine which installation options are available to a specific user, based on the policy that has been defined for that user at the client computer that initiated the network service boot request.
If you have a Windows 2000 Server operating system infrastructure with RIS installed and a client computer with the appropriate hardware, you can install Windows XP and any applications on that client computer remotely and automatically.
To ensure that a remote installation can proceed successfully, prepare the client computer for installation from a RIS server by completing the following tasks:
Verify the hardware compatibility of the client computer.
Set user rights.
Set permissions.
Specify the installation options.
Configure the network adapter.
Select and restrict client computer installation options.
Use Riprep to prepare the client image.
Deploy RIS.
Table 2-18 lists the tasks that the server administrator performs on a RIS server versus those that the desktop administrator performs on the client computer.
| Task | Description | User |
|---|---|---|
| Verify that the client hardware meets all requirements. | The client computer must meet the requirements for Windows XP installation and have a bootable network adapter or be enabled for remote startup. All computers that meet the PC98 0.6 and later design specification include a PXE remote boot ROM for RIS. For client computers that do not contain a PXE ROM, use the Remote Installation boot disk to create a floppy disk that initiates the RIS process. | Desktop administrator |
| Set required permissions on the RIS server. | If users are allowed to use RIS to install an operating system on client computers, those users need correct permissions for creating computer accounts within the domain, specifically the Organizational Unit container specified in the Advanced Settings on the RIS Server. Use Active Directory Users and Computers to set permissions on a container that allows users to use RIS to install an operating system on their own computers. | Server administrator |
| Specify installation options on the RIS server. | On the RIS server, you can use Group Policy settings to restrict the installation options available to users during remote installation. To restrict images, set access control permissions on the folders containing the installation images. | Server administrator |
| Configure the network adapter on the client computer. | You must configure the network adapter of the client computer as the primary startup device within the system BIOS. This allows the client computer to request a network service startup from the RIS server on the network. Many computers with built-in PXE compliant network adapters have three settings for the network adapter in the BIOS: off, on, and on with PXE. After the network adapter is set to on with PXE, on with PXE is typically available as an option in the boot order section of the BIOS. | Desktop administrator |
The Remote Installation Preparation tool (Riprep.exe) provides the ability to prepare a Windows XP Professional installation for disk imaging and to replicate the image to an available RIS server on the network. The image can include locally installed applications and specific configuration settings. The wizard feature supports replication of a single partition (drive C only) installation. This means that the operating system and the applications included with the standard installation must reside on drive C before the wizard is run.
| Warning | To deploy Windows XP Professional Riprep-based images from Windows 2000 RIS Servers, you must install the Remote Installation Preparation tool update. For more information about the Remote Installation Preparation tool 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 Riprep.exe, Setupcl.exe, Imirror.dll, and Windows XP Images. |
It is recommended that you use RIS to install the operating system on a client computer. After the operating system is installed, you can install any applications, including line-of-business applications. You can then configure the installation to comply with company policies. For example, you might define specific screen colors, set the background bitmap to a company logo, and configure intranet proxy server settings within Internet Explorer. After the workstation has been configured and tested, you can run Riprep from the RIS server.
The destination computer (the computer that installs the image) does not need to have hardware that is identical to the computer that was used to create the image. However, the Hardware Abstraction Layer (HAL) drivers must be the same. For example, both HALs must be ACPI-based or non-ACPI-based (see Table 2.16, earlier in this chapter). In many cases, workstation class computers do not require unique HAL drivers, as server-class computers do. During image installation, the wizard uses Plug and Play to detect differences between hardware on the source and destination computers.
Riprep-based images are usually larger than Risetup-based images because Riprep-based images are a complex copy of the client computer s hard disk that is stored on the server. Riprep-based images contain the operating system in addition to preinstalled programs and tools. To store a Riprep-based image on a RIS server, your configuration must meet the following requirements:
You must have at least one Risetup image stored on the same RIS server as the Riprep-based image.
The Risetup image must use the same language and it must be based on the same version of the operating system as the reference computer.
The template (.sif) file refers the client computer to the RIS server to detect and load files for the client computer s network adapter. The template (.sif) file also uses the Risetup image to provide drivers to start text-mode Setup. Setup then copies the image to the installing client computer s hard disk.
When you image a client computer by using Riprep.exe, the following requirements must be met:
At least one Risetup image must exist on the server so the user can access system files later. The Risetup image must use the same language and be based on the same version of the operating system as the reference computer.
Only one partition is supported.
Client computers must use the same HAL (for example, ACPI or non-ACPI).
Destination computers must have a local hard disk that is at least equal to the size of the partition on the imaged computer.
When you are creating the image, the client computer must not contain any encrypted files.
To run the Remote Installation Preparation tool (Riprep)
Install the standard operating system on the reference computer. It is recommended that you use RIS to perform this task.
Install applications locally on the client computer. Configure the client computer with specific corporate standard desktop settings. Make sure the client installation is correct. After the image is replicated to the RIS server, you cannot modify the configuration.
Copy the profile of the user used to configure the computer to the Default User profile. You should also delete any unwanted profiles at this point.
Connect to a RIS server from the computer on which you want to replicate this image and run Riprep.exe. The Remote Installation Preparation Wizard starts.
Enter the name of the RIS server where you want to replicate the contents of the client hard disk. By default, the RIS server from which the wizard is being run is filled in automatically.
Type the name of the folder on the RIS server where this image is to be copied.
When prompted, provide a description and Help text for this image. These are displayed to users during operating system image selection. Provide enough information to allow a user to distinguish between images.
After you complete the Remote Installation Preparation Wizard, review your selections on the summary screen that appears, and then click Next.
The image preparation and replication process begins. The system is prepared and files are copied to the RIS server. When the replication of the image is complete, you can use any client computer that meets the restrictions described in the next section, Riprep Rules and Restrictions, and is enabled for PXE/DHCP-based remote boot technology to select and install the image from the Client Installation Wizard. You can also use any client computers that use the Remote Installation Services startup disk.
In Windows XP Professional, Riprep can reset Windows Product Activation a maximum of three times for any images that derive from an initial image and start with the installation of the initial image. When a disk image that was prepared with Riprep is rebooted, the activation timer is reset and the installation of Windows XP Professional is enabled with the full Windows Product Activation grace period. After three resets, the activation timer is no longer reset.
For more information about Windows Product Activation, see Planning Deployments in this book.
Riprep.exe is more flexible than Sysprep.exe because it starts over the network in text-mode Setup. This allows for a greater variation of hardware platforms, such as differing mass storage disk controllers. The only item that must be the same on all client computers when you use Riprep.exe is the HAL.
By default, Riprep-based images do not perform Plug and Play enumeration. If you want Plug and Play enumeration to occur, you must use the -PnP command-line parameter when you create your image. For example, at the command prompt, type riprep -pnp. After you run this command, Plug and Play enumeration always occurs. If you want to turn off Plug and Play enumeration, you must recreate the image.
To take advantage of Riprep s added functionality, be sure to follow these guidelines:
The hard disk of the computer you want to image can have only one partition. If the hard disk of the client computer contains more than one partition, a message appears and only the system partition (containing the Windows folder) is copied. If your boot partition and system partition are different, the image is not useable.
A Risetup image must reside on the RIS server.
The hard disk on the destination computer must be at least the same size as, or larger than, the reference computer.
The destination computer must also have the same HAL as the reference computer.
You can use the Remote Installation Services (RIS) boot disk with client computers that do not contain a remote boot-enabled ROM. The startup disk simulates the PXE startup process for computers that lack a remote boot-enabled ROM. The boot disk is analogous to a boot-enabled ROM, which uses the floppy disk drive to install the operating system from the RIS server.
This disk enables you to use RIS to install programs on a laptop computer. Because Personal Computer Memory Card International Association (PCMCIA) network adapters do not currently support PXE, you cannot use a PCMCIA network adapter with RIS. However, you can place the laptop computer in a docking station that contains a PCI-compliant network adapter and use a boot disk that you created by running Rbfg.exe.
| Note | Currently, Remote Boot Floppy Generator (RBFG) floppy disks only support PCI-compliant adapters. RBFG floppy disks do not support PCMCIA and ISA network adapters. |
You cannot add additional network adapters to the RIS boot disk. Microsoft adds additional network adapters over time and makes the updates in the Rbfg.exe tool that is available through distribution channels, such as the Web, Windows Update, and future service packs.
When a client computer with a PXE-enabled network adapter connects to a RIS server, the Globally Unique Identifier (GUID) of the network adapter is among the items that are exchanged before a logon screen is displayed. The GUID is a unique 32-digit number that is stored with the computer account object that is created in Active Directory. Client computers with network adapters that are not PXE-enabled cannot supply this GUID. Instead, client computers that start from the RIS boot floppy with non-PXE-enabled network adapters send the network adapter s 12 character Media Access Control (MAC) address, prepended by 20 zeroes.
To generate a GUID in Windows 2000 Server, the Boot Information Negotiation Layer (BINL) service uses the 12 character MAC address and prepends 20 zeroes. This process creates a 32-digit number that is used as the GUID. The computer account object is associated with the network adapter, not with the computer. Even if you move the network adapter to a different computer, the GUID is still associated with the network adapter and not with the computer.
Because the computer account object is associated with the network adapter, if you move the network adapter to another computer, RIS assigns the attributes of the old computer to the new computer. Therefore, the administrator must delete the GUID from the computer account object for the old computer. If a user tries to install the new computer by using a different computer name, a message appears during the CIW that displays the names of the computers on the network that already have the same GUID. GUIDs and computer account objects must have a one-to-one relationship.
The RIS boot disk can be used with a variety of supported PCI-compliant network adapters. 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
One disk is used for all network adapters. The supported network adapters are listed in the Remote Boot Floppy Generator dialog box. You can display this dialog box by running Rbfg.exe. You can use this utility to create the boot disk. When RIS installation is complete, you can find Rbfg.exe on the RIS server partition, in the \RemoteInstall\admin\i386 folder.