Article ID: 2850582 - View products that this article applies to.
Microsoft User Experience Virtualization (UE-V) supports Microsoft Application Virtualization (App-V) applications out of the box, without the need for any modifications to either the App-V package or the UE-V template. However, an additional step is needed since you cannot run the UE-V Generator directly against a virtualized App-V application; you must first install the application locally, generate the template, then apply the template to the virtualized application. UE-V supports both App-V 4.5/4.6 and App-V 5.0 packages.
To implement UE-V for App-V applications, use the following steps:
To test replication, make a settings change in the App-V application, exit the application, then launch the application on a second machine that has the UE-V Agent installed and the template from step 3 configured.
UE-V monitors for process launch by executable name and optionally file and product version numbers. The executable may be either locally installed or virtualized via App-V. When the application is launched, UE-V injects its agent DLL (Microsoft.Uev.AppAgent.dll) in to the App-V process, applies any settings stored in the user's Settings Storage Path, then allows the application to launch normally. UE-V is aware of App-V applications, and will automatically translate the relative file and registry paths to the virtualized location (as opposed to the physical location outside of the App-V environment).
When MyApp.exe version 1.0 launches inside the App-V bubble, UE-V will inject its Agent DLL in to the process and check for a settings storage package. If a package exists, UE-V will then make a call to apply the registry settings to HKCU\Software\MyApp. App-V will automatically translate this to its virtualized location (for example, HKEY_USERS\S-1-5-21-11111111-222222222-22222222-55555\Software\Microsoft\AppV\Client\Packages\F0790437-0020-407B-ACFB-C81A4E05681\REGISTRY\USER\S-1-5-21-11111111-222222222-222222222-55555\Software\MyApp). On exit, any changes to HKCU\Software\MyApp will be written back to the Settings Storage Path. Monitored files work similarly.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.