LYNC servers use topology builder to build the topology.

Put the topology information over SQL server

called CMS (Central Management Store)
Topology builder is the tool installed to architect your LYNC environment. Using topology builder you are
going to define pools, Sites, Server, Backend SQL DB server, what are the other features you are
required etc
The process of Defining the topology inside the topology builder is typically referred as authoring the
topology.
AD, SCHEMA and FOREST Preparation
Then prepare the AD schema to add new Objects and attribute classes for the LYNC
environment.
Prepare AD Forest for create the universal security groups and roles to provide role based access
control for the LYNC Environment.
We need prepare all the domains that are going to host or contain any of the LYNC server roles
or clients. This process will modify the access control list.
Forest and domain functional level should be windows 2003 or higher.
After completing all the above requirements and authoring the LYNC topology you need to publish the
topology in a backend SQL server database. Enterprise edition requires a full working version of SQL 64
Bit server Database.
Before installing LYNC you need to add the first server in the AD domain.
Every LYNC server in your environment is going to get a local copy of the CMS (Read only copy) (Central
Management Store). This database containing the topology and policy configuration in your
environment.
In an enterprise edition of LYNC there will be a backed SQL server that hosts the CMS. Every server will
get a local coy, a read only copy. To install LYNC you need to retrieve a local copy of topology from CMS.
Your LYNC server requires a certificate, possibly multiple certificates depending on the server roles that
you are going to deploy.
After installing the Microsoft LYNC server you can verify the installation from the LYNC control panel and
make sure the services corresponding the roles are started.
SQL server
In enterprise Edition of LYNC deployment we will have a central copy of CMS in the backend SQL server.
We deploy a topology on the SQL server where the CMS run.
Database Server Requirements:
SQL server 2008 R2 Enterprise 64 Bit / SQL server 2008 R2 Standard 64 Bit
SQL server 2012 Standard 64 bit
SQL server should be installed with the latest Service Pack
SQL server will be used as a backend database for front end pool, Persistent Chat server
Database, Archiving and monitoring Server database.
Each of the LYNC servers will contain a local copy of the CMS database and LYNC will install a
local copy of SQL server 2012 Express edition 64 bit on all of the LYNC servers.
LYNC server also support SQL server Mirroring (New feature with 2013).
Preparing the infrastructure and systems.
Memory Requirements for Enterprise edition front end server 32 GB, 2.26 GHZ Hex core
72 GB free space for OS and database local copies
Recommended to install OS in a RAID1 (Mirroring)
File Server Requirements
Enterprise edition of LYNC server requires a file server( File server share).
The file share is used by the enterprise edition of servers within a pool to share content across
pool such as application content.
Enterprise edition of LYNC server requires shared file storage for the servers participating within
the pool. With full control to the administrator.
This file share can be in the SAN, DAS, Clustered file share( for high Availability)
OS Requirements for LYNC server( on All the servers)
Windows 2008 R2 SP1 or higher
Powershell V3 (Windows Management Framework PowerShell V3)
.NET framework 4.5 or later( if you are installing 2012 server After the installation of .NET
Framework 4.5 install HTTP server activation from server manager, this is a server manager
feature.)
Windows Identity Foundation
IIS
Windows Desktop Experience.
Windows media format runtime.
Microsoft Message Queuing ( This component is for Persistent chat, Archiving and monitoring
support)
Certificate Infrastructure requirements

Internal DNS Requirements

Name resolution for pool. All the devices in the pool will be normally connected to a hardware load
balancer and a virtual IP (Single Virtual name against multiple IPs) will be assigned for all the servers in a
pool.

Eg:
LYNCPool.Costi.org 192.168.5.10
LYNCPool.Costi.org 192.168.5.11
LYNCPool.Costi.org 192.168.5.12

Defining LYNC server 2013 Topology
CMS (Central Management Store)
MS has moved away from storing the LYNC configuration information in the Configuration partition of
AD to SQL server. This is mainly because of reducing AD replication delay due to more data stores in AD
database.
Now we are using SQL server to store the configuration information about the LYNC configuration.
The database is called xds.mdf
Every LYNC server in the environment will store a local copy of topology information in the local SQL
database ( Express Edition of SQL installed with LYNC)
CMS database contains:
Topology Information
Configuration Settings
Policies
This information is replicated among other servers in the environment.
Your servers will use a share in the format \\servername\xds-replica . This share is used for replicating
xds database content among all the servers.
Defining the topology in the topology builder.
Topology builder is a tool that we will use to define the sites, Pools, servers( servers participating in front
end pool, mediation server configuration, gateway, etc)
SIP is the Session Initiation Protocol. In IP and traditional telephony, network engineers have always
made a clear distinction between two different phases of a voice call. The first phase is "call setup," and
includes all of the details needed to get two telephones talking. Once the call has been setup, the
phones enter a "data transfer" phase of the call using an entirely different family of protocols to actually
move the voice packets between the two phones. In the world of VoIP, SIP is a call setup protocol that
operates at the application layer.

in addition to simple telephone calls, SIP can also be used to set up video and audio multicast meetings,
or instant messaging conferences.
While defining Topology you need to specify the SIP domain,

Then Define the first Site Name ( here you can specify the site name as College or Brampton.

Front End pool FQDN (Here we are choosing whether we are using Standard edition or enterprise
edition of Lync.

When you choose enterprise edition you need to provide the name of the servers in the pool. If you
choose standard edition you dont have the option to provide a pool name. you can add up to 20 servers
in the pool.

Next will be the features that you are going to use in your environment. Instant messaging and presence
are always enabled. When you choose archiving it will enable exchange server integration.

Next is to choose to collocate the mediation server in the front end server. This is the server that
communicate with your gateway(IP/PSTN gateway)




Next is to define SQL server store



Nest is to define a file share for XDS

Next is for providing the web services URL (for internal and external)

Next is to specify the office 2013 web app server. This enables users to share and view
PowerPoint presentation during meetings with enhancements including animations, slide
transitions, embedded video and the ability for users to independently navigate slides.


Next is to define the Archiving SQL server store.

Define the Monitoring SQL server store.


After completing the topology builder you can verify or modify the parameters as shown
below.


Right click on enterprise Edition front end pool pool name properties



Once you complete the topology using topology builder you need to publish it in CMS. Also you
can edit the existing topology. When you are editing you are not editing the working copy. After
you complete the editing you need the republish it to effect the changes.

To publish the topology you need to do it from the topology builder as shown below.





Installing and setup LYNC Server


Installation process is broken up in to different pieces.