Lync 2013 Complete Lab Guide Using Single Public IP Address – Part 1 – Setting Up the Lab

The following guides will walk you through setting up a complete, fully functional Lync 2013 Standard Edition deployment complete with Enterprise Voice, Remote Access, Mobility and Exchange Integration. Before we embark on this it is important to understand that this is for Lab purposes only and should not be used in any production deployment.

At times this guide will deviate from Microsoft Best Practices in order to achieve the end goal of emulating a deployment in the real world. I think it is a good idea to outline these now before we start so that you are aware

Guide Liberties

  • We will be using only 1 public IP address instead of the minimum recommended of 2 for the simple reason, I only have one
  • We will be installing the Lync Edge Server in the same LAN segment as the front end server because my lab kit does not support multiple network segments
  • We will be using non standard ports for some services in order to achieve a fully featured environment
  • We will be using our own Certificates from the Internal CA for external access because I am not spending money on proper certificates in a Lab

To begin this Lab, lets start with the basic requirements

Physical Server Requirements

COMPONENT CAPACITY
CPU 2 x Quad Core Intel 1.86GHz
Memory 32GB
Hard Drive 470GB RAID 5 10K SAS
Networking 1 x GB/s Ethernet
OS Microsoft Server 2012 Datacenter

In order to create the servers required for Lync we will use the Hyper-V role of Microsoft Windows Server 2012 to facilitate this.

Hyper-V Installation

This guide will not cover the exact steps to install Hyper-V but you should add the role and accept the defaults unless you know what you are doing. Once Hyper-V is installed you should configure a Hyper-V virtual switch that has access to your LAN.

Virtual Machines

The following Virtual Machines will need to be created. Replace the IP addresses with the IP range of your LAN

VM Name CPU Memory HDD Networking OS IP Address
DC01 1 vCPU 2048MB 40GB 1 vNIC 2012 DC 172.198.255.41
EX01 2 vCPUs 6144MB 100GB 1 vNIC 2012 DC 172.198.255.42
LS01 2 vCPUs 6144MB 100GB 1 vNIC 2012 DC 172.198.255.43
LE01 1 vCPU 4096MB 40GB 2 vNICs 2012 DC 172.198.255.44, 172.198.255.45
PBX 1 vCPU 2048MB 20GB 1 vNIC TBC 172.198.255.46
WA01 1 vCPU 4096MB 40GB 1 vNIC 2012 DC 172.198.255.47
RP01 1 vCPU 2048MB 40GB 1 vNIC 2008 R2 172.198.255.48

 

Build each of the virtual machines to the base Operating Systems shown.

Firewall Requirements (NAT)

While these virtual machines are building you can get your firewall NAT translation rules ready. You will need these for providing external access to your Lync Lab

Source

TCP/UDP Port Destination

ANY

TCP 80 172.198.255.41

ANY

TCP 443 172.198.255.47

ANY

TCP 442 172.198.255.45

ANY

TCP 5061

172.198.255.45

ANY TCP 446

172.198.255.45

ANY UDP 3478

172.198.255.45

ANY

TCP & UDP 50000-59999

172.198.255.45

ANY TCP 5060

172.198.255.46

ANY TCP & UDP 5004-5005

172.198.255.46

ANY TCP 5269

172.198.255.45

Public DNS Requirements

You will need an external domain name to use if you want external access. For simple reasons this will form the name of our Active Directory Domain Name to make certificates a little easier to generate. Lync requires a number of DNS records for its services to be published to the external DNS zone of your domain name. As these changes can take upwards of 24 hours to propagate it is best these get changed now before the Lab is ready. This way you get to test immediately when your lab is ready.

Name Record Type Value
meet A Public IP of Your Router
dialin A Public IP of Your Router
lyncdiscover A Public IP of Your Router
lyncweb A Public IP of Your Router
sip A Public IP of Your Router
lyncadmin A Public IP of Your Router
mail A Public IP of Your Router
autodiscover A Public IP of Your Router
webapp A Public IP of Your Router
webconf A Public IP of Your Router
av A Public IP of Your Router
crl A Public IP of Your Router
_sip._tls SRV 1 442 sip.domain.com
_sipfederationtls._tcp SRV 1 5061 sip.domain.com
_xmpp-server._tcp SRV 1 5269 sip.domain.com

Once you have these in your external DNS you have satisfied the external networking requirements for Lync.

Download Supporting Software

You will need the following Software Downloaded to a file share in addition to the Operating Systems

Product Download Link
Exchange 2013 SP1 http://www.microsoft.com/en-gb/download/details.aspx?id=41994
Lync 2013 http://products.office.com/en-us/lync/lync-server-2013-free-trial-unified-communications
UCMA 4.0 http://www.microsoft.com/en-gb/download/details.aspx?id=35463
Office 2010 Filter Pack http://www.microsoft.com/en-gb/download/details.aspx?id=17062
Office 2010 Filter Pack SP2 http://support.microsoft.com/kb/2687447
Office Web App Server http://www.microsoft.com/en-gb/download/details.aspx?id=35489
Lync Client Basic http://www.microsoft.com/en-gb/download/details.aspx?id=35451

This completes Part 1 of the Lab. In this part we should have completed the setup of the Hyper-V server, created all virtual machines and installed the required operating systems in preparation for the configuration. We should have also created all the firewall access rules and port forwards as well as setting up the external DNS zone of you domain. In Part 2 we will setup the pre-requisites needed for Lync including domain, certificate services, exchange, reverse proxy and office web apps

One thought on “Lync 2013 Complete Lab Guide Using Single Public IP Address – Part 1 – Setting Up the Lab

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s