How to configure multiple ICG instances in UMS to support 3500 remote clients using a Citrix Netscaler to load balance and SSL Bridging using UMS 6.5.100 and ICG 2.2.100


Looking for info on what the correct way to configure multiple ICG instances in UMS to support 3500 remote clients using a Netscaler to load balance and SSL Bridging using UMS 6.5.100 and ICG 2.2.100

Learn more, read the entire thread inside the IGEL Community o Slack

Start here — kb.igel.com/igelicg-2.02/en/using-citrix-netscaler-adc-as-an-ssl-bridge-for-icg-31601172.html


The NetScaler SSL bridge documentation we have in the KB should only be used in a 1:1 manner and not for any sort of load balancing – the rmagent on the thin client becomes aware of the entire ICG topology once it registers to one so load balancing/availability is typically handled from there 🙂 you can typically implement something like Round Robin DNS for simple load balancing upon initial check-in, as well


Something else to look at … Is persistence

docs.citrix.com/en-us/netscaler/12/getting-started-with-netscaler/load-balancing/configure-persistence-settings.html


What type of SSL cert should I use? SAN or wildcard? Also, I am using an SSL bridge on the netscaler

Continue reading and comment on the thread ‘How to configure multiple ICG instances in UMS to support 3500 remote clients using a Citrix Netscaler to load balance and SSL Bridging using UMS 6.5.100 and ICG 2.2.100’.  Not a member? Join Here!

Learn more, search the IGEL Knowledge Base



Ask a question or comment on the above message thread?

Join or log in to the IGEL Community to ask us anything and meet other IGEL customers, partners, and EUC enthusiasts.

Submit a question, or Join Today!


Popular Message Threads


Categories & Tags: