Installing Lync 2010 Edge Server – Part 1

I have written an article series on how to install a Lync 2010 Standard Edition Server. Read part one, two and three of the series before proceeding with the Edge install, as an internal Lync server is a pre-req for Edge server. I am using the same lab used for the std edition install and…

I have written an article series on how to install a Lync 2010 Standard Edition Server. Read part one, two and three of the series before proceeding with the Edge install, as an internal Lync server is a pre-req for Edge server.

I am using the same lab used for the std edition install and hence the IPs & domain name remain the same. The AD domain name is Exchangemaster.local on a 172.160.0/16 network. Following are the servers that I have in the internal network.

DC & CA                      172.16.0.1

Exchange 2010         172.16.0.4

Lync Std Edition       172.16.0.5

I am having split-DNS, which means I have a zone for my public domain exchangemaster.me in the internal DNS. My public domain is my email and sip domain. Since I have split-DNS, I already have admin, meet and dialin.exchangemaster.me pointing to my internal Lync server.

Let me give you a run-down of the Edge server setup.

  • I have an internal and external NIC. Internal NIC has an IP of 172.16.0.10 (internal AD range) and external has 192.168.0.230 (DMZ IP range).
  • I only have one public IP, which means I will be using different ports over the same IP for SIP, Web conferencing and Audio/Video.

Before we start to do anything on the Lync server, we need to update our topology to have a new Edge server. For that, we need to login to the Lync Front End server & run the topology builder. Do note that the builder needs to be run from the FE server, the Std Edition server in our case.

Right click on the Edge Pool in topology builder & select New Edge Pool.

New Edge Pool_1

Click Next on the Define Edge Pool page.

New Edge Pool_2

Enter the Edge pool fqdn, this will be your edge server fqdn as we are only planning to have one edge server. My edge server fqdn is lyncedge.exchangemaster.local (yes, the fqdn should match your internal AD domain name).

EM Edge Pool

Next windows gives us the option to select the features we need. We will select all three options – first one because we only have one IP address, second as we need federation and third as we will be using NAT.

New Edge Pool_4

We need to configure our external fqdns for Lync in the next window. As I only have one IP, all three services will use the same fqdn, sip.exchangemaster.me over different ports. If I had three public IPs, I could have published all three services on port 443 with different fqdn.

New Edge Pool_5

Specify the Edge server’s internal NIC’s IP address in the next window. In my case, this will be from the 172.16.0.0/16 range.

EM Internal IP

Next window needs the external IP address of the Edge server (DMZ or perimeter IP). Mine will be from 192.168.0.0/24 range.

EM External IP

Specify the public IP in the next window.

New Edge Pool_8

Select the next hop pool, which will be the front end server.

EM FE Pool

Select the check box to associate the front end pool with the edge.

EM Associated Pool

Click Finish and you will see the edge server in the topology builder.

EM Topology

Now we need to publish the topology so that the front end server is aware of the edge.

New Edge Pool_12

Make sure you have green tick all the way through and click Finish.

New Edge Pool_13

Clicking the to-do list highlighted above opens a text file, which instructs us to run Lync setup on the edge server.

New Edge Pool_14

Next step is to enable external access for users, federation and public IM connectivity. Launch Lync Control Panel, navigate to External User Access –> External Access Policy. Enable the options as in the screenshot and save.

Enabling external access global policy

Edit the Access Edge Configuration next. Enable the options as in the screenshot.

Editing access edge configuration

Before we start working on the edge server, we need to export the configuration on the Front End server and copy the file to a drive on the edge. For that, open Lync Shell from FE server and run Export-CsConfiguration –Filename c:\Topology.zip.

New Edge Pool_15

Copy & paste the file to the edge server’s drive. We will need it while we run Lync setup on edge.

This completes part one of the articles series. In part two, we will run the Lync setup on the edge server, play with the internal & external certificates, name resolution etc. Stay tuned!

Leave a Reply

Your email address will not be published. Required fields are marked *