This post is also available in TechNet Wiki:

http://social.technet.microsoft.com/wiki/contents/articles/18347.app-v-5-0-sp1-client-with-citrix-xenapp-6-5.aspx

There is very limited information you can find on configuring the App-V 5.0 client with XenApp 6.5, most existing blogs and guides are based on App-V 4.x and these do longer apply with App-V 5.0. I decided to write this blog about how to configure App-V with XenApp 6.5 and hopefully save many a lot time in searching for answerers on Google on how to get this to work.

 

First make sure you have the SP1 version of App-V 5.0 and that you have the correct client, there is a separate App-V client for Remote Desktop Services and that is the one you will need to use with XenApp 6.5

 

1. Install the App-V client for Remote Desktop Services (basic next->next finish setup) Optionally you can enable using the Shared Content Store during the installation of the App-V client by using “appv_client_setup.exe /SHAREDCONTENTSTOREMODE=1 /q ” This can also be configured after the installation.

 

2. Connect the App-v client to your App-V 5.0 SP1 publishing server

 

Start PowerShell with “run as administrator”

 

appv1

Import the appvclient module

appv2

Connect to the publishing server with the command “Add-AppvPublishingServer -Name displayname -URL http://publishingservername:port

So if I would have a Publishing server named “appv5test” with the publishing server configured on port 8081 then the command would be:
“Add-AppvpublishingServer -Name Appv5test -URL http://apv5test:8081

 

Note: if you have multiple App-V publishing servers with a loadbalanced address then use the loadbalanced servername and port.

 

appv3

Configure the App-V client for using Shared Content Store. (App-V packages will not be cached locally but will remain on the share where the .appv packages are stored).

 

You can find more information on the shared content store here: http://blogs.technet.com/b/virtualvibes/archive/2012/10/24/introducing-shared-content-store-in-app-v-5-0-goodbye-shared-read-only-cache.aspx

Command to enable the content store: Set-AppvClientConfiguration -SharedContentStoreMode 1

 

appv4

You can check if all configuration settings are correct with the following command: Get-AppvClientConfiguration

 

appv5

3. Publish Applications in XenApp 6.5

Make sure you have imported one or more application in the App-V 5.0 enviroment in the App-V Management console and that you have published them

appv6

In XenApp 6.5 AppCenter publish a new application.

In this example I am going to Publish UltraEdit.

appv7

Publish the app as a local installed Application

appv8

Next we are going to publish the local cached App-V (with shared content sharing only emtpy pointer files will be localy availbe)

The command line should be entered as “c:\programdata\app-v\long GUID\ long GUID\Root\VFS\ProgramFilesX86\appname\appname.exe”

So in this example for Ultra Edit this would be “C:\ProgramData\App-V\0FA1D473-27B4-445C-8DDB-A55CBCA9F2C1\4FD5EBBE-4A1F-4209-941B-F2D3477CA2B9\Root\VFS\ProgramFilesX86\IDM
Computer Solutions\UltraEdit\uedit32.exe”

The working directory will be the same folder as where the application executable is started:

C:\ProgramData\App-V\0FA1D473-27B4-445C-8DDB-A55CBCA9F2C1\4FD5EBBE-4A1F-4209-941B-F2D3477CA2B9\Root\VFS\ProgramFilesX86\IDM Computer Solutions\UltraEdit\

The rest of the publishing settings do not require any specific App-V 5 settings you can finish these with your regular default. Select at least one XenApp host server to offer the app tt test if the applications work.

appv9

4. Use the published application.

In this example I am running Storefront to deliver the published application. Logon to the Storefront portal and start the application.

appv10

Ad the application (Ultra Edit in this example) will start.

appv11