In my environment the TMG server is already in use to publish Exchange web services(OWA, Active Sync, Outlook Anywhere) . Since this is a single NIC TMG, you can only create one listener. If you try to create another listener for Lync services, an error “A web listener specifying the same port and similar IP Addresses already used by the rule “[Your_Exchange_Services_Rule]”. The port and IP addresses specified in a Web Listener cannot overlap with the IP addresses specified web listener already used in a different rule”
To overcome this issue, simply use the same listener with a SAN certificate that contains both Exchange and Lync services FQDN.
For example, my original SAN certificate for Exchange is inclusive of webmail.domain.com , autodiscover.domain.com. I regenerated a new certificate in Exchange server with additional SAN which is required by Lync mobility services - lyncdiscoverinternal.domain.com , lyncdiscover.domain.com and etc.
After that, I went ahead to request new certificate from Lync Front End server with the same SAN (inclusive of Exchange web services FQDN) and we are almost good to go.
In TMG server I removed the original listener, and created a new listener by using the certificate which is newly created (In my case I export the certificate from Exchange server), followed by creating a new publishing rule for Lync discovery. When the rule is created and the moment I clicked "Test Rule" , it is showing a positive passed result and Lync mobility is ready to go live!
This is just an overall concept on how to deploy Lync mobility with TMG single NIC configuration, I hope this will at least provide you with some ideas if you have the same environment as mine.
No comments:
Post a Comment