TMS Agent is a process that runs on the VCS to manage FindMe and Device Provisioning data.
It acts on behalf of Cisco TMS so that Cisco TMS is not a single point of failure, and enables each
VCS to share the load. It supports the replication of FindMe and provisioning data, sharing the data
among cluster peers as well as the central Cisco TMS, providing resilience in case of connection
failures between any VCS and Cisco TMS.
TMS Agent is installed as part of the VCS Platform and requires no configuration on the VCS, other
than ensuring the default password is changed (see TMS Agent account passwords below).

•

You must use Cisco TMS to create and manage Device Provisioning data.

•

FindMe accounts may be set up using Cisco TMS or VCS.

FindMe™

The TMS Agent replicates changes to FindMe account information across peers in a VCS cluster
(FindMe account changes can be made on any peer, not just the master), across to Cisco TMS and
also across to other VCS clusters managed by the same Cisco TMS.
Note that the FindMe option key must be installed on the VCS.

Device Provisioning

The TMS Agent works with the TMS Provisioning Directory to replicate and distribute the
provisioning information and phonebook from Cisco TMS via VCSs to endpoint devices. VCSs cache
and replicate data among themselves in case connection to Cisco TMS is lost.
Note that the Device Provisioning option key must be installed on the VCS.

TMS Agent account passwords

TMS agent is accessed via two accounts: one for connecting via LDAP into the TMS Agent
database, and one for managing the replication of the TMS Agent database. These accounts are
only used by the internal processes running on the VCS and Cisco TMS. System administrators
must not use these accounts.
These accounts have a username of cn=Directory Manager and a default password of TANDBERG
(all upper case). Both passwords must be changed as soon as possible to maintain security of
the VCS data. Warnings are shown on the web UI and the CLI if either account has the default
password set.

•

If your VCS uses Cisco TMS as an external manager, you must use Cisco TMS to change the
passwords on these accounts. Instructions for this are in the

Clustering deployment guide [27]

•

If your VCS is not managed by Cisco TMS, you have to change these passwords by logging into
the VCS as the root user. Instructions for this are contained in the online help; follow the link
associated with the VCS's TMS Agent password warning message. If your VCS is subsequently
reconfigured to use TMS, the password must first be reset to the default value of TANDBERG.

Overview