Corel Acquires Awingu to Accelerate Its Secure Remote Workspace Offering. Read more


How can we help?

  1. Home
  2. Knowledge Base
  3. Awingu for admins & buyers
  4. Deployment
  5. How do I deploy Awingu on an existing Citrix infrastructure?

How do I deploy Awingu on an existing Citrix infrastructure?

How do I deploy Awingu on an existing Citrix infrastructure?

Migrating away from an existing Citrix infrastructure to Awingu is one of our most frequent use cases. It’s actually a really easy and fast four-step process. We’re describing it below in full detail.

Note: There are a number of reasons why migrating from Citrix to Awingu is a good idea. We elaborate on this in more detail here.

Below is a picture of a typical Citrix XenApp Deployment:awingu vs citrix

Installing Awingu next to this setup can be achieved by deploying 1 (or more for load distribution or High Availability) in the Access Layer following this procedure which can be executed in less than 1 hour.

1)     Download and setup Awingu according to the regular installation guide.

Download the admin guide here

2)     Add non-admin users to directly access user group

When ‘Citrix Virtual Delivery Agent’ is installed on a machine, non-administrators can no longer RDP to the machine. A new local group called Direct Access Users is created on each Virtual Delivery Agent. Add your non-administrator RDP users to this local group so they can RDP directly to the machine.

awingu vs citrix_02

– Enable non-admin RDP users to get direct RDP access –

Add here the security group for the users which should have access.

awingu vs. citirx 03

– Add security group for users with access –

3)     Enable RDP policy in Citrix studio

3.a. To be able to initiate a remote session a policy needs to be added to Citrix. Open the Citrix director and browse to the policy section. On the right top choose ‘Create Policy’

awingu vs citrix 04

– Create new policy –

3.b. In the search field search for: ‘Launching of non-published programs during client connection’ and select it.

awingu vs citirx 05

– Launching of non-published programs during client connection –

3.c. Enable this policy for all objects in this site

awingu vs citrix 06

– Enable for all objects –

3.d. Give it a meaningful name and enable the policy

awingu vs citrix 07

– Give a name and enable policy –

3.e. Set the policy priority higher

citrix vs awingu 08

– Set policy priority –

3.f. If you want to speed the policy up you can always update them manually

awingu vs citirx 09

– option: manually update policies –

4)     Optional: De-Install Citrix software from app servers

The result would be like in the following picture:

awingu vs citrix 10

Please note that the Netscaler can be optionally used to load-balance to the different Awingu appliances but any load balancer will do.

There is no need any more of the Citrix Control layer. The Awingu appliances have all the knowledge needed to do the brokerage to the different RDS servers.

Have any questions or remarks? Please don’t hesitate and reach out to us.

Related Articles

Need Support?

Can't find the answer you're looking for?
Contact Support
This website uses cookies. Read our transparent cookie policy!