Export (0) Print
Expand All

Phase 4: Deploy Archiving Server and Monitoring Server

Communications Server 2007 R2

Topic Last Modified: 2009-05-15

If your current deployment includes an Archiving and CDR Server and/or a QoE Monitoring Server, you may need to deploy a new Archiving Server and possibly a new Monitoring Server, before you move users to the new Office Communications Server 2007 R2 pool.

In Office Communications Server 2007 R2, archiving and call detail recording (CDR) are performed on separate server roles. If you need to perform CDR and/or QoE monitoring, then you will need to deploy Office Communications Server 2007 R2, Monitoring Server. If your environment does not require this action, you can delay deploying Archiving Server and Monitoring Server until later in your migration plan.

Archiving and CDR services for one version of Office Communications Server do not interoperate with the same services from another version. Conversations that are hosted on Office Communications Server 2007 can be archived only by using Office Communications Server 2007, Archiving and CDR Server. Similarly, conversations that are hosted on Office Communications Server 2007 R2 servers can be archived only by using Office Communications Server 2007 R2, Archiving Server. In a mixed environment, archiving is performed by the version of Office Communications Server that homes the initiator of the conversation . If a user who is homed on an Office Communications Server 2007 R2 server starts the conversation, then Office Communications Server 2007 R2, Archiving Server, will store the conversation. If the initiator of the conversation is homed on Office Communications Server 2007, then Office Communications Server 2007, Archiving and CDR Server, will store the conversation.

Office Communications Server 2007 R2, Archiving Server, cannot use the same archiving database that is used by Office Communications Server 2007, Archiving and CDR Server. If you choose to use the same SQL Server installation to host archiving databases for both versions, you must create a new database for the new Archiving Server, or else all of the existing data will be lost.

Dd573013.note(en-us,office.13).gifNote:
For performance reasons, we recommend against collocating the archiving databases with the back-end database for the pool.

The Archiving Server requires Message Queuing and a supporting SQL database.

For details on user experience during this phase, see User Experience During Phase 4.

For details about how to install an Archiving Server, see the Office Communications Server 2007 R2 Archiving Server Deployment Guide documentation.

While not strictly needed for compliance purposes, some environments may require call detail recording as part of their compliance policy. If this is the case, you will need to install, configure, and activate Office Communications Server 2007 R2 Monitoring Server. For details, see the Office Communications Server 2007 R2 Monitoring Server Deployment Guide documentation.

If needed, associate the existing legacy mediation servers with the new Monitoring Server. To accomplish this task, you must use the script associate.vbs to create the link.  This procedure is described in Coexistence Issues.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft