Lync Virtualization Whitepaper

Just wanted to get this out there as it’s a revamped whitepaper. Get it here. Pay special attention to the mixing physical and virtual servers section.

This is somewhat confusing but it states:

2.5.1 Mixing Physical and Virtual Servers Running Lync Server 2010

Generally physical and virtual servers can be combined in a deployment, with the following limitations:

Mixed virtual and physical servers within the same pool are not supported. A pool[1] of Lync Server roles must be deployed as a homogenous set of servers (either physical or virtual) which roughly provide the same amount of resources. For virtualized deployments, ensure that the virtual machines are hosted in a way that equal resources are available to each guest in the pool. Lync Server does not perform load-based load balancing with the exception of the A/V conferencing workload. Note that a virtual Front End Server and a physical SQL Server Back End Servers are explicitly supported.

Balanced end-to end-performance is required. When sizing a virtualized Lync Server deployment, use the guidance provided in this document to size each role adequately, and perform tests using the synthetic load tools available to validate that no bottlenecks exist.

[1] A pool is defined as a Lync Server pool with more than two servers including the follow Server roles: Enterprise Edition Front End Server, Director, Mediation Server, A/V Conferencing Server, and Edge Server.

So if you have a pool of 4 front ends you can not have 2 virtual and 2 on physical servers. They must be all one or the other. But you can have 4 virtual frontends and a physical SQL backend. So the opening statement can be a little misleading. Also of important is the last note. A Lync deployment can be more than one pool . You can have a pool of mediation servers or AV conferencing servers etc. So while in the same pool you can’t mix virtual and physical you can have a mix of pools. So your frontend pool may be on virtualized servers but your AV conferencing server pool  might be physical. Like I said it’s a little confusing but hopefully that explanation helps. Of course it may seem obvious but if you are collocating AV conferencing servers and mediation servers on your frontends you can not mix those as they would be in the same pool as your frontends.

Being familiar with Lync terminology and reading this statement several times is very handy.

Comments welcomed.



  1. Hi VoIPNorm,

    After reading the doc I was not clear on whether you can have a physical front-end pool that uses a virtual SQL back-end? If you put all the fragments of info together I cannot see how this would be unsupported. However, the fact that MS go out of their way to state that a virtual front-end and physical back-end is 'explicitly supported' leaves a big question mark over the reverse scenario just because it has been omitted from the discussion.

    Just interested - what is your take?


  2. Virtual back end is not supported with Physical front ends. I think the balanced end to end performance from the second paragraph really explains why. If it was supported then you could potential cause some real issues as you scale up and the virtual machine supporting the back end started to have issues under increasing loads.

  3. Currently I work for Dell and thought your article on virtualization is quite impressive. I think virtualization, in computing, is the creation of a virtual (rather than actual) version of something, such as a hardware platform, operating system, a storage device or network resources.


Note: Only a member of this blog may post a comment.