OCS Planning Guide

8/8/2019 OCS Planning Guide

1/211

Published: July 2007

Microsoft OfficeCommunicationsServer 2007Planning Guide


2/211

Information inthis document, including URL and otherInternet Web site references, is subjecttochange withoutnotice. Unless otherwise

noted,the companies,organizations,products, domainnames, e-mail addresses, logos,people,places,and events depicted in examples

hereinare fictitious. Noassociation with any real company,organization,product, domainname, e-mail address, logo,person,place,or

event is intended orshould be inferred. Complying with all applicable copyright laws is the responsibility ofthe user. Without limitingthe

rights undercopyright,nopartofthis documentmay be reproduced, stored inorintroduced intoaretrieval system,ortransmitted inany

formorby any means (electronic,mechanical,photocopying,recording,orotherwise),orforany purpose, withoutthe express written

permissionofMicrosoft Corporation.

Microsoftmay have patents,patentapplications,trademarks,copyrights,orotherintellectualproperty rights covering subjectmatter inthis

document. Exceptas expresslyprovided inany written license agreementfrom Microsoft,the furnishingofthis document does notgive

you any license tothese patents,trademarks,copyrights,orotherintellectual property.

2007 Microsoft Corporation. All rights reserved.

Microsoft, Active Directory, Outlook, Windows,and Windows Serverare trademarks ofthe Microsoftgroupofcompanies.

All othertrademarks are property oftheirrespective owners.


3/211

Contents

Introduction ......................................................................................................... 1

Step 1. Determine Key Planning Considerations .............. ............. ............. ......... 2

Determine What Features You Want to Deploy ............. ............. ............. ......... 2

Evaluate Your Organizations Environment For Specific Needs ............ ........... 4

Step 2. Select Your Topology ............................................................................... 7

Small to Medium Deployment Scenarios ......................................................... 8

Centralized Enterprise Deployment Scenarios ............ ............. ............. ......... 22

Global Deployments ............ ............. .............. ............. ............. ............. ......... 33

Step 3. Plan Your Deployment Path .............. ............. .............. ............. ............. 42

Things You Must Know Before You Deploy............. .............. ............. ............. 42

Overview of the Deployment Process ............ .............. ............. ............. ......... 46

Permissions Required for Deployment ............ .............. ............. ............. ....... 50

Step 4. Prepare Your Infrastructure ............. .............. .............. ............. ............. 51

Active Directory Domain Services .................................................................. 52

Certificate Infrastructure ............. .............. ............. .............. ............. ............. 57

DNS (Domain Name Service) ......................................................................... 64

Requirements for Automatic Client Sign-In .................................................... 70

Ports Required by Office Communications Server ......................................... 72

Step 5. Review System and Network Requirements ............ ............... ............. .. 74

Capacity Planning .......................................................................................... 75

User Model ............. ............. ............. .............. ............. ............. ............. ......... 78

Network Requirements .................................................................................. 79

Server Platform Requirements ............. .............. ............. ............. .............. .... 80

Client Software Requirements ....................................................................... 86

Step 6. Plan for External User Access ............ ............... ............. ............. ........... 87

When You Need an Access Edge Server ........................................................ 88

When You Need a Web Conferencing Edge Server ............. .............. ............. 90

When You Need an A/V Edge Server.............................................................. 91

Supported Topologies .................................................................................... 91

Plan for Edge Servers in Your Perimeter Network ............ ............... ............. .. 99

Edge Server Deployment Process ............ .............. .............. ............. ........... 100

Publicly Routable IP Address for External A/V Access ............ ............. ......... 102


4/211

DNS Requirements ...................................................................................... 103

Certificate Requirements ............ ............. .............. .............. ............. ........... 108

Firewall Requirements ............ ............. .............. ............. ............. .............. .. 113Step 7. Plan for Deploying Load Balancers .............. ............. .............. ............. 130

Load Balancer Requirements for Office Communications Server 2007 Enterprise

Pools ............................................................................................................ 131

Load Balancer Requirements for Edge Servers ............ ............. ............. ..... 134

Step 8. Plan for VoIP ........................................................................................ 140

Determine the Number and Distribution of Users ............. .............. ............. 140

Select a Deployment Option......................................................................... 141

Migration Paths and Integration Strategies ............. ............. .............. ......... 147

Plan for Media Gateways ............ .............. ............. .............. ............. ........... 149Plan for User Authorization and Outbound Call Routing............. ............. ..... 155

Plan for Exchange Server 2007 SP1 Unified Messaging ................ ............. 173

Planning to Move Users to Enterprise Voice ................... ............. .............. .. 177

Step 9. Plan for Address Book Server ............. ............. ............. .............. ......... 180

Step 10. Plan for High Availability and Fault Tolerance ............. ............. ......... 183

Making Your System Fault Tolerant ............ ............. .............. ............. ......... 184

Protecting Your Back-End Database ......................... ............. ............. ......... 185

Step 11. Plan for Database Storage ................................................................ 185

Step 12. Plan for Compliance and Usage Analysis .................... ............. ......... 196Archiving Topologies .................................................................................... 196

Archiving and CDR Scalability ...................................................................... 201

Configuring the Archiving and CDR Service ............ ............. .............. ........... 202

Appendix A Implementing in a QoS Environment ............ ............. ............. ....... 202

QoSService Types ............. ............. ............. .............. ............. ............. ......... 203

QoS Packet Scheduler ................................................................................. 205

Appendix B Disabling IPSec ............................................................................. 206


5/211

IntroductionWelcome totheMicrosoft Office Communications Server 2007 Planning Guide. This guide

describes how toplana smooth, successful Office Communications Server2007 deploymentfor

organizations ofall sizes and levels ofcomplexity,from large,geographically dispersed global

enterprises to small, local businesses.

Planning is essential to successful deployment. The new Office Communications Server2007

deploymenttool,combined with new wizards formany ofthe more commontasks, such as

configuringpools and obtainingcertificates,greatly simplifies the process ofinstalling,

configuring,and activating Office Communications Server2007. Butthe deploymenttool and

wizards donottake the place ofplanning;they simply make carryingout yourplans easier.

This guide divides theplanningprocess into 12 steps. Some steps are essential forall

deployments;others are more importantforsome environments thanforothers; butall should be

reviewed before actual deployment begins. These steps are summarized below:

y Step 1. Determine Key Planning Decisions

Discusses the main decisionpoints you need toconsiderbefore selectingatopology.

y Step 2. Select Your Topology

Presents several sample deployments based on size and desired functionality. Thesetopologies are intended toguide you through the possible options available when you plan

yourdeployment.

y Step 3. Plan Your Deployment Path

Summarizes importantthings you need toknow before you beginany Office

