Export (0) Print
Expand All

The <SystemData> Element

The <SystemData> Element

The <SystemData> element is required in every answer file. <SystemData> can contain the following elements for installing system data during Setup. For more information, click an element name.

ElementDescription
OSConfigurationThis element contains values for setting operating system configuration information.
RegionalSettingsThis element contains regional and language settings for the user interface.
SecurityThis element contains settings to add a machine to a domain and create new user accounts on the local machine.
ComponentsThis element specifies optional components to install.
NetworkingThis element contains information about advance network settings.

Example:

    <SystemData>
        <RegionalSettings>
            <!--This section contains elements for selecting regional and language settings for the user interface-->
            <UserInterface Value="12" />
        </RegionalSettings>
    </SystemData>

Back to top

The <OSConfiguration> Element

The <OSConfiguration> element contains the following element for installing operating configuration settings during Setup. For more information, click the element name.

ElementDescription
PageFileSpecifies the location and size for a pagefile.
NoPageFileSpecifies that no pagefile should be created.

Example:

<OSConfiguration>
    <!-- This section contains elements for setting OS configuration information.-->
    <PageFile Path="C:\pagefile.sys" InitialSize="256" MaximumSize="512" />
</OSConfiguration>

Back to top

The <PageFile> Element

Syntax:

<PageFile Path=“path” InitialSize=“InitSize_in_MBsMaximumSize="MaxSize_in_MBs" />

Path must be a local drive path. The wildcard character "*" (asterisk) sets the tag to the default value: %SYSTEMDRIVE%\pagefile.sys. It is recommended that you use the default path value (*). If you specify a drive other than the default drive, you must confirm that the pagefile was created, or your installation may have errors.

InitSize_in_MBs is the initial size of the pagefile. The wildcard character "*" (asterisk) sets the tag to the default value: 1.5 times the size of the machine's RAM.

MaxSize_in_MBs is the maximum size for the pagefile. The wildcard character "*" (asterisk) sets the tag to the default value: twice the size of the machine's RAM.

The InitialSize and MaximumSize arguments must both have integer values, both have wildcard values, or both be omitted.

Examples:

<PageFile Path="C:\pagefile.sys" InitialSize=“256” MaximumSize="512" />
<PageFile Path="*" InitialSize=“*” MaximumSize="*" />
<PageFile />

Back to top

The <NoPageFile> Element

Syntax:

<NoPageFile />

Normally, this element should not be used. When necessary, it should only be used for machines with a physical memory size of at least 512 MB. For these machines, Setup automatically creates a pagefile when certain optional components are installed through use of an unattended answer file. The <NoPageFile> element prevents Setup from creating a pagefile under any circumstances; this may result in virtual memory errors during installation.

For machines with 512 MB or more of memory, <NoPageFile> will not affect the installation of WEPOS. For machines with less than 512 MB of memory, <NoPageFile> may result in errors and could cause the operating system not to install properly.

Back to top

The <RegionalSettings> Element

The <RegionalSettings> element contains the following elements for installing regional settings during Setup. For more information, click the element name.

ElementDescription
UserInterfaceSpecifies the language used in menus and dialog boxes. This element is required.
StandardsAndFormatsSpecifies the standards and formats used for currency, date and time format, and digit separator.
DefaultInputLanguageSpecifies the default keyboard layout used to interpret user input.
NonUnicodeLanguageSpecifies the code page used for non-Unicode programs running on the computer.
GeographicalLocationSpecifies the location of the computer.
TimeZoneSpecifies the time zone in which the computer is located.

Example:

   <RegionalSettings>
      <!-- This section contains elements for selecting regional and language settings for the user interface-->
      <UserInterface Value="12" />
      <StandardsAndFormats Value="1036" />
      <DefaultInputLanguage Value="1036" />
      <NonUnicodeLanguage Value="1036" />
      <GeographicalLocation Value="84" />
      <TimeZone Value="030" />
   </RegionalSettings>

Back to top

The <UserInterface> Element

Syntax:

<UserInterface Value=“Language_ID/>

Language_ID is the value for the default interface language. The supported language groups and values are listed below. This element is required. Default values for <StandardsAndFormats>, <DefaultInputLanguage>, and <NonUnicodeLanguage> elements are based on this <UserInterface> value.

LanguageLanguage_ID Value
Chinese-Simplified4
English9
French12
German7
Italian16
Japanese17
Korean18
Spanish10

Example:

<UserInterface Value=“12” />

Back to top

The <StandardsAndFormats> Element

Syntax:

