Home > Lync 2013 > LYNC 2013 – Test Lab Design

LYNC 2013 – Test Lab Design

I recently deployed Lync 2013 with great success and wanted to share a test diagram that depicts the infrastructure that was used.

In my environment we have the following requirements or constraints:

Environment Requirements\Constraints

  • Single Forest with Multiple Peer User Domains
  • No Split DNS, so all users are treated as External users
  • All IP addresses are publically routable – (Private IPs are used for test lab purposes)
  • DNS Load Balancing is used for all non-HTTPS Traffic
  • Hardware Load Balancing is used for all HTTPS traffic
  • Threat Management Gateway 2010 is used for Reverse Proxy role
  • We have no WAC or Office App server deployed
  • Only basic IM, Web Conferencing, Desktop Sharing, and Mobility is offered
  • No telephony or voice integration at the moment
  • Lync AutoDiscover SRV and DNS records point at the Lync Edge Access IPs
  • Mobile AutoDiscover points at the HWLB for the TMG Array
  • Public Certificates are used
  • Lync 2013 servers are running on Windows 2008 R2
  • SQL Servers are running SQL 2012 on Windows 2012
    We decided to go with Windows 2008 R2 on all of the Lync 2013 Edge and Frontend servers due to an issue with Certificates and the Windows Fabric Manager service.  After a lengthy Microsoft case, it was recommended we use Windows 2008 R2 until they fixed the bug internally.  (My project had a short deadline, so we did not have time to wait)

User Requirements

  • 75,000 Users
  • Basic IM, Web Conferencing, Desktop Sharing, Mobility, File Transfer, Outlook Integration
  • Mixture of Communicator 2007 and Lync 2013 clients
  • Broad BYOD mobile policy, where we support iOS, Android and Windows mobile devices
  • Multiple User domains
  • Archiving is Enabled – 30 day retention
  • Outlook Integration is Enabled
  • We only have a peak utilization rate of 15% for logged in, concurrent users.  (11,000 of the 75,000 at one time)
  • Note: Each virtual Lync Frontend server can support roughly 7,500 concurrent users, so scale accordingly.

Server Specifications:

3 Lync 2013 Front-end Servers – 16 GB RAM, 8 Logical Processors – Single 100 GB Volume

2 Lync 2013 Edge Servers – 16 GB RAM, 8 Logical Processors – Single 100 GB Volume

2 SQL Standalone Servers – 16 GB RAM, 8 Logical Processors – (1) 40 GB OS, (1) 100 GB SQL

1 SQL Standalone Quorum Server – 4GB RAM,  8 Logical Processors – Single 50 GB Volume

Note: All servers are Virtual Machines running on VMware.

Networking Specifications:

    • Publically routable IP addresses (not in the lab of course)
    • No Split DNS
    • DNS Load Balancing and HWLB design
    • SRV records point at SIP.domain.com, SIP.domain.com points at Lync Edge servers
    • Both TMG and Lync Edge servers have two NICs, in dual homed setup.
    • Edge and TMG are non-domain members

The Diagrams:

Lync2013-Test-Lab-Diagram

GET THE FULL FILE HERE – Lync 2013 PDF Diagram Download it now

I’ll get into the installation steps at another time, but this should give you general idea of how the architecture will look like when you don’t have split DNS, all IPs are publically routable, and all users must be treated as external users.

Best of luck!

Ed McKinzie

Advertisements
Categories: Lync 2013
  1. sarmakumar
    June 27, 2013 at 4:10 AM

    Hi,
    I am planning to deploy lync 2013 in lab environment, I have a question, is it possible to use Microsoft CA for edge external certificate,

    • August 6, 2013 at 10:45 AM

      You can use any signing CA server as long as that CA is in the Trusted Certificate store on every client connecting to your Lync servers.

      Cheers!

      Ed McKinzie

  2. Matt Ray
    August 13, 2013 at 9:15 AM

    Hi Ed, can you please clarify how many vCPUs your VMs have. By quad core 8 procs, do you mean 4, 8 or 32 vCPUs per VM? I hope it’s not 32!

    Thanks,

    Matt

    • August 13, 2013 at 11:31 AM

      Yes, it is only 8 vCPUs or Logical Processors per VM. I’ll update the doc.

      Thanks!

      Ed McKinzie

  3. HBleezy
    May 24, 2014 at 5:32 PM

    Hi Ed, you ran this in production? Based on the recent MS publication for Lync 2013 virtualized best practices, your VM seems extremely undersized for your user base.

  1. No trackbacks yet.

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

%d bloggers like this: