Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Known limitations
Cisco TelePresence Management Suite Release notes
Page 18 of 25
Known limitations
Cisco products
Equipment
Summary
VCS 5.X
Both VCSDatabase and DeviceProvisioning packages needs to be upgraded. If
only one of the packages is updated, an error message will be displayed:
Component installation failed: Could not install ‘Device
Provisioning’, opends (>= 2.0.1) not installed.
only one of the packages is updated, an error message will be displayed:
Component installation failed: Could not install ‘Device
Provisioning’, opends (>= 2.0.1) not installed.
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 main 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 main release of Cisco TMS. Customer with this problem is
encouraged to contact support.
Upgrading to Cisco TMS
13.0
13.0
If replication is enabled when running the Cisco TMS 13.0 setup, the installer will
stop the installation and show a warning. Due to a weakness in how TMS
12.1/12.2 handled disabling of replication, the user is given the option to continue
the installation. Continue only if upgrading from TMS 12.1 or TMS 12.2 and
disabling replication has failed.
stop the installation and show a warning. Due to a weakness in how TMS
12.1/12.2 handled disabling of replication, the user is given the option to continue
the installation. Continue only if upgrading from TMS 12.1 or TMS 12.2 and
disabling replication has failed.
E20
Cisco TMS cannot guarantee that a scheduled E20 upgrade provisioned by the
TMSAgent is actually upgraded.
TMSAgent is actually upgraded.
MCU 4200 and 4500
series
Media MSEs
series
Media MSEs
Cisco TMS 13.0 assumes all MCUs/MSEs have at least 2.0 version software
installed. Using older software can cause problems in Cisco TMS.
installed. Using older software can cause problems in Cisco TMS.
Cisco TMS
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 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
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 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.
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.
Cisco TMS, Provisioning
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.
MCU
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.
E20
Pre-registering of E20 endpoints in Cisco TMS that will be provisioned by the TMS
Agent is not supported at this time. This will be corrected in a future version of
Cisco TMS.
Agent is not supported at this time. This will be corrected in a future version of
Cisco TMS.
Cisco TMS, Provisioning
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
back online. However, all new changes will be copied as normal. If necessary,
missing entries modified or added during the downtime can be recovered to the
server by running the “dsreplication initialize” from the command line on the
server.
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
back online. However, all new changes will be copied as normal. If necessary,
missing entries modified or added during the downtime can be recovered to the
server by running the “dsreplication initialize” from the command line on the
server.
Cisco TMS, Provisioning
Information for the screen Directory, in Systems > Provisioning > Directory is