Cisco Cisco TelePresence Management Suite (TMS) Version 15
4. Click Add.
5. Provide the TAC engineer with the generated account name and passphrase.
Using the command line:
1. SSH to Cisco TelePresence Manager.
2. Log in as a user with administrative privileges.
3. Type utils remote_account enable
4. Type utils remote_account create ciscotac 1 (the number is the number of days until
password expiry).
5. Provide the TAC engineer with the generated account name and passphrase.
Task 5: Assessing meeting compatibility and preparing for
mitigation
mitigation
High-level, there are six main categories of issues that will or may arise when meetings are imported from
Cisco TelePresence Manager to Cisco TMS, as described in the following table.
Cisco TelePresence Manager to Cisco TMS, as described in the following table.
Type of issue
Result on import
Recommended mitigation
All meetings are affected by
the changes to dial plan, but
Microsoft security policies
prevent Cisco TMSXE from
updating organizer or
invitee calendars.
the changes to dial plan, but
Microsoft security policies
prevent Cisco TMSXE from
updating organizer or
invitee calendars.
All imported meetings will have
new routes that will not be
reflected in organizer calendars.
Resource calendars will correctly
reflect all updates.
new routes that will not be
reflected in organizer calendars.
Resource calendars will correctly
reflect all updates.
As an administrator:
n
Pre-import, set One Button To Push as the
default conference type in Cisco TMS to
make endpoints handle the new routing
information automatically. See
default conference type in Cisco TMS to
make endpoints handle the new routing
information automatically. See
.
n
Post-import, use Meeting Updater to re-
apply dial-in information and send updates
to organizers of meetings with dial-in
participants, so they can update their
calendars and forward the information to
invitees. See
apply dial-in information and send updates
to organizers of meetings with dial-in
participants, so they can update their
calendars and forward the information to
invitees. See
Some meetings may be
outside of the booking
horizon or have recurrence
patterns not bookable in
Cisco TMS.
outside of the booking
horizon or have recurrence
patterns not bookable in
Cisco TMS.
Meeting is declined by Cisco
TMS and will also be removed
from Exchange resource
calendars. For detail on booking
horizon, see
TMS and will also be removed
from Exchange resource
calendars. For detail on booking
horizon, see
.
As an administrator, do both of the following
before import:
before import:
n
.
n
Pre-import, get affected organizers to update
their meetings that have unsupported
recurrence, which includes:
their meetings that have unsupported
recurrence, which includes:
l
More than 100 occurrences.
l
No specified end date.
l
A yearly recurrence pattern.
Table 3: Categories of compatibility issues when importing meetings from Cisco TelePresence Manager to
Cisco TMS
Cisco TMS
Replacing Cisco TelePresence Manager with Cisco TMS and Cisco TMSXE Deployment Guide (14.5 and
4.1)
4.1)
Page 19 of 51
Planning the change of deployment