Cisco Cisco TelePresence Management Suite (TMS) Version 15 Installation Guide
Cisco TMS requirements
Cisco TelePresence Management Suite Installation and Getting Started Guide
Page 8 of 69
Windows 2008 default firewall rules
Windows Server 2008 includes a new Windows Firewall feature that controls both inbound and
outbound ports. This feature is enabled by default. If Windows Firewall is enabled, the ports required
for Cisco TMS must be opened. For details see
outbound ports. This feature is enabled by default. If Windows Firewall is enabled, the ports required
for Cisco TMS must be opened. For details see
SQL database server
SQL Server version compatibility
Note: Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) and Microsoft SQL 2000 are no
longer supported. Assistance on upgrading to SQL 2005 Server can be found in the
longer supported. Assistance on upgrading to SQL 2005 Server can be found in the
Cisco TMS supports:
Microsoft SQL Server 2005 Database Server with Mixed Authentication Mode enabled. All 32bit
versions of Microsoft SQL Server 2005, including the Express Edition (see caveat below).
versions of Microsoft SQL Server 2005, including the Express Edition (see caveat below).
Microsoft SQL Server 2008 both 32bit and 64bit.
If you are installing SQL Server 2008 on the same server as Cisco TMS, .NET 2.0 SP2 is
required.
required.
Note: Large installations with databases more than 4GB must use a full edition of SQL Server 2005,
because of the 4GB database limitation in Express Edition.
because of the 4GB database limitation in Express Edition.
If there is not an SQL DB present on the server, MS SQL Server 2008 Express 32 bit will be installed.
Cisco TMS operational
The following are required by Cisco TMS to function properly:
Domain Membership Preferred
– Each user logging into Cisco TMS needs a Windows User
Login to authenticate: either a local account on the Cisco TMS Windows Server or a Domain
account that the server trusts through Active Directory. By making the server a member of the
domain, trusted domain users will automatically be able to use their Windows credentials to log
into Cisco TMS. You can still limit user permissions using Cisco TMS. Active Directory
membership is the recommended deployment for most installations because it avoids creating
local Windows accounts for each user.
account that the server trusts through Active Directory. By making the server a member of the
domain, trusted domain users will automatically be able to use their Windows credentials to log
into Cisco TMS. You can still limit user permissions using Cisco TMS. Active Directory
membership is the recommended deployment for most installations because it avoids creating
local Windows accounts for each user.
ASP.NET and ASP Enabled
– These IIS components must be enabled. If you are using
Cisco TMS Web site Accessible by IP and Hostname - Because not all devices support DNS
hostnames or Port Numbers, Cisco TMS must be accessible by an IP Address on port 80. Some
functionality requires Cisco TMS to be reachable by hostname; therefore, Cisco TMS is also
accessible by a fully qualified hostname.
hostnames or Port Numbers, Cisco TMS must be accessible by an IP Address on port 80. Some
functionality requires Cisco TMS to be reachable by hostname; therefore, Cisco TMS is also
accessible by a fully qualified hostname.
Mail Server Access - Cisco TMS requires access to an SMTP (Mail) server to send emails. Cisco
TMS does not require its own SMTP server and can be configured to use existing mail servers. If
you are unsure which server to use, contact your IT administrator. (Cisco TMS supports SMTP
Auth login for authentication if required.)
TMS does not require its own SMTP server and can be configured to use existing mail servers. If
you are unsure which server to use, contact your IT administrator. (Cisco TMS supports SMTP
Auth login for authentication if required.)
Network Access to Managed Devices
– Cisco TMS needs specific protocols and access to
manage devices. Any network firewalls or NAT routers must allow traffic to flow to and from Cisco
TMS. The specific protocols and directions in use will vary depending on devices being managed:
see the
TMS. The specific protocols and directions in use will vary depending on devices being managed:
see the
specific information about firewall requirements for each type of supported device.
DNS records and Provisioning Directory functionality (Cisco TMS Agent)
– In installations
using the Cisco TMS Provisioning Directory functionality for Cisco TelePresence Movi and E20