User Experience Virtualization (UE-V) Configuration Pack

1 Introduction 2

2 Configuration Baseline Reference 2

2.1 Generate UE-V Agent Policy configuration item 2

2.1.1 Procedures for Creating the First ue-v Policy configuration item 3

2.1.2 Procedures for Updating a ue-v Policy configuration item 4

2.2 Generate UE-V Template Baseline 5

2.2.1 Procedures for Creating the First ue-v template Baseline 5

2.2.2 Procedures for Updating a ue-v template baseline 5

1 Introduction

After Microsoft User Experience Virtualization (UE-V) and its required components are installed, UE-V must be configured. This UE-V Configuration Pack provides a way for administrators to use the Compliance Settings feature of System Center Configuration Manager 2012 SP1 to apply consistent configuration across sites where UE-V is installed.

The UE-V Configuration Pack provides tools to do the following:

1. Create UE-V template distribution baselines.

a. Defines UE-V templates to be registered or unregistered

b. Updates UE-V template configuration items and baselines as templates are added or updated.

c. Distribute and register UE-V templates using standard Configuration Item remediation

2. Create an Agent policy configuration item to manage the following settings:

a. Max package size

b. Setting import delay

c. Settings import notification

d. Settings storage path

e. Sync enablement

f. Sync method

g. Sync timeout

h. Enable/disable Windows 8 app sync

i. Sync unlisted Windows 8 apps

j. IT contact URL

k. IT contact descriptive text

l. Tray icon enabled

m. First use notification

n. Wait for sync on application start

o. Wait for sync on logon

p. Wait for sync timeout

q. Settings template catalog path

r. Start/Stop UE-V agent service

s. Define which Windows 8 apps will roam settings

2 Configuration Baseline Reference

2.1 Generate UE-V Agent Policy configuration item

All UE-V agent policy and configuration is distributed via a single configuration item that is generated using the UevAgentPolicyGenerator.exe tool. This tool reads all desired configuration from an XML configuration file and creates a CI containing all discovery and remediation settings needed to bring the machine into compliance.

The UE-V agent policy configuration item cab file is created using the UevTemplateBaselineGenerator.exe command line tool. This tool has the following parameters:

-Site <site code>

-PolicyName <name> Optional: Defaults to “UE-V Agent Policy” if not present

-PolicyDescription <description> Optional: A description will be provided if not present

-CabFilePath <full path to configuration item .cab file>

-ConfigurationFile <full path to agent configuration XML file>

Note: It may be necessary to change the PowerShell execution policy to allow these scripts to run in your environment. This can be accomplished in the Configuration Manager console under Administration->Client Settings->Properties then selecting the User Agent tab to set the PowerShell Execution Policy to Bypass.

2.1.1 Procedures for Creating the First ue-v Policy configuration item

1. Copy the default settings configuration file from the UE-V Config Pack installation directory to a location visible to your ConfigMgr Admin Console:
copy C:\Program Files (x86)\Microsoft User Experience Virtualization\ConfigPack\AgentConfiguration.xml c:\<target path>
The default configuration file contains five sections:

· Computer Policy
All UE-V machine level settings. The DesiredState attribute can be ‘Set’ to have the value assigned in the registry, ‘Clear’ to remove the setting or ‘Unmanaged’ to have the configuration item left at its current state. Do not remove lines from this section. Instead, set the DesiredState to ‘Unmanaged’ if you do not want CM to alter current or default values.

· CurrentComputerUserPolicy
All UE-V user level settings. These entries will override the machine settings for a user. The DesiredState attribute can be ‘Set’ to have the value assigned in the registry, ‘Clear’ to remove the setting or ‘Unmanaged’ to have the configuration item left at its current state. Do not remove lines from this section. Instead, set the DesiredState to ‘Unmanaged’ if you do not want CM to alter current or default values.

· Services
Entries in this section will control service operation. The default configuration file contains a single entry for the UevAgentService. The DesiredState attribute may be set to ‘Running’ or ‘Stopped’.

