iOS Receiver w/APM & StoreFront 1.2

As taken from my internal blog about "Citrix ICA Proxying (aka removing the requirement for a Citrix gateway on-site) v.1.1 (TMOS 11.4.1))

2014-08-08: A year (almost) after last updating this.. there is a new step .. to support Storefront 2.0+ by default, "APM recognizes /Citrix/PNAgent/config.xml as the default URL that Citrix Receiver clients (iOS and Android) request. If your Citrix Receiver clients use a value that is different from /Citrix/PNAgent/config.xml, you must configure a data group so that APM can recognize it." (http://support.f5.com/kb/en-us/products/big-ip_apm/manuals/product/apm-citrix-integration-11-4-0/2.html Well we know that Storefront 2.0+ uses /Citrix/Store/PNAgent/config.xml so we need to add these into a special data-group that APM is hard coded to look for (yet interestingly is not auto created???) .

modify ltm data-group internal APM_Citrix_ConfigXML { records add { remote.xx.catholic.edu.au { data /Citrix/Store/PNAgent/config.xml } } }

Hi Michael,

I've just installed and tested the hotfix. It works perfectly.

Thanks very much. Happy to provide any further info or assistance to anyone who needs it.

Cheers.

"To clarify, the correct configuration of the iRule data group would be Name = 'APM_Citrix_ConfigXML', String = VIP hostname e.g. 'apm.website.com', Value = full PNAGent path e.g. '/Citrix//PNAgent/Config.xml'."

Yes.

"Do we need a blank stream profile?"

Yes.

"Has the fix been tested with a specific iOS Receiver configuration?

For example, should we be using the automatic setup, with either the base (https://apm.website.com) or full URI (https://apm.website.com/Citrix/Store/PNAgent/config.xml), or a manual setup, specifying either of these formats, along with AG / Enterprise Edition types?"

Yes, iOS Receiver 5.8.2 has been tested with automatic setup configuration - just enter apm.website.com URL and the rest should be "magic". :)

Hi Michael,

I have opened a support ticket to request the HF as you suggested.

To clarify, the correct configuration of the iRule data group would be Name = 'APM_Citrix_ConfigXML', String = VIP hostname e.g. 'apm.website.com', Value = full PNAGent path e.g. '/Citrix//PNAgent/Config.xml'.

Do we need a blank stream profile?

Has the fix been tested with a specific iOS Receiver configuration?

For example, should we be using the automatic setup, with either the base (https://apm.website.com) or full URI (https://apm.website.com/Citrix/Store/PNAgent/config.xml), or a manual setup, specifying either of these formats, along with AG / Enterprise Edition types?

Thanks.

Yes, that is the one. What exactly is the error that you're getting with iOS? Also, what did you us to configure your Citrix environment? Did you use the latest iApp?

One thing I found out recently is that iOS client for some reason sense Accept-Encoding compression header, and if IIS is configured to process compression(it might) and sends compressed data in response to enum.aspx request, it will cause an error during account creation process. You can do a tcpdump to see if that's the issue on your end. if it is, you can add Accept-Encoding header to the list of headers to be removed in the HTTP profile assigned to your virtual, and it should solve that problem.

regardless, tcpdump data should greatly help troubleshoot this further.

Which engineering HF are those available in? We installed Hotfix-BIGIP-11.4.0-HF3-2419.40-ENG yesterday and are still experiencing the issue. I'm curious to find out if this HF resolves the problem for anyone else.

Yes, good news, there issue has been identified and fixes produced. If you are experiencing an issue with APM 11.4.0 HF3, please open a support case and request an engineering Hotfix for BZ427743 and BZ417908. Please advise the support engineer that this hotfix has already been built and they need to escalate the case to make it available to you.

Yes, we did identify this as an issue and are currently working on investigating and fixing it. As soon as we'll have an update, I will post it here - it should be very soon.

Yes, we did identify this as an issue and are currently working on investigating and fixing it. As soon as we'll have an update, I will post it here - it should be very soon.

Hi,

I am experiencing the same issue with Storefront 2.0. Access via the Web is working fine, as is the Windows Receiver. Cant seem to get the iPad receiver working though.

Looking through the forum posts here, it has been suggested that in order for a data group to work, a 'stream' profile must be attached to the Virtual Server. I have tried that though, and it doesn't seem to make a difference.