Cisco TELEPRESENCE MANAGEMENT SUITE User manual

Cisco TelePresence
Management Suite
Installation and Getting Started guide
D14389.04
December 2010

Operator safety summary (appliance)
Cisco TelePresence Management Suite Installation and Getting Started Guide Page 2 of 70
Operator safety summary (appliance)
Equipment markings
The lightning flash symbol within an equilateral triangle is intended
to alert the user to the presence of uninsulated “dangerous voltages”
within the product enclosure that may be of sufficient magnitude to
constitute a risk of electrical shock.
The exclamation mark within an equilateral triangle is intended to
alert the user to the presence of important operating and
maintenance (servicing) instructions accompanying the equipment.
Warnings
 Water and moisture - Do not operate the equipment under or near water - for example near a
bathtub, kitchen sink, or laundry tub, in a wet basement, or near a swimming pool or in areas with
high humidity.
 Cleaning - Unplug the apparatus from the wall outlet before cleaning or polishing. Do not use
liquid cleaners or aerosol cleaners. Use a lint-free cloth lightly moistened with water for cleaning
the exterior of the apparatus.
 Ventilation - Do not block any of the ventilation openings of the apparatus. Install in accordance
with the installation instructions. Never cover the slots and openings with a cloth or other material.
Never install the apparatus near heat sources such as radiators, heat registers, stoves, or other
apparatus (including amplifiers) that produce heat.
 Grounding or Polarization - Do not defeat the safety purpose of the polarized or grounding-type
plug. A polarized plug has two blades with one wider than the other. A grounding type plug has
two blades and a third grounding prong. The wide blade or third prong is provided for your safety.
If the provided plug does not fit into your outlet, consult an electrician.
 Power-Cord Protection - Route the power cord so as to avoid it being walked on or pinched by
items placed upon or against it, paying particular attention to the plugs, receptacles, and the point
where the cord exits from the apparatus.
 Attachments - Only use attachments as recommended by the manufacturer.
 Accessories – It is recommended systems only be used with a cart, stand, tripod, bracket, or table
specified by the manufacturer, or sold with the apparatus. When a cart is used, use caution when
moving the cart/apparatus combination to avoid injury from tip-over.
 Lightning - Unplug this apparatus during lightning storms or when unused for long periods of time.
 Servicing - Do not attempt to service the apparatus yourself as opening or removing covers may
expose you to dangerous voltages or other hazards, and will void the warranty. Refer all servicing
to qualified service personnel.
 Damaged Equipment - Unplug the apparatus from the outlet and refer servicing to qualified
personnel under the following conditions:
•When the power cord or plug is damaged or frayed
•If liquid has been spilled or objects have fallen into the apparatus
•If the apparatus has been exposed to rain or moisture
•If the apparatus has been subjected to excessive shock by being dropped, or the cabinet has
been damaged
•If the apparatus fails to operate in accordance with the operating instructions

Operator safety summary (appliance)
Cisco TelePresence Management Suite Installation and Getting Started Guide Page 3 of 70
Table of Contents
Operator safety summary (appliance) ................................................................................2
Equipment markings......................................................................................................................... 2
Warnings .......................................................................................................................................... 2
Table of Contents.................................................................................................................3
Introduction..........................................................................................................................6
Cisco TMS requirements .....................................................................................................7
Operating system .................................................................................................................................... 7
Web server .............................................................................................................................................. 7
Hardware Specifications................................................................................................................... 7
Version compatibility ........................................................................................................................ 7
Windows Server 2000 is no longer supported ................................................................................. 7
Microsoft .NET Framework 4.x now required................................................................................... 7
IIS 7 is required ................................................................................................................................ 7
Windows 2008 default firewall rules................................................................................................. 8
SQL database server............................................................................................................................... 8
SQL Server version compatibility..................................................................................................... 8
Cisco TMS operational............................................................................................................................ 8
Cisco TMS client...................................................................................................................................... 9
Minimum specifications.................................................................................................................... 9
Recommended specifications .......................................................................................................... 9
Installation and upgrade guidelines..................................................................................10
Moving the Cisco TMS database .......................................................................................................... 10
Dedicated vs. shared server.................................................................................................................. 10
Cisco TMS integration compatibility matrix ........................................................................................... 10
Device support....................................................................................................................................... 10
SQL database server guidelines ........................................................................................................... 11
Disk space...................................................................................................................................... 11
Local vs. Remote server................................................................................................................. 11
Database permissions.................................................................................................................... 11
Performing SQL database backups ............................................................................................... 12
Upgrading Windows 2000 to Windows 2003......................................................................................... 12
Restricting IIS 7 modules (optional) ...................................................................................................... 12
Ports required by Cisco TMS ................................................................................................................ 13
Version specific upgrade notes ........................................................................................14
Notes for upgrades from Cisco TMS 12.5/12.6..................................................................................... 14
Notes for all versions earlier than Cisco TMS 12.2........................................................................ 14
Notes for upgrades from Cisco TMS 12.1 or 12.2.......................................................................... 14
Notes for upgrades from Cisco TMS 12.0...................................................................................... 14
Notes for upgrades from Cisco TMS v11.x.................................................................................... 15
Additional Notes for upgrades from versions 9.x and 10.x ............................................................ 15
Additional notes for upgrade from versions prior to 9.x ................................................................. 15
Installation and upgrade of Cisco TMS.............................................................................16

