Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Upgrading to 13.2.2
Cisco TelePresence Management Suite 13.2.2 Software Release Notes
Page 7 of 10
Equipment
Summary
Cisco TMS
Uploading software files larger than 30MB using
Systems > System Upgrade >
Software Manager >
Upload New Software will not work if Cisco TMS is running on
a Windows 2008 server. Software files larger than 30MB must be copied directly to the
folder specified in
folder specified in
Administrative Tools > Configuration > Network Settings >
General Network Settings >
URL Where Software Packages Can Be Downloaded.
This is a default limitation of IIS7.
Upgrading to 13.2.2
Prerequisites and software dependencies
The operating system and database server requirements for Cisco TMS have not changed in this release. Refer to
the
the
operating systems and database servers.
Important notes for installations using Cisco TMS Agent Legacy
For installations using the Provisioning Directory of Cisco TMS (used for Cisco Jabber Video for TelePresence and
large scale provisioning) there is a software version dependency between Cisco TMS and Cisco VCS. The TMS
Agent that runs on the Cisco VCS must be compatible with the version running in the Cisco TMS installation and may
require additional steps to perform an upgrade. The TMS Agent included with Cisco TMS version 13.2.2 is
backwards compatible with the version shipped with Cisco VCS version X5.2 or later and is unchanged from Cisco
TMS version 13.2.
large scale provisioning) there is a software version dependency between Cisco TMS and Cisco VCS. The TMS
Agent that runs on the Cisco VCS must be compatible with the version running in the Cisco TMS installation and may
require additional steps to perform an upgrade. The TMS Agent included with Cisco TMS version 13.2.2 is
backwards compatible with the version shipped with Cisco VCS version X5.2 or later and is unchanged from Cisco
TMS version 13.2.
Caution: If you use or intend to use the Cisco TMS Agent Legacy and Provisioning Directory features of Cisco TMS,
the following must be strictly adhered to before starting an upgrade of Cisco TMS:
the following must be strictly adhered to before starting an upgrade of Cisco TMS:
Before upgrading, Cisco recommends ensuring you have a backup of the Cisco TMS Agent Legacy data. This
can be accomplished using the TMS Agent Setting page located at
can be accomplished using the TMS Agent Setting page located at
Administrative tools > Configuration >
TMS Agent Setting
.
If you are upgrading Cisco TMS from a version earlier than 12.6, or your Cisco VCS servers are not running
X5.2 or later software, you must follow the upgrade procedures in the document
X5.2 or later software, you must follow the upgrade procedures in the document
Cisco TMS. Cisco TMS version 13.2.2 is not specifically mentioned in the guide, but is interchangeable with
references to Cisco TMS 13.0 or Cisco TMS 12.6.
references to Cisco TMS 13.0 or Cisco TMS 12.6.
The local hostname of the Cisco TMS server must match the DNS A record of the server for Cisco TMS Agent
Legacy to operate correctly. Ensure that the DNS servers used by Cisco TMS contain forward and reverse
(PTR) lookups for the Cisco TMS server.
Legacy to operate correctly. Ensure that the DNS servers used by Cisco TMS contain forward and reverse
(PTR) lookups for the Cisco TMS server.
For specific instructions on setup of the Provisioning Directory feature of Cisco TMS, see
and
Important notes for all installations
To upgrade an existing installation, you will need the SQL Server ‘sa’ password from the initial Cisco TMS
installation to complete the upgrade.
installation to complete the upgrade.
Upgrades will interrupt Cisco TMS availability as the installation requires Cisco TMS services to be stopped and
the server rebooted.
the server rebooted.
If upgrading from a version earlier than Cisco TMS 12.6, the default Booking Confirmation email templates and
phrase files will be updated. If you have customized these templates, these changes are not automatically
added to your customized files but will still be available for use. To see the default usage of these new values
and have them in your templates, customers with customized Booking Confirm templates or phrases must use
the Revert to Default
phrase files will be updated. If you have customized these templates, these changes are not automatically
added to your customized files but will still be available for use. To see the default usage of these new values
and have them in your templates, customers with customized Booking Confirm templates or phrases must use
the Revert to Default
button on the
Edit Email Template
page. Once reset, you may re-add your
customizations to the templates or phrase files.