Cisco Cisco TelePresence Management Suite (TMS) Version 15
Task 40: Performing the import
New Cisco TMS with trial import
If you performed the trial import and are working with a new Cisco TMS installation, all endpoint and mailbox
information is already available in Cisco TMSXE.
information is already available in Cisco TMSXE.
When you are ready to begin the resource-intensive import of existing meetings from the resource mailboxes:
Go to the Windows Services Control Panel on the Cisco TMSXE server.Change the disabled Cisco TMSXE
service to automatic startup, and start the service.
Go to the Windows Services Control Panel on the Cisco TMSXE server.Change the disabled Cisco TMSXE
service to automatic startup, and start the service.
Existing Cisco TMS or no trial import
If you are working with an existing Cisco TMS deployment where you needed to re-add systems during
cutover, or you did not perform the trial import, you must add the systems to Cisco TMSXE before you can
start the import:
cutover, or you did not perform the trial import, you must add the systems to Cisco TMSXE before you can
start the import:
1. On the Cisco TMSXE server, open the configuration tool and go to the
Systems
tab.
The configuration tool will refuse to use the file if the format is not valid.
3. At the bottom of the
Systems
tab are options to enable or disable the sending of notifications to meeting
organizers for imported meetings.
These notices are only sent for meetings that could not be scheduled in Cisco TMS based on the
reserved endpoints, not for feature incompatibilities.
We recommend setting the options to not send notices to meeting organizers if:
These notices are only sent for meetings that could not be scheduled in Cisco TMS based on the
reserved endpoints, not for feature incompatibilities.
We recommend setting the options to not send notices to meeting organizers if:
l
you plan for administrators to intervene post-import to correct impacted meetings.
l
your deployment has a very large number of future meetings.
4. Click Save.
Cisco TMSXE will start a verification process for all of the linked accounts to check their mailbox
configuration. This process can take a significant amount of time depending on how many linked systems
are configured.
The validation process takes approximately 1 minute for every 180 endpoints.
configuration. This process can take a significant amount of time depending on how many linked systems
are configured.
The validation process takes approximately 1 minute for every 180 endpoints.
5. Close the configuration tool.
When prompted whether you wish to start the Cisco TMSXE service, click No.
6. When you are ready to begin the resource-intensive import of existing meetings from the resource
mailboxes: Go to the Windows Services Control Panel on the Cisco TMSXE server.Change the disabled
Cisco TMSXE service to automatic startup, and start the service.
Cisco TMSXE service to automatic startup, and start the service.
Monitoring the import
Once started, the Cisco TMSXE service will continue importing meetings in the background until all future
meetings have been processed.
meetings have been processed.
1. In the tool of your choice, monitor the Cisco TMSXE service log. Default location:
C:\ProgramData\Cisco\TMSXE\Logs\TMSXE-log-file.txt.
It has completed when no new bookings are logged for several minutes.
It has completed when no new bookings are logged for several minutes.
2. The replication of bookings back to Exchange will impact Cisco TMS for some time after the import has
completed.
Replacing Cisco TelePresence Manager with Cisco TMS and Cisco TMSXE Deployment Guide (14.5 and
4.1)
4.1)
Page 40 of 51
Cutover (downtime)