Operator safety summary (appliance)
Cisco TelePresence Management Suite Installation and Getting Started Guide Page 4 of 70
Installation and upgrade requirements.................................................................................................. 16
Software requirements................................................................................................................... 16
Installing and upgrading Cisco TMS.................................................................................17
Initial installation process....................................................................................................................... 17
Complete installation process................................................................................................................ 18
Custom installation process................................................................................................................... 22
Configuring the Cisco TelePresence Management Server..............................................29
Installation precautions and hardware compliances ...................................................................... 29
Unpacking....................................................................................................................................... 30
Installation site preparations........................................................................................................... 30
Rack mounting (optional) ............................................................................................................... 30
Connecting cables................................................................................................................................. 31
LAN cable....................................................................................................................................... 31
Power cable.................................................................................................................................... 31
Connecting a Monitor and Keyboard (Optional)............................................................................. 31
IP address configuration........................................................................................................................ 31
Configuring the server IP address.................................................................................................. 32
Server OS configuration........................................................................................................................ 32
Configuring the server OS.............................................................................................................. 32
Operation, maintenance, and upgrading the Cisco TelePresence Management Server...................... 35
Cisco TelePresence Server Appliance Security Updates..................................................................... 35
Basic server tasks ................................................................................................................................. 35
Starting and stopping the Cisco TelePresence Management Server Appliance ........................... 35
Cisco TelePresence Management Server software installation/upgrades............................................ 36
Getting started with Cisco TMS.........................................................................................37
New installations verses upgrades................................................................................................. 37
Getting started topics............................................................................................................................. 37
Configuration topics ..........................................................................................................38
Cisco TMS user concepts...................................................................................................................... 38
Accessing Cisco TMS for the first time.................................................................................................. 39
Moving around Cisco TMS and the TMS GUI....................................................................................... 39
Permissions and groups in Cisco TMS ................................................................................................. 40
Configure a baseline permissions setup........................................................................................ 41
Review and set important Cisco TMS defaults...................................................................................... 42
WebEx integration.......................................................................................................................... 44
Cisco TMS routing and zones ............................................................................................................... 45
ISDN zones .................................................................................................................................... 45
IP zones.......................................................................................................................................... 45
Adding zones for initial configuration ............................................................................................. 46
Orientation topics...............................................................................................................47
The system navigator............................................................................................................................ 47
Set up default folders ..................................................................................................................... 47
Adding a system............................................................................................................................. 48
Viewing and editing a managed system......................................................................................... 49
Update automatically discovered systems..................................................................................... 50
Configuration templates......................................................................................................................... 50

Operator safety summary (appliance)
Cisco TelePresence Management Suite Installation and Getting Started Guide Page 5 of 70
Editing a template........................................................................................................................... 50
Creating a new template ................................................................................................................ 52
Applying templates to systems....................................................................................................... 52
Phone books.......................................................................................................................................... 53
The default ‘all systems’ phone book............................................................................................. 53
Scheduled conferencing........................................................................................................................ 53
Creating your first scheduled call................................................................................................... 54
Viewing existing conferences......................................................................................................... 56
Monitoring and managing ongoing conferences ................................................................................... 59
Conference control center.............................................................................................................. 59
Graphical monitor........................................................................................................................... 59
Monitoring an ongoing scheduled call............................................................................................ 60
Reporting............................................................................................................................................... 62
Appendix 1 – Uninstalling Cisco TMS...............................................................................63
Uninstalling the Cisco TMS Application................................................................................................. 63
Removing all Cisco TMS information from a server.............................................................................. 64
Checking for updates and getting help.............................................................................67
References and related documents..................................................................................68
Contact us...........................................................................................................................69
Document feedback ....................................................................................................................... 69

Introduction
Cisco TelePresence Management Suite Installation and Getting Started Guide Page 6 of 70
Introduction
The Cisco TelePresence Management Suite (Cisco TMS) is a portal for managing and monitoring your
video conferencing system from a single structured overview. Cisco TMS provides centralized control
for on-site and remote video systems, and a deployment and scheduling system for your entire video
network.
Cisco TMS can be downloaded from Cisco.com.
Cisco TMS is a powerful tool for maintaining, operating, and increasing the value of your conferencing
network. Cisco TMS adds intelligence, diagnostics, and functionality that enhance your video network
components and the return on your investment.
Cisco TMS automates system configuration for a basic H.323 network, operating ‘right out of the box’.
You can tune Cisco TMS default behavior to suit your organization needs, set up user permissions,
and configure your network model so that all of Cisco TMS call handling functionalities are available.
This document provides information for fresh installs, upgrading an existing version, or configuring the
Cisco TMS version that comes preinstalled on a Cisco TelePresence Management Server. There is
also a guide for uninstalling Cisco TMS.
Along with installation/upgrade processes, you will find guidelines on software and hardware
requirements, integrating Cisco TMS with other applications, and version specific upgrade information.
Further information on Cisco TMS functionality is available online. Cisco also maintains a Cisco TMS
knowledgebase.
Note: For the Cisco TMS user guide, see the online help available via the question mark icon (?) on
the Cisco TMS client.
A list of relevant documents referred to in this guide can be found in the References and related
documents section.

