You have two main deployment
scenarios when it comes to Enterprise Voice. You can choose stand-alone confi gurations in
greenfi eld or departmental scenarios, or PBX coexistence.
The next step in your planning phase should be to select a topology. Microsoft, in its
Offi ce Communications Server 2007 Planning Guide, presents three examples of OCS 2007
topologies that provide IM and conferencing functionality and other features: small to
medium-size deployment, centralized enterprise deployment, and global deployments.
I won??™t discuss these in detail here. The point is that you should download the Planning
Guide and carefully examine these three scenarios. Depending on your requirements, you can
combine the different pieces of these example deployments to meet your company??™s needs.
56 Chapter 2 ??? Microsoft Offi ce Communications Server 2007
The next step concerns how to plan your deployment path. There are three areas of
concern:
?– Things you need to know before deploying
?– An overview of the deployment process
?– Permissions required for deployment
There are some important things you need to know about the OCS 2007 requirements
before you start. First, a PKI is required for OCS 2007. If you don??™t have an internal
PKI, you??™ll need to use a public certifi cate authority (CA). Also, all domains where you
deploy OCS 2007 require Windows 2000 native mode minimum (Windows Server
2003 native mode is strongly recommended). OCS 2007 can??™t be installed in a mixed-mode
domain.
Pages:
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120