How to configure an App-V 5.1 Full Infrastructure

This blog post will cover the first configuration tasks that needs to be done after installing an App-V 5.1 Full Infrastructure. In case you haven’t already installed an App-V 5.1 Full Infrastructure, you can check out my earlier blog post, which covers all the necessary steps that needs to be in place for the configuration tasks: How to install an App-V 5.1 Full Infrastructure

With the App-V 5.1 Full Infrastructure up-and-running, we will do the following things in this blog post:

The Installation of the App-V Client will not be covered in this blog post. If you are interested in deploying the App-V Client using ConfigMgr or MDT, drop me a comment or write me on twitter.

So, let’s start 🙂


My Lab Setup is a bit different, then on my earlier blog post where I installed the Full Infrastructure. However, you can find everything relevant below:


Creating the DNS Alias

I actually always recommend to use a DNS Alias (CNAME) that points to your App-V Management / Publishing Server. If you are setting up App-V High-Available and using a Load-Balancer you actually need to use an Alias which points to you VIP (Virtual IP Address).

Using a CNAME gives you the advantage of not depending on the Server Name. Maybe you want to replace your current Server within a few years and using a Server with a new name. With a DNS Alias, you can simply switch the hostname and point to your new server.



I usually use the alias “appv”, which will work if you only have one App-V Environment. What you will using is up to you 😉

Creating the Package Share

Switch to your File Server and create the Package Share, using the following Power-Shell Code:

# Change to your needs
$folder = 'D:\AppVContent'
$shareName = 'AppVContent$'
$serverGroup = 'G_App-V_Servers'
$adminGroup = 'G_App-V_Admins'

# Creating the content folder
New-Item -ItemType Directory -Path $folder

# Setting Modify Permissions for Admins
icacls $folder /grant "${serverGroup}:(OI)(CI)(RX)"

# Setting Read and Execute Permissions for Servers
icacls $folder /grant "${adminGroup}:(OI)(CI)(M)"

# Setting Read and Execute Permissions for Domain Users
icacls $folder /grant "Domain Users:(OI)(CI)(RX)"

# Creating Share with Everyone Share Permissions
New-SmbShare -Name $shareName -Path $folder -FullAccess 'EVERYONE'

The Security Groups that I used were created in the earlier Blog Post: How to install an App-V 5.1 Full Infrastructure

Try to reach the Package Share and create a dummy file to make sure, that the above Script did its job:


Adding the Office 2016 Package to the Management Console

Next up, we will add an Office 2016 App-V Package to the Management Console. For generating the App-V Package, you can check out my blog post: How to create an Office 2016 App-V Package


Add the generated App-V Files to the Package Share into a new folder.


Open the App-V Management Console by accessing the App-V Server via the Port that you specified during the Setup. Click “Add or Upgrade”


Enter the UNC Path to the .appv file, that you added to the package share. Click “Add Package”


The package should have been added successfully. If you receive an Error message, double-check the Management Servers permission on the package share. Click “Close”

 Publishing the Office 2016 Package


Head over to “Active Directory Users and Computers” and create a new Security Group.


Add the user account that should receive the Package into this Group.


Change again to the App-V Management Console, Click on the added package, and click “Edit” next to “AD Access”


Click “Add AD Group”


Enter the created AD Group with a leading “DOMAIN\”. To verify the Group Name you can Click “Check”. Click “Grant Access”, when the correct Group is selected.


Click the Package Name to return into the main Edit Section.


Click “Publish”


The Status of the Package should now change from Unpublished into Published

Publishing Refresh Schedule

By default, the Publishing Service refreshes the Packages every 10 Minutes. For testing purposes you will most likely don’t want to wait 10 minutes after publishing each package. To force the Publishing Service to immediately update it’s package list, you can trigger a reset of the Publishing Services Application Pool in IIS Manager:


Another way is to adjust the Publishing Server Refresh Schedule in the Registry. You can find more information about this in the following KB: How to adjust the App-V v5 Publishing Server Refresh schedule

Configure the App-V Client via a Group Policy Object

Download the Microsoft Desktop Optimization Pack Group Policy Administrative Templates and extract the CAB-File into a temporary location. You can remove the language folders that you don’t need inside the App-V 5.1 Folder.


Copy the content of the App-V 5.1 Folder into your Group Policy Central Store or in your local PolicyDefinitions folder.

More information about the Group Policy Central Store can be found in the following KB: How to create and manage the Central Store for Group Policy Administrative Templates in Windows


Create a new, or edit an existing Group Policy Object. Link the Group Policy Object to the OU, where you Client is located.


Navigate to the following setting, and click Edit:

Computer Configuration\Policies\Administrative Templates\System\App-V\Publishing\Publishing Server 1 Setting

appv51_configure_part22 appv51_configure_part23

Specify the URL to the Publishing Server. Make sure you use the correct Port for the Publishing Server and not for the Management Server! All other options are described in detail in the help section. The Values on the screenshot are for a Lab Environment, so make sure you take appropriate settings for your environment.

Click OK, to submit the settings.


If you are using the Office 2016 App-V Package, make sure you enable Package Scripts in the App-V GPO.


Switch to your Client and login with a local Administrator  Don’t login yet, with the user that has the App-V Package assigned!

Run a Group Policy Update, using the following command.

gpupdate /force


Fire-up PowerShell and execute the following Cmdlet:


You should see the registered Publishing Server with all the setting that you specified via Group Policy Object.

Testing the published Office 2016 App-V Package


As you see on the above Screenshot, there is no Office 2016 installed on my Test Client.


Login with the user, that has the Office 2016 App-V Package assigned. A few seconds after the login, you should see the Start Menu Shortcuts appear.


Run a few Applications (e.g. Word, Excel, PowerPoint and OneNote). To verify the functionality you can run the following Cmdlets, as in the above screenshot:


Make sure you run the above Cmdlets in the context of the user, which has the App-V Package assigned.

5/5 - (1 vote)


  1. Fred Tardif 20. April 2016
    • mm Simon Dettling 21. April 2016
      • Fred Tardif 21. April 2016
  2. Nicolas 10. May 2016
  3. John 31. May 2016
  4. christian 18. October 2016
    • mm Simon Dettling 19. October 2016
      • christian 19. October 2016
  5. Cristiano 26. October 2016
    • mm Simon Dettling 26. October 2016
  6. John 11. January 2017
  7. Dirk van Lierop 26. January 2017
    • mm Simon Dettling 27. January 2017
    • Morten Tollefsen 20. April 2017
      • mm Simon Dettling 22. April 2017
  8. Mukesh Khimji 28. April 2017
    • Mukesh Khimji 28. April 2017
  9. Martin Lederer 13. February 2018
  10. Mike_FG 4. April 2018
    • mm Simon Dettling 5. April 2018
  11. Ade 23. April 2018
    • mm Simon Dettling 25. April 2018
  12. Deeps 14. September 2018
  13. Rajendra 24. May 2019
  14. Rajendra 24. May 2019
    • mm Simon Dettling 28. May 2019
  15. Gareth Edmondson 10. June 2019

Leave a Reply

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