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.
An example of a typical Citrix XenApp Deployment:
Installing Awingu next to this setup can be achieved by deploying one (or more for load distribution or High Availability) Awingu node in the Access Layer.
1. Download and setup Awingu
Please consult the admin manual and perform a default installation.
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.
Add here the security group for the users which should have access.
3) Enable RDP policy in Citrix studio
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.
In the search field, enter Launching of non-published programs during client connection and select it.
Enable this policy for all objects in this site.
Give it a meaningful name and enable the policy.
3.Set the policy priority higher.
It may take some time for group policies to apply automatically. You can always force a manual update.
4) Optional: De-Install Citrix software from app servers
The end result would be similar to this:
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 for the Citrix Control layer anymore. The Awingu appliances will do the brokerage to the different RDS servers.