deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-16 23:37:22 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Merge pull request #85 from JanKeller1/6641851a

Browse Source 
Chgd UE-V Generator to UE-V template generator; updated getting started & relnotes
This commit is contained in:
Brian Lich 2016-07-28 09:52:43 -07:00 committed by GitHub
commit e6a5b9010f
10 changed files with 55 additions and 75 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
windows/manage/uev-administering-uev.md
View File

@ -21,12 +21,12 @@ In the course of the UE-V lifecycle, you have to manage the configuration of the
[Manage Configurations for UE-V](uev-manage-configurations.md)
## Working with custom UE-V templates and the UE-V Generator
## Working with custom UE-V templates and the UE-V template generator
This topic provides instructions for how to use the UE-V Generator and manage custom settings location templates.
This topic provides instructions for how to use the UE-V template generator and manage custom settings location templates.
[Working with Custom UE-V Templates and the UE-V Generator](uev-working-with-custom-templates-and-the-uev-generator.md)
[Working with Custom UE-V Templates and the UE-V Template Generator](uev-working-with-custom-templates-and-the-uev-generator.md)
## Backup and restore application and Windows settings that are synchronized with UE-V

28
windows/manage/uev-application-template-schema-reference.md
View File

@ -12,7 +12,7 @@ ms.prod: w10
# Application Template Schema Reference for UE-V
Microsoft User Experience Virtualization (UE-V) uses XML settings location templates to define the desktop application settings and Windows settings that are captured and applied by UE-V. UE-V includes a set of default settings location templates. You can also create custom settings location templates with the UE-V Generator.
Microsoft User Experience Virtualization (UE-V) uses XML settings location templates to define the desktop application settings and Windows settings that are captured and applied by UE-V. UE-V includes a set of default settings location templates. You can also create custom settings location templates with the UE-V template generator.
An advanced user can customize the XML file for a settings location template. This topic details the XML structure of the UE-V settings location templates and provides guidance for editing these files.
@ -53,7 +53,7 @@ This section details the XML structure of the UE-V settings location template an
**Type: String**
The XML declaration must specify the XML version 1.0 attribute (<?xml version="1.0">). Settings location templates created by the UE-V Generator are saved in UTF-8 encoding, although the encoding is not explicitly specified. We recommend that you include the encoding="UTF-8" attribute in this element as a best practice. All templates included with the product specify this tag as well (see the documents in %ProgramFiles%\\Microsoft User Experience Virtualization\\Templates for reference). For example:
The XML declaration must specify the XML version 1.0 attribute (<?xml version="1.0">). Settings location templates created by the UE-V template generator are saved in UTF-8 encoding, although the encoding is not explicitly specified. We recommend that you include the encoding="UTF-8" attribute in this element as a best practice. All templates included with the product specify this tag as well (see the documents in %ProgramFiles%\\Microsoft User Experience Virtualization\\Templates for reference). For example:
`<?xml version="1.0" encoding="UTF-8"?>`
@ -208,7 +208,7 @@ Name specifies a unique name for the settings location template. This is used fo
**Note**  
UE-V does not reference external DTDs, so it is not possible to use named entities in a settings location template. For example, do not use &reg; to refer to the registered trade mark sign ®. Instead, use canonical numbered references to include these types of special characters, for example, &\#174 for the ® character. This rule applies to all string values in this document.
See <http://www.w3.org/TR/xhtml1/dtds.html> for a complete list of character entities. UTF-8-encoded documents may include the Unicode characters directly. Saving templates through the UE-V Generator converts character entities to their Unicode representations automatically.
See <http://www.w3.org/TR/xhtml1/dtds.html> for a complete list of character entities. UTF-8-encoded documents may include the Unicode characters directly. Saving templates through the UE-V template generator converts character entities to their Unicode representations automatically.
 
