Cisco Cisco TelePresence Management Suite (TMS) Version 15 Installation Guide
Database information
The installer detects where the Cisco TMS SQL database (tmsng) is located and recommends installing
Cisco TMSPE's SQL databases (tmspe, tms_userportal and tmspe_vmr) to the same location and
instance. tmspe, tms_userportal and tmspe_vmr must be co-located.
Cisco TMSPE's SQL databases (tmspe, tms_userportal and tmspe_vmr) to the same location and
instance. tmspe, tms_userportal and tmspe_vmr must be co-located.
In this case, the administrator needs to know the following about the tmsng database:
n
SQL server name
n
SQL server instance
n
SQL server credentials with adequate privileges
Database location
During installation, the installer offers the possibility of storing the tmspe, tms_userportal and tmspe_
vmr
vmr
databases to another location and instance. However, we recommend storing them in the same location
as the tmsng database. Note that the database names must be tmspe, tms_userportal and tmspe_
vmr
vmr
, using the same casing and underscore.
If desired, the installer also offers the ability to use separate SQL credentials for tmspe to operate in. Select
Use separate SQL Credentials for the TMS Provisioning Extension during the installation to change
these credentials. See the section
Use separate SQL Credentials for the TMS Provisioning Extension during the installation to change
these credentials. See the section
for appropriate operation
permissions.
User import requirements
Cisco TMSPE does not support user names that contain characters that needs to be "escaped" in an URL
string.
string.
Cisco TMSPE supports the import of users from the following external sources:
n
Active Directory
n
Active Directory with Kerberos
n
Lightweight Directory Access Protocol (LDAP)
Service account
You must define a service account in Active Directory that has read access to the Global Catalog. This
service account must have a password with no retention policies applied to it so that the password does not
expire.
service account must have a password with no retention policies applied to it so that the password does not
expire.
Secure connection
To achieve a secure connection, you must use either:
n
Active Directory with Kerberos
n
LDAP with StartTLS
Otherwise, by default the LDAP connection uses the SIMPLE bind type, which is not secure. Also, using
LDAP with the SSL connection type does not provide a secure connection, as by default, all certificates will
be trusted.
LDAP with the SSL connection type does not provide a secure connection, as by default, all certificates will
be trusted.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide (1.2)
Page 12 of 88
Prerequisites and recommendations