Cisco TMS requirements
Cisco TelePresence Management Suite Installation and Getting Started Guide Page 7 of 70
Cisco TMS requirements
This section details software and hardware requirements. Review and verify these requirements
before installing, upgrading or configuring your preinstalled Cisco TelePresence Management Servers.
Operating system
Previous versions of Cisco TMS required a 32bit Windows operating system.
Note: As of version 13 Cisco TMS functions with 64bit Windows 2008 operating systems. See below
for further details.
The operating system must be English, Japanese or Chinese.
Web server
Hardware Specifications
Pentium compatible processor:
2GHz or higher
Memory:
1GB RAM or more (2GB or more recommended)
For Provisioning, 2GB or more is recommended. The installer will warn you
during installation if less than 2GB is detected.
Disk Space:
4GB for installation and application footprint
(Additional space is required if you are installing the SQL Server
locallyD14389_TANDBERG_ Management_Suite_
Installation_and_Getting_Started_Guide(ek_edit).docx -
_SQL_Database_Server)
Version compatibility
The following Windows versions are compatible with Cisco TMS:
 Windows 2003 Server Standard/Enterprise/DataCenter Editions w/SP1 or greater (latest Service
Pack recommended)
 Windows 2003 R2 Standard/Enterprise/DataCenter Editions w/SP1 or greater (latest Service
Pack recommended)
 Windows 2008 R1 or R2 Standard 32bit and 64bit Editions (latest Service Pack recommended)
Windows Server 2000 is no longer supported
Microsoft Windows Server 2000 (any version) is no longer supported. Customers running Cisco TMS
on a Windows Server 2000 OS must upgrade their server to Windows Server 2003. See Upgrading
Windows 2000 to Windows 2003.
Microsoft .NET Framework 4.x now required
Cisco TMS 13.x requires Microsoft .NET Framework version 4.x. The Cisco TMS installer prompts you
to install .NET 4.x if it is not detected. (Previously, Cisco TMS 12.x required Microsoft .NET
Framework version 3.5).
IIS 7 is required
If you are using Windows 2008 Standard 32bit or 64bit Editions, the installer will install IIS 7 if it is not
already present.

Cisco TMS requirements
Cisco TelePresence Management Suite Installation and Getting Started Guide Page 8 of 70
Windows 2008 default firewall rules
Windows Server 2008 includes a new Windows Firewall feature that controls both inbound and
outbound ports. This feature is enabled by default. If Windows Firewall is enabled, the ports required
for Cisco TMS must be opened. For details see Ports required by Cisco TMS.
SQL database server
SQL Server version compatibility
Note: Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) and Microsoft SQL 2000 are no
longer supported. Assistance on upgrading to SQL 2005 Server can be found in the Cisco TMS
Database Knowledge Base Tips.
Cisco TMS supports:
 Microsoft SQL Server 2005 Database Server with Mixed Authentication Mode enabled. All 32bit
versions of Microsoft SQL Server 2005, including the Express Edition (see caveat below)
 Microsoft SQL Server 2008 both 32bit and 64bit
Note: Large installations with databases more than 4GB must use a full edition of SQL Server 2005,
because of the 4GB database limitation in Express Edition.
If there is not an SQL DB present on the server, MS SQL Server 2008 Express 32 bit will be installed.
Cisco TMS operational
The following are required by Cisco TMS to function properly:
 Domain Membership Preferred – Each user logging into Cisco TMS needs a Windows User
Login to authenticate: either a local account on the Cisco TMS Windows Server or a Domain
account that the server trusts through Active Directory. By making the server a member of the
domain, trusted domain users will automatically be able to use their Windows credentials to log
into Cisco TMS. You can still limit user permissions using Cisco TMS. Active Directory
membership is the recommended deployment for most installations because it avoids creating
local Windows accounts for each user.
 ASP.NET and ASP Enabled – These IIS components must be enabled. If you are using
Windows 2008, see Installing IIS 7 for Windows 2008.
 Cisco TMS Web site Accessible by IP and Hostname - Because not all devices support DNS
hostnames or Port Numbers, Cisco TMS must be accessible by an IP Address on port 80. Some
functionality requires Cisco TMS to be reachable by hostname; therefore, Cisco TMS is also
accessible by a fully qualified hostname.
 Mail Server Access - Cisco TMS requires access to an SMTP (Mail) server to send emails. Cisco
