Small to Medium Deployment Scenarios
Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.
This section provides sample deployments that are based on Standard Edition Server internally. The simplest topology, a Standard Edition Server, is presented first. Each subsequent topology builds upon this topology, adding functionality and the components necessary to enable it.
The following deployment scenarios are presented:
Small deployment supporting IM and conferencing for internal users only
Small deployment with support for internal and external access
Medium-sized deployment with support for external user access and voice
Medium-sized deployment with support for archiving, external access, and voice
Small Deployment Supporting IM, Presence, and Conferencing for Internal Users Only
The simplest Office Communications Server topology provides IM and conferencing internally for a small user base. It consists of a single Standard Edition Server deployment in which the Front-End, Web Conferencing, A/V Conferencing server roles, and IIS are installed on a single computer. This topology is appropriate for small to medium organizations with fewer than 5,000 users or pilot deployments in which the main goals are simplicity and ease of management and where high availability is not a requirement. The following figure shows a sample Standard Edition deployment.
Figure 1 Standard Edition Deployment
.gif "6a32c4c6-fdba-4cdb-b941-2a36b71e6eeb")
The following table summarizes the key characteristics of this topology.
Table 2 Deployment Profile for Standard Edition Topology
| Key Aspect | Description |
|---|---|
Deployment scenario |
|
Key goals for deployment |
Simplicity, ease of management |
Geographic distribution |
Centralized single location |
Functionality |
IM presence and conferencing |
Functionality not provided |
|
Number of Office Communications Server servers |
1 |
User base |
Fewer than 5,000 users |
Prerequisites |
Active Directory deployed in Microsoft Windows® 2000 native mode in the domain where Standard Edition Server will be deployed. PKI infrastructure available |
How to Use the Planning Guide for this Topology
Although you may want to read the entire planning guide for a comprehensive understanding of Office Communications Server planning considerations, you may also choose to focus on the key chapters specific to your deployment.
Read these key chapters
Skip these chapters if you choose
Deployment Steps and Relevant Documents for this Topology
If this topology is appropriate for your organization, begin your deployment by preparing Active Directory for Office Communications Server. After you complete your Active Directory preparation, deploy a Standard Edition server, and then deploy Office Communicator 2007 and the Live Meeting 2007 client for your users.
Table 3 Deployment Steps and Where to Get More Information
| Required Step | Read This Guide for Step-by-Step Instructions |
|---|---|
Active Directory Preparation |
Microsoft Office Communications Server 2007 Active Directory Guide |
Deploy Standard Edition Server |
Microsoft Office Communications Server 2007 Standard Edition Deployment Guide |
Deploy Office Communicator clients |
Microsoft Office Communicator 2007 Planning and Deployment Guide |
Deploy Live Meeting 2007 clients |
Deploying the Microsoft Office Live Meeting 2007 Client with Office Communications Server 2007 |
Small Deployment with Support for External User Access
If you are deploying Office Communications Server 2007 in a small company or a pilot project and want to support IM, presence, and conferencing both for internal users and external users, build upon the Standard Edition deployment by adding an edge server to allow external user access—specifically, public IM connectivity, remote user access, federation, and the ability of external users to participate in A/V sessions and Web conferencing. For this topology, a single edge server is deployed in the perimeter network and all three edge server roles, Access Edge Server, Web Conferencing Edge Server, and A/V Edge Server are installed on a single computer. Figure 2 shows a simple deployment with support for external user access.
Figure 2 Simple Deployment with Support for External User Access
.gif "3f5feb9e-324f-48c3-ab34-099882a1e26e")
Deployment Profile
The following table summarizes the key characteristics of this topology.
Table 4 Deployment Profile for Small Deployment Supporting IM, Presence, and Conferencing for Internal and External Users
| Key Aspect | Description |
|---|---|
Deployment scenario |
|
Key goals for deployment |
Simplicity, ease of management |
Geographic distribution |
Centralized single location |
Functionality |
|
Functionality not provided |
|
Number of Office Communications Server servers |
2 |
User base |
Less than 5,000 active users * For external, 10 percent of the total active users or 500 |
Prerequisites |
Active Directory deployed in Windows 2000 native mode in the domain where Standard Edition Server will be deployed. PKI infrastructure available Reverse proxy available in the perimeter network |
How to Use the Planning Guide for This Topology
Although you may want to read the entire planning guide for a comprehensive understanding of Office Communications Server planning considerations, you may also choose to focus on the key chapters specific to your deployment.
Read these key chapters
Skip these chapters if you choose
Deployment Steps and Relevant Documents for This Topology
If this topology is appropriate for your organization, we recommend that you deploy Office Communications Server internally first. Deploying Office Communications Server internally involves preparing Active Directory and then deploying and configuring your Standard Edition Server and deploying your clients. After your internal topology is operational, deploy the edge server. In the perimeter network, also ensure that you have a reverse HTTP proxy. This proxy will allow outside users access to meeting content, address book files and distribution group expansion information that is stored internally on the IIS server.
Table 5 Deployment Steps and Where to Get More Information
| Required Step | Read This Guide for Step-by-Step Instructions |
|---|---|
Active Directory Preparation |
Microsoft Office Communications Server 2007 Active Directory Guide |
Deploy Standard Edition Server |
Microsoft Office Communications Server 2007 Standard Edition Deployment Guide |
Deploy Office Communicator clients |
Microsoft Office Communicator 2007 Deployment Guide |
Deploy Live Meeting 2007 clients |
Deploying the Microsoft Office Live Meeting 2007 Client with Office Communications Server 2007 |
Deploy Edge Server |
Microsoft Office Communications Server 2007 Edge Server Deployment Guide |
Medium-Sized Deployment with Support for External User Access and Voice
If you are deploying in a small to medium sized company and want to support IM, presence, and conferencing both for internal users and external users and voice functionality, build upon the simple deployment with external access, and connect your Standard Edition Server to an existing advanced media gateway. Like the simple deployment with external access described earlier in this document, a single edge server is deployed in the perimeter network, and all three edge server roles—Access Edge Server, Web Conferencing Edge Server, and A/V Edge Server—are installed on a single computer. The Standard Edition Server is connected to through an Office Communications Server Mediation Server to a media gateway for voice functionality. The following figure shows a simple deployment with support for external user access and voice.
Figure 3 Medium-Sized Deployment with Support for External User Access and Voice in a Single Location
.gif "757ba6a1-5ca5-4949-a164-528f76a035e1")
Deployment Profile
The following table summarizes the key characteristics of this topology.
Table 6 Deployment Profile for Small Deployment Supporting IM, Presence and Conferencing for Internal and External Users
| Key Aspect | Description |
|---|---|
Deployment scenario |
Small to medium business Initial pilot or regional site deployment in an enterprise |
Key goals for deployment |
Simplicity, ease of management |
Geographic distribution |
Centralized single location |
Functionality |
|
Geographic distribution |
Centralized single location |
Functionality not provided |
No high availability No IM archiving or CDR functionality |
Number of Office Communications Server servers |
3 |
User base |
Fewer than 5,000 active users* For external, 10 percent of the total active users or 500 For supported voice usage, refer to the Step 8. Plan for VoIP section later in this guide and the Microsoft Office Communications Server 2007 Enterprise Voice Planning and Guide. |
Prerequisites |
Active Directory deployed in Windows 2000 native mode in the domain where Standard Edition Server will be deployed. PKI infrastructure available Reverse http proxy available in the perimeter network Advanced media gateway |
How to Use the Planning Guide for This Topology
Although you may want to read the entire planning guide for a comprehensive understanding of Office Communications Server planning considerations, you may also choose to focus on the key chapters specific to your deployment.
Read these key chapters
Skip these chapters if you choose
Deployment Steps and Relevant Documents for This Topology
If this topology is appropriate for your organization, we recommend that you deploy IM, presence, and Web conferencing functionality first and then deploy voice. To configure IM, presence, and conferencing, you will need to prepare Active Directory for Office Communications Server and then deploy Standard Edition Server. After your Office Communications Server is deployed, roll out your Communicator and Live Meeting clients to your end users. After your internal deployment is operational, you can deploy an edge server in your perimeter network.
In the perimeter network, also ensure that you have a reverse HTTP proxy. This proxy will allow outside users access to meeting content, address book files and distribution group expansion information that is stored internally on the IIS server (which runs on the Standard Edition Server in this topology). Once these pieces are working together, you will want to deploy enterprise voice.
Table 7 Deployment Steps and Where to Get More Information
| Required Step | Read This Guide for Step-by-Step Instructions |
|---|---|
Active Directory Preparation |
Microsoft Office Communications Server 2007 Active Directory Guide |
Deploy Standard Edition Server |
Microsoft Office Communications Server 2007 Standard Edition Deployment Guide |
Deploy Office Communicator clients |
Microsoft Office Communicator 2007 Deployment Guide |
Deploy Live Meeting 2007 clients |
Deploying the Microsoft Office Live Meeting 2007 Client with Office Communications Server 2007 |
Deploy Enterprise Voice |
Microsoft Office Communications Server 2007Enterprise Voice Planning and Deployment Guide |
Deploy Edge Server |
Microsoft Office Communications Server 2007 Edge Server Deployment Guide |
Medium-Sized Deployment with External Access and Voice in Multiple Locations
If you are deploying in a medium size company and want to support the following functionality, the following topology may meet your needs:
IM, presence, and conferencing for internal users and external users
Voice functionality for multiple locations
This topology is based upon the preceding topology with a single voice location, with the addition of existing media gateway in each voice location. An Office Communications Server 2007 Mediation Server is placed between an existing media gateway to translate between the gateway and Standard Edition Server. In the advanced media gateways or the basic hybrid media gateway, the Mediation Server is not required because the logic of the Mediation Server is integrated into the gateway itself. You can find a current list of qualified gateways that work with Communications Server at https://r.office.microsoft.com/r/rlidOCS?clid=1033&p1=IPpbxVend. The following figure depicts a sample topology.
Figure 4 Medium-Sized Deployment with Support for External User Access and Voice in Multiple Locations
.gif "c6c9f1ef-eb1a-4c67-8864-e1235f723b6d")
Deployment Profile
The following table summarizes the key characteristics of this topology.
Table 8 Medium-Sized Deployment with Support for External User Access and Voice in Multiple Locations
| Key Aspect | Description |
|---|---|
Deployment scenario |
Medium business Deployment in an enterprise supporting external user access and voice in multiple locations |
Key goals for deployment |
Simplicity, ease of management |
Geographic distribution |
Centralized single location with multiple regional voice locations |
Functionality |
IM presence and conferencing External user access including federation, public IM connectivity, anonymous user participation in Web conferencing external user access to audio and video sessions Voice functionality for multiple locations and area codes (one area code per PSTN termination point). |
Functionality not provided |
No high availability No IM archiving or CDR functionality |
Number of Office Communications Server servers |
3 plus the basic hybrid media gateway and the advance media gateway |
User base |
Fewer than 5,000 active users For external, 10 percent of the total active users or 500 For supported voice usage, refer to Step 8. Plan for VoIP later in this document |
Prerequisites |
Active Directory deployed in Windows 2000 native mode in the domain where Standard Edition Server will be deployed. PKI infrastructure available Reverse http proxy available in the perimeter network Advanced media gateway* Basic media gateway |
How to Use the Planning Guide for This Topology
Although you may want to read the entire planning guide for a comprehensive understanding of Office Communications Server planning considerations, you may also choose to focus on the key chapters specific to your deployment.
Read these key chapters
Skip these chapters if you choose
Deployment Steps and Relevant Documents for This Topology
If this topology is appropriate for your organization, we recommend that you deploy IM, presence, and Web conferencing functionality first and then deploy voice. To configure IM, presence, and conferencing, we recommend you deploy Office Communications Server internally first and then deploy inside your perimeter network. First, you will need to prepare Active Directory for Office Communications Server, and then deploy a Standard Edition Server. After your Office Communications Server is deployed, roll out your Communicator and Live Meeting clients to your end users.
Next, deploy your edge server in the perimeter network, and ensure that you have a reverse HTTP proxy. This proxy will allow outside users access to meeting content, address book files and distribution group expansion information that is stored internally on the IIS server.
After these pieces are working together, you will want to deploy enterprise voice.
Table 9 Deployment Steps and Where to Get More Information
| Required Step | Read This Guide for Step-by-Step Instructions |
|---|---|
Active Directory Preparation |
Microsoft Office Communications Server 2007 Active Directory Guide |
Deploy Standard Edition Server |
Microsoft Office Communications Server 2007 Standard Edition Deployment Guide |
Deploy Office Communicator clients |
Microsoft Office Communicator 2007 Deployment Guide |
Deploy Live Meeting 2007 clients |
Deploying the Microsoft Office Live Meeting 2007 Client with Office Communications Server 2007 |
Deploy Enterprise Voice |
Microsoft Office Communications Server 2007 Enterprise Voice Planning and Deployment Guide |
Deploy Edge Server |
Microsoft Office Communications Server 2007 Edge Server Deployment Guide |
Deployment with Archiving, Communicator Web Access, External Access, and Voice in Multiple Locations
If you are deploying in a medium size company and want to support the following functionality, this sample topology may meet your needs:
IM, presence, and conferencing for internal users and external users
Voice functionality for multiple locations
Internet access to IM functionality using a Web browser
The ability to archive messages or usage data and capture call detail records
This topology is based upon the preceding topology but adds an Archiving and CDR Server to enable your company to archive instant messages and capture call data records, and a Communicator Web Access Server to provide your users with Communicator Web Access for instant messaging over secure HTTP (HTTPS). In our sample topology, the Archiving and CDR Server is collocated with its required back-end SQL database. As a variation, you could deploy the back-end SQL database on a dedicated server. Figure 5 depicts a sample topology.
Figure 5 Medium-Sized Deployment with Support for External User Access and Voice in a Multiple Locations
.gif "66465f11-5688-4c2b-a52b-d8b67cb6cb42")
Deployment Profile
The following table summarizes the key characteristics of this topology.
Table 10 Deployment Profile for Small Deployment Supporting IM, Presence, and Conferencing for Internal and External Users
| Key Aspect | Description |
|---|---|
Deployment scenario |
Small to medium business Initial pilot or regional site deployment in an enterprise |
Key goals for deployment |
Simplicity, ease of management |
Geographic distribution |
Centralized single location with multiple regional voice locations |
Functionality |
IM presence and conferencing External user access including federation, public IM connectivity, anonymous user participation in Web conferencing external user access to audio and video sessions Voice functionality for a multiple locations and area codes (one area code per PSTN termination point). Communicator Web Access for Office Communications Server users Archiving and CDR |
Functionality not provided |
No high availability |
Number of Office Communications Server servers |
6 including a Mediation Server for each basic media gateway |
User base |
Fewer than 5,000 active users |
Prerequisites |
Active Directory deployed in Windows 2000 native mode in the domain where the Standard Edition Server will be deployed. PKI infrastructure available Reverse HTTP proxy available in the perimeter network Advanced media gateway Basic media gateway |
How to Use the Planning Guide for This Topology
Although you may want to read the entire planning guide for a comprehensive understanding of Office Communications Server planning considerations, you may also choose to focus on the key chapters specific to your deployment.
Read these key chapters
Skip these chapters if you choose
Deployment Steps and Relevant Documents for This Topology
If this topology is appropriate for your organization, we recommend that you deploy IM, presence, and Web conferencing functionality first and then deploy voice. To configure IM, presence and conferencing, we recommend that you deploy Office Communications Server internally and then deploy inside your perimeter network. Internally, you will need to prepare Active Directory for Office Communications Server and then deploy the Standard Edition Server and the Archiving and CDR Server. Finally, roll out your Communicator and Live Meeting clients to your end users.
Next, deploy your edge server in the perimeter network, and ensure that you have a reverse HTTP proxy. This proxy will allow outside users access to meeting content, address book files and distribution group expansion information that is stored internally on the IIS server, which in this topology runs on the Standard Edition Server. You can deploy Communicator Web Access independently of your client deployment, but your Office Communications Server 2007 infrastructure must be in place.
Once these pieces are working together, you will want to deploy Enterprise Voice.
Table 11 Deployment Steps and Where to Get More Information
| Required Step | Read This Guide for Step-by-Step Instructions |
|---|---|
Active Directory Preparation |
Microsoft Office Communications Server 2007 Active Directory Guide |
Deploy Standard Edition Server |
Microsoft Office Communications Server 2007 Standard Edition Server Deployment Guide |
Deploy Archiving and CDR Server |
Microsoft Office Communications Server 2007 Archiving and CDR Server Deployment Guide |
Deploy Office Communicator clients |
Microsoft Office Communicator 2007 Deployment Guide |
Deploy Live Meeting 2007 clients |
Deploying the Microsoft Office Live Meeting 2007 Client with Office Communications Server 2007 |
Deploy Communicator Web Access |
Microsoft Office Communicator Web Access (2007 release) Planning and Deployment Guide |
Deploy Edge Server |
Microsoft Office Communications Server 2007 Edge Server Deployment Guide |
Deploy Enterprise Voice |
Microsoft Office Communications Server 2007 Enterprise Voice Planning and Deployment Guide |