Datasheet

Cisco Preferred Architecture for
Midmarket Collaboration PAGE 35
Applications
Cisco TelePresence Management Suite Extension for Microsoft Exchange (TMSXE)
TMSXE allows end users to schedule meetings using their Microsoft Outlook clients and including room video systems.
Room resources in Microsoft Exchange are mapped to systems within TMS. When resources are booked in Exchange,
TMSXE provides TMS with the following information:
•
User requesting the meeting
•
Meeting subject
•
All TMS associated resources
The TMS scheduling engine then uses conference templates to build the meeting and provides connection information
back through Exchange to the end user.
Recommended Deployment
Deploy a single instance of TMS for the organization, and leverage the integrated system navigator folder structure to
organize all endpoints and infrastructure devices. Even multinational and global organizations can benefit from a single
instance of TMS to facilitate video connections.
For Cisco BE 6000 deployments, TMS and all of its supporting components can be installed on a single Windows server
instance. This is called a TMS Regular Deployment and is subject to the following constraints:
•
TMS Solution — TelePresence Management Suite (TMS), TelePresence Management Suite Provisioning Extension
(TMSPE), TelePresence Management Suite Extension for Microsoft Exchange (TMSXE), and an embedded
Microsoft SQL server all reside on a single virtual machine.
•
TMS
◦ Maximum of 200 controlled systems
◦ Maximum of 100 concurrent participants
◦ Maximum of 50 concurrent ongoing scheduled conferences
•
TMSXE
◦ Up to 50 endpoints bookable in Microsoft Exchange
•
TMSPE
◦ Up to 1,000 Collaboration Meeting Rooms
Redundancy for TMS and TMS Extensions
Redundancy of TMS and its extensions is different from other components in the Preferred Architecture. TMS and TMSPE
operate in an active/passive node model instead of clustering.
Redundancy for TMS requires an external Microsoft SQL database on a separate server from the TMS application server.
This instance of SQL may be shared by other applications within the organization. Also necessary for redundancy to work
effectively, a network load balancer (NLB) must be deployed in front of the TMS/TMSPE application server. Because this
is outside the scope of a TMS deployment on the BE 6000, redundancy for TMS and its extensions is not included in the
Cisco PA for Midmarket Collaboration.
See the Cisco TelePresence Management Suite Installation and Upgrade Guide for details on larger deployments with full
redundancy for TMS and TMS extensions.
Benefits
The benefits of a properly configured and deployed TMS instance, with the software extensions, provide end users with a
user-friendly and feature-rich experience.
•
Conferences for video, voice, and web participants are scheduled through a single unified interface.
•
On supported endpoint devices, users can launch a conference session with One Button to Push (OBTP), according
to the device schedule.