TMS does not require its own SMTP server and can be configured to use existing mail servers. If
you are unsure which server to use, contact your IT administrator. (Cisco TMS supports SMTP
Auth login for authentication if required.)
 Network Access to Managed Devices – Cisco TMS needs specific protocols and access to
manage devices. Any network firewalls or NAT routers must allow traffic to flow to and from Cisco
TMS. The specific protocols and directions in use will vary depending on devices being managed:
see the Cisco TMS Product Support document (available on the Cisco TMS installation media) for
specific information about firewall requirements for each type of supported device.
 DNS records and Provisioning Directory functionality (Cisco TMS Agent) – In installations
using the Cisco TMS Provisioning Directory functionality for Cisco TelePresence Movi and E20
deployments, the local hostname of the Cisco TMS server must match the DNS A record for the
Cisco TMS Agent to operate correctly.

Cisco TMS requirements
Cisco TelePresence Management Suite Installation and Getting Started Guide Page 9 of 70
 TCP Port 25 – Many anti-virus programs block applications from sending mail directly using the
SMTP Port (TCP Port 25). Verify your anti-virus program is configured to allow
this.http://www.tandberg.com/support/video-conferencing-
documentation.jsp?selProducts=73&selProductType=&selDocumentType=24&selDisplayType=1
&SearchButton.x=50&SearchButton.y=12&SearchButton=Search
Cisco TMS client
Cisco TMS is accessed by both administrators and users via a web browser. Disable all pop-up
blocking functions for the Cisco TMS web site.
Minimum specifications
 Microsoft Internet Explorer 6.0 or later
 Mozilla Firefox 2.0 or later
 Java Virtual Machine Runtime Engine (JRE) 1.5.0 or later
 A Windows username and password to the Cisco TMS Server (either a local machine account, or
a domain account, if the server is joined to a domain)
Recommended specifications
 Microsoft Internet Explorer 7.0 or 8.0
 Mozilla Firefox 4.0 or 5.0
 Java Virtual Machine Runtime Engine (JRE) 1.5.0 or later
A Java Virtual Machine Runtime Engine (JRE) is required to use the Cisco TMS monitoring function. If
browser does not automatically prompt to download and install the missing browser plug-in, you can
install it manually from the JRE installation file found on the Cisco TMS installation media or at
http://www.java.com.

Installation and upgrade guidelines
Cisco TelePresence Management Suite Installation and Getting Started Guide Page 10 of 70
Installation and upgrade guidelines
Cisco TelePresence recommend reviewing these guidelines before installation or upgrading, and
cover a number of issues that may relate to your Cisco TMS application.
Moving the Cisco TMS database
To move the Cisco TMS database to a new server, it is recommended the database and/or database
server be moved prior to running the Cisco TMS v12 installer. Use the standard Microsoft SQL tools
(the Cisco TMS database is named ‘TMSng’), and then select ‘Custom’ during the Cisco TMS v12
installation. You can then specify the database location.
Dedicated vs. shared server
Cisco TMS is resource intensive with specific server requirements and installation is not
recommended on a server hosting other applications or web sites. CPU time and memory usage will
vary between installations depending on the activity level and size of the video network being
managed.
Note: Cisco TelePresence will not support installations on shared servers. Cisco TelePresence
strongly recommends installing Cisco TMS on a dedicated server.
Cisco TMS can be installed on a Virtual Server, but the Cisco TMS virtual machine (child partition)
must be provided with sufficient processor resources, memory, and disk resources. The minimum
requirements assume Cisco TMS has full access to resources. Cisco TMS runs on VMWare ESX and
Virtual Server products and on Microsoft Virtual Server 2007.
Cisco TMS integration compatibility matrix
Note: The most recent software versions may be required for all features and fixes to be available.
Product Compatible Version
TANDBERG See&Share v3.3
Cisco TelePresence Microsoft Exchange Integration All Versions
Cisco TelePresence Microsoft LCS Integration All Versions
Cisco TelePresence Conferencing eXtensions All Versions
Cisco TMS – IBM Lotus Notes Integration All Versions
Cisco TMS - IBM Lotus Sametime Integration All Versions
Cisco TelePresence Movi for IBM Lotus Sametime All Versions
Cisco TelePresence Management Suite Extension Booking API All Versions
Device support
Cisco TMS supports video conferencing systems from both Cisco TelePresence and other major
vendors, and Cisco TelePresence constantly strives for the best possible feature parity. However, due
to differences in capabilities and APIs, some features of Cisco TMS and device support are dependent
on the individual products and their software versions. Some system types require additional
configuration.
Cisco TelePresence maintains Cisco TMS Product Support Documentation, including information on:
 version compatibility information
 network requirements (firewall information)
 device configuration settings

Installation and upgrade guidelines
Cisco TelePresence Management Suite Installation and Getting Started Guide Page 11 of 70
 feature support
 device notes
