Virtual Desktop Infrastructure is becoming a hot issue nowadays with many companies adopting this technology due to its flexibility, machines density, mobility, security, manageability and overall total cost of ownership. VDI can be either dedicated/Personal desktop assigned for specific user or pool of desktops available for all users (First come is first served); both flavors have their own benefits/drawbacks depending on your exact need and infrastructure. Microsoft allows you to publish the VDI solution on its UAG portal/Trunk however it’s not straight forward and not well explained/documented.
For an introduction to VDI components, please check the following link.
To publish your VDI Pool on UAG for External users, you need to do the following:
1. Ensure the UAG server is fully updated and patched with latest UAG Service Pack and Rollups.
2. From the UAG 2010 Server Copy the file …Microsoft Forefront Unified Access Gatewaycommonconfrd-template.txt to …Microsoft Forefront Unified Access GatewaycommonconfCustom Updaterd-template.txt. This is needed to modify some RDP Parameters to make the VDI redirection work. For more information please check the attached link
For more information on the UAG Custom Update mechanism and a detailed example please check the following articles
3. Add the below two lines to rd-template.txt and save it in Custom Update folder (mentioned in previous steps).
use redirection server name:i:1
use redirection server name => Specifies whether a redirection server is allowed.
loadbalanceinfo => Contains the load balancing cookie used to choose the best server for the client computer. If you know your VDI Pool ID then you can change this command to be loadbalanceinfo:s:tsv://vmresource.1.PoolID
To get your VDI Pool ID, you need to connect to your Internal Connection Broker server then open the Server Manager – Roles – Remote Desktop Services – Remote Desktop Connection Manager – RD Virtualization Host servers– Pooled Virtual Desktops and then you can see all the properties including the Pool ID.
4. From your UAG Portal/Trunk add new Application – Terminal Services– Remote Desktop (Predefined).
5. In the Server Settings add the VDI Redirector session Host IP or Full Address and in the below space make sure to add all IP addresses or names of any system in your VDI solution (Session Broker, Gateway, Redirector, Session Host Virtualization and Virtual machines subnet). This is very critical step for the publishing rule to work fine. The Easiest thing is to add the full IP range for your VDI subnet. Then Activate your UAG.
Note: If you already created the VDI publishing application and it wasn’t working, make sure to delete this application, apply all previous changes and then add the application again, the Custom update changes won’t work for existing published applications.