· Windows8AppsComputerPolicy
All machine level Windows 8 application synchronization settings. Each a PackageFamilyName listed in this section may be assigned a DesiredState of ‘Enabled’ to have settings roam, ‘Disabled’ to prevent settings from roaming or ‘Cleared’ to have the entry removed from UE-V control. Additional lines may be added to this section based on the list of installed Windows 8 applications that can be viewed using the PowerShell cmdlet GetAppxPackage.

· Windows8AppsCurrentComputerUserPolicy
Identical to the Windows8AppsComputerPolicy with settings that override machine settings for an individual user.

2. Edit the configuration file by changing the desired state and value fields.

3. Run the following command on a machine running the ConfigMgr Admin Console:
C:\Program Files (x86)\Microsoft User Experience Virtualization\ConfigPack\UevAgentPolicyGenerator.exe –Site ABC –CabFilePath “C:\MyCabFiles\UevPolicyItem.cab” –ConfigurationFile “c:\AgentConfiguration.xml”

3. Import the CAB file using ConfigMgr console or PowerShell Import-CMConfigurationItem.

2.1.2 Procedures for Updating a ue-v Policy configuration item

1. Edit the configuration file by changing the desired state and value fields.

2. Rerun step 3 in the previous section. If you changed the name with the –PolicyName parameter, make sure you enter the same name.

3. Reimport the cab. The version in ConfigMgr will be updated.

2.2 Generate UE-V Template Baseline

UE-V templates are distributed using a baseline containing multiple configuration items. Each configuration item contains the discovery and remediation scripts needed to install one UE-V template. The actual UE-V template is embedded within the remediation script for distribution using standard Configuration Item functionality.

The UE-V template baseline is created using the UevTemplateBaselineGenerator.exe command line tool. This tool has the following parameters:

-Site <site code>

-BaselineName <name> (Optional: defaults to “UE-V Template Distribution Baseline” if not present)

-BaselineDescription <description> (Optional: a description will be provided if not present)

-TemplateFolder <UE-V template folder>

-Register <comma separated template file list>

-Unregister <comma separated template list>

-CabFilePath <Full path to baseline CAB file to generate>

The result is a baseline CAB file that is ready for import into CM. If at a future date, you update or add a template, you can rerun the command using the same baseline name. Importing the cab will result in CI version updates on the changed templates.

2.2.1 Procedures for Creating the First ue-v template Baseline

Create a “master” set of UE-V templates in a stable folder location visible to the machine running your ConfigMgr Admin Console. As templates are added or updated, this folder is where they will be pulled for distribution. The initial list of templates can be copied from a machine with UE-V installed. The default template location is C:\Program Files\Microsoft User Experience Virtualization\Templates
Create a text .bat file where you can add the template generator command. This is optional, but will make regeneration simpler if you save the command parameters.
Add the command and parameters to the .bat file that will generate the baseline. The following example will create a baseline that distributes Notepad and Calculator:
C:\Program Files (x86)\Microsoft User Experience Virtualization\ConfigPack\UevTemplateBaselineGenerator.exe –Site “ABC” –TemplateFolder “C:\ProductionUevTemplates” –Register “MicrosoftNotepad.xml, MicrosoftCalculator.xml” –CabFilePath “C:\MyCabFiles\UevTemplateBaseline.cab”

4. Running the .bat file will create UevTemplateBaseline.cab ready for import into ConfigMgr

2.2.2 Procedures for Updating a ue-v template baseline

The template generator uses the template version to determine if a template should be updated. If you make a template change and update the version, the baseline generator will compare the template in your master folder with the template contained in the CI on the ConfigMgr server. If a difference is found, the generated baseline and modified CI versions will be updated.

To distribute a new Notepad template, the procedure would be as follows:

Update the template and template version located in the <Version> element of the template.
Copy the template to your master template directory.
Rerun the command in your .bat file that was created previously.
Import the generated CAB file into ConfigMgr using the console or PowerShell Import-CMBaseline.