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!

External Lync 2013 Users Need a 2013 Edge Server to Use Mobility Services

3 thoughts on “External Lync 2013 Users Need a 2013 Edge Server to Use Mobility Services

  • September 12, 2014 at 8:40 am

    So – Microsoft recommends that we ‘wait until all users are OFF of the 2010 pool prior to migrating to the 2013 edge’ – I get that – but, I don’t see why I can’t go ahead and move over to the 2013 edge.

    I’m in pilot with the IT users over on the 2013 edge, and the rest of the enterprise on the 2010 side still – I really want to simply move the 2013 app pool to the 2013 edge. Maybe keep federation on 2010 – but, – I want the 2013 mobile clients to be able to get in.

    Are you saying that we could just go ahead and do it? Something that i’m really wanting to go anyways …

  • September 12, 2014 at 8:41 am

    I mispoke earlier, sentance one, paragraph 2 – I’m in pilot with the IT users over on the 2013 app pool, and the rest of enterprise on 2010 app pool … etc .etc. sorry. zzz

    • September 12, 2014 at 8:57 am

      Hehe, no problem Greg. In answer to your question, I would say yes – go ahead and do it. Once we’d moved the users over to the 2013 Edge, completing the transfer was quick and pretty painless. 2013 is fully supported and has several updates to bolster it. No reason to stay on Lync Server 2010 if you don’t want to.

      I doubt you will, but if you do run into trouble, please let me know and we’ll do our best to help you out.


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.