Communications Serverdeploymentand provides anoverview ofthe deploymentprocess.

y Step 4. Prepare Your Infrastructure

Discusses requirements forActive Directory Domain Services,certificates, DNS,

automaticclient sign-in,and ports.

y Step 5. Review System and Network Requirements

Lists hardware and software requirements forOffice Communications Server2007 server

roles and clients.

y Step 6. Plan for External User Access

Important

This guide presents guidance and topologies specifically for Office

Communications Server 2007. If you are migrating from Live

Communications Server 2005, use this guide in conjunction with the

Migrating to Microsoft Office Communications Server 2007 document.


6/211

2 Microsoft Office Communications Server 2007 Planning Guide

Provides guidelines fordeploying Office Communications Server2007 in yourperimeter

networkforthe purpose ofsupportingmessaging,presence,and conferencing with users

connectingfromoutside yourorganizationfirewall.

y Step 7. Plan for Deploying Load Balancers

Examines hardware load balancerrequirements and configurations foran Enterprisepool.

Also discusses the advantages ofusing hardware load balancers with edge serverarrays.

y Step 8. Plan for VoIP

Discusses all the factors,requirements,and configurationtasks that you need toconsiderin

orderto deploy Microsofts software-powered VoIP solution.

y Step 9. Plan for Address Book Server

Discusses requirements forsupportingthe Address BookServer, includingIIS (Internet

Information Services),networkfile share,and required diskspace.

y Step 10. Plan for High Availability and Fault Tolerance

Provides guidelines forassuring high availability and describes Office Communications

Server2007 features foroptimizingavailability and faulttolerance.

y Step 11. Plan for Database Storage

Discusses storage requirements forthe various databases and file shares thatare required by

Office Communications Server2007, including storage requirements forArchivingand

CDR (Call Detail Records) database and new messaging supportforrich textformat. Also

discusses RAID (DAS), NAS,and SAN tradeoffs,as well as basiccalculations ofdiskspace

needed permeetingandperpool, based onnumbers ofusers.

y Step 12. Plan for Compliance and Usage Analysis (moderate revisions from beta 3)

Describes how tomeetcompliance requirements forarchivingand call datarecording.

Step 1. Determine Key Planning ConsiderationsMicrosoft Office Communications Server2007 is the first Microsoftproducttocombine

enterprise-ready IM (instantmessaging),presence,and conferencing ina single offering. Builton

Microsoft Office Live Communications Server2005, Office Communications Serveradds more

capabilities tothe core features ofIM andpresence,and provides additional functionality ofon-

premise Web conferencing,multimediacapabilities,and Enterprise Voice.

In initial planningphase, several key decisionfactors will affect how you choose to deploy

Office Communications Server2007 in yourorganization. Decide whatfeatures ofOffice

Communications Serveryou wantto enable within yourorganizationand evaluate your

organizationsparticularrequirements.

Determine What Features You Want to Deploy

Office Communications Server2007 Standard Edition serverand Enterprisepool provide IM,

presence,and conferencingforusers within your internal organization. Office Communications


7/211

Microsoft Office Communications Server 2007 Planning Guide 3

Serveralsoprovides a several otherfeatures that you canofferby deployingadditional server

roles, dependingonthe functionality that yourorganization wants to support. Forexample, if

yourorganization wants toprovide internal users with the ability tocommunicate with external

users,thenan edge serveris required. Ifyou wanttoarchive your instantmessages orcall detail

records,an Archivingand CDR Service is required.

The followingtable lists the majorfeatures and functionalityprovided by Office

Communications Server2007 along with the serverroles and clients they require. Formore

detailed discussiononthe Office Communications Server2007 serverroles and architecture, see

theMicrosoft Office Communications Server 2007 Technical Overview.

Table 1 Communications Server functionality mapped to server roles and clients

Ifyou want to provide thisfunctionality

You must deploy this server role inaddition to Standard Edition Server or

Enterprise pooland this client

Instant messaging and presence

for internal usersNo additional server roles required.

Communicator 2005 or

2007Communicator 2007 is

required for enhanced

presence

On-premise Web conferencing Standard Edition: No additional server

roles required.

Enterprise Edition: Web Conferencing

Server and Web Components Server

Communicator 2007

Live Meeting 2007 client

Outlook add-in for

scheduled conferences

A/V conferencing Standard Edition: No additional serverroles required.

Enterprise Edition: A/V ConferencingServer

Communicator 2007


Outlook add-in for

scheduled conferences Address Book Server No additional server roles required.

Enterprise Edition: Web Components

Server

No requirement

Archiving and Call Detail Records Archiving and CDR Server No requirement

External User AccessAccess Edge Server *

HTTP reverse proxy*

Communicator 2005 or

2007Federation

Public IM Connectivity

Web conferencing with external

users

Web Conferencing Edge Server*

HTTP reverse proxy*

Communicator 2007


A/V conferencing with external

users

A/V Edge Server* Communicator 2007


IM and presence through a

browser based client

Communicator Web Access Server Communicator Web

Access


8/211


Ifyou want to provide thisfunctionality

You must deploy this server role inaddition to Standard Edition Server or

Enterprise pooland this client

Enterprise Voice Mediation Server and basic media

gateway

OR

basic-hybrid media gateway (Mediation

Server is collocated with basic media

gateway)

OR

advanced media gateway (Mediation

server logic incorporated in gateway

design; available soon)

A/V Edge Server (on which the A/V

Authentication Service is collocated)

Communicator 2007

OR

Office Communicator2007 Phone Edition

* Access Edge Serveris always required ifyou wantto support external useraccess.

Additionally,an HTTP reverseproxy is required to support external useraccess tomeeting

content, Address Bookfiles and distributiongroup expansion.

Evaluate Your Organizations Environment ForSpecific Needs

Before you beginto design yourOffice Communications Serverenvironment, you mustaddress

the mainpoints that will dictate the topology you choose:

y Importance ofhigh availability

y Geographic distributionofyourorganization

y Whetherornot you planto support external useraccess

y Whetherornot you planto deploy Enterprise Voice

Importance ofHigh Availability

Ifyourorganization will require that yourOffice Communications Server2007 topology offer

high availability,then you will wantto deploy one ormore Enterprisepools in your internal

topology. Ifhigh availability is notaconsiderationand simplicity and economy are more

important, Standard Edition Servermay be anappropriate choice. You canalso support high

availability in yourperimeternetwork ifrequired. The following sections summarize the

availability offerings ofthese deploymentoptions.

Standard Edition

Standard Editionprovides all IM,presence,and conferencingcomponents, including data

storage,ona single computer. This is an efficient, economical solutionfororganizations

