[This is pre-release documentation and subject to change in future releases. This topic's current status is: Milestone-Ready]

Topic Last Modified: 2010-07-18

The only component required to use a Director is to deploy the Director server role.


You can implement a single Director server, or a pool of Directors. The Director is always a separate server or pool, not collocated with any other server role in Microsoft Communications Server 2010.

If you have a pool of directors, they must be load balanced. You can use only a hardware load balancer, or you could implement DNS load balancing to take care of the SIP traffic. Doing so makes the administration of the hardware load balancer simpler, as the hardware load balancer would need to balance only HTTP traffic, which hardware load balancer administrators are accustomed to. Traffic unique to Communications Server 2010, such as SIP traffic, would be handled entirely by DNS load balancing. For details, see DNS Load Balancing.

    A Director pool