@ -230,7 +230,7 @@ ID populates a unique identifier for a particular template. This tag becomes the
**Maximum Value: 2147483647**
Version identifies the version of the settings location template for administrative tracking of changes. The UE-V Generator automatically increments this number by one each time the template is saved. Notice that this field must be a whole number integer; fractional values, such as `<Version>2.5</Version>` are not allowed.
Version identifies the version of the settings location template for administrative tracking of changes. The UE-V template generator automatically increments this number by one each time the template is saved. Notice that this field must be a whole number integer; fractional values, such as `<Version>2.5</Version>` are not allowed.
**Hint:** You can save notes about version changes using XML comment tags `<!-- -->`, for example:
@ -319,7 +319,7 @@ A value of **True** indicates that the string contains illegal characters. Here
- Program&lt;1&gt;.exe
**Note**  
The UE-V Generator encodes the greater than and less than characters as &gt; and &lt; respectively.
The UE-V template generator encodes the greater than and less than characters as &gt; and &lt; respectively.
 
@ -400,7 +400,7 @@ The product and file version elements may be left unspecified. Doing so makes th
**Example 1:**
Product version: 1.0 specified in the UE-V Generator produces the following XML:
Product version: 1.0 specified in the UE-V template generator produces the following XML:
``` syntax
<ProductVersion>
@ -411,7 +411,7 @@ Product version: 1.0 specified in the UE-V Generator produces the following XML:
**Example 2:**
File version: 5.0.2.1000 specified in the UE-V Generator produces the following XML:
File version: 5.0.2.1000 specified in the UE-V template generator produces the following XML:
``` syntax
<FileVersion>
@ -990,7 +990,7 @@ This section details the XML structure of the UE-V 2.0 settings location templat
**Type: String**
The XML declaration must specify the XML version 1.0 attribute (&lt;?xml version="1.0"&gt;). Settings location templates created by the UE-V Generator are saved in UTF-8 encoding, although the encoding is not explicitly specified. We recommend that you include the encoding="UTF-8" attribute in this element as a best practice. All templates included with the product specify this tag as well (see the documents in %ProgramFiles%\\Microsoft User Experience Virtualization\\Templates for reference). For example:
The XML declaration must specify the XML version 1.0 attribute (&lt;?xml version="1.0"&gt;). Settings location templates created by the UE-V template generator are saved in UTF-8 encoding, although the encoding is not explicitly specified. We recommend that you include the encoding="UTF-8" attribute in this element as a best practice. All templates included with the product specify this tag as well (see the documents in %ProgramFiles%\\Microsoft User Experience Virtualization\\Templates for reference). For example:
`<?xml version="1.0" encoding="UTF-8"?>`
@ -1145,7 +1145,7 @@ Name specifies a unique name for the settings location template. This is used fo
**Note**  
UE-V does not reference external DTDs, so it is not possible to use named entities in a settings location template. For example, do not use &reg; to refer to the registered trade mark sign ®. Instead, use canonical numbered references to include these types of special characters, for example, &\#174 for the ® character. This rule applies to all string values in this document.
See <http://www.w3.org/TR/xhtml1/dtds.html> for a complete list of character entities. UTF-8-encoded documents may include the Unicode characters directly. Saving templates through the UE-V Generator converts character entities to their Unicode representations automatically.
See <http://www.w3.org/TR/xhtml1/dtds.html> for a complete list of character entities. UTF-8-encoded documents may include the Unicode characters directly. Saving templates through the UE-V template generator converts character entities to their Unicode representations automatically.
 
@ -1167,7 +1167,7 @@ ID populates a unique identifier for a particular template. This tag becomes the
**Maximum Value: 2147483647**
Version identifies the version of the settings location template for administrative tracking of changes. The UE-V Generator automatically increments this number by one each time the template is saved. Notice that this field must be a whole number integer; fractional values, such as `<Version>2.5</Version>` are not allowed.
Version identifies the version of the settings location template for administrative tracking of changes. The UE-V template generator automatically increments this number by one each time the template is saved. Notice that this field must be a whole number integer; fractional values, such as `<Version>2.5</Version>` are not allowed.
**Hint:** You can save notes about version changes using XML comment tags `<!-- -->`, for example:
@ -1256,7 +1256,7 @@ A value of **True** indicates that the string contains illegal characters. Here
- Program&lt;1&gt;.exe
**Note**  
The UE-V Generator encodes the greater than and less than characters as &gt; and &lt; respectively.
The UE-V template generator encodes the greater than and less than characters as &gt; and &lt; respectively.
 
