Licensing Requirements; Explanation Of Resource Booking Models - Cisco TELEPRESENCE MANAGEMENT SUITE EXTENSION - FOR MICROSOFT EXCHANGE 2.2 Administrator's Manual

 Creates two security groups which are used to assign calendar permissions (Only created in
Exchange 2003 installations)

A role-restricted COM+ Application is created on the Exchange Server which runs as the TMS-
Service service account

An installation folder with a log directory is created and the service user is granted access to the
log directory
 A Configuration Utility is installed to manage the product, and is accessible via a TANDBERG
Program Group added to the Start Menu
 Registry keys are created within a TANDBERG Hive in the Registry and the service user is
granted permission to these keys
Changes on Cisco TMS Server
 A local Windows User account named 'tmsconfuser' is created on the Cisco TMS Server (Normal
Windows User privileges only) with a strong random password.
•
Alternatively an existing account can be specified during installation if manually configured
 Assigns the 'tmsconfuser' account the 'Exchange Integration Account' permission within Cisco
TMS and adds it to the Site Administrators Group
Permissions Granted to Service Users
The service users permissions will be configured automatically when created by the installer, but the
following permissions must not be restricted for the service users.
Exchange Side Service User—TMS-service
 Log on as a Batch job
 Read/Write permissions to the TANDBERG Key in the registry
 Write permissions to log files directory

Read permissions to log files directory and the installation directory

Activate permissions to the TANDBERG COM+ package

Do not grant this user any Exchange Administrator Roles to prevent it from accessing other
mailboxes
Cisco TMS Side Service User—tmsconfuser
 Must have access to login to the Windows Server hosting TMS

Needs to be a member that has "Book on behalf of" permissions in Cisco TMS

Must have Exchange Integration Service Account set to Yes in its Cisco TMS Profile

Must have booking permission to the systems in Cisco TMS to be integrated

Licensing Requirements

Exchange Licensing
The Cisco TMSXE Integration has no impact on your Exchange licenses from Microsoft.
Cisco TMS Licensing
Each system that is to be integrated with Exchange must already exist in Cisco TMS and be properly
licensed itself in Cisco TMS. For licensing of Cisco TMSXE Integration, the licensing can be per
system, or per Exchange Server integrated with Cisco TMS depending on the type of license you
purchase.
When using per system licensing, controlling which systems are consuming licenses is set by the
Remote Booking flag in System Navigator on each system. By default, Remote Booking will be set
to No for each system. The first time a system is used from Exchange, if there is a free license
available on the Cisco TMS server, Remote Booking will be toggled to Yes for that system. In doing
so, licensing is automatically enabled for systems you have integrated with Exchange. If no more
licenses are available, and Remote Booking = No for that system, the requested booking will be
denied.

Explanation of Resource Booking Models

Microsoft Exchange and Outlook offers two distinct ways to book resource accounts. The different
models have different requirements and user experiences. Both models should be understood so an
Cisco TMSXE Administrator Guide 2.2 Page 43 of 60