<StandardsAndFormats Value=“locale_ID/>

locale_ID is one of the Microsoft locale ID values for supported locales. If this element is omitted, the default locale ID value will be used. Default locale IDs are based on the value specified for <UserInterface>.

Example:

<StandardsAndFormats Value=“1036” />

Back to top

The <DefaultInputLanguage> Element

Syntax:

<DefaultlnputLanguage Value="locale_ID/>

locale_ID is one of the Microsoft locale ID values for supported locales. If this element is omitted, the default locale ID value will be used. Default locale IDs are based on the value specified for <UserInterface>.

Note: If you specify a locale ID that is not in the following group of locale IDs as the default input language, the Additional Input Device image will automatically be installed: Chinese locale IDs 2052 and 4100, any locale ID for English, French, German, Italian, Japanese, Korean, or Spanish.

Example:

<DefaultlnputLanguage Value=“1036” />

The <NonUnicodeLanguage> Element

Syntax:

<NonUnicodeLanguage Value=“locale_ID/>

locale_ID is one of the Microsoft locale ID values for supported locales. If this element is omitted, the default locale ID value will be used. Default locale IDs are based on the value specified for <UserInterface>.

Example:

<NonUnicodeLanguage Value=“1036” />

Back to top

The <GeographicalLocation> Element

Syntax:

<GeographicalLocation Value=“Default_Location/>

Default_Location specifies the location of the computer on which to install Microsoft Windows Embedded for Point of Service. Default_Location must be one of the Microsoft geographical location values. If this element is omitted, the default value will be used. Default geographical location values are based on the Microsoft locale ID value specified for <UserInterface>.

Example:

<GeographicalLocation Value=“84” />

Back to top

The <TimeZone> Element

Syntax:

<TimeZone Value=“Index/>

Index must be one of the Microsoft Time Zone Index numbers. If this element is omitted, the default value will be used. Default time zone values are based on the Microsoft locale ID value specified for <UserInterface>.

Example:

<TimeZone Value=“030” />

Back to top

The <Security> Element

The <Security> element specifies the network identification of a computer during Setup. <Security> can contain the following elements. For more information, click an element name.

ElementDescription
JoinDomainSpecifies the name of the domain the computer will join and supplies user name and password.
JoinWorkGroupSpecifies the name of the workgroup the computer will join.
AccountSpecifies additional account(s) to set up on the computer and supplies user name(s) and password(s).

Note that you can specify either the <JoinDomain> element or the <JoinWorkGroup> element, but you cannot specify both.

If these elements are not present or if not enough information is supplied for this element, Setup adds the computer to the default WorkGroup.

Sample <Security> Element

<Security>
   <!-- This section contains elements about joining a machine to a domain and creating new use accounts on the local machine-->
   <JoinDomain Username="Domain1\JANEDOE" Password="123!123abc" MachineDomain="Domain2" EncryptedPassword="No" />
   <JoinWorkgroup Value="MSHome" />
   <Account Username="user1" Password="eM34!Cf" Group="Power Users" EncryptedPassword="No" />
</Security>

Back to top

The <JoinDomain> Element

Syntax:

<JoinDomain Username=“Username” Password =“PasswordEncryptedPassword="Yes|No" MachineDomain=“Domain_Name” />

Username is any user who has the authority to add the computer to the domain. Username can be expressed in two forms: Domain\Username or Username@domain. If the domain does not require credentials, the Username attribute can be omitted.

Password is the password associated with the domain account in the Username field. If the domain does not require credentials, the Password attribute can be omitted.

EncryptedPassword=“Yes” means the password has been obfuscated; EncryptedPassword=“No” means it has not. Always set EncryptedPassword="No" unless you are using an obfuscated password.

Domain_Name is the name of the domain which the machine is to be joined to.

Example:

<JoinDomain Username=“OurGroup\JDOE” Password=”123!l23abc” EncryptedPassword=“No” MachineDomain=“Store1” />

Back to top

The <JoinWorkgroup> Element

Syntax:

<JoinWorkgroup Value=“WorkGroup_Name/>

WorkGroup_Name is the name of the workgroup the computer is to be joined to. WorkGroup_Name may not include any of the following characters: *=+ [ ] \ / | “ : ; , < > ?

Example:

<JoinWorkgroup Value=“BigStore12” />

Back to top

The <Account> Element

Syntax:

<Account Username=“Username” Password="PasswordEncryptedPassword="Yes|No" Group=“Groupname/>

