Planning for Custom Template Deployment for Desktop Applications in UE-V 2.0
Updated: January 28, 2014
Applies To: User Experience Virtualization 2.0
For desktop applications, that is, pre-Windows 8 applications, which run on the desktop, Microsoft User Experience Virtualization (UE-V) uses XML settings location templates that define the settings that are captured and applied by UE-V. You can use the UE-V Generator to create custom settings location templates that let users synchronize the settings of applications other than those that are included in the default UE-V templates. After you test the custom template to ensure that the application settings synchronize settings correctly in a test environment, you can deploy these settings location templates to computers in the enterprise.
You can deploy your custom settings location templates with an existing deployment infrastructure system, such as Enterprise Software Distribution (ESD), with Group Policy preferences, or by configuring a UE-V settings template catalog. Templates that are deployed by using ESD or Group Policy must be registered with UE-V Windows Management Instrumentation (WMI) or Windows PowerShell.
Settings template catalog
The User Experience Virtualization settings template catalog is a folder path on UE-V computers or a Server Message Block (SMB) network share that stores all the custom settings location templates. The UE-V Agent retrieves new or updated templates from this location. The UE-V Agent checks this location one time each day and updates its synchronization behavior, which is based on the templates in this folder. The UE-V agent registers templates that were added or updated in this folder after the last time that the folder was checked. The UE-V Agent unregisters templates that are removed from this folder. By default, templates are registered and unregistered one time per day at 3:30 A.M. local time by the Task Scheduler and at system startup. For more information about the UE-V tasks, see Changing the Frequency of UE-V 2.0 Scheduled Tasks.
You can configure the settings template catalog path by using the installation command-line options, Group Policy, WMI, or Windows PowerShell. Templates that are stored at the settings template catalog path are automatically registered and unregistered by a scheduled task. You can customize this scheduled task as required.
Replace the inbox Microsoft templates
The UE-V Agent installs a default group of settings location templates for common Microsoft applications and Windows settings. If your enterprise requires customized versions of these templates, the UE-V Agent can be configured to use a settings template catalog. Include the inbox and any additional templates your environment might want to include.
During the installation of the UE-V Agent, the command-line parameter,
RegisterMSTemplates, can be used to disable the registration of the default Microsoft templates. For more information about how to set the UE-V parameters, see Planning for UE-V 2.0 Configuration Methods.
When you use Group Policy to configure the settings template catalog path, you can choose to replace the default Microsoft templates. If you configure the policy settings to replace the default Microsoft templates, all of the default Microsoft templates that are installed by the UE-V Agent are deleted from the computer, and only the templates that are located in the settings template catalog are used. The UE-V Agent configuration setting parameter
RegisterMSTemplates must be set to true in order to override the default Microsoft template.
|If you disable this policy setting after it has been enabled, the UE-V Agent does not restore the default Microsoft templates.|
If there are customized templates in the settings template catalog that use the same ID as the default Microsoft templates, and the UE-V Agent is not configured to replace the default Microsoft templates, the Microsoft templates in the catalog are ignored.
You can also replace the default templates by using the UE-V Windows PowerShell features. To replace the default Microsoft template with Windows PowerShell, unregister all of the default Microsoft templates, and then register the customized templates.
|Old settings packages remain in the settings storage location even if you deploy new settings location templates for an application. These packages are not read by the agent, but neither are they automatically deleted.|