Lync 2010 mobile client problems in co existing migration scenario to 2013

We are in a process of migrating from lync 2010 to 2013. I have a problem with Lync 2010 mobile client that i can't understand. When a user is on 2010 pool ... the mobile client works from outside using 2013 edge. When i move the user to 2013 pool the client can't connect to the server.? Why is that? The 2013 client doesn't work at all since is not published with the TMG. All dns records still points to the 2010 pool .. that is federated with the 2013 pool.

Thank you
LVL 2
amnhtechAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Jeff_SchertzConnect With a Mentor Commented:
The 2013 Mobility clients are hard-coded to always use the external URL regardless of which web services (internal or external) they are pointed to via your Lyncdiscover configuration.  This is different than the 2010 behavior.

Neither client utilizes the Edge Server for registration; the 2013 client only uses it for media traversal and the 2010 does not use the Edge Server at all.  You MUST publish the 2013 external web services to support any mobile client connectivity for users on the 2013 pool.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.