XenMobile 10.13 upgrade breaks LDAP configuration, should be fixed in rolling patch 1, EDIT: Rolling patch 1 fixes the issue 50% (use FQDN instead of IP on LDAP)
We tried upgrading (from XenMobile 10.12 RP4) to XenMobile 10.13: https://docs.citrix.com/en-us/xenmobile/server/whats-new.html, which resulted in our LDAP configuration to stop working.
After hours of troubleshooting and checking all ports, certs and IP’s of our domain controllers, Citrix support admitted there is a port bug in XenMobile 10.13.
The warning we received in the console looks like this:
In short, don’t upgrade to 10.13, yet! We had to revert our VM snapshot in order to get XenMobile working again…
EDIT1: We tried installing the Rolling Patch 1 (https://support.citrix.com/article/CTX289495), but the issue is still present sadly…
EDIT2: Apparently the XenMobile 10.13 RP1 fixes the issue partly. You need to change the IP address for the LDAP server to FQDN for it to work again:
Started working in IT since 2016 for several Managed Service Providers. IT is always changing, which is why I like to learn from others. A challenge is never too much and will try to get my work up to a higher level each time.
Personal characteristics:
Motivated, calm, sincere and honest
Free time spending:
Kickboxing, technology, cars and day trips
Hi Silas,
Can you confirm it has been fixed in RP1 (CTX289495) ?
Best regards, Joost
Dear Joost,
I haven’t tested the new Rolling Patch 1 yet. We just upgraded to 10.12 RP5 before new years.
Hi Joost,
To get back to you, we treid Rolling Patch 1 which still has the issue. Will be opening a case with Citrix again.
EDIT: issue is fixed in Rolling Patch 1, but you have to use FQDN instead of IP Address for the LDAP servers (Primary and Secondary Server)
It seems to be a bug on the NetScaler firmware. We built new NetScalers on 13.0.71.48 and LDAP failed. Downgraded to 13.0.71.44 and bingo – LDAP worked perfect. But I see you say fixed in Rolling Patch 1 – which was not available when we built so it may have been resolved through that. Hope that helps
Hi Philip,
There was also a NetScaler release where SSO was disabled globally. That was also something that broke our test environment at the time.