To allow connections through Access Gateway from the different versions of Receiver, you need to create session policies and profiles with specific rules to make the connections to work. You can create separate session policies and profiles for the following:
Receiver for Android
Receiver for Blackberry 2.2
Receiver for Chromebook
Receiver for HTML5
Receiver for iOS
Receiver for Linux
Receiver for Mac
Receiver for Playbook 1.0
Receiver for Windows 8/RT
Receiver for Web
Access Gateway Plug-in
The following table shows the policy expression to configure based on the version of Receiver and the Access Gateway Plug-in you are using :
Receiver version does not support StoreFront services protocols
REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver && REQ.HTTP.HEADER X-Citrix-Gateway NOTEXISTS
Receiver version supports StoreFront services protocols
REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver && REQ.HTTP.HEADER X-Citrix-Gateway EXISTS
Access Gateway Plug-in for Windows & Access Gateway Plug-in for Mac
REQ.HTTP.HEADER User-Agent NOTCONTAINS CitrixReceiver && REQ.HTTP.HEADER Referer NOTEXISTS
Receiver for Web
REQ.HTTP.HEADER User-Agent NOTCONTAINS CitrixReceiver && REQ.HTTP.HEADER Referer EXISTS
Receiver for Windows 8/RT
REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver && REQ.HTTP.HEADER User-Agent CONTAINS WindowsRT
Receiver for Android
REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver && REQ.HTTP.HEADER User-Agent CONTAINS Android/
Receiver for Blackberry 2.2
REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver && REQ.HTTP.HEADER User-Agent CONTAINS Blackberry/
Receiver for Chromebook
REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver && REQ.HTTP.HEADER User-Agent CONTAINS Chromebook/
Receiver for HTML5
REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver && REQ.HTTP.HEADER User-Agent CONTAINS HTML5/
Receiver for iOS
REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver && REQ.HTTP.HEADER User-Agent CONTAINS iOS/
Receiver for Linux
REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver && REQ.HTTP.HEADER User-Agent CONTAINS Linux/
Receiver for Mac
REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver && REQ.HTTP.HEADER User-Agent CONTAINS MacOSX/
Receiver for Playbook 1.0
REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver && REQ.HTTP.HEADER User-Agent CONTAINS Playbook/
Receiver for Windows 8/RT
REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver && REQ.HTTP.HEADER User-Agent CONTAINS Win8/
Receiver for Windows
REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver && REQ.HTTP.HEADER User-Agent CONTAINS Windows/
Receiver for Windows Phone 8
REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver && REQ.HTTP.HEADER User-Agent CONTAINS WindowsPhone
Thank you for this awesome list. One more for you: REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver/CitrixVPN
Useful for the newish Citrix VPN client for Android.
Thanx 🙂
Great article! Bookmarked.
Have you found a way to enforce mobile users to a specific store on the StoreFront? I ran in to problems as I have the Unified Experience enabled which breaks the SSO on the mobile devices (at least on Android). I needed to setup a separate store for mobile users and now as they’re adding the Store they get to pick either the one with Unified Experience on or disabled. I would want to direct all of these users to the one that UE is disabled so they couldn’t mess the setup.
Hi Kari,
Well, you can do that by having a separate session “policy & profile” on Netscaler with higher priority then the current one. Of course you need to tweak the policy filter so you capture all mobile devices…