Cisco Cisco TelePresence Management Suite (TMS) Version 15
Setting up and maintaining the Provisioning Directory
Cisco TelePresence Management Suite Agent Legacy Deployment Guide (13.2)
Page 32 of 55
username
Username
sAMAccountName
emailAddress
Email
address
address
mail
externalId
objectGUID
The objectGUID is prefixed with the LDAP URL the
user was imported from.
user was imported from.
firstName
First Name
givenName
name
Displayname
displayName
If displayname is null or empty, user.username is
used.
used.
lastName
Last Name
sn
If sn is null or empty, username is used.
title
Title
title
company
Company
company
department
Department
department
officePhone
Office Phone
telephoneNumber
mobilePhone
Mobile Phone
mobile
As a minimum, the sAMAccountName and mail attributes are required to import to the Cisco TMS
Provisioning Directory appropriately.
Provisioning Directory appropriately.
Disabled accounts
Note that Cisco TMS also filters out anything that is disabled in AD, meaning that if the account is disabled,
Cisco TMS does not import it.
Cisco TMS does not import it.
If an active account is imported to the Cisco TMS Provisioning Directory and is subsequently disabled in
Active Directory, Cisco TMS will remove it from the Provisioning Directory on the next synchronization.
Active Directory, Cisco TMS will remove it from the Provisioning Directory on the next synchronization.
FindMe configuration—an example
Next, Tore wants to set up FindMe to automatically include all the endpoints they have in his company. For
example, some of his users have endpoints from the Cisco TelePresence EX Series and these devices have
URIs on the form: <username>.office@example.com
example, some of his users have endpoints from the Cisco TelePresence EX Series and these devices have
URIs on the form: <username>.office@example.com
Tore goes to the root group and clicks Add FindMe Templatewhich displays the popup below:
He then gives the FindMe Template a name,chooses to use it as the active profile, and clicks Save.