I recently enabled the new 2013 mobile client for a couple of customers, through the Lync Server 2013 February update (aka CU1). One of the deployments was a Migration scenario from Lync Server 2010, whereas the other was a “first timer”. A couple of experiences to make notice of:
1. When you have a migration scenario, make sure you update your Reverse Proxy to publish the 2013 pool, or the new UCWA web Components will not be available
2. The Lync 2013 mobile client relies on the external web servides for mobility service, so make sure you also direct your INTERNAL users to the Public Reverse Proxy address (or they will Connect to the 443 port instead of 4443).
3. Since your mobile clients will get the final connection info through the Autodiscover Service, they will also need to be able to lookup the external web services FQDN, which they will get, which also needs to point to the Public Reverse Proxy address for proper Connection.
So, a quick summary:
- Internal DNS, lyncdiscover.<sipdomain> -> Public IP address of Reverse Proxy (for initial lookup)
- Internal DNS, extpoolFQDN.<sipdomain> -> Public IP address of Reverse Proxy (for Connection)
- Reverse Proxy Publishing rule -> Internal Web Pool address port 4443
Especially when having a split-brain DNS, for which the internal DNS is authorative for the same namespace as the public one, the extpoolFQDN record can kinda throw you off – at least it did for me – since you would not normally need to apply that. At least it’s not mentioned anywhere.