@ -1337,7 +1337,7 @@ The product and file version elements may be left unspecified. Doing so makes th
**Example 1:**
Product version: 1.0 specified in the UE-V Generator produces the following XML:
Product version: 1.0 specified in the UE-V template generator produces the following XML:
``` syntax
<ProductVersion>
@ -1348,7 +1348,7 @@ Product version: 1.0 specified in the UE-V Generator produces the following XML:
**Example 2:**
File version: 5.0.2.1000 specified in the UE-V Generator produces the following XML:
File version: 5.0.2.1000 specified in the UE-V template generator produces the following XML:
``` syntax
<FileVersion>
@ -1868,6 +1868,6 @@ Add or vote on suggestions [here](http://uev.uservoice.com/forums/280428-microso
## Related topics
[Working with Custom UE-V Templates and the UE-V Generator](uev-working-with-custom-templates-and-the-uev-generator.md)
[Working with Custom UE-V Templates and the UE-V Template Generator](uev-working-with-custom-templates-and-the-uev-generator.md)
[Technical Reference for UE-V](uev-technical-reference.md)

4
windows/manage/uev-deploy-uev-for-custom-applications.md
View File

@ -17,7 +17,7 @@ After you’ve reviewed
To start, here are the main steps required to synchronize settings for custom applications:
- [Install the UE-V template generator](uev-deploy-uev-for-custom-applications.md#uevgen)
- [Install the UE-V template generator](#install-the-uev-template-generator)
Use the UEV template generator to create custom XML settings location templates.
@ -126,7 +126,7 @@ To install the UE-V template generator:
<!--
Link to <https://technet.microsoft.com/en-us/itpro/mdop/uev-v2/working-with-custom-ue-v-2x-templates-and-the-ue-v-2x-generator-new-uevv2>
AKA
[Working with Custom UE-V Templates and the UE-V Generator](uev-working-with-custom-templates-and-the-uev-generator.md)
[Working with Custom UE-V Templates and the UE-V Template Generator](uev-working-with-custom-templates-and-the-uev-generator.md)
-->
To verify that the installation was successful, click **Start** &gt; **All Programs** &gt; **Microsoft User Experience Virtualization** &gt; **Microsoft User Experience Virtualization template generator**.

4
windows/manage/uev-for-windows.md
View File

@ -46,14 +46,14 @@ Use these UE-V components to create and manage custom templates for your third-p
| Component | Description |
|-------------------------------|---------------|
| **UE-V Generator** | Use the **UE-V generator** to create custom settings location templates that you can then distribute to user computers. The UE-V generator also lets you edit an existing template or validate a template that was created with a different XML editor. <br>With the Windows 10, version 1607 release, the UE-V generator is installed with the [Windows 10 Assessment and Deployment kit](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit) (Windows ADK). <br>If you are upgrading from an existing UE-V installation, you’ll need to use the new generator to create new settings location templates. Application templates created with previous versions of the UE-V generator are still supported, however. |
| **UE-V template generator** | Use the **UE-V template generator** to create custom settings location templates that you can then distribute to user computers. The UE-V template generator also lets you edit an existing template or validate a template that was created with a different XML editor. <br>With the Windows 10, version 1607 release, the UE-V template generator is installed with the [Windows 10 Assessment and Deployment kit](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit) (Windows ADK). <br>If you are upgrading from an existing UE-V installation, you’ll need to use the new generator to create new settings location templates. Application templates created with previous versions of the UE-V template generator are still supported, however. |
| **Settings template catalog** | The **settings template catalog** is a folder path on UE-V computers or a Server Message Block (SMB) network share that stores the custom settings location templates. The UE-V service checks this location once a day, retrieves new or updated templates, and updates its synchronization behavior.<br>If you use only the UE-V default settings location templates, then a settings template catalog is unnecessary. For more information about settings deployment catalogs, see [Deploy a UE-V settings template catalog](uev-deploy-uev-for-custom-applications.md#deploycatalogue). |
<!-- PRESERVING ORIGINAL IMAGE CODING JUST IN CASE
<img src="media/image2.gif" width="595" height="330" />
-->
![UE-V Generator process](images/uev-generator-process.gif)
![UE-V template generator process](images/uev-generator-process.gif)
## Settings Synchronized by Default

9
windows/manage/uev-getting-started.md
View File

@ -34,8 +34,8 @@ The standard installation of UE-V synchronizes the default Microsoft Windows and
Before you proceed, ensure that your environment meets the following requirements for running UE-V.
| **Operating system** | **Edition** | **Service pack** | **System architecture** | **Windows PowerShell** | **Microsoft .NET Framework** |
|-------------------------|-------------|------------------|-------------------------|---------------------------------|------------------------------|
| Windows 10, version 1607 | ??? | NA | 32-bit or 64-bit | Windows PowerShell 3.0 or higher | ???? |
|-------------------------|-------------|------------------|-------------------------|----------------------------------|------------------------------|
| Windows 10, version 1607 | Windows 10 Enterprise | NA | 32-bit or 64-bit | Windows PowerShell 3.0 or higher | .NET Framework 4 or higher |
| Windows 7 | Ultimate, Enterprise, or Professional Edition | SP1 | 32-bit or 64-bit | Windows PowerShell 3.0 or higher | .NET Framework 4 or higher |
| Windows Server 2008 R2 | Standard, Enterprise, Datacenter, or Web Server | SP1 | 64-bit | Windows PowerShell 3.0 or higher | .NET Framework 4 or higher |
| Windows 8 and Windows 8.1 | Enterprise or Pro | None | 32-bit or 64-bit | Windows PowerShell 3.0 or higher | .NET Framework 4.5 |
@ -43,7 +43,6 @@ Before you proceed, ensure that your environment meets the following requirement
## Step 2: Deploy the settings storage location
You’ll need to deploy a settings storage location, a standard network share where user settings are stored in a settings package file. When you create the settings storage share, you should limit access to users that require it. [Deploy a settings storage location](https://technet.microsoft.com/library/dn458891.aspx#ssl) provides more detailed information.
**Create a network share**
@ -120,7 +119,7 @@ You’re ready to run a few tests on your UE-V evaluation deployment to see how
2. Change the default fonts.
3. Open Calculator and set it to **scientific**.
3. Open Notepad and set format -&gt; word wrap **on**.
4. Change the behavior of any Windows app, as detailed in [Managing UE-V settings location templates using Windows PowerShell and WMI](uev-managing-settings-location-templates-using-windows-powershell-and-wmi.md).
@ -130,7 +129,7 @@ You’re ready to run a few tests on your UE-V evaluation deployment to see how
3. Log in to the second device (Computer B) as the same user as Computer A.
4. Open Windows Desktop and verify that the taskbar location matches that of Computer A. Verify that the default fonts match and that Calculator is set to **scientific**. Also verify the change you made to any Windows app.
4. Open Windows Desktop and verify that the taskbar location matches that of Computer A. Verify that the default fonts match and that Notepad is set to **word wrap on**. Also verify the change you made to any Windows app.
You can change the settings in Computer B back to the original Computer A settings. Then log off Computer B and log in to Computer A to verify the changes.

2
windows/manage/uev-managing-settings-location-templates-using-windows-powershell-and-wmi.md
View File

@ -12,7 +12,7 @@ ms.prod: w10
# Managing UE-V Settings Location Templates Using Windows PowerShell and WMI
Microsoft User Experience Virtualization (UE-V) uses XML settings location templates to define the settings that User Experience Virtualization captures and applies. UE-V includes a set of standard settings location templates. It also includes the UE-V Generator tool that enables you to create custom settings location templates. After you create and deploy settings location templates, you can manage those templates by using Windows PowerShell and the Windows Management Instrumentation (WMI). For a complete list of UE-V PowerShell cmdlets, see [UE-V 2 Cmdlet Reference](http://go.microsoft.com/fwlink/p/?LinkId=393495) (http://go.microsoft.com/fwlink/p/?LinkId=393495).
Microsoft User Experience Virtualization (UE-V) uses XML settings location templates to define the settings that User Experience Virtualization captures and applies. UE-V includes a set of standard settings location templates. It also includes the UE-V template generator tool that enables you to create custom settings location templates. After you create and deploy settings location templates, you can manage those templates by using Windows PowerShell and the Windows Management Instrumentation (WMI). For a complete list of UE-V PowerShell cmdlets, see [UE-V 2 Cmdlet Reference](http://go.microsoft.com/fwlink/p/?LinkId=393495) (http://go.microsoft.com/fwlink/p/?LinkId=393495).
## Manage UE-V settings location templates by using Windows PowerShell

12
windows/manage/uev-prepare-for-deployment.md
View File

@ -34,9 +34,9 @@ First, review these tasks that you’ll need to do to deploy UE-V:
Review this topic to determine whether you want UE-V to support the synchronization of settings for custom applications (third-party or line-of-business), which requires these UE-V features:
- [Install the UE-V template generator](uev-deploy-uev-for-custom-applications.md#uevgen) so you can create, edit, and validate the custom settings location templates required to synchronize custom application settings
- [Install the UE-V template generator](uev-deploy-uev-for-custom-applications.md#install-the-uev-template-generator) so you can create, edit, and validate the custom settings location templates required to synchronize custom application settings
- [Create custom settings location templates](uev-deploy-uev-for-custom-applications.md#createcustomtemplates) by using the UE-V generator
- [Create custom settings location templates](uev-deploy-uev-for-custom-applications.md#createcustomtemplates) by using the UE-V template generator
- [Deploy a UE-V settings template catalog](uev-deploy-uev-for-custom-applications.md#deploycatalogue) to store your custom settings location templates
@ -52,7 +52,7 @@ The workflow diagram below illustrates a typical UE-V deployment and the decisio
- [Decide whether to synchronize settings for custom applications](#decide-whether-to-synchronize-settings-for-custom-applications)
If you want to synchronize settings for custom applications, you’ll need to install the UE-V generator during deployment. Use the generator to create custom settings location templates, which involves the following tasks:
If you want to synchronize settings for custom applications, you’ll need to install the UE-V template generator during deployment. Use the generator to create custom settings location templates, which involves the following tasks:
- Review the [settings that are synchronized automatically in a UE-V deployment](#settings-automatically-synchronized-in-a-ue-v-deployment).
@ -423,11 +423,11 @@ If you do not enable VDI mode for non-persistent VDI sessions, certain features
The VDI template is provided with UE-V and is typically available here after installation: C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\VdiState.xml
### Prerequisites for UE-V generator support
### Prerequisites for UE-V template generator support
Install the UE-V generator on the computer that is used to create custom settings location templates. This computer should be able to run the applications whose settings are synchronized. You must be a member of the Administrators group on the computer that runs the UE-V generator software.
Install the UE-V template generator on the computer that is used to create custom settings location templates. This computer should be able to run the applications whose settings are synchronized. You must be a member of the Administrators group on the computer that runs the UE-V template generator software.
The UE-V generator must be installed on a computer that uses an NTFS file system. The UE-V generator software requires .NET Framework 4. For more information, see [Use UE-V with custom applications](uev-deploy-uev-for-custom-applications.md).
The UE-V template generator must be installed on a computer that uses an NTFS file system. The UE-V template generator software requires .NET Framework 4. For more information, see [Use UE-V with custom applications](uev-deploy-uev-for-custom-applications.md).
## Other resources for this product

27
windows/manage/uev-release-notes-1607.md
View File

@ -14,7 +14,7 @@ Applies to: Windows 10, version 1607
This topic includes information required to successfully install and use UE-V that is not included in the User Experience Virtualization (UE-V) documentation. If there are differences between the information in this topic and other UE-V topics, the latest change should be considered authoritative.
### Upgrading from UE-V 1.0 to the Windows 10, version 1607 in-box version of UE-V is blocked
### Upgrading from UE-V 1.0 to the in-box version of UE-V is blocked
Version 1.0 of UE-V includes client-side caching technology used to pin the UE-V sync folder, however, this technology was removed in UE-V 2.x. As a result, UE-V 1.0 users are blocked from upgrading to UE-V for Windows 10, version 1607.
@ -26,19 +26,6 @@ When a user generates a valid settings location template for the Skype desktop a
WORKAROUND: Remove or unregister the Skype template to allow Skype to work again.
### Existing scripts for silent installations of UE-V may fail
Two changes made to the UE-V installer can cause silent installation scripts that worked for previous versions of UE-V to fail when installing UE-V 2.1 SP1. The first is a new requirement that users must accept the license terms and agree to or decline participation in the Customer Experience Improvement Program (CEIP), even during a silent installation. Using the /q parameter is no longer sufficient to indicate acceptance of the license terms and agreement to participate in CEIP.
Second, the installer now forces a computer restart after installing the UE-V Agent. This can cause an install script to fail if it is not expecting the restart (for example, it installs the UE-V Agent first and then immediately installs the generator).
WORKAROUND: The UE-V installer (.msi) has two new command-line parameters that support silent installations.
| Parameter | Description |
|---------------|--------------|
| /ACCEPTLICENSETERMS=True | Set this parameter to **True** to install UE-V silently. Adding this parameter implies that the user accepts the UE-V license terms, which are found (by default) here: %ProgramFiles%\\Microsoft User Experience Virtualization\\Agent |
| /NORESTART | This parameter prevents the mandatory restart after the UE-V agent is installed. A return code of 3010 indicates that a restart is required prior to using UE-V. |
### Registry settings do not synchronize between App-V and native applications on the same computer
When a computer has an application that is installed through both Application Virtualization (App-V) and locally with a Windows Installer (.msi) file, the registry-based settings do not synchronize between the technologies.
@ -51,9 +38,9 @@ When a user has both Office 2010 and Office 2013 installed, any common settings
WORKAROUND: Install only one version of Office or limit which settings are synchronized by UE-V.
### Uninstall and re-install of Windows 8 app reverts settings to initial state
### Uninstall and re-install of Windows 8 applications reverts settings to initial state
While using UE-V settings synchronization for a Windows 8 app, if the user uninstalls the app and then reinstalls the app, the app’s settings revert to their default values. This happens because the uninstall removes the local (cached) copy of the app’s settings but does not remove the local UE-V settings package. When the app is reinstalled and launched, UE-V gather the app settings that were reset to the app defaults and then uploads the default settings to the central storage location. Other computers running the app then download the default settings. This behavior is identical to the behavior of desktop applications.
While using UE-V settings synchronization for a Windows 8 application, if the user uninstalls the application and then reinstalls the application, the application’s settings revert to their default values. This happens because the uninstall removes the local (cached) copy of the application’s settings but does not remove the local UE-V settings package. When the application is reinstalled and launched, UE-V gather the application settings that were reset to the application defaults and then uploads the default settings to the central storage location. Other computers running the application then download the default settings. This behavior is identical to the behavior of desktop applications.
WORKAROUND: None.
@ -65,7 +52,7 @@ WORKAROUND: None
### MSI’s are not localized
UE-V includes a localized setup program for both the UE-V Agent and UE-V generator. These MSI files are still available but the user interface is minimized and the MSI’s only display in English. Despite the file being in English, the setup program installs all supported languages during the installation.
UE-V includes a localized setup program for both the UE-V Agent and UE-V template generator. These MSI files are still available but the user interface is minimized and the MSI’s only display in English. Despite the file being in English, the setup program installs all supported languages during the installation.
WORKAROUND: None
@ -97,12 +84,6 @@ Operating system settings for Narrator and currency characters specific to the l
WORKAROUND: None
### UE-V 1 agent generates errors when running UE-V 2 templates
If a UE-V 2 settings location template is distributed to a computer installed with a UE-V 1 agent, some settings fail to synchronize between computers and the agent reports errors in the event log.
WORKAROUND: When migrating from UE-V 1 to UE-V 2 and it is likely you’ll have computers running the previous version of the agent, create a separate UE-V 2.x catalog to support the UE-V 2.x Agent and templates.
## Hotfixes and Knowledge Base articles for UE-V 2.1 SP1
This section contains hotfixes and KB articles for UE-V 2.1 SP1.

4
windows/manage/uev-using-uev-with-application-virtualization-applications.md
View File

@ -12,7 +12,7 @@ ms.prod: w10
# Using UE-V with Application Virtualization Applications
Microsoft User Experience Virtualization (UE-V) supports Microsoft Application Virtualization (App-V) applications without any required modifications to either the App-V package or the UE-V template. However, an additional step is required because you cannot run the UE-V Generator directly on a virtualized App-V application. Instead, you must install the application locally, generate the template, and then apply the template to the virtualized application. UE-V supports App-V 4.5, App-V 4.6, and App-V 5.0 packages.
Microsoft User Experience Virtualization (UE-V) supports Microsoft Application Virtualization (App-V) applications without any required modifications to either the App-V package or the UE-V template. However, an additional step is required because you cannot run the UE-V template generator directly on a virtualized App-V application. Instead, you must install the application locally, generate the template, and then apply the template to the virtualized application. UE-V supports App-V 4.5, App-V 4.6, and App-V 5.0 packages.
## UE-V settings synchronization for App-V applications
@ -21,7 +21,7 @@ UE-V monitors when an application opens by the program name and, optionally, by
**To implement settings synchronization for a virtualized application**
1. Run the UE-V Generator to collect the settings of the locally installed application whose settings you want to synchronize between computers. This process creates a settings location template. If you use a built-in template such as the Microsoft Office 2010 template, skip this step. For more information about running the UE-V Generator, see [Deploy UE-V for Custom Applications](uev-deploy-uev-for-custom-applications.md#createcustomtemplates).
1. Run the UE-V template generator to collect the settings of the locally installed application whose settings you want to synchronize between computers. This process creates a settings location template. If you use a built-in template such as the Microsoft Office 2010 template, skip this step. For more information about running the UE-V template generator, see [Deploy UE-V for Custom Applications](uev-deploy-uev-for-custom-applications.md#createcustomtemplates).
2. Install the App-V application package if you have not already done so.

34
windows/manage/uev-working-with-custom-templates-and-the-uev-generator.md
View File

@ -1,6 +1,6 @@
---
title: Working with Custom UE-V Templates and the UE-V Generator
description: Working with Custom UE-V Templates and the UE-V Generator
title: Working with Custom UE-V Templates and the UE-V Template Generator
description: Working with Custom UE-V Templates and the UE-V Template Generator
author: jamiejdt
ms.pagetype: mdop, virtualization
ms.mktglfcycl: deploy
@ -9,12 +9,12 @@ ms.prod: w10
---
# Working with Custom UE-V Templates and the UE-V Generator
# Working with Custom UE-V Templates and the UE-V Template Generator
To synchronize application settings between user computers, Microsoft User Experience Virtualization (UE-V) uses *settings location templates*. Some settings location templates are included in User Experience Virtualization. You can also create, edit, or validate custom settings location templates by using the UE-V Generator.
To synchronize application settings between user computers, User Experience Virtualization (UE-V) uses *settings location templates*. Some settings location templates are included in User Experience Virtualization. You can also create, edit, or validate custom settings location templates by using the UE-V template generator.
The UE-V Generator monitors Windows desktop applications to discover and capture the locations where the application stores its settings. The application that is monitored must be a desktop application. The UE-V Generator cannot create a settings location template for the following application types:
The UE-V template generator monitors Windows desktop applications to discover and capture the locations where the application stores its settings. The application that is monitored must be a desktop application. The UE-V template generator cannot create a settings location template for the following application types:
- Virtualized applications
@ -24,15 +24,15 @@ The UE-V Generator monitors Windows desktop applications to discover and capture
- Windows apps
**Standard and Nonstandard settings locations:** The UE-V Generator helps you identify where applications search for settings files and registry settings that applications use to store settings information. The generator only discovers settings in locations that are accessible to a standard user. Settings that are stored in other locations are excluded. Discovered settings are grouped into two categories: **Standard** and **Non-standard**. Standard settings are recommended for synchronization, and UE-V can readily capture and apply them. Non-standard settings can potentially synchronize settings but, because of the rules that UE-V uses, these settings might not consistently or dependably synchronize settings. These settings might depend on temporary files, result in unreliable synchronization, or might not be useful. These settings locations are presented in the UE-V Generator. You can choose to include or exclude them on a case-by-case basis.
**Standard and Nonstandard settings locations:** The UE-V template generator helps you identify where applications search for settings files and registry settings that applications use to store settings information. The generator only discovers settings in locations that are accessible to a standard user. Settings that are stored in other locations are excluded. Discovered settings are grouped into two categories: **Standard** and **Non-standard**. Standard settings are recommended for synchronization, and UE-V can readily capture and apply them. Non-standard settings can potentially synchronize settings but, because of the rules that UE-V uses, these settings might not consistently or dependably synchronize settings. These settings might depend on temporary files, result in unreliable synchronization, or might not be useful. These settings locations are presented in the UE-V template generator. You can choose to include or exclude them on a case-by-case basis.
The UE-V Generator opens the application as part of the discovery process. The generator can capture settings in the following locations:
The UE-V template generator opens the application as part of the discovery process. The generator can capture settings in the following locations:
- **Registry Settings** – Registry locations under **HKEY\_CURRENT\_USER**
- **Application Settings Files** – Files that are stored under \\ **Users** \\ \[User name\] \\ **AppData** \\ **Roaming**
The UE-V Generator excludes locations, which commonly store application software files, but do not synchronize well between user computers or environments. The UE-V Generator excludes these locations. Excluded locations are as follows:
The UE-V template generator excludes locations, which commonly store application software files, but do not synchronize well between user computers or environments. The UE-V template generator excludes these locations. Excluded locations are as follows:
- HKEY\_CURRENT\_USER registry keys and files to which the logged-on user cannot write values
@ -48,17 +48,17 @@ The UE-V Generator excludes locations, which commonly store application software
If registry keys and files that are stored in these locations are required to synchronize application settings, you can manually add the excluded locations to the settings location template during the template creation process.
## <a href="" id="edit"></a>Edit Settings Location Templates with the UE-V Generator
## <a href="" id="edit"></a>Edit Settings Location Templates with the UE-V template generator
Use the UE-V Generator to edit settings location templates. When the revised settings are added to the templates by using the UE-V Generator, the version information within the template is automatically updated to ensure that any existing templates that are deployed in the enterprise are updated correctly.
Use the UE-V template generator to edit settings location templates. When the revised settings are added to the templates by using the UE-V template generator, the version information within the template is automatically updated to ensure that any existing templates that are deployed in the enterprise are updated correctly.
**Note**  
If you edit a UE-V 1.0 template by using the UE-V 2 Generator, the template is automatically converted to a UE-V 2 template. UE-V 1.0 Agents can no longer use the edited template.
 
**To edit a UE-V settings location template with the UE-V Generator**
**To edit a UE-V settings location template with the UE-V template generator**
1. Click **Start**, click **All Programs**, click **Microsoft User Experience Virtualization**, and then click **Microsoft User Experience Virtualization Generator**.
@ -88,7 +88,7 @@ If you edit a UE-V 1.0 template by using the UE-V 2 Generator, the template is a
5. Click **Save** to save the changes to the settings location template.
6. Click **Close** to close the Settings Template Wizard. Exit the UE-V Generator application.
6. Click **Close** to close the Settings Template Wizard. Exit the UE-V template generator application.
After you edit the settings location template for an application, you should test the template. Deploy the revised settings location template in a lab environment before you put it into production in the enterprise.
@ -109,16 +109,16 @@ If you edit a UE-V 1.0 template by using the UE-V 2 Generator, the template is a
5. Save the settings location template file, and then close the XML editor.
6. Validate the modified settings location template file by using the UE-V Generator.
6. Validate the modified settings location template file by using the UE-V template generator.
7. You must register the edited UE-V settings location template before it can synchronize settings between client computers. To register a template, open Windows PowerShell, and then run the following cmdlet: `update-uevtemplate [templatefilename]`. You can then copy the file to the settings storage catalog. The UE-V Agent on users’ computers should then update as scheduled in the scheduled task.
## <a href="" id="validate"></a>Validate Settings Location Templates with the UE-V Generator
## <a href="" id="validate"></a>Validate Settings Location Templates with the UE-V template generator
It is possible to create or edit settings location templates in an XML editor without using the UE-V Generator. If you do, you can use the UE-V Generator to validate that the new or revised XML matches the schema that has been defined for the template.
It is possible to create or edit settings location templates in an XML editor without using the UE-V template generator. If you do, you can use the UE-V template generator to validate that the new or revised XML matches the schema that has been defined for the template.
**To validate a UE-V settings location template with the UE-V Generator**
**To validate a UE-V settings location template with the UE-V template generator**
1. Click **Start**, point to **All Programs**, click **Microsoft User Experience Virtualization**, and then click **Microsoft User Experience Virtualization Generator**.
@ -128,7 +128,7 @@ It is possible to create or edit settings location templates in an XML editor wi
4. Click **Validate** to continue.
5. Click **Close** to close the Settings Template Wizard. Exit the UE-V Generator application.
5. Click **Close** to close the Settings Template Wizard. Exit the UE-V template generator application.
After you validate the settings location template for an application, you should test the template. Deploy the template in a lab environment before you put it into a production environment in enterprise.