Enabling built-in App-V client in Windows Server 2016

Microsoft has integrated their application virtualization technology named Microsoft App-V within Windows 10 and Windows Server 2016. In this post I will explain how to enable the integrated client and how to use it.

To demonstrate the built-in App-V client in Windows Server 2016 I will use a clean installed Virtual Machines running on VMware Workstation 12 Pro.

With the following powershell command you will get the Windows version.

<pre class="lang-bsh prettyprint prettyprinted">```
<span class="pun">(</span><span class="typ">Get</span><span class="pun">-</span><span class="typ">WmiObject</span> <span class="pun">-</span><span class="pln">class </span><span class="typ">Win32_OperatingSystem</span><span class="pun">).</span><span class="typ">Caption</span>

[![Windows version](https://stefandingemanse.com/wp-content/uploads/2016/10/powershell-windows-version-300x221.png)](https://stefandingemanse.com/wp-content/uploads/2016/10/powershell-windows-version.png)

## The binaries

Without enabling the App-v Client in Server 2016 there are already files for App-V present on the system. These binaries are located in “C:\\Windows\\System32”

[![App-V files](https://stefandingemanse.com/wp-content/uploads/2016/10/Appv-binaries-300x175.png)](https://stefandingemanse.com/wp-content/uploads/2016/10/Appv-binaries.png)

Also the Microsoft App-V Client Services is by default installed. The service is disabled by default, you cannot start this services without enabling App-V.

[![App-V service](https://stefandingemanse.com/wp-content/uploads/2016/10/appv-service-300x221.png)](https://stefandingemanse.com/wp-content/uploads/2016/10/appv-service.png)

## App-V Powershell commands

The following App-V Powershell commands are available:

[![App-V commands](https://stefandingemanse.com/wp-content/uploads/2016/10/powershell-appv-commands-300x220.png)](https://stefandingemanse.com/wp-content/uploads/2016/10/powershell-appv-commands.png)

There is one new command: **Enable-Appv** We will use this command to Enable the App-V client on this Server 2016 OS.

![Enable App-V](https://stefandingemanse.com/wp-content/uploads/2016/10/enable-app-v-300x221.png)

After enabling App-V you can use the App-V powershell commands like you always do.

You can show the configuration in powershell with the following command:

Get-AppvClientConfiguration

[![Get-AppVClientconfiguration](https://stefandingemanse.com/wp-content/uploads/2016/10/get-appvclientconfig-300x221.png)](https://stefandingemanse.com/wp-content/uploads/2016/10/get-appvclientconfig.png)

**Publish App-V package**

To demonstrate the function of the App-V client I will publish an App-V package on Server 2016.

For publishing an App-V package you first need to add it to the client, after adding it you can publish it. Here an oneliner to accomplish this.

Add-AppvClientPackage “%AppVShare%\7-Zip_16.04\7-Zip_16.04.appv” | Publish-AppvClientPackage

[![Import App-V package 7-Zip](https://stefandingemanse.com/wp-content/uploads/2016/10/import-appv-7zip-300x221.png)](https://stefandingemanse.com/wp-content/uploads/2016/10/import-appv-7zip.png)

After publishing the application you can use it like any other application. In this case I can start 7-Zip manager via menu start.

![7-zip App-V](https://stefandingemanse.com/wp-content/uploads/2016/10/7zip-300x113.png)

During the publishing of the application the App-V client will create a cache of the files needed to run the App-V package. Default these cached files are located in “C:\\ProgramData\\AppV”

[![App-V cache](https://stefandingemanse.com/wp-content/uploads/2016/10/programdata-1-300x128.png)](https://stefandingemanse.com/wp-content/uploads/2016/10/programdata-1.png)