PDF(1.1 MB) View with Adobe Reader on a variety of devices
Updated:March 16, 2016
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.
ESXi to Download: Cisco Custom Image for VMware ESXi 5.5.0 GA Install CD
Digital Image Signing Off TCS
There are two types of file used in TCS that is Digital Signed:
Verification of digital signatures of.exe files
Follow the below steps to verify the digital signature of.exe files:
Step 1 Right click on ‘Windows’ icon to look at the file properties.
Step 2 Select the Properties.
Step 3 Check if the signature is deemed valid by Windows on the Digital Signature tab. Refer the image below:
Verification of digital signatures of.exe files
Step 1 Log into the vsphere client.
Step 2 Select the File > Deploy OVF Template.
Step 3 Select the Signed OVA file.
Step 4 Click Next. ‘Publisher, Vendor’ Windows will appear.
Refer the image below:
Installation Prerequisites Checklist
1. Download the VM Content Server Release 7.1 software by using an external download location link that will be provided in the E-delivery notification email:
a. Content Server software image
b. OVA template that is specific for the host hardware
c. System configuration scripts
2. Confirm that you have this system software available for installation:
a. Windows Server 2012 Standard R2
b. VMware vSphere Hypervisor (ESXi) software version that is specific for the Content Server second- or third-generation hardware (see Table 1).
c. SQL Server 2012 Express or Enterprise or Standard Edition.
3. Before installing VMware ESXi vSphere on the host server, check that:
a. Virtualization Technology (VT) is enabled in the BIOS
b. “Virtual Machine Startup/Shutdown” is configured to “Allow Virtual machines to start and stop automatically with the system” and the VM Content Server has been moved to the Automatic startup section
c. Valid NTP server is configured that is the same NTP server that will be specified in the Content Server
To install VM Content Server Release 7.1 on new hardware, you will need the software base Product Authorization Key (PAK) and option PAK. This information is part of the claim certificate that you received after ordering the VM Content Server. See the Installing TCS Installer section for more information.
SQL Sever 2012 Support
Earlier SQL Server 2005 was being installed internally as local database server by the TCS installer. In 7.x, the approach is changed. Internal installation of SQL Server 2005 was dropped and now SQL Server 2012 is required as a prerequisite for TCS installation.
So before installation, A SQL Server instance named TCS must be present at local machine. The edition of SQL Server 2012 can be any of Standard editions, Enterprise Edition or Express edition.
These instructions represent a typical installation. The Deploy OVF Template wizard dynamically changes to reflect the host configuration.
Step 1 Log in to the vSphere client to access the ESXi Host.
Step 2 Select File > Deploy OVF Template.
Step 3 On the Source page, Browse to the location of the OVA file that is specific to the host appliance. Click Next.
Note For TCS 7.1, OVA file is S_7_1_TCSVM_Bundle.zip and for BE6K, OVA file is S_7_1_TCSBE6K_Bundle.zip.
Step 4 On the Name and Location page, enter the Name for the VM Content Server guest, for example “Virtual_TCS”. Click Next.
Step 5 On the Disk Format page, confirm that the Thick Provision Lazy Zeroed default disk format is selected. Click Next.
Step 6 On the Ready to Complete page:
a. Confirm the deployment settings.
b. Select the Power on after deployment check box.
c. Click Finish.
Step 7 The installation process begins and a progress bar is displayed. The Content Server OVA is now deployed as a guest on the VM host.
Installing Windows Server 2012 Standard R2
These instructions represent a typical installation.
Step 1 Obtain the Windows Server 2012 Standard R2 software to begin installation process.
Step 2 Power on the VM.
Step 3 Depending on your Windows Server media type, perform one of these steps:
a. Insert the Windows 2012 DVD in DVD drive. In ESXi, connect the DVD drive letter by using the ESXi option Connect/Disconnect the CD/DVD devices of Virtual Machine > Connect to <DVD drive letter>.
b. Mount the Windows 2012 ISO image file in ESXi by using the option Connect/Disconnect the CD/DVD devices of Virtual Machine > Connect to ISO Image on local disk and browse the Windows Server ISO image file.
Step 4 Press CTRL + ALT + Insert to boot from the DVD or the mounted ISO image.
Step 5 If prompted, choose Windows Server 2012 R2 Standard (Server with GUI) x64.
Step 6 In the Install Windows Server screen, choose Custom (Advanced).
Step 7 Create two partitions on the host while installing Windows:
First partition for program files with a minimum of 100 GB space
Second partition for media files with the remainder of available space (450 GB)
Note In case of BE6K platform, create two partition of the following sizes:
First partition for program files with a minimum of 50 GB space
Second partition for media files with the remainder of available space (250 GB)
Note The drive letter might differ in your OS. Go to Disk Management to change the drive to E:.
Step 8 Follow the prompts to complete the Windows Server installation.
Step 9 Install VMware Tools:
a. Right click the Content Server VM node. Select Guest > Install/Upgrade VMware Tools.
b. Click the Console tab. In the Console window double click the mounted drive (VMware Tools)
c. Double click setup64.exe to launch the Setup wizard. Choose Typical to complete the installation.
d. When installation is complete, click Finish. Click Restart to restart the system.
Step 10 Go to the console to configure the Content Server networking parameters. Assign the IP address, the netmask, the default gateway, and the DNS server address. For more information, see the Cisco TelePresence Quick Start Guide on Cisco.com.
Step 11 Go to My Computer > Properties and enable Remote Desktop services.
Installing Roles and Features
Step 1 Install Internet Information Services (IIS8). On VM host, navigate to Server manager > Dashboard. Click on Add roles and Features.
Step 2 On Select Server Roles page, click the WebServer IIS check box. A pop-up appears for installing the dependent features, click Add Features to continue and Click Next.
Step 3 On Select Features page, select Net framework 3.5 and ASP.Net 4.5 as shown in the below image. Also select Windows Server backup and Desktop Experience. A pop-up appears for installing the dependent features, click Add Features to continue and click Next.
Step 4 On the Select Role Services page, select all the features and sub features on this page under webserver. Click Next.
Step 5 On the Confirmation Installation Selection page, click on ‘specify an alternate source path’. Mount the Windows Server 2012 R2 standard Edition image to a drive. On the Specify alternate source path page, specify the path <OS Mounted drive letter>:\sources\sxs, as shown in the image. Click OK.
Step 6 On Confirmation Installation selection page, click Install.
Step 7 Once feature installation is completed, click Close. Restart the system.
Local Policy Setting
Local Policy Object Display Name
Backup files and directories
Se Backup Privilege
Se Debug Privilege
Manage auditing and security log
Se Security Privilege
To add the rights to the local administrator account, follow these steps:
Step 1 Log on to the computer as a user, who has administrative credentials.
Step 2 Click Start.
Step 3 Click Run, type ‘Control admintools’ and then click OK.
Step 4 Double-click Local Security Policy.
Step 5 In the Local Security Settings dialog box, click Local Policies,
Step 6 Double-click User Rights Assignment, and then double-click Backup Files and Directories.
Step 7 In the Backup Files and Directories Properties dialog box, click Add User or Group.
Step 8 In the Select User or Groups dialog box, type the user account that is being used for setup, and then click OK two times.
Step 9 Repeat the procedure for the other two policies that are mentioned in the “Local policies” section.
On the File menu, click Exit to close the Local Security Settings dialog box.
Installing SQL Server 2012 database server
Complete the following steps to install SQL server 2012:
Step 1 Under Installation tab, click ‘New SQL Server stand-alone installation or add features to an existing installation’.
Step 2 Click ‘I accept the license terms’.
Step 3 Click Next.
Step 4 Check the Database Engine Services box and click Next.
Step 5 In Instance Name, click Named instance radio button and enter the instance name as TCS.
Step 6 Click Next.
Step 7 In the Service Account, choose Use the built-in System account (Local system, or Network service).
Note SQL server collation should be set to Latin1_General_CI_AS, 'Dictionary, case insensitive, 1252 character set'.
Step 8 In the Authentication Mode, you can click any of the two given modes:
Windows authentication or
Note If Mixed mode is selected, click Enter and Confirm the SA (system administrator) password.
Installing TCS Installer
To install the VM Content Server and the license and option keys, you will need the software base Product Authorization Key (PAK) and option PAK. This information is part of the claim certificate that you received after ordering the VM Content Server.
Note You must be logged in as a Local Administrator to install, uninstall, or manage the VM Content Server.
Step 1 Copy the S_7_1_TCSVM_Bundle.zip or S_7_1_TCSBE6K_Bundle.zip file to a folder on your system and extract the files. Launch the command prompt and change the directory to the folder location.
Note For TCS 7.1, file name is S_7_1_TCSVM_Bundle.zip and for BE6K, file name is S_7_1_TCSBE6K_Bundle.zip.
Step 2Run GetTCSVirtualSN.exe to generate the virtual serial number (vSN) for your Content Server VM. Copy the virtual serial number.
Note To get the virtual serial number, use the command prompt and run as an administrator. Go to the location, where the S_7_1_TCSVM_Bundle.zip is extracted. Run GetTCSVirtualSN.exe from the command prompt.
Note For BE6K, extracted directory is S_7_1_TCSBE6K_Bundle.zip. In the license text file, make sure that there are no extra spaces before or after the license keys.
Step 5 In the command prompt, run the PreInstaller.cmd from the extracted S_7_1_TCSVM_Bundle.zip or S_7_1_TCSBE6K_Bundle.zip directory to configure the Content Server Pre-Installer.
Step 6 Run S7_1_VM.exe to install the VM Content Server software on the appliance.
Follow the prompts to complete the TCS installation.
Step 7 Run the PostInstaller.cmd from the VM Scripts folder in the command prompt to configure the Post-Installer. This will reboot the system.
Step 8 To make sure the newly created TCS VM is Up and Running. Launch TCS UI in a web browser.
Migrations options for New Customers
Appliance TCS 7.1 Release: M4 Appliance with TCS and Windows and SQL 2012 Packaged.
Virtual TCS 7.1 Release: Customers can deploy vTCS on a M4 server or spec based.
About Data Migration
If you have existing TCS with 5.x or 6.x build, you can migrate configuration and data files from your existing hardware to the newly created VM TCS. Follow the below link for more details on data migration:
Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.