Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
New features
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.6.1)
Page 14 of 90
Versions of Cisco TMS prior to 14.4 do not rely upon the ExternalPrimaryKey being unique, and are not at risk
of data corruption unless upgraded to 14.4 or 14.4.1.
of data corruption unless upgraded to 14.4 or 14.4.1.
Similar mechanisms are used for synchronization with Cisco TMSXN, so some conferences in IBM Domino
deployments may also be affected by this issue.
deployments may also be affected by this issue.
Resolution of CSCup76424 in 14.4.2
Cisco TMSXE and Microsoft Exchange
This version of Cisco TMS fixes the majority of affected conferences automatically, but in some cases that
will not be possible:
will not be possible:
n
A tool has been added to
TMS Tools
that identifies most remaining duplicate conferences allowing the
administrator to select which is the correct conference after upgrading Cisco TMS.
n
A small number of duplicated appointments could remain in the Exchange resource calendars after the
Cisco TMS and Cisco TMSXE upgrades. These cannot be cleaned up automatically by Cisco TMS, or by
using
Cisco TMS and Cisco TMSXE upgrades. These cannot be cleaned up automatically by Cisco TMS, or by
using
TMS Tools
.
Cisco TMSXN and IBM Domino
This version of Cisco TMS fixes the majority of affected conferences automatically, but in some cases that
will not be possible:
will not be possible:
n
A tool has been added to
TMS Tools
that identifies most remaining duplicate conferences allowing the
administrator to select which is the correct conference after upgrading Cisco TMS.
n
A small number of duplicate bookings originating in IBM Domino could still exist in Cisco TMS. Re-
replicating all conferences from Cisco TMS to IBM Domino will resolve these issues. See
replicating all conferences from Cisco TMS to IBM Domino will resolve these issues. See
.
n
There is a very small chance that bookings may exist in IBM Domino but not in Cisco TMS. These cannot
be cleaned up by Cisco TMS, Cisco TMSXN, or by using
be cleaned up by Cisco TMS, Cisco TMSXN, or by using
TMS Tools
. It is most likely that these bookings
were created either from Conference Templates, or by copying existing conferences in versions of Cisco
TMS earlier than 14.4, and that these conferences were subsequently edited (either in Cisco TMS or in IBM
Domino) in 14.4 or 14.4.1.These 'ghost' bookings will cause incorrect free/busy information in IBM Domino.
The only impact here is that the room will appear to be booked in Domino when it is not booked in Cisco
TMS. It is not possible to identify these bookings, but if you notice that a video resource cannot be booked
in Domino, but has no corresponding booking in Cisco TMS, you can simply delete the booking in Domino.
TMS earlier than 14.4, and that these conferences were subsequently edited (either in Cisco TMS or in IBM
Domino) in 14.4 or 14.4.1.These 'ghost' bookings will cause incorrect free/busy information in IBM Domino.
The only impact here is that the room will appear to be booked in Domino when it is not booked in Cisco
TMS. It is not possible to identify these bookings, but if you notice that a video resource cannot be booked
in Domino, but has no corresponding booking in Cisco TMS, you can simply delete the booking in Domino.
using Cisco TMSXE or Cisco TMSXN.
Resolve duplicate keys
Cisco TMS version 14.4 introduced an issue affecting customers using Cisco TMSBA clients such as Cisco
TMSXE who have upgraded to Cisco TMS versions 14.4 and 14.4.1. See above for a description of the
problem.
TMSXE who have upgraded to Cisco TMS versions 14.4 and 14.4.1. See above for a description of the
problem.
A new tool:
Resolve Duplicate Keys
, has been added to TMS Tools to assist administrators with resolving
any duplicate conferences remaining after upgrading to 14.4.2.
The tool displays the duplicate conferences, and allows the administrator to select which of a number of
conferences is the correct one. Once a conference has been selected, the one or more duplicates that were
not selected are deleted from the Cisco TMS database.
conferences is the correct one. Once a conference has been selected, the one or more duplicates that were
not selected are deleted from the Cisco TMS database.