PDF(315.1 KB) View with Adobe Reader on a variety of devices
Updated:January 27, 2015
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes how to use the TelePresence Management Suite (TMS) tool in order to configure the certificate used by the TMS application when it initiates outbound connections. If the TMS server is a part of a domain, then the certificate creation option might not be visible on the TMS tool.
Cisco recommends that you have:
TMS installed and accessible through HTTP and HTTPS
Access to restart the Internet Information Services (IIS) server
Admin rights for the user
Access to the Transport Layer Security (TLS) certificate that must be installed
The information in this document is based on TMS Versions14.3.2, 14.2.2, and 14.5.
All screenshots in this document are from the TMS Version 14.5 interface. Certificates for other versions can also be generated with the same procedure.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
When you want to have complete TLS communication from the TMS server and you want TMS to use a TLS certificate, you must configure it with the TMS tools.
You should see the certificate here from the personal certificate store on the system. This screen lists the certificates currently available in the server's personal trust store that can be selected to be used as described previously.
There are two requirement mentioned in the admin guide for the certificate to be listed here:
If there are no certificates listed here, check that the account you use in order to run Cisco TMS Tools has read access to the private keys of the certificates.
Ensure that all accounts the TMS services are logged on have read access to the private keys of the certificates.
In order to install a certificate on a personal trust store, you need to open Microsoft Management Console (MMC) and add Snap-in for certificate:
Open MMC with run on the Microsoft Windows server.
Add the certificate Snap-in on MMC:
Ensure that you add the certificate in the Computer account:
Import the certificate on Personal > Certificates and click Manage Private Keys:
Add access to all users through which the TMS tool can be accessed and provide Read access.
Open TMS Tools and navigate to TLS Client Certificates:
Click Save and restart IIS.
There is currently no verification procedure available for this configuration.
There is currently no specific troubleshooting information available for this configuration.