Publish Microsoft Lync Server 2010 Web Services and Simple URLS through ISA Server 2006
Posted by Chad McGreanor on October 6, 2010
With Lync Server 2010 we still need to publish a Web Services URL. In addition to that URL we also need to publish 2 other Simple URLS. Meet.domain.com and Dialin.domain.com. The meet url is used for attending meetings this also replaces the use for Live Meeting. Dialin is for users to set their dialin conferencing pin and to find local access numbers.
I created 3 new A records:
These are fictional but you get the point.
lync-abs.domain.com
meet.domain.com
dialin.meet.com
I created a new web listener and a new firewall rule in ISA server 2006. I added the 3 domain names to the public names tab and under bridging I changed the port to 4443 since that is where Lync Server 2010 is listening in this version. I also purchased a new GoDaddy certifiacate with lync-abs.domain.com as well as the other domains in the SAN field and assigned it to my rule in ISA. I needed to assign another external IP addres to ISA as well due to other services already running port 443, like OCS 2007 R2 (we are in co-existence mode now).
I will post more detailed information shortly but it is all working on 1 ISA server.
Steve said
Hi
I couldn’t get this working, I just get no reply fromthe Lync Server.
Also, what did you use to request the certificate, and generate the CSR? I had to use the Exchange console to do this as the Lync certificate tool does not allow you to request a new common name, in your case lync-abs.domain.com, as it is hard coded to use your edge or internal names. What did you do about this?
Cheers
Chad McGreanor said
The documenatation that is available for OCS 2007 R2 reverse proxy can be used for Lync for the most part. If you have other services running on ISA that use the same port you will need a seperate IP assigned to the ISA server for Lync. The major change here is that Lync external services are running on a different port (4443). When you configre ISA you need to ensure the port you are forwarding to is configured correctly. As far as generating the certificate I used IIS installed on ISA to generate the CSR.
Bob said
Hey Chad, quick question if you don’t mind:
The Web Service URL: I am assuming that is the director’s URL if I have a Director configured. However, my question is in the topology builder there is a “External Web Services FQDN” under both the SE Front end Web Services properties, and the Director’s Web Services Properties. Should these both be set to the same FQDN (my director?)
What I am seeing right now is that when I have a meeting w/2 users – one internal, one external, the external user cannot see the meeting content because the internal user is uploading the content to C:\Share\1-WebServices-1\MeetingContent and I am assuming the external user is trying to read the content from C:\Share\1-WebServices-2\MeetingContent which is empty.
Again, thanks for your article.
Bob
Bob said
Well, never mind – looks like the Topology Builder will not let you make them the same…