Order (Standard 8 Module Reference)

Article
09/29/2016

7/8/2014

Review the applicable Embedded Core modules and any examples for the Order setting in Windows Embedded 8 Standard (Standard 8).

This setting contains an incremental integer that specifies the order in which partitions are created or modified, commands are run, or sensors are modified.

You can also specify a unique ID for a group of regions.

Modules

The following table shows the modules that you can apply this setting to. In Image Configuration Editor (ICE), you can follow the corresponding path to set this setting for a module.

Module	Path	Setting Description
Proximity, Sensor and Location	Features/Natural User Interface/Proximity, Sensor and Location/SensorPermissions/Sensor/Order	Specifies the order in which sensors are modified. This setting is required, even if you modify only one sensor. Note: If sensor categories and types overlap, the setting that is applied last will override previous values.
Deployment	Products/Embedded Core/Deployment/RunAsynchronous/RunAsynchronousCommand/Order	Specifies the order in which to run the asynchronous command that is specified by Path. All RunAsynchronous commands run in the system context.
Deployment	Products/Embedded Core/Deployment/RunSynchronous/RunSynchronousCommand/Order	Specifies the order in which to run the synchronous command that is specified by Path. All RunSynchronous commands run in the system context.
Setup	Products/Embedded Core/Setup/DiskConfiguration/Disk/CreatePartitions/CreatePartition/Order	Specifies the order in which partitions are created, numbered beginning from 1. This setting is required even if you create only one partition.
Setup	Products/Embedded Core/Setup/DiskConfiguration/Disk/ModifyPartitions/ModifyPartition/Order	Specifies the order in which partitions are modified, numbered beginning from 1. This setting is required even if you modify only one partition. We recommend that you use the same values for Order and PartitionID to make it easier to keep track of your partitions. To do this, add a ModifyPartition element for each partition, including those that will not be modified.
Setup	Products/Embedded Core/Setup/ImageInstall/DataImage/Order	This setting contains an integer that specifies the order in which the data image is installed, numbered beginning from 1.
Setup	Products/Embedded Core/Setup/RunAsynchronous/RunAsynchronousCommand/Order	Specifies the order in which to run the asynchronous command that is specified by Path. All RunAsynchronous commands run in the system context.
Setup	Products/Embedded Core/Setup/RunSynchronous/RunSynchronousCommand/Order	Specifies the order in which to run the synchronous command that is specified by Path. All RunSynchronous commands run in the system context.
Shell-Setup	Products/Embedded Core/Shell-Setup/FirstLogonCommands/SynchronousCommand/Order	Contains an integer from 1 to 500 that specifies the order in which the command is run.
Shell-Setup	Products/Embedded Core/Shell-Setup/LogonCommands/AsynchronousCommand/Order	Specifies the order in which to start the asynchronous command. The device does not wait for one command to finish before it starts the next command.
Shell-Setup	Products/Embedded Core/Shell-Setup/StartTiles/RegionalOverrides/RegionalOverride/Order	A two-digit integer from 01 to 19 that specifies a unique ID for a group of regions. For each region group, the system displays a customized set of apps on the Start and Lock screens for a region. The user can select a region during Windows Welcome, or you can specify a region by using UserLocale settings in International-Core. If a region is selected, the following occurs: If the selected region matches a region in RegionalOverrides, then the system displays the apps from that override. If the selected region does not match any of these regions, then Standard 8 displays the apps from StartTiles for WideTiles, SquareTiles, and LockScreen.

XML Example

The following XML examples show how to set Order.

DataImage

The following XML example shows how to install a data image and set the order.

<ImageInstall>
    <DataImage wcm:action="add">
        <InstallTo>
            <DiskID>0</DiskID>
            <PartitionID>2</PartitionID>
        </InstallTo>
        <InstallFrom>
            <Credentials>
                <Domain>FabrikamDomain</Domain>
                <Password>MyPassword</Password>
                <Username>MyUsername</Username>
            </Credentials>
            <Path>\\networkshare\share\data.wim</Path>
            <MetaData wcm:action="add">
                <Key>/IMAGE/NAME</Key>
                <Value>FabrikamData</Value>
            </MetaData>
        </InstallFrom>
        <Order>1</Order>
    </DataImage>
</ImageInstall>

For an XML example that shows how to set the ImageInstall setting to install both an OS image and a data image, see Setting the ImageInstall Setting XML Example.

Create Disk Partitions

The following XML example for the DiskConfiguration setting shows how to create two partitions on a hard drive on a BIOS/MBR-based system.

