Resolving Custom Attribute Conflicts; Additional Reference Materials For Administrators; Functional Overview Of Cisco Tmsxe Integration - Cisco TELEPRESENCE MANAGEMENT SUITE EXTENSION - ADMINISTRATOR GUIDE FOR MICROSOFT EXCHANGE 2.2 Administrator's Manual

Resolving Custom Attribute Conflicts

The Cisco TMSXE integration relies on being able to set/read a Custom Attribute 1 in the mailboxes
used for its Exchange Service account and the resource accounts integrated with Cisco TMS. In some
customer installations, this custom attribute is already in use for other customer-specific uses. To
accommodate these situations, administrators can specify any AD user object field that is also
replicated to Global Catalogue Servers, for use by Cisco TMSXE. A typical example of such a field
would be extensionAttribute2.
Perform these changes before installing Cisco TMSXE:
1. Open the Registry Editor regedit.exe.
Navigate to the registry key
2.
HKEY_LOCAL_MACHINE\SOFTWARE\Tandberg\TANDBERG Management Suite Exchange
Integration .
If it does not exist, create a new registry key in this location.
TANDBERG Management Suite Exchange Integration
3. Select the
right click and select New > String Value. Name the new value TMS Id AD Attribute. Note that
this is case sensitive.
4. Double-click the newly created string value, and in the input field enter the name of the AD
attribute that you wish to use and click OK. Note that this field is also case sensitive.
5. Close the registry editor.
When running the Cisco TMSXE installer and Configuration tool, they will now use the custom
attribute ID defined in the registry key. If you need to make these changes and Cisco TMSXE has
already been installed; uninstall, set the key, and then reinstall Cisco TMSXE.

Additional Reference Materials for Administrators

The following sections are reference material for Exchange Administrators. These sections provide
additional details on the technology behind the Cisco TMSXE integration and the impact on the
Exchange Server itself so administrators can be confident in how the Cisco TMSXE software affects
their environment.

Functional Overview of Cisco TMSXE Integration

The calendaring functionality of Microsoft Outlook and Microsoft Exchange allows users to create
meeting events in their calendars, invite other participants, resources, or equipment directly from their
Outlook client. The workflow and steps to book such meetings are commonly understood by Outlook
users. Cisco TMSXE leverages the programmable extensibility of Microsoft Exchange to expand this
functionality to include functionality from Cisco TMS while making minimal or no changes to the User's
experience. This reduces training needed to deploy the product and makes scheduling of video
conference resources easier and more accessible.
To model rooms or equipment that can be invited to meetings by users, Exchange uses designated
mailbox and user accounts to represent what users can schedule. Exchange Server 2007 updates
this model by having special designations of ‗room' or ‗equipment'. These accounts have their own
calendars and permissions, just like a normal user. In a traditional installation, these accounts are
configured to automatically accept all meeting invitations sent to them, and their calendar is updated
so other users can see when the room is available.
Cisco TMS has its own database which maintains scheduling information and availability for all
systems it manages. Beyond availability, Cisco TMS also understands notions such as are other
resources such as is a MCU required? How to automate any call connections? Are the systems using
for example compatible protocols? Users are able to make requests to book resources managed by
Cisco TMS directly from the Cisco TMS web interface.
Cisco TMSXE Administrator Guide 2.2
key, and in the right panel,
Page 41 of 60