Citrix Local Application access – aka RES VDX

This blog will show you how to setup Citrix Local Application Access as is made available with the Platinum license. Citrix bought the license to the technique from RES Software who had a product named VDX doing the same for some years already.


In short, the customer runs endpoints with Windows XP SP3The servers we’re building are Windows 2008 R2.Citrix version used is XenApp 7.5 Platinum edition. Local App Access is only available in the platinum edition which is a shame. Citrix always seems to put this kind of features in Platinum and with that withholds it for the common customer. This customer has Platinum so we can go along. 

Prepare the Controllers

First we have to prepare the controllers to be able to deploy local applications. To do that we have to add a registry key to both controllers (assuming you have two running, I have).


The registry location is HKLMSoftwareWOW6432NodeCitrixDesktopStudio

The entry we have to add is a Dword entry called ClientHostedAppsEnabledThe value is 1. After adding this registry entry you have to restart the controller.After you restarted the controller you can setup the delivery group, so lets get on with that.

Setup the Delivery group

After the controllers are rebooted you start up Citrix Studio to setup the delivery group. The delivery group needs to be configured with Client local applications. Click on the Delivery group and select the Application tab.On the right side of the menu you have an extra option called “Add local access application”.

In the next screen you will select the delivery group through which you will deliver the local application.

Enter the local application with the complete path and executable as shown in the screenshot below.

Enter an Application name and perhaps something for administrators so they understand it’s a local application.

You can add a start menu location, here I left it empty but in tests further on I added local apps there.This will show up in the start menu so that the users knows the application is from his local computer.

..and there you are, the application is added. Now we have to do some configuration and we’re good to go.


Citrix policy

Perhaps this one is not necessary but I’ve configured it anyway. I added a Citrix policy to the delivery group to allow local application access. Just one policy to make sure it’s allowed.


 At this point we’re done at the server side, we will continue at the client side.

Setup the client (The endpoint device)

## Added info ## You don’t need to reinstall the receiver, through the GPO the client will be set to allow access to local applications — Credits Andrew Morgan. The receiver is not installed to allow access to local applications, we need to install the receiver to allow access to local applications. The command to setup the receiver to allow local applications is Receiver.exe //ALLOW_CLIENTHOSTEDAPPSURL=1Start the receiver installation with this option, it doesn’t matter if it’s the receiver or receiver Enterprise.


Next to setting up the receiver to allow access to local applications you need to change the client policy to allow the client to use local application access. The settings for this are configured through the ICAClient.ADM which is located in the CitrixConfiguration folder on the client. 

The setting is found under User Experience and is called Access to local apps.

If you open the GPO setting you will see an option for URL redirection, I also enabled that one.


Register browser add-on

Another thing I did was register the browser add-on to allow integration with IE and chrome I executed that on both the client and the XenApp server. The command for this is; On the Client: Redirector.exe /RegAll  The location for the redirector.exe on the Citrix client is the installation folder (C:Program FilesCitrixICA Client). On the server: VDARedirector.exe /RegAll The location for the VDAredirector.exe on the XenApp server is the VDA installation folder (C:Program Files(x86)CitrixSystem32). 

The proof of the pudding is in the tasting

 After doing all this I was ready for a test.So I logged on with a user, CTX1 a normal domain user with no additional rights. The folder localapps as well as the application was not there. I added security rights for the user but the application is not there.

 So I logged on with my account, the one I use to build the environment, I’m a domain admin with my account. The application shows up in the start menu.

When I start the application you can see that this customer is still on Windows XP so the calculator is a bit different then the one on Windows 2008R2 which I started also.



I works with the documentation from eDocs, but there is still something to find out.I don’t want the users to be admin locally to start an application. They didn’t have to be Admin before and shouldn’t be now. Perhaps I’m overlooking something so if you know what let me know. I’ll be investigating this here also for I’m very interested in it.   

Leave a Reply

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