Deploying User Experience Virtualization with ConfigMgr 2012

Author by Rob Plank

In this post I am going to show you how to deploy the User Experience Virtualization (UE-V) 2.0 agent and UE-V Configuration Pack with Configuration Manager. If you need to refer to the Technical Documentation you can find it here the known issues you can find here. If you are brand new to UE-V and want a high level of what UE-V does you can find that here. You will need to download a few requirements: UE-V 2.0 it can be found in the MDOP 2013 R2 ISO and the System Center 2012 Configuration Pack for Microsoft User Experience Virtualization 2.0 First we need to create two file shares on a file server. 1. Creating the Setting Storage Path – here is the documentation for permissions. 2. Creating the Settings Template Catalog Path – here is the documentation for permissions. You will need these file share paths later in the configuration file. Configuration Manager Configuration We need to update the ConfigMgr Client Policy and set the PowerShell Execution policy to bypass. This will allow the powershell detection scripts in the configuration baseline to detect if the UEV agent is installed. clip_image002 We need to create a new Application in ConfigMgr clip_image004 clip_image006 You can add the x86 agent as a second deployment type if you still have any x86 Operating Systems on your network. You will want to update the install command to msiexec /I agentSetupx64.msi /qn, the install will reboot your client machines after the install is complete. Create the deployment to push out the UE-V agent clip_image008 Install the Configuration Pack Make a copy of the xml Configuation file that you can find in the C:\Program Files (x86)\Microsoft User Experience\ConfigPack\ directory on the machine you installed the Configuration Pack on. Copy C:\Program files (x86) Microsoft User Experience Virtualization\ConfigPack\AgentConfiguration.xml C:\temp\AgentConfiguration.xml Edit the configuration file with any changes you would like to make to the UE-V Policy. Make sure to update any of the UNC paths with the UNC path of the share you created at the beginning of this post. Here is part of the configuration file and what you will need to edit to enforce the settings via the configuration Item. clip_image010 Note the comments in green they will guide on how to edit the config file. DesiredState has three accepted values: Set, Clear and Unmanaged, Make sure if you change any of the values you update the DesiredState to equal Set. Replace the unc paths with the shares you created at the beginning of this post. Once you have finished editing the xml file copy it to a machine that has the ConfigMgr console and the ConfigPack installed and run the following command UevAgentPolicyGenerator.exe -site ABC -cabFilePath "C:\Temp\" -configurationFile "C:\temp\UevAgentConfiguration.xml" The cab file you just created is now ready to be imported as a Configuration Item in the ConfigMgr console. clip_image012 clip_image014 clip_image016 If you are going to be deploying this configuration item to Windows 8.1 make sure to edit the Supported Platforms. You can now add this Configuration Item to a Configuration Baseline or create a new configuration Baseline, I am going to create a new Baseline. clip_image017 Once you have created the new baseline you need to deploy the baseline. I am going to deploy this baseline to the same collection that I used to deploy the agent too. You could create collection that queried the software inventory and just deploy the baseline to machines that have successfully installed the agent or had the agent manually installed but the detection scripts will make sure the agent is installed before applying the configuration item. clip_image019 Take note that I have checked the checkbox to remediate noncompliant rules when supported, this will take the configuration items you selected in the configuration file and enforce them on the machines this configuration baseline is deployed too. Once the agent has been installed on the client machines you should be ready to start syncing application settings between machines. And few General/trouble shooting tips learned along the way. UEV agent installs a powershell module here is a list of all the cmdlets clip_image020 You can use Get-UevConfiguration to confirm your settings have applied to the client As you can see the settings in the xml conf file above have been configured on this client clip_image021 If you see an event ID 13000 in the UEV Log in the Event viewer with the description: An exception has occurred while synchronizing settings packages. Exception message: "There is no synchronization provider URI configured." Your agent has not been configured with a SettingStoragePath and you need to check your xml configuration file or you didn’t deploy the Configuration baseline. You can download custom templates from the TechNet Gallery

Rob Plank

Systems Engineer