deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-18 20:03:40 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Merge pull request #2749 from MicrosoftDocs/jreeds-seoproject-2

Browse Source 
Jreeds seoproject 2
This commit is contained in:
Gary Moore
2020-05-12 16:22:08 -07:00
committed by GitHub
parent cadddcc5c4 c24506e166
commit a68f3291ed
2 changed files with 11 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
windows/configuration/ue-v/uev-upgrade-uev-from-previous-releases.md
View File

@ -1,6 +1,6 @@
--- ---
title: Upgrade to UE-V for Windows 10 title: Upgrade to UE-V for Windows 10
description: Explains how to upgrade to the latest version of UE-V. description: Use these few adjustments to upgrade from User Experience Virtualization (UE-V) 2.x to the latest version of UE-V.
author: dansimp author: dansimp
ms.pagetype: mdop, virtualization ms.pagetype: mdop, virtualization
ms.mktglfcycl: deploy ms.mktglfcycl: deploy
@ -30,7 +30,8 @@ If you’re already using UE-V 2.x and you’re planning to upgrade user devices
5. Install the UE-V template generator if you want to synchronize application settings for custom applications. 5. Install the UE-V template generator if you want to synchronize application settings for custom applications.
> **Important**  You can upgrade your existing UE-V installation to Windows 10, version 1607 from UE-V versions 2.1 or 2.0 only. If you are using a previous version of UE-V, you’ll need to upgrade from that version to UE-V 2.x before you upgrade to Windows 10, version 1607.. > [!IMPORTANT]
> You can upgrade your existing UE-V installation to Windows 10, version 1607 from UE-V versions 2.1 or 2.0 only. If you are using a previous version of UE-V, you’ll need to upgrade from that version to UE-V 2.x before you upgrade to Windows 10, version 1607.
## Upgrade user devices to Windows 10, version 1607 ## Upgrade user devices to Windows 10, version 1607
@ -38,7 +39,7 @@ Performing an in-place upgrade on user devices automatically installs the UE-V s
## Verify that UE-V settings were migrated correctly ## Verify that UE-V settings were migrated correctly
After upgrading a user device to Windows 10, version 1607, it’s important to verify that UE-V settings and template registrations were migrated correctly during the upgrade. You can verify UE-V settings using Windows Powershell or the device’s registry. After upgrading a user device to Windows 10, version 1607, it’s important to verify that UE-V settings and template registrations were migrated correctly during the upgrade. You can verify UE-V settings using Windows PowerShell or the device’s registry.
**To verify UE-V settings using Windows PowerShell** **To verify UE-V settings using Windows PowerShell**
@ -48,7 +49,8 @@ After upgrading a user device to Windows 10, version 1607, it’s important to v
3. Type **Get-UEVTemplate** and press ENTER to check that your templates are still registered. 3. Type **Get-UEVTemplate** and press ENTER to check that your templates are still registered.
> **Note** You’ll need to register the NotePad template again after you upgrade the device to Windows 10. > [!NOTE]
> You’ll need to register the NotePad template again after you upgrade the device to Windows 10.
**To verify UE-V settings using the device’s registry** **To verify UE-V settings using the device’s registry**
@ -68,7 +70,8 @@ The UE-V service is the client-side component that captures user-personalized ap
With Windows 10, version 1607 and later, the UE-V service replaces the UE-V Agent and no longer requires a separate download and installation. Enable the service on user devices to start using UE-V. You can enable the service with the Group Policy editor or with Windows PowerShell. With Windows 10, version 1607 and later, the UE-V service replaces the UE-V Agent and no longer requires a separate download and installation. Enable the service on user devices to start using UE-V. You can enable the service with the Group Policy editor or with Windows PowerShell.
> **Important**  The UE-V Agent used in prior releases of UE-V is replaced with the UE service. The UE-V service included with Windows 10, version 1607 and later releases, does not include the agent user interface and is configurable through cmdlets or registry settings only. > [!IMPORTANT]
> The UE-V Agent used in prior releases of UE-V is replaced with the UE service. The UE-V service included with Windows 10, version 1607 and later releases, does not include the agent user interface and is configurable through cmdlets or registry settings only.
**To enable the UE-V service with Group Policy** **To enable the UE-V service with Group Policy**

7
windows/configuration/ue-v/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 Template 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 description: Create your own custom settings location templates by working with Custom User Experience Virtualization (UE-V) Templates and the UE-V Template Generator.
author: dansimp author: dansimp
ms.pagetype: mdop, virtualization ms.pagetype: mdop, virtualization
ms.mktglfcycl: deploy ms.mktglfcycl: deploy
@ -98,9 +98,8 @@ Use the UE-V template generator to edit settings location templates. When the re
1. Create a local copy of the settings location template .xml file. UE-V settings location templates are .xml files that identify the locations where application store settings values. 1. Create a local copy of the settings location template .xml file. UE-V settings location templates are .xml files that identify the locations where application store settings values.
>**Note**   > [!NOTE]
A settings location template is unique because of the template **ID**. If you copy the template and rename the .xml file, template registration fails because UE-V reads the template **ID** tag in the .xml file to determine the name, not the file name of the .xml file. UE-V also reads the **Version** number to know if anything has changed. If the version number is higher, UE-V updates the template. > A settings location template is unique because of the template **ID**. If you copy the template and rename the .xml file, template registration fails because UE-V reads the template **ID** tag in the .xml file to determine the name, not the file name of the .xml file. UE-V also reads the **Version** number to know if anything has changed. If the version number is higher, UE-V updates the template.
2. Open the settings location template file with an XML editor. 2. Open the settings location template file with an XML editor.