Automatically offering optimal Citrix connectivity method for Windows and Mac clients
I'd like to ask about a long-standing issue that we have with enabling access to our large Citrix XenDesktop environment for both Windows and Mac users.
We have a very large XenDesktop deployment used by hundreds of external vendors and contractors. The mix of clients is huge and as such must offer as 'client agonostic' solution as possible.
The problem we have is that it's very difficult to create Resource Profiles that automatically offer the best client option for both Windows and Non-Windows clients.
Resource Profiles only allow you to configure one type of client: CTS, WSAM or JSAM. Our desire is to use CTS (ActiveX + Citrix Receiver) for Windows clients and JSAM (Java + Citrix Receiver) for Mac clients. There is however no option to say 'auto-detect based on client capabilities'.
Because of this, we've had to resort to creating two separate Resource Profiles (A Windows version with CTS and a non-Windows version using JSAM) and then tie those Resource Profiles to a platform-specific Role that is dynamically assigned to the user's session at login, based on the User Agent.
This solution is very much imperfect and creates all sorts of problems with Host Checker not properly rejecting the user's login if the Host Checker policy does not pass.
In short: its a hack and an ugly one.
This really is an incredibly clunky way to accomplish what should be something that is taken care of automatically - so much so that I'm wondering if we are missing a trick here? Is there a simpler way to do it? Is there an easier way to provide cross-platform access to Citrix XenDesktop that automatically detects the client and offers the most appropriate method (CTS, JSAM, WSAM) automatically?
If not, are there updates planned that will address this in the future?
Re: Automatically offering optimal Citrix connectivity method for Windows and Mac clients
That is the solution to allow connectivity if HTML5-based VDI/Storefront and/or L3 VPN is not desired or possilbe. As far as future planning, I cannot comment on that; but it would be a good idea to bring up to your account team. For the roles, I would recommend user-agent for assigning the roles rather than Host Checker.