I spent all this months introducing UC, showing solutions and their capabilities. Since I reach the 30th milestone post it is time to show how to deploy those solutions, starting with a Lync infrastructure. There are already several great blogs about this, but I will try make some things a little different … by going ‘behind’ the traditional step-by-step deployment, using my Reference Lab environment (RLab).
Although is just a lab, I intend to use it to support all my future posts based on it, following the names and updating diagrams as I extend it with more and new features.
So, like a real production environment, planning is the first and an important step and the Lync setup procedure really enforce you to do that. Reading the Lync planning guide can give a good overview, but Microsoft also create a capacity calculator and a planning tool that will help you about server sizing, TCP port requirements, firewall/DMZ configuration, …
I will start with a deployment of an Enterprise edition, and as for a lab, server sizing is not an issue (no more then 10 users) and will not follow some recommendations like a separate audio/video server.
Now let’s present the RLab v1.0 with this initial configuration and elements:
- built on a Vmware vSphere 5.0 platform;
- Windows 2008 R2 domain;
- Domain Controller, DNS and an Enterprise CA – Windows 2008 R2 Standard Core ;
- Database/File Server – Windows 2008 R2 Standard with and SQL 2008 R2 Standard;
- Lync Node #1 – Windows 2008 R2 Standard with a Lync 2010 Enterprise;
- Workstations – (2) Windows 7 x64 and (1) Mac OSX 10.6.
To minimize the number of posts to complete the setup, I will just consider for now: one Lync server, with internal IM, audio, video and web-conferencing. External connectivity, enterprise voice and other features will be included and ‘posted’ later.
If you intend to follow this deployment, familiar yourself with this names:
- Windows Domain: uc.lab
- Domain Controller: DC-10.uc.lab
- Database Server: DB-10.uc.lab (SQL instance: PRD)
- Lync Server Node#1: COMM-10.uc.lab
- Workstations: WS70, WS71, WS80
- Lync Enterprise Pool: uc.lync.lab
- SIP host domains: mylync.
- to minimize virtual resources, the Certificate Authority is installed on the Domain Controller. This is not recommended on a production environment and you should follow other resources to plan and deploy a CA;
- You should host the Lync user resources on your dedicated file share, if exists. Avoid using any Lync server of the pool;
- the setup procedures for the Domain, DNS, CA and SQL are not covered. Only the steps to complete a Lync setup will be documented on the next posts.
If I caught your attention, keep visiting this blog.
I intend to show how far you can build a rich UC infrastructure 😉