Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Limitations
Cisco TelePresence Management Suite 13.1.2 Software Release Notes
Page 9 of 18
Limitations
Cisco products
Equipment
Summary
TMS Phone books
It is not possible to preview provisioning source (phone book) if you have more
than 100 groups. Cisco has not found any low risk fix for this and has decided to
rewrite this for the next major release of Cisco TMS. Customer with this problem is
encouraged to contact support.
than 100 groups. Cisco has not found any low risk fix for this and has decided to
rewrite this for the next major release of Cisco TMS. Customer with this problem is
encouraged to contact support.
Upgrading to Cisco TMS
13.1.2
13.1.2
When upgrading from Cisco TMS 12.1 or 12.2 if replication is enabled the installer
will stop the installation and show a warning. To compensate for a weakness in
version 12.1 or 12.2 which may cause disabling replication to fail, the installer will
allow the user to select to continue the installation. The Continue option should
only be used if upgrading from TMS 12.1 or TMS 12.2 and disabling replication
failed.
will stop the installation and show a warning. To compensate for a weakness in
version 12.1 or 12.2 which may cause disabling replication to fail, the installer will
allow the user to select to continue the installation. The Continue option should
only be used if upgrading from TMS 12.1 or TMS 12.2 and disabling replication
failed.
E20
It is not possible to use ‘pre-registration’ for E20 devices in Cisco TMS if the
device is to be managed by Cisco TMS Agent.
device is to be managed by Cisco TMS Agent.
MCU 42xx /45xx series
MSE 84 xx/85xx series
MSE 84 xx/85xx series
Cisco TMS 13.1.2 is not compatible with MCU and MSE blades using software
older then version 2.0.
older then version 2.0.
MCU 42xx /45xx series
MSE 84 xx/85xx series
MSE 84 xx/85xx series
Participant drag and drop is not available for SIP participants on a Cisco
TelePresence MCU that were originally dial-out calls.
TelePresence MCU that were originally dial-out calls.
Hardware devices
provisioned by Cisco
TMS Agent
provisioned by Cisco
TMS Agent
Cisco TMS will report an upgrade as successful for a Cisco TMS Agent
provisioned endpoint before the upgrade my actually start or finish successfully on
the device. The reporting of success in Cisco TMS is reporting that the job was
successfully provisioned to the device’s profile in the Cisco TMS Agent.
provisioned endpoint before the upgrade my actually start or finish successfully on
the device. The reporting of success in Cisco TMS is reporting that the job was
successfully provisioned to the device’s profile in the Cisco TMS Agent.
Hardware devices
provisioned by Cisco
TMS Agent
provisioned by Cisco
TMS Agent
When performing a software upgrade for Cisco TMS Agent managed device,
Cisco TMS will report the upgrade as successful even if the device is offline at the
time. The upgrade is successfully provisioned into the device’s profile, and the
device will attempt the upgrade the next time it is online and provisioned.
Cisco TMS will report the upgrade as successful even if the device is offline at the
time. The upgrade is successfully provisioned into the device’s profile, and the
device will attempt the upgrade the next time it is online and provisioned.
Hardware devices
provisioned by Cisco
TMS Agent
provisioned by Cisco
TMS Agent
Cisco TMS is able to upgrade EX systems on version TC4.2 and higher, however
upgrading is not possible with TC4.1 software.
upgrading is not possible with TC4.1 software.
Cisco TMS Agent
Cisco VCS
Cisco VCS
Network latency and ‘distance’ between Cisco TMS and the Cisco VCS systems
can affect the ability to enable Cisco VCS clusters with provisioning on those
Cisco VCS. On a network with high latency and lower throughput, enabling a
provisioning cluster may lead to timeouts and potentially partial configurations of
the Cisco TMS Agents. To minimize this impact of network ”distance”, it is
important to configure provisioning clusters before populating the provisioning
directory with users as described in the
can affect the ability to enable Cisco VCS clusters with provisioning on those
Cisco VCS. On a network with high latency and lower throughput, enabling a
provisioning cluster may lead to timeouts and potentially partial configurations of
the Cisco TMS Agents. To minimize this impact of network ”distance”, it is
important to configure provisioning clusters before populating the provisioning
directory with users as described in the
. However, if replication is being re-enabled or a Cisco VCS or VCS cluster is
being added to the solution in a network with high latency, then the default timeout
(one hour) can be increased by adding the registry key
tmsAgentReplicationSetupTimeout (in minutes) at the following registry location on
the Cisco TMS server:
HKEY_LOCAL_MACHINE\SOFTWARE\Tandberg\TANDBERG Management
Suite.
(one hour) can be increased by adding the registry key
tmsAgentReplicationSetupTimeout (in minutes) at the following registry location on
the Cisco TMS server:
HKEY_LOCAL_MACHINE\SOFTWARE\Tandberg\TANDBERG Management
Suite.
Cisco TMS, Pro visioning
Directory
Directory
Provisioning Directory will not be available immediately after server restart as it
takes longer to start up than the rest of the Cisco TMS interface. If a user browses
to the Systems > Provisioning > Directory before the service has finished
starting up, an information message is shown to have the user check back shortly.
takes longer to start up than the rest of the Cisco TMS interface. If a user browses
to the Systems > Provisioning > Directory before the service has finished
starting up, an information message is shown to have the user check back shortly.
Cisco TMS, Pro visioning
Directory
Directory
When TMS Agent Data Replication is enabled, if a server (such as Cisco TMS or
Cisco VCS) is out of the replication topology for more than 24 hours and then
comes online again, all changes that have happened on any other replication
member during that time will not be copied across to the server when it comes
Cisco VCS) is out of the replication topology for more than 24 hours and then
comes online again, all changes that have happened on any other replication
member during that time will not be copied across to the server when it comes