Cisco Cisco TelePresence Management Suite (TMS) Version 15 Installation Guide
Migrating from Cisco TMS Agent Legacy
Cisco TMSPE Provisioning Deployment Guide
Page 21 of 88
Migrating from Cisco TMS Agent Legacy
This section describes how to perform an installation when you have a previous version of the Cisco TMS
provisioning tool (Cisco TMS Agent Legacy).
provisioning tool (Cisco TMS Agent Legacy).
About the migration
Cisco TMSPE will migrate the following from Cisco TMS Agent Legacy:
n
Groups and users
n
Active Directory import settings
n
Provisioning configurations
n
FindMe configurations
n
Access control list (ACL) data
n
Phone book data
Provisioning configurations can only be set on a group level in Cisco TMSPE. Configurations set on a user
level in Cisco TMS Agent Legacy will be migrated as read-only. Handling these settings after migration is
described in
level in Cisco TMS Agent Legacy will be migrated as read-only. Handling these settings after migration is
described in
.
The following will not be migrated:
n
Duplicate users: Duplicate users are not supported and will result in a failed migration. Remove the
duplicate(s) before migrating from Cisco TMS Agent Legacy.
duplicate(s) before migrating from Cisco TMS Agent Legacy.
n
URIs set directly on devices: In Cisco TMS Agent Legacy, you can assign a URI directly on an endpoint
device if you want the URI to apply universally, such as a shared device in a meeting room. This feature is
not available in Cisco TMSPE.
device if you want the URI to apply universally, such as a shared device in a meeting room. This feature is
not available in Cisco TMSPE.
n
FindMe home clusters set directly on users: In Cisco TMS Agent Legacy, the homeCluster field allows
administrators to assign a FindMe home cluster directly to a user. In Cisco TMSPE, this field is not
supported, and the contents will be migrated to the SIP Server Address field as a read-only user-level
provisioning configuration.
Example: If you have two Cisco VCS clusters, one for production and the other for testing, you could use
the user-level configuration in Cisco TMS Agent Legacy to move a user to the test cluster as part of a test
exercise. To perform a similar exercise in Cisco TMSPE, create one group for production and one for test,
and configure them to point to the production and test Cisco VCS clusters respectively. Move users
between the groups when testing.
administrators to assign a FindMe home cluster directly to a user. In Cisco TMSPE, this field is not
supported, and the contents will be migrated to the SIP Server Address field as a read-only user-level
provisioning configuration.
Example: If you have two Cisco VCS clusters, one for production and the other for testing, you could use
the user-level configuration in Cisco TMS Agent Legacy to move a user to the test cluster as part of a test
exercise. To perform a similar exercise in Cisco TMSPE, create one group for production and one for test,
and configure them to point to the production and test Cisco VCS clusters respectively. Move users
between the groups when testing.
n
Numeric user IDs: In Cisco TMS Agent Legacy, you can use the User ID field to generate numeric user
IDs. In Cisco TMSPE, the User ID field is not available. To assign numeric IDs to users, you must apply
them to the Username field instead.
IDs. In Cisco TMSPE, the User ID field is not available. To assign numeric IDs to users, you must apply
them to the Username field instead.
Preparing data for migration
Migrating from Cisco TMS Agent Legacy to Cisco TMSPE may raise issues resulting from differences
between the two provisioning options. Some issues can only be resolved prior to migrating. For other issues,
you can choose whether to resolve them before or after migrating, depending on which option you find to be
easier and quicker to complete.
between the two provisioning options. Some issues can only be resolved prior to migrating. For other issues,
you can choose whether to resolve them before or after migrating, depending on which option you find to be
easier and quicker to complete.