consistingofarelatively small numberofusers whoare based ata single locationand whose IM

and online conferencingrequirements are notmissioncritical. A Standard Edition server

monitors its own state and inthe eventoffailure restarts automatically without loss offiles,

meetingcontent,ormeeting schedules. Meetings and conversations, however inprogress,are


9/211


interrupted,a situationthatmaypersistforaprolongedperiod, dependingonthe reasonforthe

failure.

Because a Standard Edition serverrepresents a single pointoffailure, we donotrecommend itformission-critical deployments where high availability is essential. Forsuch deployments,

Enterprise Edition is the necessary choice.

Enterprise Edition

The architecture ofOffice Communications Server2007 Enterprise Editionreduces single points

offailure through the use ofmultiple Enterprise Edition Servers and dedicated Back-End

Database server. Forgreaterredundancy,the database can be clustered inatwo-node active-

passive configuration. Office Communications Server2007 alsoprovides mechanisms for

automatically reconnectingclients. Momentary interruptions and terminated sessions can

occasionally occur, butthe system is largely immune tototal outages.

The multiple Front End Servers thatmake upan Enterprise Editionpool provide a high

availability solution wherein ifa single Front End Serverfails,clients will detectthe failure and

automatically reconnecttoone ofthe otheravailable Front End Servers. Meeting state is

preserved because ameeting is hosted by the pool,not by any single server. Multiple Front End

Servers alsomake itpossible totake any given serveroffline forhardware orsoftware updates

with minimal service interruption. Whenthe servergoes down due to hardware ornetwork

failure,there will be an interruption inthe experience ofthe clients thatare usingthat serverfor

IM,presence,and conferencing. Those clients will reconnecttoresume the service.

Locatingthe pools SQL databases onone oraclusterofback-end servers thatare separate from

the Front End Servers notonly insulates the databases frompossible Front End failure, but

improves overall throughputand Front Endperformance. The same is true fordeployingthe Web

Conferencing Serverand A/V Conferencing Serveron separate computers fromthe Front End

Servers inthe Enterprise Edition Expanded Configuration.

Perimeter Network

Ifyou planto enable external access ina highly available topology,then you will wantto deploy

multiple edge servers connected toa hardware load balancer(referred toas anarray ofedge

servers) in yourperimeternetwork. Conversely, ifyourorganization does notrequire high

availability inthe perimeternetwork, you cancollocate all three serverroles (Access Edge, Web

Conferencing Edge and A/V Edge) ona single server.

The Step 2. Select YourTopology section laterinthis document explains these configurations in

greaterdetail.

Important

The back-end database must be installed on a separate physical computerfrom any Enterprise Edition server. For Enterprise Edition, collocating the

back-end database with any Office Communications Server role is not

supported. Additionally, Office Communications Server requires a separate

SQL instance not shared with any other server application.


10/211


11/211


internal Communications Serverinfrastructure. The Mediation Server is the onlyadditional

Communications Serverrole required forEnterprise Voice.

Communications Serveroffers three options fordeployinga Mediation Serverand mediagateway. The firstoptionconsists ofa basicmediagateway and a separate Mediation Server. The

second option is a basic-hybrid gateway, in which the basicgateway and Mediation Serverare

collocated ona single computer. The third option is anadvanced mediagateway, in which the

Mediation Server logic is incorporated withinthe gateway software itself. Formore information

ongateway choices, see Choosingthe Type ofGateway to Deploy.

Inadditionto deployinggateways, you mustalsoplanforthe normalizationofyourphone

numbers thatare stored in Active Directory and create dial plans foreach location where your

organization does business. Toprovide call answering, subscriberaccess,and auto-attendant

services, you alsoneed to deploy Microsoft Exchange Server2007 Unified Messaging (UM) and

configure Exchange UM and Communications Serverto worktogether.

Enterprise Voice supports twomain deployment scenarios: stand-alone configurations in

greenfield ordepartmental scenarios,and PBX coexistence, in which users enjoy both thefamiliarity oftheirexisting PBXphones and the advantages ofUnified Communications,

includingrich audio, intuitive call control, enhanced presence notification,and the ability to

communicate directly from Microsoft Office applications. The following section includes some

basic Enterprise Voice scenarios, butforan in-depth discussionofsupported voice topologies,as

well as otherVoIP planning issues, see PlanforEnterprise Voice. Foracomplete guide to

understanding,planning, deploying,and managing Enterprise Voice ina single guide, see The

Microsoft Office Communications Server 2007 Enterprise Voice Planning and Deployment

Guide.

Step 2. Select Your Topology

This sectionpresents examples ofOffice Communications Servertopologies designed toprovideIM and conferencingfunctionality and otherfeatures ofOffice Communications Serverranging

froma very small orpilot deployment uptoa large global deployment. These topologies are

provided as sample deployments; dependingon yourspecificrequirements, you cancombine

differentpieces ofthese topologies tomeet yourneeds. They arepresented inorderof

complexity and size:

y Small to Medium Deployment Scenariospresenttopologies appropriate forsmall orpilot

deployments where high availability is notarequirement. These topologies build upon

Standard Edition serverto support internal IM and conferencinga userbase ofless than

5,000.

y Centralized Enterprise Deployment Scenariospresenttopologies thatprovide high

availability and supportforuserpopulationofover5,000 fororganizations ina single

physical site.

y Global Deploymentspresents topologies that spanmultiple sites andprovide highavailability and scalability.


12/211


Small to Medium Deployment Scenarios

This sectionprovides sample deployments thatare based on Standard Edition Serverinternally.

The simplesttopology,a Standard Edition Server, is presented first. Each subsequenttopology

builds uponthis topology,addingfunctionality and the components necessary to enable it.

The following deployment scenarios arepresented:

y Small deployment supportingIM and conferencingforinternal users only

y Small deployment with supportforinternal and external access

y Medium-sized deployment with supportforexternal useraccess and voice

y Medium-sized deployment with supportforarchiving, external access and voice

Small Deployment SupportingIM, Presence and ConferencingforInternal Users Only

The simplest Office Communications Servertopologyprovides IM and conferencing internally

fora small userbase. Itconsists ofa single Standard Edition Serverdeployment in which theFront-End, Web Conferencing, A/V Conferencing serverroles,and IIS are installed ona single

computer. This topology is appropriate forsmall tomediumorganizations with fewerthan 5,000

users orpilot deployments in which the maingoals are simplicity and ease ofmanagementand

where high availability is notarequirement. The followingfigure shows a sample Standard

Edition deployment.

Figure 1 Standard Edition Deployment


13/211


Deployment Profile

The followingtable summarizes the key characteristics ofthis topology.

Table 2 Deployment Profile for Standard Edition Topology

