Issue: Lync Mobility not working.
Error: Can't connect to the Server. It may be busy or temporarily unavailable. Please try again.
Problem Statement: Recently I have implemented Lync Mobility on Lync Server 2013, configured Server corrected.
Not using Edge server, just using reveres proxy for external mobility and simple URL access.
· Configured reverse proxy correctly, means VIP external interface listening on 443 and 80 and forwarding to FE pool 4443 and 8080.
· Certificate and DNS record was correctly configured.
· However still mobility was not working.
Resolution:
I was getting autodiscover traffic in FE and was seeing autodiscover entries in IIS log.
However Lync 2013 login on mobile was not working.
Checked Reverse proxy configuration and found Persistence profile shows cookie persistence.
Removed cookie persistence and checked Lync sign-in mobile and everything works as expected.
Means Lync Server 2013 does not required cookie persistence.
Microsoft documents shows below: [Cookie-based affinity will not affect]For deployments that will not use cookie-based affinity:
· On the reverse proxy publishing rule for port 4443, set Forward host header to True. This will ensure that the original URL is forwarded.
For deployments that will use cookie-based affinity:
· On the reverse proxy publishing rule for port 4443, set Forward host header to True. This will ensure that the original URL is forwarded.
· Hardware load balancer cookie MUST NOT be marked httpOnly
· Hardware load balancer cookie MUST NOT have an expiration time
· Hardware load balancer cookie MUST be named MS-WSMAN(This is the value that the Web services expect, and cannot be changed)
· Hardware load balancer cookie MUST be set in every HTTP response for which the incoming HTTP request did not have a cookie, regardless of whether a previous HTTP response on that same TCP connection had already obtained a cookie. If the load balancer optimizes cookie insert to only occur once per TCP connection, that optimization MUST NOT be used
You get the complete Hardware configuration details on below site:
Thank you