Username can be either a local user name, or a domain user name, if the JoinDomain element was used. Setup adds a local user unless Username is in one of two forms: Domain\Username or Username@domain. (The \ or @ distinguishes a domain user from a local user.) Note that Setup will add only an existing domain user account.

Password is used only when setting the password for a local user account. A password cannot be set or reset for a domain account.

EncryptedPassword=“Yes” means the password (if used) has been obfuscated; EncryptedPassword=“No” means it has not. Always set EncryptedPassword="No" unless you are using an obfuscated password.

Groupname is the user group to which the account will be added. The group must already exist on the computer or be one of these groups: Power Users, Administrators, Guests, Users. Setup will not allow the same user to be joined to multiple groups.

Example:

<Account Username=“JaneDoe” Password =“wRKgGrl” EncryptedPassword="No" Group=“Power Users” />

Back to top

The <Components> Element

The <Components> element contains information about installing optional components in addition to Microsoft® Windows® Embedded for Point of Service. <Components> can contain the following elements. For more information, click an element name in the list below.

ElementDescription
WindowsMediaPlayer9Specifies whether to install the Windows Media Player 9.0 Component.
IISSpecifies whether to install the Windows Internet Information Services Component.
LocalManagementToolsSpecifies whether to install the Local Management Tools Component.
ChineseSimplifiedLangPackSpecifies whether to install the Chinese-Simplified Language Pack Component.
FrenchLangPackSpecifies whether to install the French Language Pack Component.
GermanLangPackSpecifies whether to install the German Language Pack Component.
ItalianLangPackSpecifies whether to install the Italian Language Pack Component.
JapaneseLangPackSpecifies whether to install the Japanese Language Pack Component.
KoreanLangPackSpecifies whether to install the Korean Language Pack Component.
SpanishLangPackSpecifies whether to install the Spanish Language Pack Component.
AdditionalCodePageSupportSpecifies whether to install the Additional CodePage Support Component. This includes all supported Windows XP codepages. If you need a codepage that isn’t in the language family you selected for your interface language, then you should install this component.
AdditionalFontsSpecifies whether to install the Additional Fonts Component, which includes all supported Windows XP fonts. If you need a font that isn’t in the language family you selected for your user interface language, then you should include this component.
AdditionalDriverSupportSpecifies whether to install the Additional Driver Support Component, which includes all drivers supported by Windows XP.
AdditionalInputDeviceSpecifies whether to install the Additional Input Device Component, which includes all supported Windows XP input devices. If you need a different input device (keyboard, IME, etc.) than is standard for your user interface language, then you should include this component.
ManagementClientSupportSpecifies whether to install the Management Client Support Component. This component is designed to allow advance management clients to work on WEPOS. If you are installing a management application on WEPOS, then you should include this component.

Sample <Components> Element

<Components>
   <!--The elements here specify optional components to be installed-->
   <AdditionalDriverSupport Value="Yes" />
   <WindowsMediaPlayer9 Value="Yes" />
   <IIS Value="Yes" />
   <LocalManagementTools Value="Yes" />
   <ManagementClientSupport Value="Yes" />
   <ChineseSimplifiedLangPack Value="Yes" />
   <FrenchLangPack Value="Yes" />
   <GermanLangPack Value="Yes" />
   <ItalianLangPack Value="Yes" />
   <JapaneseLangPack Value="Yes" />
   <KoreanLangPack Value="Yes" />
   <SpanishLangPack Value="Yes" />
   <AdditionalCodePageSupport Value="Yes" />
   <AdditionalFonts Value="Yes" />
   <AdditionalInputDevice Value="Yes" />
</Components>

Back to top

The <WindowsMediaPlayer9> Element

Syntax:

<WindowsMediaPlayer9 Value=“Yes|No” />

Value=”Yes” installs the Windows Media Player and DirectX 9.0c; Value=”No” does not. The wildcard character "*" (asterisk) sets the tag to the default value: No.

You may want to install these components if you run training videos or other multimedia programs on the computer.

Note: By default, Windows Media Player is set to automatically update the player whenever new updates come out. To disable this functionality, set the following registry key:

HKLM\Software\Policies\Microsoft\WindowsMediaPlayer
Value Name: DisableAutoUpdate
Type: DWORD
Value: 1

Example:

<WindowsMediaPlayer9 Value=“Yes” />

Back to top

The <IIS> Element

Syntax:

<IIS Value=“Yes|No” />

Value=”Yes” installs the Microsoft Internet Information Services (IIS); Value=”No” does not. The wildcard character "*" (asterisk) sets the tag to the default value: No.

