Chapter 3 - Sysprep.inf File Parameters
This chapter lists the various keys and their parameters that can be included in the Sysprep.inf file. Many keys/parameters are interdependent; please note the interdependencies where specified.
A sample Sysprep.inf file may include:
[GuiUnattended] TimeZone = 20 [UserData] FullName = "Authorized User" ComputerName = W2B32054 OrgName = "Company Name, Inc."
[Unattended]
ExtendOemPartition
Value: 0 | 1 | <extra size in MB>
The ExtendOemPartition key is used to extend the partition on which you are installing Windows 2000. This key causes Setup to extend this destination partition into any available unpartitioned space that physically follows it on the disk.
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. |
Important:
| • | Only NTFS partitions can be extended. If the destination partition you plan to extend is FAT or FAT32, set FileSystem = ConvertNTFS to convert the partition but only during text-mode Setup. Setup will not extend FAT 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 master computer's hard disk. |
InstallFilesPath
Value: <path to installation files on computer>
Only valid for Sysprep.inf. Specifies the location of files that may be necessary for installation during Mini-Setup, such as the language files, so that the installation is not interrupted to prompt for user input. For example, for multilingual support, you can:
| • | Use Setup Manager |
| • | Use Sysprep.inf |
To use Sysprep.inf for multilingual support
1. | Create a subfolder named \i386 under \$OEM$\$1\Sysprep\ in the distribution folder. |
2. | Copy the following files from \i386 of the Windows 2000 product CD to the \i386 directory in the Sysprep folder: *.nl? kbd*.dl? |
3. | In Sysprep.inf, add: [Unattended] InstallFilesPath = C:\Sysprep\i386 |
Note:
| • | InstallFilesPath is only valid when used in the Sysprep.inf file in conjunction with Sysprep.exe to indicate the location of files needed during Mini-Setup, such as the localization files for installing additional code pages. |
| • | InstallFilesPath does not support environment variables (i.e., %systemdrive%). Instead, a valid path with an actual drive letter must be used. |
KeepPageFile
Value: 0 | 1
Default: 0
Optional
Only valid for Sysprep.inf. When Sysprep is run, the Mini-Setup wizard automatically regenerates the system's pagefile to accommodate differences in the amount of RAM between the master and destination computers. The pagefile is set to regenerate by default (KeepPageFile = 0). This ensures that the pagefile is large enough to accommodate the amount of RAM on the computer.
If the amount of RAM between the master computer and the destination computers is the same, the pagefile does not need to be regenerated. The pagefile is regenerated automatically only when you do not include this parameter and a value in Sysprep.inf.
Note:
| • | KeepPageFile is only valid when used in the Sysprep.inf file in conjunction with Sysprep.exe. |
| • | Known Issue: If you add KeepPageFile to your Sysprep.inf file, regardless of the value assigned, the pagefile is not regenerated. |
OemPnPDriversPath
Value: "<folder 1 on system drive>;<folder 2 on system drive>; ..."
Specifies the path to folders that contain PnP drivers that do not ship on the Windows 2000 CD. The folders must contain all the files necessary to install the particular devices—catalog files, .inf files, and drivers.
For example, if you have a folder called \Drivers with subfolders called \Audio and \Net, you would specify OemPnPDriversPath = "drivers\audio;drivers\net" in the answer file. Setup adds:
| • | %systemdrive% to each of the folder names |
| • | the path for each subfolder to the PnP device search path |
Note: When using this parameter, be sure that the folders are available during GUI-mode Setup or Mini-Setup; you can use the \$OEM$\$1 directory structure mechanism for this.
OemSkipEula
Value: Yes | No
Determines whether the user should be prompted to accept the Microsoft License Agreement (previously known as the End User License Agreement or EULA) included with Windows 2000. Writing this key and setting it to Yes implies that the person performing the installation has read and agreed to the contents of the License Agreement included with the product. It also implies that the end user on whose behalf Windows 2000 is being installed has agreed to the License Agreement.
UpdateHAL
Value: "hwid,%windir%\inf\hal.inf"
(where hwid is either MPS_MP or ACPIAPIC_MP)
Only valid for Sysprep.inf. Required if you are using compatible HALs that are based on an APIC uni-processor-system (UP) master computer image that is to be placed on a compatible multiprocessor-system (MP) destination computer.
Important: A Sysprep.inf file containing this parameter should not be used on destination UP computers, because UpdateHAL loads the MP HAL on the destination computer whether it is a UP or an MP computer. An MP kernel on a UP computer will noticeably reduce the computer's performance.
To add the modified Sysprep.inf file to the destination computer, you can:
| • | Save the .inf file to a floppy disk and insert the disk before Mini-Setup starts. |
| • | Update the image on the destination computer to include the .inf file. |
UpdateUPHAL
Value: "hwid,%systemdrive%\Sysprep\i386\Uniproc\Mp2up.inf"
(where hwid is either MPS_UP or ACPIAPIC_UP)
Only valid for Sysprep.inf. Required if you are using compatible HALs that are based on an APIC MP master computer image that is to be placed on compatible APIC UP or MP destination computers.
In this situation, Windows 2000 automatically identifies the processor type and loads the appropriate kernel.
[Oem_Ads]
All keys are supported (Logo and Background). For more information about these keys, see "[Oem_Ads]," in Chapter 1.
[GuiUnattended]
Only the following keys are supported by Sysprep.inf.
AdminPassword
Value: <password> | *
Sets up the Administrator account password. If the value is set to *, the administrator password is blank or NULL. (The maximum password length is 127 characters.)
Note: If a password is specified in the Administrator account , you cannot use AdminPassword in the Sysprep.inf file to change it—the administrator password remains the same. However, if the administrator password was initially blank (either manually or through an unattended installation), you can use the AdminPassword key to change it to a non-blank password.
However, if a non-blank password is used, end users cannot change or specify their own passwords in the Mini-Setup wizard. A new password may be entered in the appropriate dialog box, but the password is not changed.
In addition, security breaches may occur if you use a common, non-blank administrator password for all computers provided to end users. Prior to running Sysprep, you should use an automation process to set the administrator password to blank. End users can then specify their own passwords upon receipt of the computer.
AutoLogon
Value: Yes | No
Sets up the computer to automatically log on once with the Administrator account if set to Yes. The default behavior is No. This key is not valid on upgrades.
Note:
| • | If you specify a password by using AdminPassword, that password is used when you automatically log on. After the installation is complete, the password is deleted from the copy of the answer file left on the computer. |
| • | If AdminPassword = * (is blank) and AutoLogon = Yes, the computer logs on only one time. However, if AdminPassword = <password>, the computer logs on repeatedly and the non-blank password is saved in the registry. |
AutoLogonAccountCreation
Value: Yes | No
Default: Yes
Specifies whether a computer account should be created automatically for the user whose name is specified by FullName. For more information about this parameter, see "FullName," in Chapter 1. AutoLogonAccountCreation also allows the generated user account to automatically log on to the computer.
This parameter is only valid on computers that are configured with the Workgroup option. This parameter will not work for computers that are configured as members of a domain.
Note:
| • | The user's account is only configured to log on automatically by default when the option to join a workgroup is specified. This does not apply to computers that are members of a domain. |
| • | This parameter is not related to AutoLogon or AutoLogonCount; these parameters apply to the Administrator account only. |
AutoLogonCount
Value: <integer>
Specifies the number of times that the computer automatically logs on using the Administrator account and password specified. The value decrements after each logon, and the feature is disabled after the specified number of logon attempts.
Note: For the count to be decremented, you must reboot the computer.
This parameter is only useful when AutoLogon = Yes and AdminPassword = <password> are specified in the answer file.
Important:
| • | Make sure that the password for the master computer (the computer being used for disk duplicating) is blank. |
| • | If AdminPassword = * (is blank) and AutoLogon = Yes, the computer logs on only one time, regardless of the value given for AutoLogonCount. |
OEMDuplicatorString
Value: <user defined string>
Only valid for Sysprep.inf. This string contains a description of the duplication utility used, as well as any other information an OEM or administrator wants to store in the registry. The value can have a maximum of 255 characters and is stored in the HKLM\System\Setup\OemDuplicatorString registry key.
OEMSkipRegional
Values: 0 | 1
Allows unattended Setup to skip the Regional Options page in GUI-mode Setup and Mini-Setup.
Note: When specifying OemPreinstall = Yes and providing values for the [RegionalSettings] section, set OEMSkipRegional to 1 to ensure that Setup completes without prompting the user for regional information.
OEMSkipWelcome
Value: 1 | 0
Allows unattended Setup to skip displaying the Welcome page in GUI-mode Setup and Mini-Setup.
Note: If OemPreinstall = Yes, unattended Setup automatically stops at the Welcome page. To avoid this pause, set OEMSkipWelcome to a value of 1. However, OEMs must not ship computers with this setting enabled.
TimeZone
Value: <index>
Specifies the time zone where the computer is located. If the key is not present, the user is prompted to select a time zone. For a list of valid time zone indices, see "TimeZone," in Chapter 1.
[UserData]
All keys are supported. For more information about these keys, see "UserData]," in Chapter 1.
[LicenseFilePrintData]
All keys are supported. For more information about these keys, see "[LicenseFilePrintData]," in Chapter 1.
[GuiRunOnce]
All keys are supported. For more information about these keys, see "[GuiRunOnce]," in Chapter 1.
[Display]
All keys are supported. For more information about these keys, see "[Display]," in Chapter 1.
Note: Sysprep uses the video settings in the [Display] section of Sysprep.inf. If there are no display settings in the [Display] section of Sysprep.inf or if Sysprep.inf is not used, Sysprep uses the video settings in the registry. If the display settings were configured manually, set in the answer file, or used as the defaults, then Sysprep retains those settings.
[RegionalSettings]
All keys are supported, provided the files are available on the hard disk. For more information about [RegionalSettings], see "InstallFilesPath," earlier in this chapter and "[RegionalSettings]," in Chapter 1.
[TapiLocation]
All keys are supported. The values are only valid if a modem is present on the computer. For more information about these keys, see "[TapiLocation]," in Chapter 1.
Note: If you use the Sysprep.inf file with Sysprep, the modem information (Telephony Application Programming Interface (TAPI)) and the Networking screens are not displayed during Mini-Setup. The default networking components are used if the networking components are not configured and if they are not specified in Sysprep.inf.
[Networking]
No keys are required.
[Identification]
All keys are supported. For more information about these keys, see "[Identification]," in Chapter 1.
