Microsoft Windows XP Professional Resource Kit 2003
ISBN: N/A
EAN: N/A
EAN: N/A
Year: 2005
Pages: 338
Pages: 338
Windows XP Professional contains keywords and options that simplify creating unattended installations of new computers and silent configuration of existing computers. In addition, when installing and configuring the Windows XP Professional MUI Pack, special considerations must be taken into account.
For unattended installations of any language version of Windows XP Professional, you may need to specify additional options for running Winnt32.exe or Winnt.exe. Also, you must specify certain keywords and values in your Unattend.txt or Sysprep.inf answer file.
There are also special considerations for performing unattended installations of the Windows XP MUI Pack.
If your organization requires the installation of East Asian language and locale support, you must specify /copysource:lang or /rx:lang to copy the necessary language files. If you do not, and the [RegionalSettings] section of your answer file contains East Asian values, Setup will ignore everything in the [RegionalSettings] section.
| Note | If you install one of the East Asian localized language versions of Windows XP Professional, you do not need to specify the /copysource or /rx parameters, because East Asian language and locale support are installed by default. |
For Winnt32.exe, the appropriate syntax is:
winnt32.exe /unattend:"path to answer file" /copysource:lang /s:"path to install source"
To run Winnt.exe from a 16-bit, MS DOS network startup disk, the appropriate syntax is:
winnt.exe /u:"path to answer file" /rx:lang /s:"path to install source"
| Note | For the MUI Pack, you must specify certain options to run Winnt32.exe. You cannot run Winnt.exe. For more information about specifying options for the MUI Pack, see Special Considerations for Installing the Windows XP Professional MUI Pack later in this chapter. |
For unattended installations of Windows XP Professional, you can customize the following sections of the answer file to address specific language and other regional needs:
[RegionalSettings] Options
[GuiUnattended] Options
[TapiLocation] Options
| Warning | If you are creating an answer file for a localized language version of Windows XP Professional other than International English, create the answer file using that localized language version. Otherwise, change the language for non-Unicode programs to that of the localized language version, and save the answer file as ANSI text using the appropriate text encoding method for the language version that you are installing. For example, if you are creating an answer file to install the Russian localized language version on a desktop, use the Russian localized language version of Windows XP Professional to create the answer file. Otherwise, change the language for non-Unicode programs to Russian and use the Cyrillic OEM code page to author the answer file. |
The [RegionalSettings] section of the answer file specifies multilingual and international settings such as the language collections installed, the input languages installed, and the language for non-Unicode programs. All of the [RegionalSettings] values can be specified in either Unattend.txt or Sysprep.inf.
| Warning | Any [RegionalSettings] values specified in Sysprep.inf will override any values set in Unattend.txt. In addition, if you use Sysprep, all of the appropriate additional language files specified must already be installed on the computer. |
The following shows the correct syntax for the [RegionalSettings] section:
[RegionalSettings]
Language="locale ID"
LanguageGroup="language group ID","language group ID"
SystemLocale="locale ID"
UserLocale="locale ID"
InputLocale="locale ID:keyboard layout ID", "locale ID:keyboard layout ID",
UserLocale_DefaultUser="locale ID"
InputLocale_DefaultUser="locale ID:keyboard layout ID",
| Note | The Windows XP Professional MUI Pack requires additional considerations to ensure consistency among language settings for unattended installations. For more information about creating unattended installations of the MUI Pack, see Special Considerations for Installing the Windows XP Professional MUI Pack later in this chapter. |
Table 3-6 describes the [RegionalSettings] keys and identifies the corresponding settings in the Regional and Language Options Control Panel. For a complete listing of valid values for these keys, see the Locales and Language link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources
| Key | Usage | Regional and Language Options Control Panel Settings |
|---|---|---|
| Language | Specifies the language installed. If this key is specified, the SystemLocale, UserLocale, and Input Locale keys are ignored. |
|
| LanguageGroup | Specifies the language groups installed on the computer. Installing one language group also installs support for all of the other language groups in the same language collection. For example, if you install the Korean language group (8), Windows XP Professional installs support for all of the other language groups in the East Asian Language Collection (i.e., Japanese (7), Traditional Chinese (9), and Simplified Chinese (10)). For a list of the language groups installed under each language collection, see Built-In Language Support earlier in this chapter. | Same effect as:
|
| SystemLocale | Enables non-Unicode applications to run and display menus and dialog boxes in the localized language. | Language for Non-Unicode Programs. |
| UserLocale | Controls settings for sorting numbers, time, currency, and dates. | Standards and Formats. |
| InputLocale | Specifies input language and keyboard layout combinations. The first keyboard layout specified becomes the system default. Specified combinations must be supported by one of the languages defined by using either the LanguageGroup key or the default language for the language version of Windows XP Professional being installed. If an available language does not support the specified combination, the default combination is used. This key is ignored if the Language key is specified. | Input Language(s). |
| UserLocale_DefaultUser* | Controls the formats for numbers, time, currency, and dates for the default user. The specified setting must be supported by one of the languages specified using the LanguageGroup key, or the default language for the language version of Windows XP Professional being installed. | Same effect as:
|
| InputLocale_DefaultUser | Sets the input language and keyboard layout combinations for the default user. | Same effect as:
|
| *Denotes new keys added in Windows XP Professional | ||
| Note | If you specify a Language key, the value associated with it overrides all of the values specified in the InputLocale, SystemLocale, and UserLocale keys. Typically, using the Language key is the preferred method for specifying input languages because it prevents the occurrence of incompatible values in the InputLocale, SystemLocale, and UserLocale keys and installs locales appropriate for the specified language and locale combinations. |
You must specify the time zone of the computer by using the TimeZone key in the [GuiUnattended] section of your answer file. If the TimeZone key is not present in Unattend.txt, the user is prompted for a time zone during setup.
To preset time zones
In your answer file, add the following entry in the [GuiUnattended] section:
[GuiUnattended]TimeZone="index"
Index specifies the time zone of the computer. For a list of valid Time Zone indices, see Unattend.doc in Support\Tools\Deploy.cab on the Microsoft Windows XP Professional operating system CD.
| Note | If you specify OemPreinstall=Yes in the [Unattended] section of your answer file, you may want to add OemSkipRegional=1 to the [GuiUnattended] section to ensure that setup does not prompt the user for regional information during GUI-mode setup. |
You can specify dialing rules specific to your country/region by using the [TapiLocation] section of your answer file. These dialing rules specify the default country code and area code that a modem uses when dialing the phone. The [TapiLocation] keys described here are supported in both Unattend.txt and Sysprep.inf, and are valid only for computers with modems.
To preset telephone dialing rules
In your answer file, specify the appropriate values in the [TapiLocation] section:
[TapiLocation]
CountryCode="CountryCode"
AreaCode="AreaCode"
For a complete list of country codes to use for telephony, search on the Internet for ISO 3166, or see the International Telecommunication Union link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources
In the following example, an International English language version of Windows XP Professional is configured with additional support for the East Asian Language Collection installed. English (U.S.) is the default for both the language for non-Unicode programs (the SystemLocale) and the standards and formats (the UserLocale). Additional input languages and keyboard layouts are also installed for Japanese, Chinese (Taiwan), Chinese (People s Republic of China), Korean, and German. The telephone country code is set to U.S. and the area code is 425. The time zone is Redmond (U.S.) Pacific Standard Time.
[GuiUnattended]
TimeZone="020"
[RegionalSettings]
LanguageGroup="1","7","8","9","10"
SystemLocale="0409"
UserLocale="0409"
InputLocale="0409:00000409","0411:e0010411","0404:00000404","0804:00000804","0412:E0010412", "0407:00000407"
[TapiLocation]
CountryCode="US"
AreaCode="425"
Unattended setup of the Windows XP Professional MUI Pack is slightly different from that of the Windows XP Professional International English or localized language versions for the following reasons:
Because the Windows XP Professional MUI Pack requires the use of files from several CD ROMs, you should carefully review how this affects different deployment methods, including network installation, creating custom images on multiple CD ROMs using SysPrep, or a combination of CD ROM and network installation.
You must specify OemPreinstall=Yes and OemFilesPath="path to install source" in the [Unattended] section of your answer file to point to the location of the user interface language files. If you are installing the MUI Pack from the default location of \i386\$OEM$, you do not need to specify an OemFilesPath value.
The [Commands] section of Cmdlines.txt must be used to specify the execution of Muisetup.exe, the program that installs the user interface languages.
The MUI Pack requires special attention to ensure consistency within the [RegionalSettings] section of the answer file. You must specify the language groups and locales to install to support the appropriate user interface languages and applications.
The other settings that you specify in the [RegionalSettings] section depend on your workstation configurations:
For single user systems. Set locales to the same value as the default user interface language (specified when running Muisetup.exe). For example, if German is set as the default user interface language, specify one of the German locales in the answer file.
For shared workstations and in Terminal Services environments. Set the default user interface language and the language for non-Unicode programs to English, the administrative language of the MUI Pack. You can set the input language according to individual preferences or requirements. Or, if specified by using the Language key, restrict the input language to be the same as the language for non-Unicode programs.
| Warning | Install the appropriate language groups to ensure support for both the locales and the user interface languages specified. For example, if you install the Japanese (Japan) user interface language, you must also install the East Asian Language Collection to ensure Japanese language and locale support. |
The following [RegionalSettings] example installs support for the East Asian Language Collection. English (U.S.) is the default for both the language for non-Unicode programs (the SystemLocale) and standards and formats (the UserLocale). Additional input language and keyboard layouts are also installed for Japanese, Chinese (Taiwan), Chinese (People s Republic of China), Korean, and German.
[RegionalSettings]
LanguageGroup="1","7","8","9","10"
SystemLocale="0409"
UserLocale="0409"
InputLocale="0409:00000409","0411:e0010411","0404:00000404","0804:00000804","0412:E0010412", "0407:00000407"
In addition to the [RegionalSettings] options, you must specify the following settings in the [Unattended] section when installing the MUI Pack:
[Unattended]
OemPreinstall="Yes"
OemFilesPath="path to install source"
The OemFilesPath key points to the installation share that you create to contain the MUI user interface language files. If you are installing the MUI Pack from the default location of \i386\$OEM$, you do not need to specify an OemFilesPath value.
The [GuiUnattended] section of the answer file lets you disable the OEM Regional prompt that would otherwise be displayed during setup. Because you specified OemPreinstall=Yes in the [Unattended] section of your answer file, you may want to add OemSkipRegional=1 to the [GuiUnattended] section to ensure that setup does not prompt the user for regional information during GUI-mode setup.
[GuiUnattended]
OemSkipRegional="0 | 1"
Set the value to 1 to bypass the user prompt.
For unattended installations of the Windows XP Professional MUI Pack, you must copy all of the MUI files from CD2 into a temporary directory below the top-level directory on a network share or CD. In the following example, the computer name is \\MUICORE, the share name is $OEM$, and the temporary directory is MUIINST.
\\MUICORE
\$OEM$
\MUIINST
<...all MUI Pack files>
| Tip | For CD-based deployments, if the MUI Pack files are located on the CD (and not on a network share), the user may need to change CDs to complete the installation. This would require user intervention to change CDs, effectively breaking the unattended nature of the installation. |
For the Windows XP Professional MUI Pack, you must create a Cmdlines.txt file in the top level of your temporary directory. Cmdlines.txt must contain a [Commands] section that executes the Muisetup program using the appropriate parameters and values, using the following syntax:
[Commands]
".\temporary directory name\MUISETUP.exe [/i LangID LangID...] [/d LangID] /r /s"
You must use quotation marks around the command, and the path to Muisetup.exe must specify the temporary directory you created in the installation source. Table 3-7 describes the Muisetup parameters.
| Key | Description |
|---|---|
| /i | Specifies the user interface language(s) to be installed. Typically, languages are entered in four-digit hexadecimal LangID values. |
| /d | Specifies the default user interface language (applied to all new user accounts and used in places such as the Winlogon screen). |
| /r | Specifies that the restart message not be displayed. |
| /s | Specifies that the installation complete message not be displayed. |
The following Cmdlines.txt answer file is created in the temporary directory specified by the OemFilesPath key in yourUnattend.txt answer file (in the example specified earlier, the location is \\MUICORE\$OEM$). If Unattend.txt does not specify a custom location for OemFilesPath, Cmdlines.txt uses the default location of \i386\$OEM$.
The following specifies that Muisetup install the Japanese (Japan) and German (Germany) user interface languages, and sets Japanese (Japan) as the default user interface language used for the Winlogon screen and applied to all new user accounts.
[Commands]
".\MUIINST\MUISETUP.exe /i 0411 0407 /d 0411 /r /s"
You can use Windows Installer (.msi) packages to install additional MUI user interface language support. To do this, you must copy the .msi files for those user interface languages to the installation share, and then invoke Windows Installer in your Cmdlines.txt file to install the user interface languages on the computer. To install multiple user interface languages, repeat the msiexec invocation, specifying the appropriate .msi file for each additional user interface language that you want to install.
In the following example, the German (Germany) user interface language is silently installed from the German .msi package and the Japanese (Japan) user interface language is silently installed from the Japanese .msi package.
[Commands]
"msiexec.exe /i 0407.msi /q"
"msiexec.exe /i 0411.msi /q"
For more information about Windows Installer packages and parameters for using the msiexec.exe command, see the Software Development Kit (SDK) information in the MSDN Library link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources
When installing Windows Installer packages, you can choose whether to set a particular user interface language for the current user, the default user, or both. You can also specify whether a user language can be uninstalled by any user. Table 3-8 describes these parameters and how to use them.
| Parameter=value | Description |
|---|---|
| currentuser=1 | Sets the user interface language being installed as the user interface language for the current user. If this is not specified, the user interface language will be installed without changing the current user s user interface language. |
| defaultuser=1 | Sets the user interface language being installed as the user interface language for the default user account, which affects the logon screen and all new user accounts. If this is not specified, the user interface language will be installed without changing the default user account s user interface language. |
| allusers=1 | Specifies that the user interface language can be uninstalled by any user of that computer. |
In the following example, the German (Germany) and Japanese (Japan) user interface languages are silently installed, and the current user and default user accounts are set to Japanese. In addition, the German .msi package is to be installed per computer, allowing all users of the computer to remove it.
[Commands]
"msiexec.exe /i 0407.msi allusers=1 /q"
"msiexec.exe /i 0411.msi defaultuser=1 currentuser=1 /q"
| Caution | Use the allusers=1 parameter carefully, because it allows any user to remove a user interface language from a computer even though that user interface language might be required by another user of the same computer. If you install a given user interface language by using the currentuser=1 and/or defaultuser=1 parameters, do not specify the allusers=1 parameter for the same user interface language. |
You might want to change a computer s Regional and Language Options silently after the initial installation. For example, if your organization locks down the desktop to prevent a group of users from accessing the Control Panel, you can update that group s Regional and Language Options by using a Group Policy applied logon script.
In these situations, you can use Rundll32.exe to call the Regional and Language Options Control Panel with an answer file that specifies the appropriate settings. The syntax for calling Rundll32.exe from the command line is as follows:
Rundll32 shell32,Control_RunDLL intl.cpl,,/f:"c:\unattend.txt"
The answer file specified in c:\unattend.txt must contain a [RegionalSettings] section that specifies the appropriate regional and language settings.
The format of the answer file specified in a silent configuration is exactly the same as that used during setup. This means that all of the [RegionalSettings] options can be changed silently after the initial installation. The following is an example of a silent configuration that:
Adds the German - German input language for the current user.
Adds the German - Swiss German input language to the list of input languages for the default user.
Configures the language for non-Unicode programs to German.
[RegionalSettings]
InputLocale="0407:00000407"
InputLocale_DefaultUser="0407:00000807"
SystemLocale="0407"
If you specify multiple input languages for the InputLocale and InputLocale_DefaultUser keys, the first value specified will be set as the default for that particular user. In the following example, the InputLocale will set German - German as the default input language for the current user while also making German - Swiss German available as an input language.
[RegionalSettings]
InputLocale="0407:00000407", "0407:00000807"
The Windows XP Professional MUI Pack contains two new keywords that you can use after running setup to perform silent configurations. These keywords are intended for silent configuration after setup, when the specified user interface language has already been installed on the computer. Table 3.9 describes these additional [RegionalSettings] keys. For a complete listing of valid values for these keys, see the Locales and Language link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources
| Key | Usage |
|---|---|
| MUILanguage | Sets the user interface language for the current user. |
| MUILanguage_DefaultUser | Sets the user interface language for the default user account, including the logon screen and the user interface language applied to all new user accounts. |
The Windows XP Professional MUI Pack includes Windows Installer packages that allow users to install user interface languages on demand. For companies that support one global image, on-demand installation enables smaller and faster setups and images. If you do regional builds or CD-based deployments, include on a CD or network share the Windows Installer package for each specific user interface language your company needs to support.
To enable on-demand installations, you can publish a Windows Installer (.msi) package for each user interface language that your company supports on the appropriate Active Directory servers. The Windows Installer packages are then listed as additional user interface languages in the appropriate users Add or Remove Programs Control Panel. If you publish the .msi packages with the Maximum UI option, users can choose whether to install and set a specific user interface language for the current user, the default user, or both. Alternatively, to set the user account settings automatically, you can publish the .msi packages with the Basic UI option and then apply transforms to the packages.
For example, assume that your company supports 12 different languages worldwide. Your IT department publishes those 12 Windows Installer user interface language packages in the global Active Directory. A clerk in the Boston office, using Windows XP Professional MUI Pack with English (U.S.) as the default user interface language, can then install Italian and Japanese user interface language support when it is needed. All that the user needs to do is open the Add or Remove Programs Control Panel and select the Italian and Japanese user interface language support packages.
For more information about Windows Installer packages and parameters for using the msiexec.exe command, see the Software Development Kit (SDK) information in the MSDN Library link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources