In light of the new OCS R2 server roles and capabilities, here is a summary of the significant changes on the server side and topology (from OCS 2007).
Changes to Existing OCS 2007 Server Role
|
OCS 2007 Role |
Change(s) |
Notes |
|
Front-End |
Several key changes: · Application Sharing Server Added (1) · Device Update Service Added · Telephony Conferencing includes PSTN dial-in audio bridge capability |
The Application Sharing Server ships with 4 new voice and conferencing applications (see below). The Device Update Service can be used to keep your R2 Communicator Phone Edition and Microsoft RoundTable devices up to date. |
|
Archiving & CDR |
CDR is removed and the Archiving capability is a dedicated R2 role. |
|
|
QoE |
Becomes the R2 Monitoring role (which includes the CDR functionality). |
|
|
Communicator Web Access (CWA) |
CWA R2 now enables desktop sharing and conferencing calling. |
|
(1) The Application Sharing Server ships with 4 new UC Applications (implemented as services on the OCS R2 Front-End in addition to the Application Sharing service)
a. Conferencing Attendant – Provides the ability for PSTN users to dial into a conference.
b. Conferencing Announcement Service – Enables audio notification when users join or leave a conference.
c. Response Group Service – Enables the creation of automated response groups by users to route or queue incoming phone calls to designated agents.
d. Outside Voice Control – Enables call control functionality for mobile phones that are not enabled for enterprise voice.
New OCS R2 Server Roles
|
New Server Role |
Notes |
|
Monitoring |
Includes QoE and Call Detail Record (CDR) functionality. The QoE functionality consists of the OCS 2007 QoE functionality plus many new metrics and redesigned reports. |
|
Group Chat Server |
Enables users to create and participate in persistent chat rooms. Archival of chat room content can be achieved by deploying an optional Group Chat Compliance Server. |
A complete list of the capabilities enabled by the OCS R2 server roles is available here: http://www.microsoft.com/communicationsserver/en/us/capabilities.aspx Key Topology Changes
|
Topology |
Change |
|
Expanded Edition Server Roles
|
Enterprise Edition Expanded Topology is no longer a preferred deployment scenario. Consolidated pools are the recommended deployment option. The Expanded pool options is not available in the R2 Pool Setup wizard. |
|
Edge |
A consolidated edge role is the only supported R2 edge topology. Multiple servers behind a load balancer is recommended and supported for redundancy and high availability. |
Twitter
LinkedIn
Directors always exist in their own pool. They are a pool with one server – the director – with no users homed in that pool.
Because you only have 1 pool, you technically do not need a director, although it is recommended. Here is an excellent recent article on the director role and why you might want to deploy one: http://technet.microsoft.com/en-us/library/ff357531.aspx.
Curtis
we have one pool ..enterprise edition pool…
with four front edn serevrs ..loadbaalcned
..my doubt abt director is ..do i need to join the director to same pool or create another pool…
apart frm these two ..whether there are any other options …