This information is available on the Cisco TMS installation media and the Cisco TelePresence support
web pages. Be sure to use the revision of the document that applies to your Cisco TMS version.
SQL database server guidelines
Cisco TMS stores all its customer data in its SQL database named ‘TMSng’. This self-contained
storage allows for convenient backup and recovery of customer information.
Disk space
Smaller deployments (<100 systems) can, on average, expect database sizes on the order of 50MB –
2GB. Medium deployments (100-500 systems) can expect databases on the order of 1GB-6GB, and
very large or very heavy networks can expect databases of approximately 6GB-10GB.
Microsoft SQL Server automatically sets and manages database size. Cisco TMS also provides a
method to manage growth in Administrative Tools > TMS Server Maintenance, where you can set
data retention limits.
Local vs. Remote server
The SQL database server and Cisco TMS can be both be hosted on the same machine, or on
separate machines. During installation, you can choose between using an existing SQL Server or
installing MS SQL Server 2008 Express 32 bit locally on the Cisco TMS server.
Running SQL on a separate server is strongly recommended for large (100+ system) or high-usage
video networks because there are performance benefits due to the high memory and disk I/O load
associated with running an SQL Server. A separate server solution improves Cisco TMS performance
by freeing up memory and disk resources.
If your TMSng database is on an external Microsoft SQL Server 2005, set the Microsoft SQL Server
compatibility level 90.
Database permissions
The SQL database server must have Mixed Mode Authentication enabled; Windows Authentication is
not supported by the Cisco TMS installer. For new installations, the installer creates a database
named ‘TMSng’ using the SQL Server defaults. Upgrades will reuse an existing Cisco TMS database.
When installing or upgrading Cisco TMS and using an existing SQL Server, the Cisco TMS installer
prompts for a SQL user and password. The default is to enter the server sa (system administrator)
username and password. If the sa account is not available, use one of the following:
 Automatic setup, but with security limited role. Ask your SQL server administrator to create a
SQL user and login that has the ‘dbcreator’ and ‘securityadmin’ server roles. This account will be
the service account for Cisco TMS. When prompted for SQL Server credentials during installation,
enter the username and password for that account. Cisco TMS will create the ‘TMSng’ database
automatically using the server defaults and assign itself as the owner. Cisco TMS will continue to
use the supplied account to access the database after installation.
 Manual database creation, max security limited role. Ask your SQL server administrator to
create:
•A database named 'TMSng' with the appropriate options. The database collation must be
SQL_Latin1_General_Cp1_CI_AS or SQL_Latin1_General_Cp1_CS_AS.
•An SQL user and login to use for the Cisco TMS Service account and grant the user the
‘dbowner’ role for the ‘TMSng’ database.
When you are prompted for the SQL Server credentials during installation, enter the username and
password for that account. The Cisco TMS installer will populate the ‘TMSng’ database as required,
and will continue to use this account to access the database after installation.

Installation and upgrade guidelines
Cisco TelePresence Management Suite Installation and Getting Started Guide Page 12 of 70
Note: For Cisco TMS to function properly the SQL user supplied for Cisco TMS to use must always
have ‘dbowner’ permission on the ‘TMSng’ database, even after installation.
Performing SQL database backups
Follow best practices and take regular backups of the Cisco TMS SQL database named ‘TMSng’.
Backups can be performed on the server via a local console or Windows Remote Desktop. Additional
help on performing SQL backups is available in the Cisco TMS Database Knowledge Base Tips
document available on the Cisco TMS installation media. It is recommended that backups are stored
at a separate location for maximum protection.
Note: The Cisco TelePresence Management Server is delivered with remote SQL access disabled.
If you enable remote access to the SQL Server for backup purposes, be sure to change the SQL sa
password from the default password. If you change the SQL password, update TMS Database
Connection properties using the TMS Tools application installed in the TANDBERG Program Group on
the Cisco TelePresence Management Server.
Note: A Cisco TMS Agent database backup can be performed and scheduled by going to the TMS
Agent Settings page found under Administrative Tools > Configuration > TMS Agent Settings.
Upgrading Windows 2000 to Windows 2003
If you are upgrading from Windows 2000 to Windows 2003, Microsoft recommends performing a clean
installation.
Cisco TelePresence recommends backing up the Cisco TMS database, along with any customized
customer files, before upgrading Windows. After the Windows upgrade, reinstall your original Cisco
TMS version and restore the Cisco TMS database backup. Then upgrade to Cisco TMS v12 or newer.
Additional assistance on backing up and restoring Cisco TMS can be found in the Cisco TMS
Database Knowledge Base.
Restricting IIS 7 modules (optional)
IIS 7 has a modular system that allows administrators to install and enable components to customize
server security. The following modules are required for Cisco TMS. Modules may be controlled at
either site or server level (some are server level only) – the following steps assume that you are
making changes at the server level.
To modify which modules are enabled in IIS 7:
1. Go to Start Menu > Administrative Tools > Internet Information Services (IIS) Manager and
open the Internet Information Services (IIS) Manager.
2. From the tree in the left panel, click on your server name.
3. In the center panel, under IIS, double-click Modules.
The list of installed Managed and Native Modules is displayed. Modules that are not needed can
be removed by clicking on them, and then clicking Remove from the Action Panel on the right.
The following modules are required for Cisco TMS and must not be removed:
•AnonymousAuthenticationModule
•BasicaAuthenticationModule
•DefaultDocumentModule
•DigestAuthenticationModule
•HttpCacheModule
•HttpLoggingModule(recommended)
•HttprRedirectionModule
•IsapiFilterModule
•ProtocolSupportModule
•RequestFilteringModule
•Session
•StaticCompressionModule
•StaticFileModule
•WindowsAuthentication
•WindowsAuthenticationModule

Installation and upgrade guidelines
Cisco TelePresence Management Suite Installation and Getting Started Guide Page 13 of 70
Ports required by Cisco TMS
The default Windows Server 2008 firewall rules interfere with Cisco TMS communications. Cisco TMS
will not function properly until these Windows Firewall port settings are modified.
The following ports are used by Cisco TMS and must be enabled in the Windows Firewall. See the
Cisco TMS Product Support document for port specifics for each managed device type.
Administrators can disable Windows Firewall or open the ports required for Cisco TMS. See
http://technet.Microsoft.com/en-us/library/cc748991.aspx for Microsoft documentation on configuring
firewall rules.
Note: Cisco TMS cannot use multiple network cards on a server and will only bind to the first
available network interface. Cisco TMS can manage a public and private network so long as the
public network connection is further upstream from Cisco TMS, rather than being directly connected
to Cisco TMS (using multiple network interface cards).

Version specific upgrade notes
Cisco TelePresence Management Suite Installation and Getting Started Guide Page 14 of 70
Version specific upgrade notes
Review the notes for your current version of Cisco TMS before starting your upgrade.
Notes for upgrades from Cisco TMS 12.5/12.6
When installing and upgrading to Cisco TMS 13.0, Cisco TelePresence recommends upgrading the
Device Provisioning and Cisco VCS Database components on the Cisco VCS (Cisco TelePresence
Video Communication Server).
Also note the .NET requirements have changed. Cisco TMS version 12.x required .NET 3.5. Version
13.x requires .NET 4.0. The installer will warn you to install the correct version of :NET if it is not
detected.
The Cisco VCS must be running or upgraded to X5.1.1 before installing these components. To
upgrade the Cisco VCS go to Maintenance > Upgrade and select the relevant upgrade component
file. It is recommended replication between the Cisco TMS and any Cisco VCS be disabled when
upgrading these components.
With regard to DNS records and Provisioning Directory functionality (Cisco TMS Agent), DNS
reverse lookups (PTR records) that were required in Cisco TMS 12.5, are no longer required for Cisco
TMS 12.6/13.x. (Note that the same requirement applies to the Cisco VCS. See the Cisco VCS
Software Release Notes (X5) at Cisco TelePresence support documentation.)
Within Cisco TMS 12.6, under Administrative Tools > General Settings, note that Enable TMS
Agents is set to No by default. If enabled, Cisco TelePresence recommends going to Cisco TMS
Agent Diagnostics under Administrator Tools > TMS Agent Diagnostics to confirm that the Local
Cisco TMS Agent shows no errors and that all diagnostic tests are OK.
If any errors are found on the Local Cisco TMS Agent, then these errors need to be fixed before
proceeding with replication to any Cisco VCS. Refer to the Diagnostic section within Cisco TMS
Provisioning Deployment Guide for help troubleshooting errors found on the Local Cisco TMS Agent.
Warning: Upgrades will be blocked if the procedures found in this document are not followed
appropriately. The error message will state that Provisioning on all clusters must be disabled before
upgrading to 12.6.
Notes for all versions earlier than Cisco TMS 12.2
A onetime database clean-up is required when upgrading versions Cisco TMS 12.1 or earlier.
For a large installation this can take 30 to 60 minutes depending on the performance of the SQL
server, the type and number of calls scheduled in Cisco TMS, and the participant count. For most
installations however, this process only takes an additional minute or two.
During this clean-up process, you will see a ‘Upgrading from Cisco TMS 12.x to Cisco TMS 12.x’
notification. The progress bar may not move but the installation is still running. Please be patient! Do
not stop or attempt to stop the installation process during this step.
For more details about this update, see the Installation and Upgrades section of the Cisco TMS 12.6
part of the Cisco TMS v12 Release Notes.
Notes for upgrades from Cisco TMS 12.1 or 12.2
If you are upgrading Cisco TMS from either 12.1 or 12.2 and Cisco VCS to X5 software, you must
follow the upgrade procedures found in the Cisco VCS Deployment Guide - Cluster creation and
maintenance (X5) documentation available at Cisco TelePresence online support.
Note: Your upgrade process will be blocked and need to be restarted if the procedures found in this
document are not followed. The error message states that provisioning on all clusters needs to be
disabled.
Notes for upgrades from Cisco TMS 12.0
It is recommended you review the Provisioning Directory Deployment Guide if:

