mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-14 06:17:22 +00:00
Merge branch 'master' into App-v-revision
This commit is contained in:
commit
1cb61d9790
@ -272,7 +272,7 @@ ms.date: 10/30/2017
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="https://onedrive.live.com/view.aspx?resid=91F4E618548FC604!2261&ithint=file%2cdocx&app=Word&authkey=!AOgLvpbaerOOfwM" target="_blank">
|
||||
<a href="https://docs.microsoft.com/en-us/microsoftteams/teams-quick-start-edu" target="_blank">
|
||||
<div class="cardSize">
|
||||
<div class="cardPadding">
|
||||
<div class="card">
|
||||
@ -283,7 +283,7 @@ ms.date: 10/30/2017
|
||||
</div>
|
||||
<div class="cardText">
|
||||
<h3>Microsoft Teams</h3>
|
||||
<p>Make the most of Microsoft Teams and find out how to deploy, launch pilot teams, and launch Teams to the rest of your institution.</p>
|
||||
<p>Make the most of Microsoft Teams and find out how to deploy, launch pilot teams, and launch Teams to the rest of your organization.</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
@ -13,7 +13,10 @@ ms.date: 04/19/2017
|
||||
# Performance Guidance for Application Virtualization
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
- Windows 7 SP1
|
||||
- Windows 10
|
||||
- Server 2012 R2
|
||||
- Server 2016
|
||||
|
||||
Learn how to configure App-V for optimal performance, optimize virtual app packages, and provide a better user experience with RDS and VDI.
|
||||
|
||||
|
@ -6,14 +6,17 @@ ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 03/08/2018
|
||||
---
|
||||
|
||||
|
||||
# Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
- Windows 7 SP1
|
||||
- Windows 10
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2016
|
||||
|
||||
You can run a locally installed application in a virtual environment, alongside applications that have been virtualized by using Microsoft Application Virtualization (App-V). You might want to do this if you:
|
||||
|
||||
@ -42,6 +45,7 @@ There is no Group Policy setting available to manage this registry key, so you h
|
||||
|
||||
Starting with App-V 5.0 SP3, when using RunVirtual, you can publish packages globally or to the user.
|
||||
|
||||
|
||||
### Steps to create the subkey
|
||||
|
||||
1. Using the information in the following table, create a new registry key using the name of the executable file, for example, **MyApp.exe**.
|
||||
@ -79,7 +83,7 @@ Starting with App-V 5.0 SP3, when using RunVirtual, you can publish packages glo
|
||||
<li><p>If you want to include multiple packages in the virtual environment, you must include them in an enabled connection group.</p></li>
|
||||
<li><p>Create only one subkey for one of the packages in the connection group. If, for example, you have one package that is published globally, and another package that is published to the user, you create a subkey for either of these packages, but not both. Although you create a subkey for only one of the packages, all of the packages in the connection group, plus the local application, will be available in the virtual environment.</p></li>
|
||||
<li><p>The key under which you create the subkey must match the publishing method you used for the package.</p>
|
||||
<p>For example, if you published the package to the user, you must create the subkey under <code>HKEY_CURRENT_USER\SOFTWARE\Microsoft\AppV\Client\RunVirtual</code>.</p></li>
|
||||
<p>For example, if you published the package to the user, you must create the subkey under <code>HKEY_CURRENT_USER\SOFTWARE\Microsoft\AppV\Client\RunVirtual</code>. Do not add a key for the same application under both hives.</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
@ -101,6 +101,8 @@ Added in Windows 10,version 1803. This node accepts a ShellLauncherConfiguration
|
||||
|
||||
> [!Note]
|
||||
> You cannot set both ShellLauncher and Configuration at the same time on the device.
|
||||
>
|
||||
> Configuring Shell Launcher using the ShellLauncher node automatically enables the Shell Launcher feature if it is available within the SKU.
|
||||
|
||||
<a href="" id="assignedaccess-statusconfiguration"></a>**./Device/Vendor/MSFT/AssignedAccess/StatusConfiguration**
|
||||
Added in Windows 10, version 1803. This node accepts a StatusConfiguration xml as input to configure the Kiosk App Health monitoring. There are three possible values for StatusEnabled node inside StatusConfiguration xml: On, OnWithAlerts, and Off. Click [link](#statusconfiguration-xsd) to see the StatusConfiguration schema.
|
||||
|
@ -6,7 +6,7 @@ ms.pagetype: mdop, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.date: 03/08/2018
|
||||
---
|
||||
|
||||
# Get Started with UE-V
|
||||
@ -25,7 +25,7 @@ The standard installation of UE-V synchronizes the default Microsoft Windows and
|
||||
|
||||
- [Step 2: Deploy the settings storage location](#step-2-deploy-the-settings-storage-location). Explains how to deploy a settings storage location. All UE-V deployments require a location to store settings packages that contain the synchronized setting values.
|
||||
|
||||
- [Step 3: Enable the UE-V service](#step-3-enable-the-ue-v-service-on-user-devices). Explains how to enable to UE-V service on user devices. To synchronize settings using UE-V, devices must have the UE-V service enabled and running.
|
||||
- [Step 3: Enable and configure the UE-V service](#step-3-enable-the-ue-v-service-on-user-devices). Explains how to enable to UE-V service on user devices and configure the storage path. To synchronize settings using UE-V, devices must have the UE-V service enabled and running.
|
||||
|
||||
- [Step 4: Test Your UE-V evaluation deployment](#step-4-test-your-ue-v-evaluation-deployment). Run a few tests on two computers with the UE-V service enabled to see how UE-V works and if it meets your organization’s needs.
|
||||
|
||||
@ -73,13 +73,34 @@ You’ll need to deploy a settings storage location, a standard network share wh
|
||||
|
||||
2. Set the registry key value to *1*.
|
||||
|
||||
## Step 3: Enable the UE-V service on user devices
|
||||
## Step 3: Enable and configure the UE-V service on user devices
|
||||
|
||||
For evaluation purposes, enable the service on at least two devices that belong to the same user in your test environment.
|
||||
|
||||
The UE-V service is the client-side component that captures user-personalized application and Windows settings and saves them in settings packages. Settings packages are built, locally stored, and copied to the settings storage location.
|
||||
|
||||
Before enabling the UE-V service, you'll need to register the UE-V templates for first use. In a PowerShell window, type `register-TemplateName` where **TemplateName** is the name of the UE-V template you want to register, and press ENTER.
|
||||
Before enabling the UE-V service, you'll need to register the UE-V templates for first use. In a PowerShell window, type `Register-UevTemplate [TemplateName]` where **TemplateName** is the name of the UE-V template you want to register, and press ENTER. For instance, to register all built-in UE-V templates, use the following PowerShell Command:
|
||||
'Get-childItem c:\programdata\Microsoft\UEV\InboxTemplates\*.xml|% {Register-UevTemplate $_.Fullname}'
|
||||
|
||||
A storage path must be configured on the client-side to tell where the personalized settings are stored.
|
||||
|
||||
**To set the storage path for UE-V with Group Policy**
|
||||
|
||||
1. Open the device’s **Group Policy Editor**.
|
||||
|
||||
2. Navigate to **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Microsoft** **User Experience Virtualization**.
|
||||
|
||||
3. Double click **Settings storage path**.
|
||||
|
||||
4. Select **Enabled**, fill in the **Settings storage path**, and click **OK**.
|
||||
|
||||
- Ensure that the storage path ends with **%username%** to ensure that eah user gets a unique folder.
|
||||
|
||||
**To set the storage path for UE-V with PowerShell**
|
||||
|
||||
1. In a PowerShell window, type **Set-uevConfiguration -SettingsStoragePath [StoragePath]** where **[StoragePath]** is the path to the location created in step 2 followed by **\%username%**.
|
||||
|
||||
- Ensure that the storage path ends with **%username%** to ensure that eah user gets a unique folder.
|
||||
|
||||
With Windows 10, version 1607 and later, the UE-V service is installed on user devices when the operating system is installed. Enable the service to start using UE-V. You can enable the service with the Group Policy editor or with Windows PowerShell.
|
||||
|
||||
@ -89,9 +110,11 @@ With Windows 10, version 1607 and later, the UE-V service is installed on user d
|
||||
|
||||
2. Navigate to **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Microsoft** **User Experience Virtualization**.
|
||||
|
||||
3. Run **Enable UEV**.
|
||||
3. Double click **Use Users Experience Virtualization (UE-V)**.
|
||||
|
||||
4. Restart the device.
|
||||
4. Select **Enabled** and click **OK**.
|
||||
|
||||
5. Restart the device.
|
||||
|
||||
**To enable the UE-V service with Windows PowerShell**
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user