Lync2010 pre-requisites

By |2017-12-11T17:26:04+00:00August 24th, 2011|Lync|0 Comments

There was a requirement for us to create a document recently which listed some general Lync2010 pre-requisites.

Thought it would be quite useful to others and so have pretty much copied it into this blog.


1.  Introduction

This document aims to detail all the pre-requisites and minimum server hardware specifications for the installation of Lync2010 into your environment.


The items detailed are based on the minimum requirements to facilitate the supported operation of Lync2010, it should be noted that more specific requirements for your own estate would be driven out as part of a typical design engagement.

2.  Server hardware requirements

The following details the minimum requirements for the relevant Lync2010 roles; these have been split into Virtual and Physical recommendations accordingly.

Table 1 – Hardware configuration – Front-End Server, Edge, Director

Physical Front-End Server, Edge Server

Hardware Item


Base Server CPU

64-bit dual processor, eight-core, 2.0GHz or higher (min)

Total RAM

16GB (Min) (4GB for Director)

Disk configuration

2 x 72GB disks for O/S

Table 2Hardware configuration – Back-End Server, Archive & Monitoring     

Back-End Server, Archiving & Monitoring Server

Hardware Item


Base Server

64-bit dual processor, quad-core, 2.0GHz or higher (min)

Total RAM

32GB (Min) (16GB for Archive & Monitoring)

Disk configuration

2 x 72GB disks for O/S + Disks as per SQL guidelines

Table 3 – Virtual Server configuration – Director

Virtual Director

Hardware Item


Virtual Server CPU allocation


Dedicated RAM

4GB (Min)

Table 4 – Virtual Server configuration – Front-End, Edge, Archive & Monitoring Server

Virtual Archiving & Monitoring Server

Hardware Item


Virtual Server CPU allocation


Dedicated RAM

16GB (Min)


Example (minimal) disk configuration for the Back-End Server role is as follows:

Table 5 – Back-End server disk configuration example

Back-End Server disk configuration

Disk Number


Drive Letter







SQL Logs




SQL Data



Note: If configured the CD / DVD drive will be assigned the Z: drive letter.

Note: All virtual servers must run Windows 2008 R2 Operating System


3.  Active Directory configuration

Lync2010 requires that the Active Directory Domain Services (AD DS) be extended with classes and attributes specific to the product. As per previous versions of the product these extensions require the operator to function as a member of the Schema Admin, Enterprise Admin, and Domain Admin groups dependent upon which of the extensions is being performed.

The AD DS extensions must be run from either Windows 2008 SP2 or Windows 2008 R2 and they must operate as 64-bit – this is because the tools to extend the schema are 64-bit only.

A comprehensive list of all schema class and attribute additions can be found on the following website: 


4.  Lync2010 Configuration

Lync2010 should be installed and then immediately updated with all the latest KB’s available from Microsoft. Risual highly recommend the installation and running of the Lync2010 Best Practise Analyser (BPA) after installation, all pertinent updates will be identified by this tool.

Microsoft Update Resource Centre for Lync2010:

There are a number of pre-requisites which are required dependant on the role being installed. The following are the requirements to simply run the Lync installation wizard:

·         .net framework 3.5.1

·         Visual C++ 2008

·         OCSCore components

·         If a Front-end is being installed there are also the following additional requirements:

·         Active Directory Admin Tools

·         Message queuing Services – Directory integration

·         IIS 

5.  Hardware Load Balancer requirements

Hardware Load Balancers are required to provide the balancing and affinity of HTTP/ HTTPS traffic to both Enterprise Edition Front-End servers, Director pools and Edge pools.


A single device can be used to balance these pools so long as it can have legs in the different security boundaries (i.e. DMZ for Edge and Production for FE).


Microsoft offers an interoperability page which details all of the HLB devices on the market which are supported for use with Lync201, see link below:


Note: a HLB is only required for Enterprise edition FE’s and Edge/ Director pools. Standard edition Lync2010 and single Edge/ Directors do not require a HLB.


6.  DNS Requirements

Lync2010 has a number of requirements, both internal and external, for the creation and usage of DNS records.


Internal DNS records are required to allow the automatic sign-in of Lync clients and Lync phones as well as providing other key functionality such as DNS Load-Balancing.


External DNS records are required for provisioning external access to clients, federation with other companies/ PIC (MSN, Yahoo, AOL) and online meetings etc.


7.  Certificate requirements

Lync2010 operates on TLS and therefore requires certificates to complete the signing process; this means that there are certificate requirements both internally and externally (if you are planning on Edge).


Internal certificates can be facilitated by an internal Certificate Authority so long as the root and issuing certificate servers has been published to Active Directory allowing all servers to trust the chain. Microsoft CA with an active Web Server template is a typical requirement to fill this role. It is also possible to use an external CA to provide certificates for use internally but this is not typically a seen as a cost-effective solution.


External certificates are required to facilitate external user login, federation and online meetings. The certificates used for external services need to come from a trusted external source (i.e. VeriSign) so that external parties automatically trust the certificate chain. Again, it is possible to use an internal CA for this process but for everyone outside of your organisation that you want to federate or support online meetings with you would need to get them to install a copy of your issuing and root CA’s.


Self-signed certificates are not suitable for use with Lync2010.


8.  DHCP requirements

If you plan to deploy Lync phones in your organisation then there may be a requirement for some specific DHCP requirements. You will need to operate DHCP on a 64-bit server to facilitate the usage of the DHCP record creation tool that comes with Lync2010. The records created by this tool are in binary format and so although they can be entered manually if needs be, it’s much simpler to let the tool input them for you.


The phones that require these DHCP records are:


Currently the models that require this authentication process are: Astra 6721 and 6725, and Polycom CX500, CX600 and CX3000.


9.  SQL Requirements

SQL is required both for the back-end database and also for storing the Archive and Monitoring details. SQL 2008/ R2 are supported and standard edition can be used so long as you don’t require any more than two nodes in the SQL cluster.

SQL reporting is also a requirement if you plan to install the Lync monitoring server.


10.      Enterprise Voice requirements

Depending on your phone system or requirements a connection to and from your existing PBX can be facilitated either by Direct SIP, if supported, or via a gateway device which essentially does the conversion and routing from PSTN to SIP. Specifics around your particular requirements would have to be driven as part of the design process as there are no real PBX generics.


Details of supported PBX’s for Direct SIP as well as supported gateway providers can be found on Microsoft’s interoperability page:


11.      Supportability requirements

The following should be considered when looking to deploy Lync2010 to your organisation.

1.     Windows XP SP3 is the minimum requirement for Lync client installation – anything older will have to use the OCS 2007 R2 client (MOC)

2.     The Active Directory Domain and Forest functional level is required to be a minimum of Windows 2003 Native mode

3.     A Reverse Proxy server is required to publish access to web services when an Edge Server is deployed

4.     When deploying a pool of Edge servers a HLB is the preferred solution. When using a HLB for an Edge pool NAT’ing of internet IP’s is not supported, they must be routable. Also, in terms of external IP requirements, 3 external IP’s are required for the HLB and a further 3 per Edge server in the pool (2x Edge servers with 1x HLB = 9 routable internet addresses)

5.     All Lync2010 virtual servers require Windows 2008 R2

6.     HLB required for Enterprise edition FE and pools of Edge/ Directors only



Hope this helps



Leave A Comment

like what you see? 

Sign-up to our newsletter and never miss out on the latest blogs, events and tech news from the world of risual
Give it a try, you can unsubscribe anytime.