Installing the App-V 5.1 Client & Hotfix with ConfigMgr current branch

Update: If you’re deploying Windows 10 1607 / Windows Server 2016 or newer, installing the App-V Client is no longer neccessary. More Details

Recently, I wrote a Blog post about How to Install the App-V 5.1 Client using Microsoft Deployment Toolkit. In case you missed it, you can find the Blog post over here.

Today, I’d like to cover the Installation Process of the App-V 5.1 Client using Microsoft’s Configuration Manager Current Branch, Version 1602. The Steps, which are provided here, will also work with older ConfigMgr Releases but some functions may vary.

We will create a single Application for the App-V Client / Hotfix with a Custom Wrapper and deploy this Application to a Client. It is also possible to create two dedicated Applications for the Main Installer and the Hotfix, but I’d like to keep things simple and use only one Application.

Packaging the App-V Client & Hotfix

I assume you already downloaded the Desktop Optimization Pack 2015. Open the ISO and navigate to the Folder “App-V 5.1\Client”. In here you find two files

  • appv_client_setup.exe
  • appv_client_setup_rds.exe

As you can guess from the Filename, the above is for the classic Installation on a Client and the other one is for the Installation on a Remote Desktop Services (RDS) System.

Copy the Non-RDS Installer to a dedicated Folder as below:

The next step is to grab the latest Hotfix, which is HF02 (KB3139245) at this certain moment. Copy the Non-RDS Hotfix to the same Folder, where you copied the Main Installer.

Create a file “Install_Wrapper.cmd” in the same Folder, with the following Content:

I’m usually not a big fan of Batch-Files, but for the really simple purpose of calling two EXEs, I’m making and exception 😉

If you are using a different Hotfix, you’ll need to adjust the filename in the Second Line of the Wrapper Script.

Creating the Application in ConfigMgr

Head over to your ConfigMgr Console and create a new Application.

App-V51_Client_ConfigMgr_Part4

Select “Manually specify the application Information” and Click “Next”

App-V51_Client_ConfigMgr_Part5

Enter the Metadata like Name, Publisher and Software Version and Click “Next”

App-V51_Client_ConfigMgr_Part6

Modify the Application Catalog Section if needed and Click “Next”

App-V51_Client_ConfigMgr_Part7

Click “Add” to create a new Deployment Type

App-V51_Client_ConfigMgr_Part8

Select Type “Script Installer” and Click “Next”

App-V51_Client_ConfigMgr_Part9

Enter a Name for the Deployment Type and Click “Next”

App-V51_Client_ConfigMgr_Part10

Specify the Content Location and the Wrapper-Script, that you created as below. Click “Next”

App-V51_Client_ConfigMgr_Part11

Click “Add Clause”

App-V51_Client_ConfigMgr_Part12

Specify the Detection Method as below. If you’re using a different Hotfix, make sure you adjust the File Version in the “Value” Field! Click “OK”

%ProgramFiles%\Microsoft Application Virtualization\Client

App-V51_Client_ConfigMgr_Part13

Click “Next”

App-V51_Client_ConfigMgr_Part14

Modify the User Experience Settings as below and Click “Next”

App-V51_Client_ConfigMgr_Part15

Add the Requirements, based on the App-V 5.1 Supported Configurations TechNet Page and Click “Next”

App-V51_Client_ConfigMgr_Part16

Click “Next”

App-V51_Client_ConfigMgr_Part17

Click “Next”

App-V51_Client_ConfigMgr_Part18

Click “Close”

App-V51_Client_ConfigMgr_Part19

Click “Next”

App-V51_Client_ConfigMgr_Part20

Click “Next”

App-V51_Client_ConfigMgr_Part21

Click “Close”

App-V51_Client_ConfigMgr_Part22

Deploying the App-V Client

Right-Click your created Application and Click “Deploy”

App-V51_Client_ConfigMgr_Part23

Select the Collection, which you want to target for the Installation. The Collection in my example is a Device Collection, which contains all Windows 10 Computers. Be careful what you choose here, because those devices will get the App-V Client. Click “Next”

App-V51_Client_ConfigMgr_Part24

Select your Distribution Point or Distribution Point Group and Click “Next”

App-V51_Client_ConfigMgr_Part25

Select the Purpose of the Deployment, Available or Required, and Click “Summary”

App-V51_Client_ConfigMgr_Part26

Click “Next” to Confirm the Deployment and Click “Close”

App-V51_Client_ConfigMgr_Part27

After you close the Deployment Wizard, you should monitor the Package Content, which should turn into “In Progress”

App-V51_Client_ConfigMgr_Part28

and after a short while, into “Success”

App-V51_Client_ConfigMgr_Part29

 Verifying the Deployment

Now switch to a Device, which you targeted with the Deployment, and open Software Center. From there, you can Click “Sync Policy”, from the “Options” Node.

App-V51_Client_ConfigMgr_Part30

If you’re running an older ConfigMgr Version, you need to force a Policy Sync via the Configuration Manager Control Panel Applet as below.

App-V51_Client_ConfigMgr_Part31

After a short while, the App-V 5.1 Application should appear in Software Center and the Installation should start.

App-V51_Client_ConfigMgr_Part32

When done, Software Center triggers a Restart Notification.

App-V51_Client_ConfigMgr_Part33

After the Restart, you have a fully working and up-to-date App-V 5.1 Client.

App-V51_Client_ConfigMgr_Part35

App-V51_Client_ConfigMgr_Part34

Installing the App-V 5.1 Client & Hotfix with ConfigMgr current branch
Rate this post

5 Comments

  1. Mark Fenwick 23. March 2017
    • mm Simon Dettling 23. March 2017
  2. Anshul 22. April 2017
    • mm Simon Dettling 22. April 2017
    • Anshul 22. April 2017

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.