Topic Last Modified: 2010-07-16
This section guides you through the deployment of Microsoft Communications Server 2010 Enterprise Voice.
Before You Begin
This deployment documentation assumes that you already accomplished all of the following:
- Read the planning documentation: topics from the “Enterprise Voice”
section of “Planning for Microsoft
Communications Server 2010”.
- Finalized plans for features and components to deploy with this
- Ran Communications Server Planning Tool to design a topology
that reflects your deployment decisions.
Note: Installation of Communications Server Topology Builder is out of scope for this documentation because it is part of the deployment process for the internal pool.
- Exported the topology design to Communications Server Topology
These prerequisite deployment steps—running Communications Server Planning Tool and exporting the topology design--are described, in particular, in the topics in the following deployment sections:
- Using the
Planning Tool to Design the Topology (Optional)
- Import the
Topology File from the Planning Tool (Optional)
Important: The results of running Communications Server Topology Builder are essential to the installation of any Communications Server 2010 server role. You must define and publish your topology using Communications Server Topology Builder before you install files for your Mediation Servers.
Furthermore, you must have already deployed Microsoft Communications Server 2010, Enterprise Edition at central sites and branch sites that correspond to the reference topology you chose to deploy. You cannot deploy Enterprise Voice components until you have defined, published, and installed files for at least one internal pool, and you must use Communications Server Topology Builder to define and publish an internal pool.
How to Use This Documentation
As you read the documentation in this section, understand that the reference topology on which your deployment is based dictates the topics that you must read and the steps within them that you must perform. To accommodate customized deployments which deviate from deployment steps for a particular reference topology, some topics also provide alternate procedures to follow at the appropriate phases of the deployment process. All topics explicitly direct you next to the most relevant topic for the deployment of your chosen reference topology.
To view reference topologies with examples of where Communications Server Enterprise Voice server roles can be deployed (and their relationship to one another and other Communications Server 2010 server roles), see “Reference Topologies” in the Planning documentation.
To view a reference topology that illustrates and explains a sample call admission control deployment, including network regions, network sites, and subnets, see “Example: Gathering the Required Information for Call Admission Control” in the Planning documentation.
Next Steps: Configure a Trunk or Verify Topology and Install Files?
|To deploy Enterprise Voice at a central site, continue reading the topics in this section. To deploy Enterprise Voice at a branch site, skip to Deploying Branch Sites.|
The documentation in this section includes procedures for deployments in which a Mediation Server collocated on each Front End Server or Standard Edition Server, as recommended, as well as deployments with a standalone Mediation Server pool.
If you used Communications Server Topology Builder to define and publish a topology that collocates a Mediation Server on each Front End Server or Standard Edition Server, you can skip to the following content because Deployment Wizard already automatically installed the files for Mediation Server when you installed files for your Front End Server or Standard Edition Server:
If you used Communications Server Topology Builder to define and publish a Mediation Server in a standalone pool, you can use the following content to a) verify that your topology meets the software and environment prerequisites, and then b) to install the files for the Mediation Server (required for the Enterprise Voice workload).