Home » Posts tagged 'Lab Guide'
Tag Archives: Lab Guide
Lync 2013 Complete Lab Guide Using Single Public IP Address – Part 2 – Building the Pre-requisites
In Part 1 we covered the basic physical, virtual machine and networking setup. In this section we will build the domain, install certificate services, office web apps server and exchange 2013. Please note that these setup processes will not be a deep dive step by step guide and will expect you to have a base knowledge of all technologies discussed.
Building the Domain
On the VM DC01 install Active Directory Domain Services and DNS roles. Once installed promote DC01 to a domain controller. Remember to name your Active Directory Domain the same as your external Public domain name. Once promoted reboot the server and continue to configure DNS. There are several DNS records internally required for Lync 2013 and these need creating manually in the AD DNS Zone. Add the following DNS records to the AD Zone:
Mark is an Independent Microsoft Teams Consultant with over 15 years experience in Microsoft Technology. Mark is the founder of Commsverse, a dedicated Microsoft Teams conference and former MVP. You can follow him on twitter @UnifiedVale
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
Mark is an Independent Microsoft Teams Consultant with over 15 years experience in Microsoft Technology. Mark is the founder of Commsverse, a dedicated Microsoft Teams conference and former MVP. You can follow him on twitter @UnifiedVale