<DiskConfiguration>
    <Disk wcm:action="add">
        <DiskID>0</DiskID> 
        <WillWipeDisk>true</WillWipeDisk> 
        <CreatePartitions>

            <!-- System partition -->
            <CreatePartition wcm:action="add">
                <Order>1</Order> 
                <Type>Primary</Type> 
                <Size>300</Size> 
            </CreatePartition>

            <!-- Windows Embedded partition -->
            <CreatePartition wcm:action="add">
                <Order>2</Order> 
                <Type>Primary</Type> 
                <Extend>true</Extend> 
            </CreatePartition>
        </CreatePartitions>
    </Disk>
    <WillShowUI>OnError</WillShowUI> 
</DiskConfiguration>

For full XML examples, see Disk Configuration XML Example and System with Two Hard Drives XML Example.

For additional full XML examples and recommended partition configurations, see How to Configure UEFI/GPT-Based Hard Disk Partitions, or How to Configure BIOS/MBR-Based Hard Disk Partitions.

Modify Disk Partitions

The following XML example for the DiskConfiguration setting shows partition modifications for a BIOS-based computer with six partitions: three primary partitions, an extended partition, and two logical partitions. There are five modifications configured, ordered 1, 2, 3, 4, and 5. The extended partition does not require modification.

<DiskConfiguration>

  <Disk wcm:action="add">
    <DiskID>0</DiskID> 
    <WillWipeDisk>true</WillWipeDisk> 
    <CreatePartitions>

      <!-- Recovery partition -->
      <CreatePartition wcm:action="add">
        <Order>1</Order> 
        <Type>Primary</Type> 
        <Size>3000</Size> 
      </CreatePartition>

      <!-- Utility2 partition -->
      <CreatePartition wcm:action="add">
        <Order>2</Order> 
        <Type>Primary</Type> 
        <Size>250</Size> 
      </CreatePartition>

      <!-- System partition -->
      <CreatePartition wcm:action="add">
        <Order>3</Order> 
        <Type>Primary</Type> 
        <Size>100</Size> 
      </CreatePartition>

      <!-- Extended partition -->
      <CreatePartition wcm:action="add">
        <Order>4</Order> 
        <Type>Extended</Type> 
        <Extend>true</Extend> 
      </CreatePartition>

      <!-- Windows Embedded partition -->
      <CreatePartition wcm:action="add">
        <Order>5</Order> 
        <Type>Logical</Type> 
        <Size>15000</Size> 
      </CreatePartition>

      <!-- Logical2 partition -->
      <CreatePartition wcm:action="add">
        <Order>6</Order> 
        <Type>Logical</Type> 
        <Size>100</Size> 
          <!-- Note: To create a logical partition that fills 

                     the rest of the extended partition, create the 
                     data partition with an initial size of 100 MB.
                     This will be changed in the ModifyPartition section. -->
      </CreatePartition>

    </CreatePartitions>
    <ModifyPartitions>

      <!-- Recovery partition -->
      <ModifyPartition wcm:action="add">
        <Order>1</Order> 
        <PartitionID>1</PartitionID> 
        <Label>Recovery</Label> 
        <Format>NTFS</Format> 
        <TypeID>0x27</TypeID>
      </ModifyPartition>

      <!-- Utility2 partition -->
      <ModifyPartition wcm:action="add">
        <Order>2</Order> 
        <PartitionID>2</PartitionID> 
        <Label>Utility2</Label> 
        <Letter>U</Letter> 
        <Format>NTFS</Format> 
      </ModifyPartition>

      <!-- System partition -->
      <ModifyPartition wcm:action="add">
        <Order>3</Order> 
        <PartitionID>3</PartitionID> 
        <Label>System</Label>
        <Format>NTFS</Format> 
        <Active>true</Active> 
      </ModifyPartition>

      <!-- Extended partition:
           This partition does not need receive a partition number, 
           nor does it need to be modified. -->

      <!-- Windows Embedded partition -->
      <ModifyPartition wcm:action="add">
        <Order>4</Order>
        <PartitionID>4</PartitionID> 
        <Label> Windows Embedded </Label> 
        <Letter>C</Letter> 
        <Format>NTFS</Format> 
      </ModifyPartition>

      <!-- Logical2 partition -->
      <ModifyPartition wcm:action="add">
        <Order>5</Order> 
        <PartitionID>5</PartitionID> 
        <Label>Logical2</Label> 
        <Letter>L</Letter> 
        <Format>NTFS</Format> 
        <Extend>true</Extend>
          <!-- Note: When modifying a logical partition, setting
                     "ModifyPartition|Extend=true" instructs the partition to  
                     fill the remainder of the extended partition.
                     This overrides the "CreatePartition|Size" value. -->
      </ModifyPartition>

    </ModifyPartitions>
  </Disk>
  <WillShowUI>OnError</WillShowUI> 
