<SystemData> and Sub-elements (Required)
2/16/2009
The <SystemData> element is required in every answer file. Each sub-element of <SystemData> and its function is listed in this topic.
Element | Description |
---|---|
OSConfiguration |
Specifies values for operating-system configuration information |
RegionalSettings |
Specifies regional and language settings for the user interface |
Security |
Specifies settings to add a computer to a domain and create new user accounts on the local computer |
Components |
Specifies optional components to install |
Networking |
Specifies information about advanced network settings |
Example:
<SystemData>
<RegionalSettings>
<!--This section contains elements for selecting regional and language settings for the user interface.-->
<UserInterface Value="12" />
</RegionalSettings>
</SystemData>
The <OSConfiguration> Element
The <OSConfiguration> element contains the following elements for installing operating-system configuration settings during Windows Embedded POSReady 2009 installation.
Element | Description |
---|---|
PageFile |
Specifies the location and size for a pagefile |
NoPageFile |
Specifies 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>
The <PageFile> Element
Syntax:
<PageFile Path="path" InitialSize="InitSize_in_MBs" MaximumSize="MaxSize_in_MBs" />
path must be a local drive path. The wildcard asterisk (*) character sets the tag to the default value: %SYSTEMDRIVE%\pagefile.sys. We recommend 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 can have errors.
InitSize_in_MBs is the initial size of the pagefile. The asterisk (*) sets the tag to the default value: 1.5 times the size of the computer's RAM. This value cannot be smaller than 2MB.
MaxSize_in_MBs is the maximum size for the pagefile. The asterisk (*) sets the tag to the default value: two times the size of the computer'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 />
The <NoPageFile> Element
Syntax:
<NoPageFile />
Usually, this element should not be used. When it is necessary, it should only be used for computers that have a physical memory size of at least 512 MB. For these computers, the POSReady installer automatically creates a pagefile when certain optional components are installed through use of an unattended answer file. The <NoPageFile> element prevents the installer from creating a pagefile under any circumstances. This might result in virtual-memory errors during installation.
For computers that have 512 MB or more of memory, <NoPageFile> will not affect the installation of POSReady. For computers that have less than 512 MB of memory, <NoPageFile> might result in errors and could cause the operating system not to install correctly.
The <RegionalSettings> Element
The <RegionalSettings> element contains the following elements for installing regional settings during POSReady installation:
Element | Description |
---|---|
StandardsAndFormats |
Specifies the standards and formats that are used for currency, date and time format, and digit separator |
GeographicalLocation |
Specifies the location of the computer. |
TimeZone |
Specifies 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.-->
<StandardsAndFormats Value="1036" />
<GeographicalLocation Value="84" />
<TimeZone Value="030" />
</RegionalSettings>
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" />
The <DefaultInputLanguage> Element
Syntax:
<DefaultInputLanguage 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.
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:
<DefaultInputLanguage 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.
Example:
<NonUnicodeLanguage Value="1036" />
The <GeographicalLocation> Element
Syntax:
<GeographicalLocation Value="Default_Location" />
Default_Location specifies the location of the computer on which to install POSReady. Default_Location must be one of the Microsoft geographical location values. If this element is omitted, the default value will be used.
Example:
<GeographicalLocation Value="84" />
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.
Example:
<TimeZone Value="030" />
The <Security> Element
The <Security> element specifies the network identification of a computer during Setup. <Security> can contain the following elements.
Element | Description |
---|---|
JoinDomain |
Specifies the name of the domain the computer will join and supplies user name and password |
JoinWorkgroup |
Specifies the name of the workgroup the computer will join |
Account |
Specifies additional account(s) to set up on the computer and supplies user name(s) and password(s) |
Note
You can specify either the <JoinDomain> element or the <JoinWorkgroup> element. However, you cannot specify both.
If these elements are not present or if enough information is not supplied for this element, Setup adds the computer to the default Workgroup.
Sample <Security> Element
<Security>
<!--This section contains elements about joining a computer to a domain and creating new use accounts on the local computer.-->
<JoinDomain Username="Domain1\JANEDOE" Password="123!123abc" MachineDomain="Domain2" EncryptedPassword="No" />
<JoinWorkgroup Value="BigStore12" />
<Account Username="user1" Password="eM34!Cf" Group="Power Users" EncryptedPassword="No" />
</Security>
The <JoinDomain> Element
Syntax:
<JoinDomain Username="Username" Password ="Password" EncryptedPassword="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. Password length must not exceed 95 characters. If the domain does not require credentials, the Password attribute can be omitted.
EncryptedPassword="Yes" means the password is encrypted; EncryptedPassword="No" means that it is not. Always set EncryptedPassword="No" unless you are using an encrypted password.
Domain_Name is the name of the domain that the computer is to be joined to.
Example:
<JoinDomain Username="OurGroup\JDOE" Password="123!l23abc" EncryptedPassword="No" MachineDomain="Store1" />
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 cannot include any of the following characters: * = + [ ] \ / | " : ; , < > ?
Example:
<JoinWorkgroup Value="BigStore12" />
The <Account> Element
You cannot specify more than 64 <Account> elements.
Syntax:
<Account Username="Username" Password="Password" EncryptedPassword="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.) Setup will add only an existing domain user account.
Password is used only when you are setting the password for a local user account. Password length must not exceed 95 characters. A password cannot be set or reset for a domain account.
EncryptedPassword="Yes" means the password (if it is used) is encrypted; EncryptedPassword="No" means that it is not. Always set EncryptedPassword="No" unless you are using an encrypted 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 let the same user to be joined to multiple groups.
Example:
<Account Username="JaneDoe" Password ="wRKgGrl" EncryptedPassword="No" Group="Power Users" />
The <Components> Element
The <Components> element specifies whether to install optional components for POSReady. You cannot specify more than 128 <Components> sub-elements, and each <Component Name> cannot exceed 128 characters. <Components> can contain the following elements:
Element | Description |
---|---|
Accessibility Tools |
Specifies whether to install the Accessibility Tools component for impaired users |
Additional Drivers |
Specifies whether to install the Additional Drivers component for additional peripheral device support |
Calculator |
Specifies whether to install the Calculator component |
Character Map |
Specifies whether to install the Character Map component for cutting and pasting characters into your documents |
Clipboard Viewer |
Specifies whether to install the Clipboard Viewer component for viewing the contents of the Clipboard |
Command Line Utilities |
Specifies whether to install the Command Line Utilities component for performing system tasks from the command prompt |
Disk Management |
Specifies whether to install the Disk Management component for managing system disks |
Fax Services |
Specifies whether to install the Fax Services component for sending and receiving faxes |
HyperTerminal |
Specifies whether to install the HyperTerminal component for connecting to other computers and online services |
Indexing Service |
Specifies whether to install the Indexing Service component for searching the contents of documents |
Internet Information Services (IIS) |
Specifies whether to install the Internet Information Services (IIS) component |
Management and Monitoring Tools |
Specifies whether to install the Management and Monitoring Tools component for managing networking performance |
Message Queuing |
Specifies whether to install the Message Queuing component for improved message delivery, routing, and security support |
.NET Framework 2.0 |
Specifies whether to install the .NET Framework 2.0 component |
Networking Services |
Specifies whether to install the Networking Services component for improved network support |
Notepad |
Specifies whether to install the Notepad component for basic text editing |
Paint |
Specifies whether to install the Paint component for basic image editing |
POS for .NET 1.12 |
Specifies whether to install the POS for .NET 1.12 component for improved POS device support |
Terminal Services |
Specifies whether to install the Terminal Services component for remote computer access support |
Touch Screen Keyboard |
Specifies whether to install the Touch Screen Keyboard component for touch screen input support. This component requires the .NET Framework 2.0 or later versions to be installed |
Update Root Certificates |
Specifies whether to install the Update Root Certificates component for improved security |
Windows Backup Utility |
Specifies whether to install the Windows Backup Utility component for improved backup support |
Windows Media Format 11 |
Specifies whether to install the Windows Media Format 11 component for additional codec support |
Windows Media Player 11 |
Specifies whether to install the Windows Media Player 11 component for improved digital media support |
WordPad |
Specifies whether to install the WordPad component for editing formatted text files |
Sample <Components> Element
<Components>
<!-- This element installs the following optional components. -->
<Component Name=".Net Framework 2.0" Install="Yes" />
<Component Name="Additional Drivers" Install="Yes" />
<Component Name="Update Root Certificates" Install="Yes" />
<Component Name="Internet Information Services (IIS)" Install="Yes" />
<Component Name="Notepad" Install="Yes" />
<Component Name="Windows Media Format 11" Install="Yes" />
<Component Name="Windows Media Player 11" Install="Yes" />
<Component Name="Command Line Utilities" Install="Yes" />
<Component Name="HyperTerminal" Install="Yes" />
<Component Name="Character Map" Install="Yes" />
<Component Name="Accessibility Tools" Install="Yes" />
<Component Name="Management and Monitoring Tools" Install="Yes" />
<Component Name="Fax Services" Install="Yes" />
<Component Name="Clipboard Viewer" Install="Yes" />
<Component Name="Windows Backup Utility" Install="Yes" />
<Component Name="WordPad" Install="Yes" />
<Component Name="POS for .Net 1.12" Install="Yes" />
<Component Name="Indexing Service" Install="Yes" />
<Component Name="Message Queuing" Install="Yes" />
<Component Name="Disk Management" Install="Yes" />
<Component Name="Calculator" Install="Yes" />
<Component Name="Paint" Install="Yes" />
<Component Name="Touch Screen Keyboard" Install="Yes" />
<Component Name="Terminal Services" Install="Yes" />
<Component Name="Networking Services" Install="Yes" />
</Components>
The <Networking> Element
<Networking> can contain the following elements.
Element | Description |
---|---|
IPAddress |
Specifies IP Address settings |
DNSServer |
Specifies DNS server settings |
WINSServer |
Specifies WINS server settings |
Sample <Networking> Element
The following sample code demonstrates one use of the <Networking> element of Unattended.xml:
<Networking>
<!--This Element contains information for pre-populating advance network settings.-->
<IPAddress DynamicIPAddress="No" StaticIPAddress="111.111.111.111" SubnetMask="211.211.211.211" DefaultGateway="123.145.167.189" />
<DNSServer DNSAuto="No" PreferredDNSServer="200.201.202.203" AlternateDNSServer="100.101.102.103" />
<WINSServer WINSAuto="No" PreferredWINSServer="160.161.162.163" AlternateWINSServer ="150.151.152.153" />
</Networking>
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 separated 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 separated 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 separated by three periods.
Example:
<IPAddress DynamicIPAddress="No" StaticIPAddress="lll.lll.lll.lll" SubnetMask="222.222.222.222" DefaultGateway="200.201.202.203" />
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 separated by three periods.
DNS_server_2 is the IP address of the DNS server that will be set as an alternative DNS server. DNS_server_2 must be a set of four to twelve numbers divided into four sets of one to three numbers separated by three periods.
Example:
<DNSServer DNSAuto="No" PreferredDNSServer="200.201.202.203" AlternateDNSServer="100.101.102.103" />
The <WINSServer> Element
Syntax:
<WINSServer WINSAuto="Yes|No" PreferredWINSServer="WINS_server_1" AlternateWINSServer="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 separated by three periods.
WINS_server_2 is the IP address of the WINS server that will be set as an alternative WINS server. WINS_server_2 must be a set of four to twelve numbers divided into four sets of one to three numbers separated by three periods.
Example:
<WINSServer WINSAuto="No" PreferredWINSServer="160.161.162.163" AlternateWINSServer="150.151.152.153" />