Version specific upgrade notes
Cisco TelePresence Management Suite Installation and Getting Started Guide Page 15 of 70
 You have Cisco VCS clusters defined in Cisco TMS 12.0. See the section on clustering for
instructions on changes to cluster configuration with Cisco VCS X4.1 software.
 You use Provisioning Directory and Movi, review software dependencies between Cisco TMS and
Cisco VCS.
If you participated in the Movi Beta, it is recommended you refer to their Beta Community Point of
Contact for specific upgrade instructions.
Notes for upgrades from Cisco TMS v11.x
If you are using a Cisco TelePresence Content Server (TCS) with Cisco TMS, all TCS must be running
version S2.0 or later. If you are upgrading from versions prior to S2, update all the server
configurations and update any future bookings (see the Supplement Notes for Manuals section of the
Cisco TMS v11.6 release in the Cisco TMS v11 Release Notes document available from the Cisco
TelePresence web site.
Starting with Cisco TMS v12.0, permissions underwent slight reorganization. It is recommended that
administrators who implement different user levels through permissions review their user group
permissions after upgrading to Cisco TMS v12, and adjust the permissions to their intended settings if
necessary.
Additional Notes for upgrades from versions 9.x and 10.x
Cisco TMS has gone through significant changes since these releases, and while the Cisco TMS
installer will import existing data, there are many new settings and existing settings that have changed.
Be sure to work through the Administrative Tools settings after installation to populate and update the
Cisco TMS installation. In particular, the permissions model has been overhauled and Group
Permissions and System Permissions must be reviewed and updated. Expect inconsistent behavior
between different systems until Cisco TMS has refreshed the configuration of each system – normally
this will happen automatically within 1-4 hours.
Additional notes for upgrade from versions prior to 9.x
Cisco TelePresence recommends a new installation rather than performing upgrade installations older
than Cisco TMS 9.0., although the Cisco TMS installer will still import existing data. Server
requirements have changed significantly, as well as the configuration and functionality throughout the
product making most direct upgrades significantly more complex than simply performing a new
installation on a new host server.

Installation and upgrade of Cisco TMS
Cisco TelePresence Management Suite Installation and Getting Started Guide Page 16 of 70
Installation and upgrade of Cisco TMS
Installation and upgrade requirements
Before you start make sure that you have:
 reviewed the Cisco TMS requirements and Installation and upgrade guidelines sections
 the Windows CD-ROM available (it may be required for installing some Windows components)
 ensured the DNS servers used by Cisco TMS contain forward lookups for the TMS server
Cisco TMS requires specific server and network elements for correct installation:
 Administrator access to the Windows server and database. You must have administrator
rights to the Windows Server. If an existing database server is to be used, you must have the
login information to be used as the Cisco TMS service account (see Database permissions).
 MS DOS or access to execute *.cmd and *.bat files (not necessarily the command prompt) must
be available on the server to install the OpenDS and Provisioning components.
Software requirements
These software applications are required and automatically installed if not present:
 Windows SNMP Services
 MS SQL Server 2008 Express 32 bit (an existing supported SQL Server can also be used)
If you are running Windows 2008 Standard/Enterprise/DataCenter, the following software component
is required:
 IIS 7
If this component if it is not present, it is installed via the Cisco TMS installer.

Installation and upgrade of Cisco TMS
Cisco TelePresence Management Suite Installation and Getting Started Guide Page 17 of 70
Installing and upgrading Cisco TMS
The installation/upgrade process is made up of two parts. After completing an initial setup process, the
next process will depend on whether you choose a complete or custom installation.
Note: You may be prompted to reboot the server more than once during installation. The installer
automatically resumes after the server reboots.
Initial installation process
1. Close all open applications and disable virus-scanning software.
2. Extract the compressed Cisco TMS ZIP file to a folder and double-click Browse.bat in the root
directory. (It may be necessary to use a RAR decompressor application).
3. Click Cisco TelePresence Management Suite.
4. You will receive a language prompt. This language is only used during the installation and does
not affect Cisco TMS after installation. Select the Cisco TMS Installer language and click Next.
The installer checks for required software components. A warning message will be displayed if
any components are missing. Follow the prompts and install any missing components.
5. If an earlier version of Cisco TMS is currently installed, you are prompted to upgrade. To upgrade
- remove the old Cisco TMS and upgrade the existing Cisco TMS database, click Yes. To abort
the installation and leave the current installation untouched, click No.
6. You are prompted to choose from two processes: Complete or Custom. They are detailed in the
following two sections.
 Complete uses default settings. It can be used for upgrades of existing installations with both local
and remote SQL installations, and is the recommended choice for performing upgrades.
 Custom allows you to specify all the options such as the installation path and SQL server choices.
7. Select Complete or Custom and click Next.
Figure 1 Select Complete or Custom.

Installation and upgrade of Cisco TMS
Cisco TelePresence Management Suite Installation and Getting Started Guide Page 18 of 70
Complete installation process
Follow the process in this section if you chose ‘Complete’ for your installation type.
8. The installer searches for an existing SQL Server and Cisco TMS database.
a. If an existing database connection is found, the existing Cisco TMS database is used. When
prompted, enter the username and password to connect to the existing SQL server and click
Next. Go to step 2.
b. If no existing Cisco TMS database connection is found, the installer looks for a local SQL
server. If one is found, enter the username and password necessary to access the server and
allow the installer to create a new Cisco TMS database. Click Next and go to step 4.
c. If no existing Cisco TMS database connection or local SQL server is found, MS SQL Server
2008 Express 32 bit is installed and a new Cisco TMS database is created. When prompted,
enter a password for the sa account (administrator). Click Next and go to step 4.
Note: Be sure to note the sa password somewhere secure as it is required for future upgrades and
Cisco TMS maintenance.
Note: If the Cisco TMS server is in a domain or you have a local policy that has a strong password
policy, ensure that you use a strong password for the SQL installation.
Figure 2 SQL server user name and password.
9. You can re-use the existing database:
 To update the existing database to a current version and retain existing information, click Yes. Go
on to the next step.
 If you wish to install a new Cisco TMS database, then manually remove the existing database
from the SQL server, click No to abort the install.
10. Cisco TelePresence recommends that you take a backup of your existing database.
 To perform the backup, enter a path for the backup file and filename, or click Browse to navigate
to a folder. (The backup is done on the SQL Server itself, so these values are local to the SQL
Server.) Click Backup to start the backup. When the backup is complete (it may take several
minutes), click Next.

Installation and upgrade of Cisco TMS
Cisco TelePresence Management Suite Installation and Getting Started Guide Page 19 of 70
 The backup is optional. To skip it, click Next.
Figure 3 Backup database.
Note: The installer automatically places the provisioning database (OpenDS) backup in the Cisco
TMS backup folder (by default, <TMS folder>\wwwTMS\Data\Backup\opends).
11. If you are upgrading, the ‘release and option keys page’ is displayed and any existing keys are
shown. Enter the key(s) to enable additional systems or feature support, such as Network
Integration or other external integration packages. A new release key is also required when
upgrading to a new major release. The release key must be entered before adding option keys.
For questions regarding release or option keys, contact your reseller or Cisco TelePresence
Support.
Figure 4 Release and option keys.
(If no release key is entered, Cisco TMS installs an evaluation version which includes support for
three systems, twenty-five clients for Cisco TMS, and Cisco TMS Scheduler.)
To add an option key, click Add Option and enter the key. Keys are validated before being added.
(Option keys can also be added post-installation via Administrative Tools.) Click Next.
You can now configure a range of default settings that allow Cisco TMS to immediately start
working with a basic network configuration (these settings can be amended after installation). After

Installation and upgrade of Cisco TMS
Cisco TelePresence Management Suite Installation and Getting Started Guide Page 20 of 70
configuration, Cisco TMS can automatically discover, monitor, log, provide phone books, and
schedule a basic existing H.323/SIP network.
Customizing Cisco TMS is covered in the Cisco TMS user guide, available via the question mark
icon (?) on the Cisco TMS client.
12. The Network Settings screen is displayed with values from the existing database (if appropriate).
Cisco TMS contacts the supplied SMTP Server to verify the settings and warns you if it was
unable to contact the server.
Figure 5 Network Settings.
 TMS Server IP Address – the IP address of the local server.
 TMS Server IPV6 Address – The IPv6 address of the local server. If IPv6 is not enabled on the
Windows Server, this field can be left blank.
 IP Broadcast Address […] – Cisco TMS will automatically search these networks for devices
using these broadcast address(es). (The management settings of systems that Cisco TMS
discovers can be automatically). For multiple broadcast addresses, separate each entry with a
comma. Cisco TMS will search any networks by sending a SNMP Discovery packet to the
supplied addresses. The default value will be the broadcast address of the Cisco TMS server
network.
 Enable automatic registration of systems in TMS – If enabled, systems Cisco TMS discovers
on the network will automatically be added into a folder in Cisco TMS and have their management
settings configured. The default value is Disabled.
 Sender Email Address – Enter the mail address you wish to appear as the ‘FROM’ mail address
in emails sent by Cisco TMS. Example: videomanagem[email protected]
 SMTP Server IP Address – The network address of the SMTP server that Cisco TMS will use to
send emails. If necessary, additional authentication settings can be configured after installation.
13. Change the settings as required and then click Next.
Zones are a Cisco TMS configuration concept used to route phone numbers and aliases when
scheduling calls and using phone books. The information entered creates the first IP Zone and
ISDN zone, and the default value to allow a basic IP network to operate immediately after
installation. Additional zones can be added post-installation for networks with multiple locations or
more complex elements.