Merge pull request #539 from TimMangan/patch-2

Update appv-running-locally-installed-applications-inside-a-virtual-e… #MVPHackADoc
This commit is contained in:
Brian Lich 2018-03-08 15:54:07 -08:00 committed by GitHub
commit 16ffdb4807
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -6,14 +6,17 @@ ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy ms.mktglfcycl: deploy
ms.sitesec: library ms.sitesec: library
ms.prod: w10 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 # Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications
**Applies to** **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: 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. Starting with App-V 5.0 SP3, when using RunVirtual, you can publish packages globally or to the user.
### Steps to create the subkey ### 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**. 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>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>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> <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> </ul></td>
</tr> </tr>
</tbody> </tbody>