Cisco Cisco TelePresence Management Suite (TMS) Version 15 Installation Guide
Using SQL Server Versions Earlier than 2008 R2 and Windows Server Versions Earlier than 2008
R2
R2
In 14.4 and 14.6, SQL and Windows server requirements changed. If you are upgrading Cisco TMS, and you are run
ning SQL Server versions earlier than 2008 R2 and/or Windows Server versions earlier than 2008 R2, you must
upgrade your servers prior to upgrading Cisco TMS. We recommend upgrading to SQL Server and Windows Server
2012.
ning SQL Server versions earlier than 2008 R2 and/or Windows Server versions earlier than 2008 R2, you must
upgrade your servers prior to upgrading Cisco TMS. We recommend upgrading to SQL Server and Windows Server
2012.
Instructions for Customers Upgrading from 14.4 or 14.4.1 Who Use Cisco TMSXE
Upgrading Cisco TMSXE and Cisco TMS
Customers who use Cisco TMSXE and are upgrading from 14.4 or 14.4.1 must follow these upgrade instructions in
the order given:
the order given:
1.
Upgrade Cisco TMSXE to version 4.1.
2.
Upgrade to this version of Cisco TMS.
3.
Wait for 15 minutes, then check the Cisco TMSXE log: TMSXE-log-file.txt for a line saying:
INFO
ReplicationEngine - No changes on TMS
.
This confirms that all problematic bookings Cisco TMS could resolve automatically have been replicated
correctly from Cisco TMS to Microsoft Exchange.
correctly from Cisco TMS to Microsoft Exchange.
If you do not see this line, contact your Cisco support representative.
Resolving Duplicate Conferences in Cisco TMS
You must follow this second procedure as soon as possible after upgrade, but it does not need to be done imme
diately, nor does it require a maintenance window.
diately, nor does it require a maintenance window.
1.
Go to Cisco TMS and check for a critical TMS ticket stating: 'Conference series with duplicate external primary
keys found'.
keys found'.
—
If you do not see this ticket, no further action is required.
—
If you do see the ticket, continue to steps 2 and 3.
2.
In Cisco TMS Tools, run the
Resolve Duplicate Keys
tool to select the correct conferences from the list of
duplicates.
If it is not clear which conference is the correct one, review the Exchange resource calendars for the systems
involved in the conference. If most or all of the resource calendars are in agreement with one of the duplicate
conferences, that is probably the correct one to select.
involved in the conference. If most or all of the resource calendars are in agreement with one of the duplicate
conferences, that is probably the correct one to select.
If it is still not possible to identify the correct conference, contact the conference owner.
3.
Wait for 15 minutes, then check the Cisco TMSXE log: TMSXE-log-file.txt for a line saying:
INFO
ReplicationEngine - No changes on TMS
. This confirms that all remaining problematic bookings have been
replicated correctly from Cisco TMS to Microsoft Exchange. If you do not see this line, contact your Cisco
support representative.
support representative.
13
Cisco TelePresence Management Suite Installation and Upgrade Guide
Prerequisites