If you are like me and use App-V to virtualize as many applications from your organization’s application catalog as you can, you will have noticed that managing the App-V client can be a bit of a nightmare from time to time. The good news is that starting in Windows 10 1607, the App-V client is now built-in to the operating system – all you need to do is enable the client to allow devices to access and run the virtual applications. Luckily there are a few different ways you can achieve this and in this post I will show you how.
Note: No matter which method you choose, the App-V Client UI still needs to be installed separately and can be found here.
If you leverage group policy to configure and secure your devices, you can easily enable the built-in App-V client by configuring the policy settings. If you still do not use group policy to configure and secure your devices, than shame on you.
Note: Make sure you already imported the Windows 10 1607 ADMX templates which you can download from here. As of this writing, the latest release was Aug 2016.
Open your Group Policy editor and navigate to Computer Configuration > Administrative Templates > System > App-V.
Double-click Enable App-V Client and then select Enabled.
Don’t forget to take a look at the other App-V settings you can set too.
If you prefer to enable the built-in App-V client during OSD or deployed by other means (like a package or compliance setting), simply run the PowerShell command Enable-Appv or Powershell.exe -ExecutionPolicy Bypass -NoProfile -Command Enable-Appv from a Windows Command prompt or batch file.
To verify that the App-V client is enabled on the device, run AppvClientEnabled or Get-AppvStatus in Windows PowerShell.