address it just automatically redirects to the /http/server/Citrix/Mobile/config.xml just as it does in IE. Once we upgraded we were able to just have our users put in the. Windows 4.1 (std) Windows 3.4 (ent) Windows 8.

Single authentication to the Access Gateway: Use of a single session for both VPN and clientless access so that a Receiver user logs on once for both types of access and consumes only one license. Linux 13.0 IOS 5.8.3 Android 3.4.13 HTML 5 1.2 Playbook 1.0 Blackberry 2.2 / BlackBerry 1.0 Tech Preview The following Citrix Receiver models do support SHA2 as of. Citrix Receiver 3.4 for Windows (CitrixReceiver.exe) provides the following new features and enhancements. From there select Citrix XenApp and Legacy Clients from the selection lists. The following Citrix Receiver models do not support SHA2 as of This mostly affects the mobile receiver. To download that version you have to log into Citrix and head to the downloads section. Currently we are using the enterprise version of the Receiver for Windows, as it allows for SSO without a ton of extra configuration. I have seen this before when we were on an older version of the Receiver and Citrix Access Gateway VPX. The primary driver has been the need for some of the fixes that have not been backdated to the 3.4 Receiver, and the fact that Citrix is pushing all the development on this new version.

When I enter in IE, it does redirect to but shouldn't the receiver do that too? My only issue is that if the server I add in the receiver goes down, users won't be able to connect / Im currently preparing to rollout Receiver 4.1 in our environment. it doesn't work if I just use - it does on mobile receiver clients. Ok, got a bit further now, basically I have to provide the following address:

Citrix receiver 3.4