Cisco Cisco TelePresence Management Suite (TMS) Version 15 Installation Guide
Troubleshooting
Cisco TMSPE Provisioning Deployment Guide
Page 74 of 88
Users with other configuration overrides
Any provisioning configurations made on a user level in Cisco TMS Agent Legacy will be migrated as read-
only, meaning that they will be applied, and can be removed, but not edited or updated. If the configuration
has been set for a specific version of endpoint, the configuration will stop working when the user's endpoint is
upgraded to a newer version.
only, meaning that they will be applied, and can be removed, but not edited or updated. If the configuration
has been set for a specific version of endpoint, the configuration will stop working when the user's endpoint is
upgraded to a newer version.
This issue does not prevent migration from completing.
Corrective action:
Migration failed. View the migration log for details
When migration fails to complete, further details are found in the log.
Click View Migration Log in the migration result dialog box to open the log directly. It can also be accessed
in the following location: C:\Program Files\TANDBERG\TMS\TMSProvisioningExtension\app\logs.
in the following location: C:\Program Files\TANDBERG\TMS\TMSProvisioningExtension\app\logs.
This log is also included in the archive of logs provided when going to
Administrative Tools > TMS Server
Maintenance
and clicking Download Log Files.
Duplicate users
While duplicate users are not allowed in either Cisco TMS Agent Legacy or Cisco TMSPE, the use of
uppercase versus lowercase characters in legacy usernames may cause duplicates to occur, and these
cannot be imported to Cisco TMSPE.
uppercase versus lowercase characters in legacy usernames may cause duplicates to occur, and these
cannot be imported to Cisco TMSPE.
Corrective action:
Remove the unwanted duplicate users from Cisco TMS Agent Legacy and re-run the
migration tool.
Provisioning requests failing after installation or migration
If provisioning and phone book requests fail, verify that:
n
n
Cisco VCS is running in the correct provisioning mode. An alarm will be raised if Cisco VCS is running in
Cisco TMS Agent Legacy mode after migration to Cisco TMSPE. See
Cisco TMS Agent Legacy mode after migration to Cisco TMSPE. See
.
n
If starting with a clean installation, verify that Cisco VCS is correctly configured for provisioning and that no
steps were missed. See
steps were missed. See
.
n
Check the relevant logs. See
Reverting to Cisco TMS Agent Legacy
If provisioning is not working as expected after migration, temporarily reverting to Cisco TMS Agent Legacy
can be done as described below.
can be done as described below.
To revert Cisco VCS to Cisco TMS Agent Legacy:
1. Go to
Systems > Navigator
, navigate to the Cisco VCS and select it.
2. Go to the
Provisioning
tab.
3. Change VCS Provisioning Mode to TMS Agent Legacy and click Save. You have now reverted the
.