Upgrading to App-V for Windows 10 from an existing installation
- Windows 10, version 1607
If you’re already using App-V and you’re planning to upgrade user devices to Windows 10, you need to make only the following few adjustments to your existing environment to start using App-V for Windows 10.
Upgrade user devices to Windows 10. Performing an in-place upgrade automatically installs the App-V client and migrates users’ App-V applications and settings.
These steps are explained in more detail below.
Upgrade user devices to Windows 10
Performing an in-place upgrade automatically installs the App-V client and migrates users’ App-V applications and settings. See the Windows 10 and Windows 10 Mobile document set for information about upgrading user devices to Windows 10.
Verify that App-V applications and settings were migrated correctly
After upgrading a user device to Windows 10, it’s important to verify that App-V applications and settings were migrated correctly during the upgrade.
To verify that the user’s App-V application packages were migrated correctly, type
Get-AppvClientPackage in Windows PowerShell.
To verify that the user’s App-V settings were migrated correctly, type
Get-AppvClientConfiguration in Windows PowerShell.
Enable the in-box App-V client
With Windows 10, the App-V client is installed automatically. You need to enable the client to allow user devices to access and run virtual applications. You can enable the client with the Group Policy editor or with Windows PowerShell.
To enable the App-V client with Group Policy
Open the device’s Group Policy Editor.
Navigate to Computer Configuration > Administrative Templates > System > App-V.
Run Enables App-V Client and then select Enabled on the screen that appears.
Restart the device.
To enable the App-V client with Windows PowerShell
Open Windows PowerShell.
Enable-Appvand press enter.
Restart the device.
To verify that the App-V client is enabled on the device, enter
Get-AppvStatusin Windows PowerShell.
Configure the in-box App-V client to point to previously installed App-V server components
Once you’ve enabled the in-box App-V client, you need to configure it to point to your existing App-V server components. You can configure the App-V client with Windows PowerShell cmdlets or with the device’s local Group Policy editor.
To modify client settings to point to an existing App-V publishing server with Windows PowerShell
Type the following cmdlet in a Windows PowerShell window:
Add-AppvPublishingServer -Name AppVServer -URL https:// appvserver:2222
To modify client settings to point to an existing App-V publishing server with Group Policy
Open the device’s Local Group Policy Editor.
Navigate to Computer Configuration > Administrative Templates > System > App-V > Publishing.
Enter your existing App-V publishing server’s details in Options and then click or press Apply.
Verify that the in-box App-V client can receive and launch .appv packages
Add and publish a package using the following Windows PowerShell cmdlets:
Add-AppvClientPackage \\path\to\appv\package.appv | Publish-AppvClientPackage
Launch the published package.
Unpublish an existing package use the following cmdlet:
For App-V issues, use the App-V TechNet Forum.