Key Aspect Description

Deployment scenario y Small to medium business

y Initial pilot or regional site deployment in an enterprise

Key goals for deployment Simplicity, ease of management

Geographic distribution Centralized single location

Functionality IM presence and conferencing

Functionality not provided y No external user access, including federation, public IMconnectivity, anonymous user participation in Web

conferencing and no external user access to audio and video

conferencing or mediay No high availability

y No PSTN voice

y No IM archiving or CDR functionality

Number of Office Communications Server

servers

1

User base Fewer than 5,000 users

Prerequisites Active Directory deployed in Microsoft Windows 2000 nativemode in the domain where Standard Edition Server will be

deployed

PKI infrastructure available

How to Use the PlanningGuide for this Topology

Although you may wanttoread the entire planningguide foracomprehensive understandingof

Office Communications Serverplanningconsiderations, you may alsochoose tofocus onthe key

chapters specificto yourdeployment.

Read these key chapters

Plan YourDeployment Path

Prepare YourInfrastructure

Review Systemand NetworkRequirements

PlanforAddress BookServer

PlanforDatabase Storage

Skip these chapters if you choose

PlanforExternal UserAccess

PlanforDeploying Load Balancers


14/211


PlanforVoIP

PlanforHigh Availability and Fault Tolerance

PlanforCompliance and Usage Analysis

Deployment Steps and Relevant Documents for this Topology

Ifthis topology is appropriate foryourorganization, begin yourdeployment bypreparing Active

Directory forOffice Communications Server. Afteryou complete yourActive Directory

preparation, deploy a Standard Edition server,and then deploy Office Communicator2007 and

the Live Meeting 2007 clientforyourusers.

Table 3 Deployment Steps and Where to Get More Information

RequiredStep 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 EditionDeployment Guide

Deploy Office Communicatorclients

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

Ifyou are deploying Office Communications Server2007 ina small company orapilotproject

and wantto supportIM,presence,and conferencing both forinternal users and external users,

build uponthe Standard Edition deployment by addingan edge servertoallow external user

accessspecifically,publicIM connectivity,remote useraccess,federation,and the ability ofexternal users toparticipate in A/V sessions and Web conferencing. Forthis topology,a single

edge server is deployed inthe perimeternetworkand all three edge serverroles, Access Edge

Server, Web Conferencing Edge Server,and A/V Edge Serverare installed ona single computer.

Figure 2 shows a simple deployment with supportforexternal useraccess.


15/211


Figure 2 Simple Deployment with Support for External User Access

Deployment Profile


Table 4 Deployment Profile for Small Deployment Supporting IM, Presence and

Conferencing for Internal and External Users


Deployment scenario y Small to medium business

y Initial pilot or regional site deployment in an enterprise



Functionality y IM presence and conferencing

y External user access including federation, public IM

connectivity, anonymous user participation in Webconferencing external user access to audio and video

sessions

Functionality not provided y No high availability

y No PSTN voice


16/211



y No IM archiving or CDR functionality

Number of Office Communications Serverservers

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


Reverse proxy available in the perimeter network

How to use the PlanningGuide for This Topology

Although you may wanttoread the entire planningguide foracomprehensive understandingofOffice Communications Serverplanningconsiderations, you may alsochoose tofocus onthe key











PlanforVoIP




Ifthis topology is appropriate foryourorganization, we recommend that you deploy Office

Communications Serverinternally first. Deploying Office Communications Server internally

involvespreparing Active Directory and then deployingand configuring yourStandard Edition

Serverand deploying yourclients. Afteryour internal topology is operational, deploy the edge

server. Inthe perimeternetwork,also ensure that you have areverse HTTP proxy. This proxywill allow outside users access tomeetingcontent,address bookfiles and distributiongroup

expansion informationthat is stored internally onthe IIS server.




17/211



Deploy Standard Edition Server Microsoft Office Communications Server 2007 Standard Edition

Deployment Guide


Microsoft Office Communicator 2007 Deployment Guide


clients



Deploy Edge Server Microsoft Office Communications Server 2007 Edge Server

Deployment Guide

Medium-Sized Deployment with Support for External User Access and Voice

Ifyou are deploying ina small tomedium sized company and wantto supportIM,presence,andconferencing both forinternal users and external users and voice functionality, build uponthe

simple deployment with external access,and connect yourStandard Edition Servertoan existing

advanced mediagateway. Like the simple deployment with external access described earlierin

this document,a single edge serveris deployed intheperimeternetwork,and all three edge

serverrolesAccess Edge Server, Web Conferencing Edge Server,and A/V Edge Serverare

installed ona single computer. The Standard Edition Serveris connected tothrough an Office

Communications ServerMediation Servertoamediagateway forvoice functionality. The

followingfigure shows a simple deployment with supportforexternal useraccess and voice.


18/211


Figure 3 Medium-Sized Deployment with Support for External User Access and Voice in

a Single Location

Deployment Profile





Deployment scenario Small to medium business

Initial pilot or regional site deployment in an enterprise



Functionality y IM presence and conferencing

y External user access including federation, public IMconnectivity, anonymous user participation in Web

conferencing external user access to audio and video

sessionsy Voice functionality for a single area code and location with a

unique PSTN termination point.



19/211



Functionality not provided No high availability

No IM archiving or CDR functionality


servers

3

User base Fewer than 5,000 active users*


For supported voice usage, refer to the Plan for VoIP section

later in this guide and the Microsoft Office Communications Server

2007Enterprise Voice Planning and Guide




Reverse http proxy available in the perimeter network

Advanced media gateway

How to Use the PlanningGuide for This Topology









PlanforVoIP







Deployment Steps and Relevant Documents for this TopologyIfthis topology is appropriate foryourorganization, we recommend that you deploy IM,

presence,and Web conferencingfunctionality firstand then deploy voice. Toconfigure IM,

presence,and conferencing, you will need toprepare Active Directory forOffice

Communications Serverand then deploy Standard Edition Server. AfteryourOffice


20/211


Communications Serveris deployed,roll out yourCommunicatorand Live Meetingclients to

yourend users. Afteryourinternal deployment is operational, you can deploy an edge serverin

yourperimeternetwork.

Intheperimeternetwork,also ensure that you have areverse HTTP proxy. Thisproxy will allow

outside users access tomeetingcontent,address bookfiles and distributiongroup expansion

informationthat is stored internally onthe IIS server(which runs onthe Standard Edition Server

inthis topology). Once these pieces are workingtogether, you will wantto deploy enterprise

voice.


Required Step Read this guide for step-by-step instructions



Deployment Guide

Deploy Office Communicator

clients


Deploy Live Meeting 2007clients