Internet Information Services is a web server that provides reliable, manageable, and scalable Web application infrastructure for all versions of Windows Server 2003.

Example:

<IIS Value=“Yes” />

Back to top

The <LocalManagementTools> Element

Syntax:

<LocalManagementTools Value=“Yes|No” />

Value=”Yes” installs local management tools; Value=”No” does not. The wildcard character "*" (asterisk) sets the tag to the default value: No.

Example:

<LocalManagementTools Value=“Yes” />

Back to top

The <ChineseSimplifiedLangPack> Element

Syntax:

<ChineseSimplifiedLangPack Value=“Yes|No” />

Value=”Yes” installs the Chinese Simplified Language Package; Value=”No” does not. The wildcard character "*" (asterisk) sets the tag to the default value: No.

Example:

<ChineseSimplifiedLangPack Value=“Yes” />

Back to top

The <FrenchLangPack> Element

Syntax:

<FrenchLangPack Value=“Yes|No/>

Value=”Yes” installs the French Language Package; Value=”No” does not. The wildcard character "*" (asterisk) sets the tag to the default value: No.

Example:

<FrenchLangPack Value=“Yes” />

Back to top

The <GermanLangPack> Element

Syntax:

<GermanLangPack Value=“Yes|No/>

Value=”Yes” installs the German Language Package; Value=”No” does not. The wildcard character "*" (asterisk) sets the tag to the default value: No.

Example:

<GermanLangPack Value=“Yes” />

Back to top

The <ItalianLangPack> Element

Syntax:

<ItalianLangPack Value=“Yes|No/>

Value=”Yes” installs the Italian Language Package; Value=”No” does not. The wildcard character "*" (asterisk) sets the tag to the default value: No.

Example:

<ItalianLangPack Value=“Yes” />

Back to top

The <JapaneseLangPack> Element

Syntax:

<JapaneseLangPack Value=“Yes|No/>

Value=”Yes” installs the Japanese Language Package; Value=”No” does not. The wildcard character "*" (asterisk) sets the tag to the default value: No.

Example:

<JapaneseLangPack Value=“Yes” />

Back to top

The <KoreanLangPack> Element

Syntax:

<KoreanLangPack Value=“Yes|No/>

Value=”Yes” installs the Korean Language Package; Value=”No” does not. The wildcard character "*" (asterisk) sets the tag to the default value: No.

Example:

<KoreanLangPack Value=“Yes” />

Back to top

The <SpanishLangPack> Element

Syntax:

<SpanishLangPack Value=“Yes|No/>

Value=”Yes” installs the Spanish Language Package; Value=”No” does not. The wildcard character "*" (asterisk) sets the tag to the default value: No.

Example:

<SpanishLangPack Value=“Yes” />

Back to top

The <AdditionalCodePageSupport> Element

Syntax:

<AdditionalCodePageSupport Value="Yes" />

Value=”Yes” installs additional codepages; Value=”No” does not. The wildcard character "*" (asterisk) sets the tag to the default value: No.

The additional codepages include all supported Windows XP codepages. If you need a codepage that isn’t in the language family you selected for your interface language, then you should set this value to Yes.

Example:

<AdditionalCodePageSupport Value=“Yes” />

Back to top

The <AdditionalFonts> Element

Syntax:

<AdditionalFonts Value=“Yes|No/>

Value=”Yes” installs additional fonts; Value=”No” does not. The wildcard character "*" (asterisk) sets the tag to the default value: No.

Example:

<AdditionalFonts Value=“Yes” />

Back to top

The <AdditionalDriverSupport> Element

Syntax:

<AdditionalDriverSupport Value=“Yes|No/>

Value=”Yes” installs additional device driver files; Value=”No” does not. The wildcard character "*" (asterisk) sets the tag to the default value: No.

Example:

<AdditionalDriverSupport Value=“Yes” />

Back to top

The <AdditionalInputDevice> Element

Syntax:

<AdditionalInputDevice Value=“Yes|No/>

Value=”Yes” installs additional input device driver files; Value=”No” does not. The wildcard character "*" (asterisk) sets the tag to the default value: No.

Note: If you specify a locale ID that is not in the following group of locale IDs in <DefaultInputLanguage>, WEPOS will automatically install the Additional Input Device component: Chinese locale IDs 2052 and 4100, any locale ID for English, French, German, Italian, Japanese, Korean, or Spanish.

Example:

<AdditionalInputDevice Value=“Yes” />

Back to top

The <ManagementClientSupport> Element

Syntax:

<ManagementClientSupport Value=“Yes|No/>

Value=”Yes” installs tools to help you manage your clients; Value=”No” does not. The wildcard character "*" (asterisk) sets the tag to the default value: No.

The Management Client Support component is designed to allow advance management clients to work on WEPOS. If you are installing a management application on WEPOS, then you should include this component.

Example:

<ManagementClientSupport Value=“Yes” />

Back to top

The <Networking> Element

<Networking> can contain these elements. For more information, click an element name.

ElementDescription
IPAddressSpecifies IP Address settings.
DNSServerSpecifies DNS Server settings.
WINSServerSpecifies WINS Server settings.

Sample <Networking> Element

This sample demonstrates one use of the <Networking> element of Unattend.xml.

<Networking>
   <!--This Element contains information for pre-populating advance network settings-->
   <IPAddress DynamicIPAddress="No" StaticIPAddress="111.111.111.111" SubnetMask="222.222.222.222" DefaultGateway="333.333.333.333" />
   <DNSServer DNSAuto="No" PreferredDNSServer="444.444.444.444" AlternateDNSServer="555.555.555.555" />
   <WINSServer WINSAuto="No" PreferredWINSServer="444.444.444.444" AlternateWINSServer ="555.555.555.555" />
</Networking>

Back to top

The <IPAddress> Element

Syntax:

<IPAddress DynamicIPAddress=“Yes|No” StaticIPAddress=“IP_Address” SubnetMask="Subnet_mask” DefaultGateway=“Gateway/>

DynamicIPAddress="Yes" uses a dynamic IP address received from a DNS server. When DynamicIPAddress is set to Yes, Setup uses no other attributes in the <IPAddress> element.

DynamicIPAddress="No" causes Setup to use the static IP address from the other attributes in the <IPAddress> element.

IP_Address is the address that will be set as the static IP address for the network device. IP_Address must be a set of four to twelve numbers divided into four sets of one to three numbers by three periods.

Subnet_Mask is the IP address of the subnet mask. Subnet_Mask must be a set of four to twelve numbers divided into four sets of one to three numbers by three periods.

Gateway is the IP address of the gateway which will be set as the default gateway. Gateway must be a set of four to twelve numbers divided into four sets of one to three numbers by three periods.

Example:

<IPAddress DynamicIPAddress=“No” StaticIPAddress=“lll.lll.lll.lll” SubnetMask=“222.222.222.222” DefaultGateway=“333.333.333.333” />

Back to top

The <DNSServer> Element

Syntax:

<DNSServer DNSAuto=“Yes|No” PreferredDNSServer=“DNS_server_1” AlternateDNSServer=“DNS_server_2/>

DNSAuto="Yes" automatically detects the DNS server to use. When DNSAuto is set to Yes, Setup uses no other attributes in the <DNSServer> element.

DNSAuto="No" causes Setup to use the DNS server addresses from the other attributes in the <DNSServer> element.

DNS_server_1 is the IP address of the DNS Server that will be set as the default DNS server. DNS_server_1 must be a set of four to twelve numbers divided into four sets of one to three numbers by three periods.

DNS_server_2 is the IP address of the DNS Server that will be set as an alternate DNS server. DNS_server_2 must be a set of four to twelve numbers divided into four sets of one to three numbers by three periods.

Example:

<DNSServer DNSAuto=“No” PreferredDNSServer=“444.444.444.444” AlternateDNSServer=“555.555.555.555” />

Back to top

The <WINSServer> Element

Syntax:

<WINSServer WINSAuto=“Yes|No” PreferredWlNSServer="WINS_server_1” AlternateWlNSServer="WINS_server_2/>

WINSAuto="Yes" automatically detects the WINS server to use. When WINSAuto is set to Yes, Setup uses no other attributes in the <WINSServer> element.

WINSAuto="No" causes Setup to use the WINS server addresses from the other attributes in the <WINSServer> element.

WINS_server_1 is the IP address of the WINS Server that will be set as the default WINS server. WINS_server_1 must be a set of four to twelve numbers divided into four sets of one to three numbers by three periods.

WINS_server_2 is the IP address of the WINS Server that will be set as an alternate WINS server. WINS_server_2 must be a set of four to twelve numbers divided into four sets of one to three numbers by three periods.

Example:

<WINSServer WINSAuto=“No” PreferredWlNSServer=“444.444.444.444” AlternateWlNSServer=“555.555.555.555” />

Back to top

© 2005 Microsoft Corporation. All rights reserved.



Show:
© 2014 Microsoft