.png)
Global Deployments
This section provides two sample global deployment enterprises with geographically dispersed sites that require high availability across multiple sites:
-
Global IM and conferencing supporting internal and external users
-
Global IM and conferencing supporting internal and external users and Enterprise Voice
In a global deployment, an enterprise may have one or more data centers in different physical locations. To support IM and conferencing, each of these data centers must host one or more pools for local users and deploy edge servers in its respective perimeter network in order to support external access.
The central corporate data center hosts a pool in the expanded configuration to support a user base of up to 125,000. In the primary perimeter network, an Access Edge Server and Web Conferencing Edge Server are collocated on one computer, and the A/V Edge Server is deployed on a separate dedicated computer. In this topology, a Director is used in the primary data center. The Director is an Office Communications Server 2007 Standard Edition server or Enterprise pool that does not host users but that, as a member of an Active Directory domain, has access to Active Directory for purposes of authenticating remote users and routing traffic to the appropriate server or Enterprise pool. Directors are recommended when you support external user access, but they are not required. You could deploy a similar topology without using a Director.
In the secondary datacenter site, a pool in the consolidated configuration is deployed to support a smaller user base of less than 30,000. In the secondary perimeter network, two local Web Conferencing Edge Server and two A/V Edge Servers are load balanced to provide high availability and to accommodate the heavy network bandwidth utilization of audio/video and Web conferencing traffic. Users in the secondary site still use the Access Edge Server in the primary data center to send SIP traffic to the corporate datacenter servers. The Access Edge Server in the primary data center routes all SIP traffic through the Director, which then routes the traffic to the appropriate pools. For audio/video or Web conferencing, users first send SIP requests through the Access Edge Server to the Director, and then the Director returns the appropriate Web Conferencing Edge Server or A/V Edge Server to which the user connects for Web conferencing or audio/video sessions. To ensure a good user experience for inter-pool scenarios, the pools should be well-connected, with low network latency.
The following figure shows an example of how one or more physical sites may be dispersed.
The following table summarizes the key characteristics of this topology.
Table 18 Deployment Profile for High Scale, High Availability for Internal and External IM and Conferencing Use
| Key Aspect | Description |
|---|---|
|
Deployment scenario |
Global, mission critical IM and conferencing usage with global external access. This topology can also form the basis for voice functionality added later. |
|
Key goals for deployment |
Global availability with external access |
|
Geographic distribution |
A central data center and one or more secondary data centers |
|
Functionality |
IM presence and conferencing External user access, including federation, public IM connectivity, anonymous user participation in Web conferencing and external user access to audio and video conferencing or media |
|
Functionality not provided |
No PSTN voice No IM archiving or CDR functionality |
|
Number of Office Communications Server servers |
21 servers (10 roles) |
|
User base |
Over 125,000 dispersed geographically |
|
Prerequisites |
Active Directory deployed in Windows 2000 native mode in the domain where Standard Edition Server will be deployed. SQL Server 2005 SP1 or SQL Server 2000 SP4 or later available for the back-end database of the pool PKI infrastructure available Hardware load balancers for pools and the Director Hardware load balancer for edge servers in central and regional sites |
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
-
Step 3. Plan Your Deployment Path
-
Step 4. Prepare Your Infrastructure
-
Step 5. Review System and Network Requirements
-
Step 6. Plan for External User Access
-
Step 7. Plan for Deploying Load Balancers
-
Step 9. Plan for Address Book Server
-
Step 10. Plan for High Availability and Fault Tolerance
-
Step 11. Plan for Database Storage
Skip these chapters if you choose
If this topology is appropriate for your organization, we recommend you deploy Office Communications Server internally first, in each site, roll out your clients, and then deploy your edge servers in your perimeter network. For your internal deployment, you will need to prepare Active Directory for Office Communications Server, and then deploy the Enterprise pool in the expanded configuration. After you have deployed your Office Communications Server infrastructure, deploy Communicator 2007 and Live Meeting 2007 clients for your end users. In the perimeter networks, before you deploy your edge servers, ensure that you have an available hardware load balancer and 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 19 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 an Enterprise pool in the expanded configuration |
Microsoft Office Communications Server 2007 Enterprise 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 |
A global deployment that supports both external access and voice is basically a variation of the preceding topology, with the addition of existing basic media gateways and advanced media gateways in each voice location. An Office Communications Server 2007 Mediation Server is placed adjacent to each existing basic media gateway to translate between the gateway and Enterprise pools. 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 http://r.office.microsoft.com/r/rlidOCS?clid=1033&p1=IPpbxVend.
Figure 12 shows a sample deployment.
The following figure shows an example of how one or more physical sites may be dispersed.
The following table summarizes the key characteristics of this topology.
Table 20 Deployment Profile for High Scale, High Availability for Internal and External IM and Conferencing Use
| Key Aspect | Description |
|---|---|
|
Deployment scenario |
Global, mission critical IM and conferencing usage with global external access. This topology can also form the basis for voice functionality added later. |
|
Key goals for deployment |
Global availability with external access |
|
Geographic distribution |
A central data center and one or more secondary data centers |
|
Functionality |
IM presence and conferencing External user access, including federation, public IM connectivity, anonymous user participation in Web conferencing and external user access to audio and video conferencing or media |
|
Functionality not provided |
No PSTN voice No IM archiving or CDR functionality |
|
Number of Office Communications Server servers |
27 servers (10 roles) |
|
User base |
Over 125,000 dispersed geographically |
|
Prerequisites |
Active Directory deployed in Windows 2000 native mode in the domain where Standard Edition Server will be deployed. SQL Server 2005 SP1 or SQL Server 2000 SP4 or later available for the back-end database of the pool PKI infrastructure available Hardware load balancers for pools and the Director Hardware load balancer for edge servers in central and regional sites |
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
-
Step 3. Plan Your Deployment Path
-
Step 4. Prepare Your Infrastructure
-
Step 5. Review System and Network Requirements
-
Step 6. Plan for External User Access
-
Step 7. Plan for Deploying Load Balancers
-
Step 8. Plan for VoIP
-
Step 9. Plan for Address Book Server
-
Step 10. Plan for High Availability and Fault Tolerance
-
Step 11. Plan for Database Storage
Skip these chapters if you choose
If this topology is appropriate for your organization, we recommend you deploy Office Communications Server internally in each site, roll out your clients, and then deploy edge servers in your perimeter network. For your internal deployment, you will need to prepare Active Directory for Office Communications Server, and then deploy Enterprise pool in the expanded configuration. After you have deployed your Office Communications Server infrastructure, deploy Communicator 2007 and Live Meeting 2007 clients for your end users.
Before you deploy your edge servers, in the perimeter network, ensure that you have a hardware load balancer to which you will connect your edge servers and 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 21 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 an Enterprise pool in the expanded configuration |
Microsoft Office Communications Server 2007 Enterprise 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 |
