With the Lync 2010 mobility add-on out in the wild for quite some time now I see an issue that comes looking round the corner in almost every deployment. It’s called internal wifi clients.
This article explains the certificate error that can appear if your environment is incorrectly configured. Use this article by Lync MVP Jeff Schertz if you haven’t configured your Lync environment for mobility yet.
Introduction
While external desktop clients need both the Lync 2010 Edge server and a Forefront server in the DMZ, the lync 2010 mobility add-on is designed to work via the reverse proxy only (Forefront TMG is used in this article). While this seems logical for external clients, internal clients should use the forefront server as well to reach the mobility website. So if you have iPhone or iPad clients on the internal wifi network, some adjustments have to be made to your lync deployment.
This article uses a simple setup to explain the issue, however the same problem can exist if your setup has split up the Lync roles across multiple servers. This article uses an infrastructure with the following features:
- Simple Lync environment with 1 internal server, 1 edge server and 1 forefront server.
- Split brain DNS configured.
Internal mobile clients connect to a lync environment as follows:
- The internal employee logs on using the Lync 2010 mobile client (i.e. Lync for iOS)
- The client looks for the lyncdiscoverinternal.company.com DNS record. In most deployments, split brain DNS is configured, so your public DNS zone is also configured on the internal DNS environment.
- The lyncdiscoverinternal record points to your forefront server, which in turn redirects you to the internal site on your lync server (on port 443).
- Here, it downloads a file with information about the autodiscover configuration, which tells the client where to find the external Lync site.
- You are now redirected to the external site on the Lync server (on port 4443).
Forefront Setup Continue reading