Deploying the Microsoft Office Live Meeting 2007 Client with OfficeCommunications Server 2007

Deploy Enterprise Voice Microsoft Office Communications Server 2007 Voice Guide


Deployment Guide

Medium Sized Deployment with External Access and Voice in Multiple Locations

Ifyou are deploying inamedium size company and wantto supportthe followingfunctionality,

the followingtopology may meet yourneeds:

y IM,presence and conferencing both forinternal users and external users

y Voice functionality formultiple locations

This topology is based uponthe precedingtopology with a single voice location, with the

additionofexistingmediagateway in each voice location. An Office Communications Server

2007 Mediation Serveris placed betweenan existingmediagateway totranslate betweenthe

gateway and Standard Edition Server. Inthe advanced mediagateways orthe basic hybrid media

gateway,the Mediation Serveris notrequired because the logicofthe Mediation Serveris

integrated intothe gateway itself. You canfind acurrent listofqualified gateways that workwith

Communications Serverathttp://r.office.microsoft.com/r/rlidOCS?clid=1033&p1=IPpbxVend.

The followingfigure depicts a sample topology.


21/211


Figure 4 Medium Sized Deployment with Support for External User Access and Voice in

Multiple Locations

Deployment Profile


Table 8 Medium Sized Deployment with Support for External User Access and Voice in

Multiple Locations


Deployment scenario Medium business

Deployment in an enterprise supporting external user access and

voice in multiple locations


Geographic distribution Centralized single location with multiple regional voice locations


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).



22/211




servers

3 plus the basic hybrid media gateway and the advance media

gatewayUser base Fewer than 5,000 active users


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 thedomain where Standard Edition Server will be deployed


Reverse http proxy available in the perimeter network

Advanced media gateway*

Basic media gateway










PlanforVoIP








Ifthis topology is appropriate foryourorganization, we recommend that you deploy IM,

presence,and Web conferencingfunctionality firstand then deploy voice. Toconfigure IM,presence,and conferencing, we recommend you deploy Office Communications Serverinternally

firstand then deploy inside yourperimeternetwork. First, you will need toprepare Active

Directory forOffice Communications Server,and then deploy a Standard Edition Server. After

yourOffice Communications Serveris deployed,roll out yourCommunicatorand Live Meeting

clients to yourend users.


23/211


Next, deploy youredge serverinthe perimeternetwork,and ensure that you have areverse

HTTP proxy. This proxy will allow outside users access tomeetingcontent,address bookfiles

and distributiongroup expansion informationthat is stored internally onthe IIS server.

Afterthesepieces are workingtogether, you will wantto deploy enterprise voice.





Deployment Guide





Deploy Enterprise Voice Microsoft Office Communications Server 2007 Enterprise Voice

Planning and Deployment Guide


Deployment Guide

Deployment with Archiving, Communicator Web Access, External Access, and Voice inMultiple Locations

Ifyou are deploying inamedium size company and wantto supportthe followingfunctionality,

this sample topology may meet yourneeds:

y IM,presence,and conferencing both forinternal users and external users

y Voice functionality formultiple locations

y Internetaccess toIM functionality usinga Web browser

y The ability toarchive messages orusage dataand capture call detail records

This topology is based uponthe precedingtopology butadds an Archivingand CDR Serverto

enable yourcompany toarchive instantmessages and capture call datarecords,and a

CommunicatorWeb Access Servertoprovide yourusers with CommunicatorWeb Access for

instantmessagingoversecure HTTP (HTTPS). Inoursample topology,the Archivingand CDR

Server is collocated with its required back-end SQL database. As a variation, you could deploy

the back-end SQL database ona dedicated server. Figure 5 depicts a sample topology.


24/211


Figure 5 Medium Sized Deployment with Support for External User Access and Voice in

a Multiple Locations

Deployment Profile


Table 10 Deployment Profile for Small Deployment Supporting IM, Presence, and



Deployment scenario Small to medium business

Initial pilot or regional site deployment in an enterprise


Geographic distribution Centralized single location with multiple regional voice locations


25/211




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



6 including a Mediation Server for each basic media gateway

User base Fewer than 5,000 active users


domain where the Standard Edition Server will be deployed


Reverse HTTP proxy available in the perimeter network

Advanced media gateway

Basic media gateway










PlanforVoIP








26/211



Ifthis topology is appropriate foryourorganization, we recommend that you deploy IM,

presence,and Web conferencingfunctionality firstand then deploy voice. Toconfigure IM,

presence and conferencing, we recommend that you deploy Office Communications Server

internally and then deploy inside yourperimeternetwork. Internally, you will need toprepare

Active Directory forOffice Communications Serverand then deploy the Standard Edition Server

and the Archivingand CDR Server. Finally,roll out yourCommunicatorand Live Meeting

clients to yourend users.

Next, deploy youredge serverinthe perimeternetwork,and ensure that you have areverse

HTTP proxy. This proxy will allow outside users access tomeetingcontent,address bookfiles

and distributiongroup expansion informationthat is stored internally onthe IIS server, which in

this topology runs onthe Standard Edition Server. You can deploy CommunicatorWeb Access

independently ofyourclient deployment, but yourOffice Communications Server2007

infrastructure must be inplace.

Once thesepieces are workingtogether, you will wantto deploy Enterprise Voice.





Server Deployment Guide

Deploy Archiving and CDR Server Microsoft Office Communications Server 2007 Archiving and CDR

Server Deployment Guide


clients



clients



Deploy Communicator Web

Access

Microsoft Communicator Web Access Planning and Deployment Guide

Deploy Edge Server Microsoft Office Communications Server 2007 Edge ServerDeployment Guide

Deploy Enterprise Voice Microsoft Office Communications Server 2007 Enterprise VoicePlanning and Deployment Guide

Centralized Enterprise Deployment ScenariosThis sectionprovides sample deployments thatare designed forlarge centralized enterprises that

require high availability internally. The simplesttopology thatprovides high availability

internally is an Enterprisepool inthe consolidated configuration. Formore robust internal

deployments with scalingflexibility,an Enterprisepool inthe expanded configurationcan be


27/211


used. The remaining deployments inthis scenario build uponthe twoconfigurations ofan

Enterprisepool,addingadditional functionality and components required to enable it.

The following deployment scenarios arepresented:y Enterprise deployment supportingIM and conferencingforinternal users only

y Enterprise deployment supportingIM and conferencingforinternal and external users

y Scaled external deployment with high availability

Enterprise Deployment SupportingIM and ConferencingforInternal Users Only

In largerenterprises, when instantmessaging,presence,and conferencingare considered mission

critical, high availability is arequirement. Any Enterprisepool with multiple Enterprise Edition

