Table of Contents
Advertisement
address to the IP address of the primary Cisco TMS server. This is the IP address Cisco TMS will use
for enforce management settings and to compare for device configuration errors. This setting is stored
in the Cisco TMS database, and therefore will be shared among all servers. This value will be
overwritten anytime you run the Cisco TMS installer on a server connected to the database so it must
be verified to be the primary Cisco TMS server's IP after running any Cisco TMS installation software.
The Cisco TMS Server DNS hostname values should also be configured to point to the primary Cisco
TMS server, but these will not be overwritten by upgrades or additional installs.
After Cisco TMS is installed, you should configure a DNS hostname record to point to the IP address
of the primary Cisco TMS server. Cisco TelePresence recommends you use the DNS hostname over
IP addresses for user access to Cisco TMS, configuring external integrations with Cisco TMS (such as
Exchange or Lotus) and is required when using the Remote/SOHO support or public/local identity
features of Cisco TMS.
Set web validation key on web servers
When running multiple web servers, each web server must use the same encryption method for the
viewstate information of the pages. This is achieved by specifying the machine key to be used by IIS
rather then letting IIS generate its own which is the default behavior. The machinekey behavior can be
controlled using the web.config file used by the Cisco TMS web application. This file is located in the
wwwCisco TMS directory (default c:\program files\tandberg\tms\wwwCisco TMS) The behavior of this
element is described in the following Microsoft articles
http://msdn2.microsoft.com/en-us/library/w8h3skw9(VS.71).aspx
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag2/html/paght000007.asp
Microsoft provides sample code to generate these keys, but there are several public websites that
simplify the creation of these keys for you. Some example sites are
http://www.orcsweb.com/articles/aspnetmachinekey.aspx
http://www.aspnetresources.com/tools/keycreator.aspx
Example machinekey string:
<configuration>
<system.web>
<machineKey
validationKey='50C6CA92F369A87AB487E3678C7D229119A47F921C8266D9FB0DE2B28829
CDECDD5FEEE7CC534497A90D0AB3B8FB9F81021A7DC00ACC6F39D67EA9036C1F8733'
decryptionKey='52480E9648080C4A87BB434CF281064243E3C09B003C49D0'
validation='SHA1'/>
</system.web>
</configuration>
Create a machinekey element using Microsoft's supplied methods or from the sample websites listed
above. Open the web.config file under the wwwCisco TMS directory and insert the new machinekey
element text under the existing <system.web> element in the document. You must update the
web.config file on each of the Cisco TMS servers. Be sure to use the same machinekey string on all
servers.
Maintenance
Users should regularly backup the SQL database. The interval between backups defines the
maximum time window over which data would be lost. Typical installations would perform full nightly
backups of the database. Please see Section
document for additional details on how to perform backups and restores of the Cisco TMS database.
As multiple Cisco TMS servers are being used, administrators should periodically check that their file
synchronization process is still functioning to ensure smooth cut-over in the case of having to use a
warm spare.
Cisco TMS redundancy configuration and overview
Cisco Redundancy Models for Cisco TMS
0 Backup and Recovery of the TMS database
of this
Page 18 of 32
Advertisement
Table of Contents
