[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-16

Deployment of Microsoft Communications Server 2010, Enterprise Edition requires using Topology Builder to define your topology and the components you want to deploy, preparing your environment for deployment of the Communications Server 2010 components, importing and publishing your topology design on the first Front End Server, and then installing and configuring Communications Server 2010 software for the components for your deployment.

Optionally, you can use the Planning Tool to facilitate the design and definition of your topology prior to running Topology Builder. For details about using the Planning Tool, see Using the Planning Tool to Design the Topology (Optional).

This documentation provides a staged approach to the Enterprise Edition deployment, starting with the minimum configuration required to get you up and running. The initial Enterprise Edition topology deployment described in this section includes the following environment and components:

This documentation then describes how to add optional server roles and components to the initial Enterprise Edition deployment. These optional server roles and components include one or more Directors, a standalone A/V Conferencing Server, and a standalone Mediation Server.

After deployment of your Enterprise pool, you can deploy other server roles and features, such as Edge Servers to support external user access.

In This Section