Servers canprovide basic high availability. It its simplestconfiguration,aconsolidated topology,

each Enterprise Edition Server inapool runs all serverroles: Front-End, A/V Conferencing,and

Web Conferencing,as well as IIS forthe Web Components. A consolidatedpool can support up

to 30,000 users. The advantage ofthe consolidated configurationoverthe expanded

configuration is ease ofmanagement, butperformance is notas fastas the expanded

configuration. The followingfigure shows a sample topology.


28/211


Figure 6 Enterprise Deployment Supporting IM and Conferencing for Internal Users Only

Deployment Profile



29/211





Deployment scenario Initial deployment for mission critical large enterprise instant

messaging and conference usage

Key goals for deployment High availability

Ease of management



Functionality not provided No external user access, including federation, public IM

connectivity, anonymous user participation in Web conferencing

and no external user access to audio and video conferencing or

mediaNo PSTN voice



4 servers (1 server role)

User base Fewer than 30,000 active users



Microsoft SQL Server 2005 SP1 or SQL Server 2000 SP4 or later

available for the back-end database of the pool


Hardware load balancer














30/211




PlanforVoIP





preparation, deploy an Enterprisepool inthe consolidated configuration,and then deploy Office

Communicator2007 and the Live Meeting 2007 clientforyourusers.




Deploy an Enterprise pool in the

consolidated configuration

Microsoft Office Communications Server 2007 Enterprise Edition

Deployment Guide


clients




High Scale, High Availability Enterprise Deployment SupportingIM and ConferencingforInternal Users Only

In largerenterprises thatrequire high availability and scalability to supportmission-critical IM

and conferencing internally,an Enterprisepool inthe expanded configuration is appropriate. A

single Enterprisepool inan expanded configurationcan support userbase ofupto 125,000

active,concurrent users.

Inthis configuration, each serverrole resides ona dedicated computer,and the Front End Servers

and Web Component Servers (IIS server_) are connected toa hardware load balancer. (You can

use a single load balancerforboth serverroles oruse two separate load balancers) Placing server

roles on separate computers allows you to scale based on serverroles. Forexample, ifyour

organization uses A/V functionality heavily, you canadd additional A/V Conferencing Servers to

meetthis need. Additionally,placingIIS on separate computers can help ifIIS is managed by a

differentteamoryourorganization has stricterlockdownrequirements forthese servers. Ifyou

planto deploy Enterprise voice ata latertime, but expect heavy voice usage,this topology will

more easily scale forthose needs. A/V Conferencing Servers and A/V Edge Servers can support

a largernumberofusers when deployed on dedicated servers.

Inthe followingfigure,the Back-End Database Serveris clustered inatwo-node activepassive

configuration. A Microsoft SQL Serverclusterforthe back-end databaseprovides additional

high availability and provides failovercapabilities. Clusteringthe database is optional.


31/211


Figure 7 High Availability Enterprise Deployment Supporting IM and Conferencing for

Internal Users Only

Deployment Profile



32/211


Table 14 Deployment Profile for High Scale, High Availability for Internal IM and

Conferencing Use




Key goals for deployment High availability; high scalability, higher performance



Functionality not provided No external user access, including federation, public IM

connectivity, anonymous user participation in Web conferencing

and no external user access to audio and video conferencing ormedia

No PSTN voiceNo IM archiving or CDR functionality


servers

9 servers (4 roles)

User base Up to 125,000 active, concurrent users internally



SQL Server 2005 SP1 or SQL Server 2000 SP4 or later available

for the back-end database of the pool


Hardware load balancer















33/211



PlanforVoIP





preparation, deploy an Enterprisepool inthe expanded configuration,and then deploy Office

Communicator2007 and the Live Meeting 2007 clientforyourusers.




Deploy an Enterprise pool in theconsolidated configuration

Microsoft Office Communications Server 2007 Enterprise EditionDeployment Guide




clients



High Scale, High Availability Enterprise Deployment SupportingIM and ConferencingforInternal and External Users

In largerenterprises thatrequire high availability and scalability to supportmission-critical IM

and conferencing internally andprovide basic external access,an Enterprisepool inthe expanded

configurationmust be deployed internally,and edge servers are deployed inthe perimeternetwork.

Inthe following edge topology,the Access Edge Serverand the Web Conferencing Edge Server

are deployed onone computer,and the A/V Edge Serveris deployed onanotherdedicated

computer. This topology is well positioned to scale ifyourneed forexternal access becomes

more critical. To scale, you add additional computers thatare runningthe same serverroles and

connectthemtoa load balancer,as explained inthe next section,Scaled External Access with

High Availability inthe PerimeterNetwork.


34/211


Figure 8 High Scale High Availability Enterprise Deployment Supporting IM and


Deployment Profile


Table 16 Deployment Profile for High Scale, High Availability for Internal and External IM

and Conferencing Use




Key goals for deployment High availability; high scalability, higher performance internally




35/211



External user access, including federation, public IM connectivity,

anonymous user participation in Web conferencing and externaluser access to audio and video conferencing or media

Functionality not provided No PSTN voice



servers

11 servers (7 roles)

User base Up to 125,000 active concurrent users.

10 percent of this user base is assumed to be external



SQL Server 2005 SP1 or SQL Server 2000 SP4 or later available

for the back-end database of the poolPKI infrastructure available

Hardware load balancer for pool

Hardware load balancer for edge servers

Notes For a simpler, edge topology, you can place all your edge server

roles on a single computer; however, the model discussed earlierin this document scales more easily, because you cannot load

balance multiple edge servers in the consolidated topology.



Office Communications Serverplanningconsiderations, you may alsochoose tofocus onthe keychapters specificto yourdeployment.











PlanforVoIP



36/211



Ifthis topology is appropriate foryourorganization, we recommend you deploy Office

Communications Serverinternally and then deploy edge servers in yourperimeternetwork. For

your internal deployment, you will need toprepare Active Directory forOffice Communications

Server,and then deploy Enterprisepool inthe expanded configuration. Afteryou have deployed

yourOffice Communications Serverinfrastructure, deploy Communicator2007 and Live

Meeting 2007 clients foryourend users.

Intheperimeternetwork, before you deploy youredge servers, ensure that you have a hardware

load balancerto which you will connect youredge servers and areverse HTTP proxy. . This

proxy will allow outside users access tomeetingcontent,address bookfiles and distribution

group expansion informationthat is stored internally onthe IIS server.




Deploy an Enterprise pool in the

expanded configuration

Microsoft Office Communications Server 2007 Enterprise Edition

Deployment Guide


clients



clients




Scaled External Access with High Availability in the Perimeter Network

As a variationofthe high scale, high availability deployment with external access, you can scale

