A Lync Insider reader emailed me the other day, asking about Mobility Services. His external users couldn’t log in using Lync Mobile, and he wasn’t sure why.
After reviewing what he said, I thought it sounded similar to a problem we encountered during the Moving to Lync Server 2013 process.
The Problem: Everything’s Working, Except Mobility Services for External Users
The reader (let’s call him Bob) runs Lync Server 2010 Standard Edition. A 2010 Front End pool and a 2010 Edge Server, in place and properly configured. Voice, video, chat, mobility services, and federation all work fine.
Bob introduces a Lync Server 2013 Front End server in a new pool, in co-existence mode. Following configuration, Bob finds that just about everything is–still working fine!
Except for one thing. A Lync 2013 user, when signing in externally with Lync Mobile, experiences an error.Â Can’t Connect to Server. It may be busy or unavailable.
What’s going on here? Bob checks his Edge Server. DNS and push settings are configured. Internal Lync users on both Lync 2010 and Lync 2013 have no issues. External users can use voice and video.
It’s just Mobility Services which aren’t working on the Lync 2013 server. Why not?
The Solution: A 2013 Edge Server is Needed
In Part 7 of the Moving to Lync Server 2013 series, I mentioned a change we made after implementing the 2013 Edge Server:
“Larry also pointed the 2010 topology to the 2013 Edge server. External DNS must point to new Edge only. The new Edge Server (provided DNS is updated) will work for both 2013 and 2010 users.”
Here is the solution for Bob’s problem.
You do need a 2013 Edge Server to fully use Mobility Services. The new Mobility Services in 2013 is designed to take tablets into account; Lync 2010 didnâ€™t have that functionality native. (Cumulative Updates did allow for tablet support, but itâ€™s better-supported in Lync Server 2013.)
We encountered a Lync Mobile error similar to Bob’s while troubleshooting the 2013 Edge. Even though most of our users still used Lync 2010 clients, we moved all users from the 2010 Edge Server to the new 2013 Edge Server.
Everyoneâ€™s Lync clients worked without a hitch, irrespective of platform, after that. Including Lync Mobile.
Bob thought he’d just missed a settings tweak. He didn’t; in fact, he’d done a very thorough job on his topology. What he was missing was an additional Edge Server. With that in place, Mobility Services for Lync 2013 works!
If you’re planning to use Co-Existence Mode to transition from Lync Server 2010 to Lync Server 2013, take note. A 2013 Edge Server is critical to begin transitioning Lync users. Not to mention mobile access.
Have you encountered a mobility error like this? Let’s discuss!