Appendix C. Using Cisco Tmsxe With Exchange 2007 Clustering; Overview; Clustering Requirements; Installation - Cisco TELEPRESENCE MANAGEMENT SUITE EXTENSION - FOR MICROSOFT EXCHANGE 2.2 Administrator's Manual

Appendix C.
Exchange 2007 Clustering

Overview

The Cisco TMSXE Integration product has been designed to be compatible with a Clustered Mail
Server created using the Continuous Cluster Replication (CCR) model of Exchange 2007.
When an organization uses Exchange Clustering, Cisco TMSXE can always be installed on another
Exchange Server within the organization that is not part of a cluster. This is true for both Exchange
2003 and 2007 installations. With clustering support, Cisco TMSXE can actually be installed on an
Exchange Server that is a node of a Clustered Mail Server (CMS) and will fail-over along with the
Exchange Service.
In a CMS setup, Cisco TMSXE is installed on each node in the Exchange Cluster. The Cisco TMSXE
Integration itself will not be clustered, and therefore will not show up in the Services/Applications of
the Failover Management Console. Instead, the Cisco TMSXE integration on each node follows the
state of the Exchange Clustered Server and is only active when the local server is the active node in
the cluster.

Clustering Requirements

Installing on a cluster requires the additional restrictions on the standard Cisco TMSXE requirements
Exchange Server 2007 w/Service Pack
1
Windows Server 2008

Installation

These instructions assume your Clustered Mail Server (CMS) is already installed and operational. For
assistance setting up and configuring your Clustered Mail Server – please refer to the Microsoft
documentation—http://technet.microsoft.com/en-us/library/bb629714.aspx
The installation on cluster nodes follows the same general steps as a stand-alone installation of Cisco
TMSXE with minor differences. Follow the steps below to perform a first time installation.
1. Create a Service User Manually—The service user that will be used by Cisco TMSXE on the
Exchange Server should be created manually rather then allow the Installer to create the
account.
a. Create a new local domain user with a strong password to act as the TMS-Service service
account. Example: TMS-Service. The TMS-Service account should have a mailbox created
on the storage group hosted by the Clustered Mailbox Server. The TMS-Service account
must have a SMTP email address that is reachable from the mail server used by Cisco TMS.
2. Add Log on as Batch Job permission – The TMS-Service user needs the Log on as Batch Job
Local Security Policy setting on each Windows Server in the cluster. As an administrator, log into
each server and grant the Log on as Batch Job permission to the TMS-Service user. See
http://technet.microsoft.com/en-us/library/cc739028.aspx
3. Add Cluster Permissions – The TMS-Service user needs access to the Cluster so it can check
the state of the cluster – it will not make any changes to the cluster. Using the Failover
Management Console in Windows, right-click on your cluster and select Properties. Under the
10
Windows 2003 Clusters are not supported due to MS DTC clustering requirement. Windows 2008
allows a local MS DTC Instance.
Cisco TMSXE Administrator Guide 2.2
Using Cisco TMSXE with
Details


10 
64bit

Must be a CCR Clustered Mail Server
Must be Service Pack 1 or greater
Clustering requires Enterprise or Datacenter Edition
Latest Service pack recommended
for assistance on assigning user rights.
Page 50 of 60