the edge topology toprovide high availability forexternal access. Ina scaled edge topology,one

ormore A/V Edge Servers are deployed on dedicated servers,and Access Edge and Web

Conferencing Edge are collocated on separate dedicated computers. All edge servers are

connected toa hardware load balancer.

Note

You cannot load balance the consolidated edge topology (all three server

roles deployed on a single computer).


37/211


Figure 9 Scaled External Access Topology

Global Deployments

This sectionprovides two sample global deployment enterprises with geographically dispersed

sites thatrequire high availability across multiple sites:

y Global IM and conferencing supporting internal and external users

y Global IM and conferencing supporting internal and external users and Enterprise Voice

Global Conferencing with Multiple Regional Sites

Inaglobal deployment,an enterprise may have one ormore datacenters in differentphysical

locations. To supportIM and conferencing, each ofthese datacenters must hostone ormore

pools forlocal users and deploy edge servers in its respectiveperimeternetworkinorderto

support external access.


38/211


The central corporate datacenterhosts apool inthe expanded configurationto supporta user

base ofupto 125,000. Inthe primaryperimeternetwork,an Access Edge Serverand Web

Conferencing Edge Serverare collocated onone computer,and the A/V Edge Serveris deployed

ona separate dedicated computer. Inthis topology,a Directoris used inthe primary datacenter.

The Director is an Office Communications Server2007 Standard Edition serverorEnterprise

pool that does not host users butthat,as amemberofan Active Directory domain, has access to

Active Directory forpurposes ofauthenticatingremote users and routingtraffictothe

appropriate serverorEnterprisepool. Directors are recommended when you support external

useraccess, butthey are notrequired. You could deploy a similartopology without usinga

Director.

Inthe secondary datacentersite,apool inthe consolidated configuration is deployed to supporta

smalleruserbase ofless than 30,000. Inthe secondaryperimeternetwork,two local Web

Conferencing Edge Serverand two A/V Edge Servers are load balanced toprovide high

availability and toaccommodate the heavy networkbandwidth utilizationofaudio/videoand

Web conferencingtraffic. Users inthe secondary site still use the Access Edge Serverinthe

primary datacenterto send SIP traffictothe corporate datacenterservers. The Access EdgeServer intheprimary datacenterroutes all SIP trafficthrough the Director, which thenroutes the

traffictothe appropriate pools. Foraudio/videoorWeb conferencing, users first send SIP

requests through the Access Edge Servertothe Director,and thenthe Directorreturns the

appropriate Web Conferencing Edge ServerorA/V Edge Serverto which the userconnects for

Web conferencingoraudio/video sessions. To ensure agood userexperience forinter-pool

scenarios,the pools should be well-connected, with low network latency.


39/211


Figure 10 Global Deployment Supporting IM and Conferencing for Internal and External

Users

The followingfigure shows an example ofhow one ormorephysical sites may be dispersed.


40/211


Deployment Profile





Deployment scenario Global, mission critical IM and conferencing usage with global

external access. This topology can also form the basis for voicefunctionality added later

Key goals for deployment Global availability with external access

Geographic distribution A central data center and one or more secondary data centers



anonymous user participation in Web conferencing and external

user access to audio and video conferencing or media





User base Over 125,000 dispersed geographically


41/211




domain where Standard Edition Server will be deployedSQL Server 2005 SP1 or SQL Server 2000 SP4 or later available



Hardware load balancers for pools and the Director

Hardware load balancer for edge servers in central and regionalsites




chapters specificto yourdeployment.Read these key chapters








PlanforDatabase StorageSkip these chapters if you choose

PlanforVoIP




Communications Serverinternally first, in each site,roll out yourclients,and then deploy your

edge servers in yourperimeternetwork. Foryour internal deployment, you will need toprepare

Active Directory forOffice Communications Server,and then deploy the Enterprisepool inthe

expanded configuration. Afteryou have deployed yourOffice Communications Server

infrastructure, deploy Communicator2007 and Live Meeting 2007 clients foryourend users. In

the perimeternetworks, before you deploy youredge servers, ensure that you have anavailablehardware load balancerand areverse HTTP proxy. Thisproxy will allow outside users access to

meetingcontent,address bookfiles and distributiongroup expansion informationthat is stored

internally onthe IIS server.


42/211





Deploy an Enterprise pool in theexpanded configuration



clients



clients




Deployment Guide

Global Conferencing with Multiple Sites External Access and Voice

A global deploymentthat supports both external access and voice is basically a variationofthe

precedingtopology, with the additionofexisting basicmediagateways and advanced media

gateways in each voice location. An Office Communications Server2007 Mediation Server is

placed adjacentto each existing basicmediagateway totranslate betweenthe gateway and

Enterprisepools. Inthe advanced mediagateways orthe basic hybrid mediagateway,the

Mediation Server is notrequired because the logicofthe Mediation Serveris integrated intothe

gateway itselfYou canfind acurrent listofqualified gateways that workwith Communications

Serverat http://r.office.microsoft.com/r/rlidOCS?clid=1033&p1=IPpbxVend. Figure 11 shows a

sample deployment.


43/211


Figure 11 Global Deployment with External Access and Voice


44/211


The followingfigure shows an example ofhow one ormorephysical sites may be dispersed.

Figure 12 Example of a Global Deployment

Deployment Profile





Deployment scenario Global, mission critical IM and conferencing usage with globalexternal 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



anonymous user participation in Web conferencing and external

user access to audio and video conferencing or media




servers


User base Over 125,000 dispersed geographically


45/211




domain where Standard Edition Server will be deployedSQL Server 2005 SP1 or SQL Server 2000 SP4 or later available



Hardware load balancers for pools and the Director

Hardware load balancer for edge servers in central and regionalsites




chapters specificto yourdeployment.Read these key chapters






PlanforVoIP


PlanforHigh Availability and Fault TolerancePlanforDatabase Storage





Communications Serverinternally in each site,roll out yourclients,and then deploy edge servers

in yourperimeternetwork. Foryour internal deployment, you will need toprepare Active

Directory forOffice Communications Server,and then deploy Enterprisepool inthe expanded

configuration. Afteryou have deployed yourOffice Communications Server infrastructure,

deploy Communicator2007 and Live Meeting 2007 clients foryourend users.

Before you deploy youredge servers, intheperimeternetwork, ensure that you have a hardwareload balancerto which you will connect youredge servers and areverse HTTP proxy. Thisproxy

will allow outside users access tomeetingcontent,address bookfiles and distributiongroup

expansion informationthat is stored internally onthe IIS server.


46/211





Deploy an Enterprise pool in theexpanded configuration



clients



clients



Deploy Enterprise Voice Microsoft Office Communications Server 2007 Enterprise Voice

Planning and Deployment Guide


Step 3. Plan Your Deployment PathThis chapterexplains how toplan yourdeploymentpath. Itcontains the following sections:

y Things you mustknow before deploying

y Overview ofthe deploymentprocess

y Permissions required fordeployment

Things You Must Know Before You DeployBefore you begin implementing yourchosentopology,there are some importantthings you must

know aboutthe Office Communications Server2007 requirements and specifictopologies:

Infrastructure Considerations

A PKI infrastructure is required forOffice Communications Server2007. Ifyou donot have an

internal PKI infrastructure, you can use apublic CA as well.

All domains in which you deploy Office Communications Serverare using Windows 2000 native

mode. You cannot deploy Office Communications Serverinamixed mode domain. Microsoft

Windows Server 2003 native mode is strongly recommended.

You must use acertificate issued by apublic CA forfederationandpublicIM connectivity.

(PublicIM connectivity requires anadditional license). Forthe MSN networkofInternetservices and Yahoo!,a Web servercertificate is required. ForAOL,the certificate mustalso

be configured forclientauthentication.


47/211


Important: Voice Considerations

Power, Network, or Telephone Service Outages

Ifthere is anoutage, disruption,orotherdegradationofthe power,network,ortelephoneservices at yourlocation,the voice, instantmessaging,presence,and otherfeatures ofOffice

Communications Server2007 and any device connected to Office Communications Server2007

may not workproperly.

Enterprise Voice Depends on Server Availability and Voice Client and Hardware

Operability

Voice communications via Office Communications Server2007 depend uponthe availability of

the serversoftware and the properfunctioningofthe voice clients orthe hardwarephone devices

connectingtothe serversoftware.

Alternative Means ofAccessing EmergencyServices

Forthose locations where you install a voice client (forexample,a PC running Office

Communicator2007 oran Office CommunicatorPhone Edition device), we recommend that you

maintaina backupoptionforusers tocall emergency services (forexample, 911 and 999) incase

ofapowerfailure,networkconnectivity degradation,telephone service outage,orotherproblem

thatmay inhibitoperationofOffice Communications Server2007, Office Communicator2007,

orthe Phone Edition devices. Such alternative options could include atelephone connected toa

standard PSTN line oracellphone.

Emergency Calls and Multi-Line Telephone Systems

The use ofamulti-line telephone system (MLTS) may be subjectto U.S. (state and/orfederal)

and foreign MLTS laws thatrequire the MLTS toprovide acallers telephone number, extension,

and/orphysical locationtoapplicable emergency services whenacallermakes acall to

emergency services (forexample, when dialingan emergency access numbersuch as 911 or

999). NeitherOffice Communications Server2007, Office Communicator2007,norOffice

CommunicatorPhone Edition Devicesprovide the callersphysical locationto emergency

services whenacallerdials emergency services. Compliance with such MLTS laws is the soleresponsibility ofthe purchaserofOffice Communications Server2007, Office Communicator

2007,and Office CommunicatorPhone Edition devices.

Web Conferencing Considerations

As a bestpractice, you should alsoperiodically run diskdefragmentationonthe diskdrives

where the meetingcontent is hosted.

Runningreal-time anti-virus scanningonthe shares that store meetingcontent,meetingcontent

meta data,and meetingcompliance data is notrecommended. Doing socanadversely affect

performance forWeb Conferencing. We recommend scanningforvirus only whenthe serverhas

little orno load and that you runanti-virusprotection enabled onclientcomputers atall times.

EdgeS

erver ConsiderationsYou cannot load balance multiple edge servers inthe consolidated topology. The only supported

load balanced topology foracentral site involves one ormore dedicated computers with

collocated Access Edge Servers with Web Conferencing Edge Servers and one ormore dedicated

computers with A/V Edge Conferencing Servers. Thus, ifyou deploy the consolidated edge

topology initially and then wantto scale, you will have to deploy an entirely new edge topology.


48/211


An external DNS SRV record must existforyourAccess Edge Serverorarray ofedge servers in

orderto supportpublicIM connectivity and federation. Formore information, see Step 6. Plan

forExternal UserAccess.

Only one Access Edge Serveroranarray ofAccess Edge Servers can be used inanorganization

forpublicIM connectivity and federation. Inotherwords,an Access Edge Serveroranarray of

Access Edge Servers canonly be inonephysical datacenter(multiple datacenters orremote

sites cannot deploy Access Edge Servers).

A reverse HTTP proxy is toallow remote users to download address bookfiles,and expand

distribution lists and toallow external users access tomeetingcontentforWeb conferences.

The network interfaces ofthe AV Edge Servermust be directly addressable atthe IP layerand

not behind a NAT.

ForWeb and IM conferences involvingfederatedparticipants, Office Communications Server

edge servers verify thatthe connecting serverhas the appropriate certificates and is configured

forfederation. However,the Office Communications Serveredge servers in yourorganization

rely onthe federatedpeerserverto send the legitimate SIP URIoftheparticipantand hencecannotguarantee the identity ofthe external conferenceparticipants inafederated Web orIM

conference. To distinguish external users, Office Communicator2007provides a visual

indicationforusers fromafederated domain inthe conference roster. Additionally,the title bar

ofthe conversation window contains aglobe iconto indicate that external participants are

included. Whenclients connecttoa Web conference oran A/V conference hosted by afederated

domain,the clients treatthe rosterand all conferencing informationcomingfromthe federated

domainas trusted information.

You should only have one inbound MTLS listenerconfigured on yourDirector. This is the

defaultconfiguration, which is recommended. Ifyou have more thanone listenerconfigured on

yourDirector,all otherlisteners besides the defaultconnection (MTLS onport 5061) must be

configured to use TLS orTCP. Havingmore thanone MTLS listenercanresult inproblems

communicating with external users and attending external conferences. Ifyou have arequirementformore thanone MTLS listener, verify thatthe portnumbers correspondingto each MTLS

listenerare openonthe internal firewall forcommunication betweenthe Access Edge Serverand

Director. This configurationapplies to yourFront End Servers ifyou donot have a Director

deployed forexternal access.

General Office Communications Server Considerations

Standard Edition serverrequires enough local diskspace formeetingcontent. Particularly ifyou

leverage multimediafunctionality ofLive Meetingclient,the size required formeetingcontent

cangrow large.

Installingany Office Communications Server2007 role onaglobal catalogcontrollerorany

otherdomaincontrolleris not supported.

Office Communications Servershould not be installed ina domain in which the lastpartoftheFQDN begins with anumeral. Forexample,xxx.yyy.4zzand aaa.bbb.1abare both invali