</DiskConfiguration>


<ImageInstall>
  <OSImage>
    <InstallTo>
      <DiskID>0</DiskID> 
      <PartitionID>4</PartitionID> 
    </InstallTo>
  </OSImage>
</ImageInstall>

For other examples, see System with Two Hard Drives XML Example and Extending a Partition XML Example.

FirstLogonCommands

The following XML example shows how to specify a command to run after first logon.

<FirstLogonCommands>
    <SynchronousCommand wcm:action="add">
        <CommandLine>c:\synccommands\command1.exe</CommandLine>
        <Description>Description_of_command1</Description
        <Order>1</Order>
    </SynchronousCommand>
</FirstLogonCommands>

For more examples of first logon commands, see FirstLogonCommands XML Example.

LogonCommands

The following XML example shows examples of how to set two logon commands. The RequiresUserInput setting has no effect for either of the commands.

<LogonCommands>
     <AsynchronousCommand wcm:action="add">
       <CommandLine>c:asynccommands\command1.exe</CommandLine>
       <Description>Description_of_command1</Description>
       <Order>1</Order>
       <RequiresUserInput>true</RequiresUserInput>
     </AsynchronousCommand>
     <AsynchronousCommand wcm:action="add">
       <CommandLine>c:asynccommands\command2.exe</CommandLine>
       <Description>Description_of_command2</Description>
       <Order>2</Order>
       <RequiresUserInput>false</RequiresUserInput>
     </AsynchronousCommand>
</LogonCommands>

Regional Overrides

The following XML example shows how to configure two set of apps, one applies to only in France and Italy, another applies only to Germany.

<RegionalOverrides>
    <RegionalOverride>
        <Order>1</Order>
        <Regions>
            <Region>
              <RegionID>IT</RegionID>
            </Region>
            <Region>
                <RegionID>FR</RegionID>
            </Region>
        </Regions>
      <!-- Square tiles, Wide Tiles, and LockScreen apps are specified here -->
    </RegionalOverride>
    <RegionalOverride>
        <Order>2</Order>
        <Regions>
            <Region>
                <RegionID>DE</RegionID>
            </Region>
        </Regions>
    <!-- Square tiles, Wide Tiles, and LockScreen apps are specified here -->
    </RegionalOverride>
<Regions>

RunAsynchronous

The following XML example shows how to configure commands to run asynchronously.

<RunAsynchronous>
      <RunAsynchronousCommand>
         <Order>1</Order>
         <Path>\\MyNetworkShare\MyApplication.exe</Path>
         <Description>DescriptionOfMyApplication</Description>
         <Credentials>
            <Domain>FabrikamDomain</Domain>
            <UserName>MyUserName</UserName>
            <Password>MyPassword</Password>
         </Credentials>
      </RunAsynchronousCommand>
      <RunAsynchronousCommand>
         <Order>2</Order>
         <Path>C:\AnotherApplication.exe</Path>
         <Description>DescriptionOfMyApplication</Description>
      </RunAsynchronousCommand>
</RunAsynchronous>

RunSynchronous

The following XML example shows how to configure commands to run synchronously.

<RunSynchronous>
    <!-- First synchronous command to execute -->
    <RunSynchronousCommand>
         <Order>1</Order>
         <Path>\\MyNetworkShare\MyApplication.exe</Path>
         <Description>DescriptionOfMyApplication</Description>
         <Credentials>
            <Domain>FabrikamDomain</Domain>
            <UserName>MyUserName</UserName>
            <Password>MyPassword</Password>
         </Credentials>
    </RunSynchronousCommand>
<!-- Second synchronous command to execute -->
    <RunSynchronousCommand>
         <Order>2</Order>
         <Path>C:\AnotherApplication.exe</Path>
         <Description>DescriptionOfMyApplication</Description>
    </RunSynchronousCommand>
</RunSynchronous>

Proximity, Sensor and Location

The following XML example shows how to set the order to enable or disable multiple sensor categories or types.

<SensorPermissions>
  <Sensor wcm:action="add">
    <Order>1</Order>
    <GUID>{CD09DAF1-3B2E-4C3D-B598-B5E5FF93FD46}</GUID>
    <GUIDClassification>Category</GUIDClassification>
    <Enable>true</Enable>
  </Sensor>
  <Sensor wcm:action="add">
    <Order>2</Order>
    <GUID>{6BD73C1F-0BB4-4310-81B2-DFC18A52BF94}</GUID>
    <GUIDClassification>Type</GUIDClassification>
    <Enable>false</Enable>
  </Sensor>
</SensorPermissions>

Share via