In the sixths post in my series of installing a High Availability solution for Lync Server 2013 we are now going to create the Lync topology.
In the previous posts we have been making some of the fundamentals ready for the Lync installation, by creating a SQL 2012 mirroring cluster, a DFS file share and making a bunch of servers ready.
I will start by the drawing below, which will summarize how the servers is placed and how the servers is named.
Frontend Pool: FEPOOL01.exchangepro.local
Frontend Server 1: FE01.exchangepro.local
Frontend Server 2: FE02.exchangepro.local
Frontend Server 3: FE03.exchangepro.local
External Name: csweb.exchangepro.dk
SQL Mirroring Cluster
SQL Server Node 1: SQL01.exchangepro.local
SQL Server Node 2: SQL02.exchangepro.local
SQL Server Witness: SQL03.exchangepro.local
DFS File Servers
DFS Server 1: DFS01.exchangepro.local
DFS Server 2: DFS02.exchangepro.local
Director Pool: DIRPOOL01.exchangepro.local
Director Server 1: DIR01.exchangepro.local
Director Server 2: DIR02.exchangepro.local
External Name: cswebdir.exchangepro.dk
Mediation Pool: MEDPOOL01.exchangepro.local
Mediation Server 1: MED01.exchangepro.local
Mediation Server 2: MED02.exchangepro.local
Access Edge Pool: EDGEPOOL01.exchangepro.local
Edge Server 1: EDGE01.exchangepro.local
Edge Server 2: EDGE02.exchangepro.local
Web Conference: webconf.exchangepro.dk
Office Web Apps Farm: wacfarm01.exchangepro.local
WAC Server 1: WAC01.exchangepro.local
WAC Server 2: WAC02.exchangepro.local
Reverse Proxy Names
We have now come to the part where we will begin starting the installation of the Lync Servers.
The first server we will start with is Front End Server 1 (FE01).
Login to the server with an administrator account that is member of the following AD groups:
- Domain Admins
- Enterprise Admins
- Schema Admins
Insert the Lync CD or ISO file in the server and start the setup, and install the core Lync components on the C: Drive.
Click on Yes
Read the EULA and accept it if you can (if you can’t find something else to do )
When Lync has been installed the “Lync Server Deployment Wizard” starts automatically.
Click on the link to install the Administrative Tools and go through the wizard.
Next we will extend the AD with the attributes that Lync needs. You do that by selecting “Prepare Active Directory”
In this wizard you start with Step 1, which will extend the schema.
Start Step 1 by clicking on Run and follow the guide.
When that has finished successful wait 5-10 min until the changes has been replicated to the domain controllers. If you have an AD setup which consist of several AD sites you might need to wait longer depended on you replication schedule in AD.
In Step 3 you will run the forest prep, which creates Universal groups, settings, etc. in the forest.
Again when that is finished, wait 5-10 min (or longer)
In Step 5 you will prepare the current domain, so that you later on will be able to enable users from that domain.
Again when that is finished, wait 5-10 min.
Make you Administrator Account member of the following new Lync groups:
After you have made changes to the account, you should logoff the server and login again to the server, so that the account is active with the new groups.
You then create a new directory on the SQL Witness server (SQL03) which you name “LyncMirroring”.
You then share this directory so that the two SQL Servers (computer accounts) and the RTCUniversalServerAdmins has Full Control of the share and directory permissions.
You then start the “Lync Server Topology Builder”
The topology builder is used for creating the basic lync installation and the servers which are in the solution. You also use the topology builder later on if you are going to add or remove servers in Lync.
Before running the topology builder to add new Lync server components, you should make sure that the servers you are going to add, is member of the domain. Otherwise you will get an error when you deploy the topology.
The first time you start the topology builder you should select “New Topology” and click OK
Type a name for the configuration file and press Save
Type the domain name which is going to be you primary SIP domain – usually this is the same as the primary e-mail domain.
If you have other e-mail domains you can type them here. The public certificates will with extra domains be more expensive, so careful consider which domain you need to be able to assign to the users,
For now I will leave this empty.
Type a name for the first site
Type the details for the new site
Press the Finish button.
Type you frontend pool’s FQDN name, and make sure that it’s a “Enterprise Edition…”
To make the start installation simple I will only add one frontend server for now (the other two is added later on when the first server is running).
As a start I have selected these features for my pool.
A good advise is to always deploy the monitoring role in every installation that you make, because it contains very useful information about how Lync sees the quality of Lync calls, and also contains statics on the usage of Lync.
Do not collocate the mediation server on the frontend pool, if you are going to use sip trunks.
Select “Enable and Edge pool…”
Click on create a new SQL Store
Type the name for the first SQL Server, and write the name for the SQL instance you created when installing the SQL server.
Select “Enable SQL Server store…” and click New
Type the name for the second SQL server and instance
Select “Use SQL Mirroring….” And press New
Type the name for the Witness Server. The instance is normally the “Default Instance”
Select “Define a new file store”
Type the name for the DFS Name Space
Type the name for the External Base Url.
Click on New to Create a new Office Web Apps Farm
Type the farm name for the Office Web Apps pool.
On the Monitoring SQL Store, select the stores you created earlier
Click on New to create an Edge Pool
Type the Edge pool name and make sure that “Multiple Computer pool” is selected.
Select the button two (Xmpp can also be exclude if you don’t want to be able to communicate with for example google talk)
Select Next (remember you can’t use NAT when you have multiple edge servers)
Type the name for the three different services
Click Add to add the first Edge Server
Type the IP address for the Internal Nic on Edge server 1, and the FQDN name of the server.
Type the public Ip addresses for the external nic on Edge server 1
Click Add again to add edge server 2
Press Finish Again
Right Click on the “Lync Server” in the top and select “Edit Properties” in the menu
Scroll down to the buttom
Select the Front End pool that we created before to be the Central Management Store and press OK
Navigate to Director Pool under Lync Server 2013 if you are going to have a Director pool
Right click and select “New Director Pool”
Type the Director Pool name
Add the two director servers
Select the “Monitoring…”
Select the File Store you created before
Change the External base Url
Right click on Mediation pools and select New Mediation Pool
Type the name for the mediation pool
Type the FQDN names for the two mediation servers
Select the Edge pool and press finish
Right click on Site name and select Edit Properties.
Navgate to Site Federation and enable SIP federation and XMPP federation
Click on the little arrow next to the Mediation pool
Right click on the first Mediation server and select Edit Properties
Because I’m not going to use NAT for my sip trunk provider I will add the IP adresses that the mediation server must use.
The Primary IP address is the internal ip address of the server, which is used to communicate with the internal servers.
The PSTN IP address is the external IP address which is used to communicate with the sip trunk provider.
Do the same for the second mediation server
After we have added the director pool we will change the next hope pool so that it point to the director pool instead of the frontend pool.
This will cause the edge pool to route all traffic to the director pool, and the director pool will communicate with the frontend pool.
This will give us an extra layer of protection of the frontend pool from external attacks.
Right click on the Edge pool and Edit Properties.
Change the Next hop server to the Director pool
Navigate to PSTN gateways under Shared Components and right click and select New IP/PSTN Gateway
Type the FQDN name for the siptrunk provider you are going to use.
Select the port and protocol you are going to use with the sip trunk provider
I will recommend that you start using TCP until you have verified that the trunk is running fine and you can receive and make PSTN calls.
The reason for this is that when you are using TLS, all communication is encrypted and it can be pretty difficult to troubleshoot that.
When the traffic is working correctly you should change it to TLS is the sip trunk vendor supports it.
Click finish when you have made the configuration.
Nagivate back to the Mediation Pool and right click on it and select Edit Properties
Select enable TCP port and type the port that the mediation will listen on (typical 5060 or 5068). Also make the trunk the default.
You are now ready to Publish the configuration which will create the Central Management Store and the database that is needed. The structure in the Lync file store is also created in this process.
So to publish the topology right click on the site name and select Topology -> Publish
Select the first SQL Server and click Advanced
Select “Use SQL Server…:” and click OK
Select SQL server 2 and press settings
Type the share on the witness server you created in the start of the post.
The process will now start to install the new topology in the databases and should succed if you have made the permission on the SQL server and file share correctly.
You might get an warning on the DFS file share which is expected.
You have now created the Lync topology, in the next post we will start to install the actual Lync servers, which is quite easy, because we have already made most of the hard work in the topology builder.
We will also add the two last frontend servers to the topology, when the first frontend server is up and running.