Table 4 lists Cisco Show and Share software versions that are compatible with Content Server software.
Table 4 Cisco Show and Share and Content Server Software Compatibility
Show and Share 5.2.1
Show and Share 5.2.2
Show and Share 5.2.3
Show and Share 5.3 and 5.3 Patch 1
Show and Share 5.5
Content Server 6.2
Table 5 lists the Cisco MXE 3500 software versions that are compatible with Content Server software.
Table 5 Cisco MXE 3500 and Content Server Software Compatibility
Content Server 6.2
Limitations and Restrictions
Content Servers in a cluster can be a mix of second and third generation hardware and Virtual Machine hardware that are all running software Release 6.2. Cluster members in a mixed hardware cluster must all be running Release 6.2.
Multicast content delivery from Windows media services is not supported on Windows 2008 Standard Edition. The Content Server version 6.2 built-in Windows Media server can only stream unicast live video. For multicast live-streaming via the built-in Windows Media server you need to use an additional external Windows Media server.
The Content Server does not support running Windows services such as Active Directory Domain Services (ADDS), DNS server, or file services. You should configure an external server for all Windows-based services.
The USB media kit is used only for a third-generation Content Server software reimage. You cannot use the USB drive to upgrade the software on first- or second-generation server hardware.
The Content Server Release 6.2 software has no partial restore or full restore functionality. To return a Content Server to the factory-default software, you can perform a software reimage. This procedure clears the server hard drive and then reinstalls the Content Server system software. See the “Maintaining the Content Server” chapter in the Cisco TelePresence Content Server Administration and User Guide for more information.
The Content Server recording does not display the content channel if the Content Mode for a conference is set to “Pass through” in the MCU. (CSCuo00042)
The Content Server does not record HD resolution if a connected device (endpoint, laptop or PC) shares a presentation in a lower resolution. The recording will be transcoded in the lower resolution regardless of whether or not a Premium Resolution license is installed. (CSCum08630)
Pin Protected Calls and Pin protected Recording playback does not work with CUCM SIP trunk.
See these sections:
During third party hardware certification, it was found that TCS UI didn't show up though TCS is successfully installed and all the services were functioning.” To ensure that installation of TCS Software gets installed on third party Hardware. Please make sure correct date and times is configured. Go to ESXI > Configuration > Time Configuration > Properties. Update the correct date and time (CSCus76714).
Note Audio only recording with SIP is not supported on TCS 6.2.
When using the Content Server with IE 11, you could encounter these issues:
– HTTPS is required for log in.
– To play WMV and QuickTime recordings, the Content Server site must be added to the compatibility view list as show below.
There are no workarounds.
Figure 1 Compatibility View Setting
When using the Content Server Content Editor with Firefox, you could encounter these issues:
– QuickTime is not viewable or working although the Content Editor for QuickTime is functional.
– In the Content Editor of WMV the recording is not viewable.
– After playing a WMV recording on Firefox, the following error might appear and Firefox stops responding:
Microsoft Windows Media Player Firefox plugin may be busy or it may have stopped responding. You can stop the plugin now, or you can continue to see if the plugin will complete. Continue or Stop Plugin?
When using Windows Media player with Firefox in HTTPS mode, the system could return this error message even if you have installed the required plugin:
Windows Media player is not installed on your computer. To play Windows Media in Firefox, you need to install a special plugin.
The workaround is to use IE10 or IE11.
The workaround is to use HTTP instead of HTTPS. For more information about installing the required plugin, see
If you change the domain name of a third-generation Content Server and then run Windows Server Backup, the system could return this error message:
The Block Level Backup Engine Service has been disabled. Enable the service and then restart Windows Server Backup.
The workaround is to start the Windows service called Virtual Disk, and then launch Windows Server Backup. If starting the Virtual Disk service does not resolve the issue, you should uninstall and reinstall the Windows Server Backup feature. (CSCuo29694)
Table 6 lists the supported playback formats with HTTPS.
Table 6 Supported HTTPS Playback Formats
Software Installation and Upgrade Notes
Netlogon Exception—If you are installing or upgrading Content Server Release 6.0 (build 3474), Release 6.0.1 (build 3528), Release 6.1 (build 3764),or Release 6.2 (build 3880) the system might display this message if the Content Server is not in a domain:
Error: Starting enabled service, Service not started [service_name = Netlogon] Service not started.
The exception message has no impact on the software installation or upgrade procedure.
Internet Connection Sharing (ICS) Exception—If you are upgrading from Release 6.0 to Release 6.2, the system might display this message:
Error: Starting enabled service, Service not started [service_name = Internet Connection Sharing (ICS)] Service not started.
The exception message has no impact on the software installation or upgrade procedure.
Table 7 lists the open caveats in Content Server Release 6.2.
Table 7 Content Server Release 6.2 Open Caveats
SIP EP playback details are not displayed in case of new recording alias.
Trunk not active need to restart services manually.
Localization is not working on UI changes for CUCM Integration.
Maximum 23 aliases can be created in Terminal mode with BE6K license.
audio only recording with SIP not supported in TCS 6.2
Table 8 lists the resolved caveats in Content Server Release 6.2.
Table 8 Content Server Release 6.2 Resolved Caveats
Before you begin, observe these guidelines and prerequisites:
You must have administrator privileges to perform a software upgrade.
You should download Release 6.2 software from Cisco.com before you begin the upgrade procedure.
A release key is not required for upgrading to Release 6.2.
Release 6.2 software cannot be installed on first- or second-generation Content Server hardware. If you attempt to run the 6.2 installer it will fail.
Release 6.2 software can be installed on Second-generation and Third-generation content Server hardware as VM.
You can use the Content Server serial number to identify the server hardware version. In the web UI go to Management > Diagnostics > Server overview. You can also check the serial number label on the top right front of the Content Server. These are the device serial number formats:
– Third-generation serial number: 49A3 xxxx
– Second-generation serial number: 49A2 xxxx
– First-generation serial number: 49A0 xxxx
must back up your Content Server and turn off anti-virus applications before upgrading. You will need a full backup for restoring to the previous version or in the unlikely event of an upgrade failure. Follow the instructions for backing up and restoring the Content Server in the online help and in the
Cisco TelePresence Content Server Administration and User Guide on Cisco.com.
If you have installed the Feature Pack for Microsoft SQL Server 2005 or any of its components (which is NOT supported for the Cisco TelePresence Content Server), you must remove the components prior to upgrading, otherwise the upgrade may fail. These unsupported components MUST be removed prior to upgrading:
Microsoft SQL Server 2005 Analysis Services 9.0 OLE DB Provider, Microsoft SQL Server 2005 Backward Compatibility Components, Microsoft SQL Server 2005 Command Line Query Utility, Microsoft SQL Server 2005 Data Mining Viewer Controls, Microsoft SQL Server 2005 JDBC Driver, Microsoft SQL Server 2005 Management Objects Collection, Microsoft SQL Server 2005 Compact Edition, Microsoft SQL Server 2005 Notification Services Client Components, Microsoft SQL Server 2005 Upgrade Advisor, Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint Technologies, Microsoft SQL Server 2005 Data Mining Add-ins for Microsoft Office 2007.
Software Upgrade Procedure
The approximate duration of an upgrade is 10 to 20 minutes. Follow these steps:
Step 1 Log in to the Content Server as the administrator by using Windows Remote Desktop Connection.
Step 2 Transfer the installer and the MD5 file that you downloaded from Cisco.com to the Content Server. Do not run the installer from a mapped or network drive.
Step 3 Verify the MD5 hash (checksum) of the installer by using the provided MD5 file. We recommend verifying that the installer is not corrupted due to file transfer, disk error, or tampering. You can use any MD5 program to verify the installer integrity.
Step 4 When the installer passes the MD5 verification, double-click the installer to run the installation wizard.
Step 5 Click Next. The InstallShield Wizard is ready to begin installation.
Step 6 At the Content Server prerequisites prompt, select the backup option that applies to your Content Server:
If you select The Content Server is backed up, click Next to proceed with the installation.
If you select The Content Server is not backed up, clicking Next displays a warning that in case of installation failure there may be no way to recover your data. You can cancel the installation, take a backup of your Content Server, and then run the installer again. You can also choose to ignore the warning and proceed with the installation, although this is not recommended.
Step 7 At the second Content Server prerequisites prompt, select the antivirus option that applies to your Content Server:
If you select There is no antivirus software installed, or The antivirus software is stopped, click Next to proceed with the installation.
If you select The antivirus software is still running, clicking Next displays a warning that this might cause your installation to fail. You can cancel the installation, stop the antivirus software, and then run the installer again. You can also choose to ignore the warning and proceed with the installation, although this is not recommended.
Step 8 At the Are you sure you wish to continue? prompt, click Yes to proceed. Click No to cancel the upgrade.
References to accessing the Window Server interface by using the Content Server user interface are no longer valid. You can access the Windows Server interface only by using Windows Remote Desktop Connection.
Cisco recommends registering your product at http://www.cisco.com/cisco/support/notifications.html in order to receive notifications about the latest software and security updates. New feature and maintenance releases are published regularly, and we recommend that your Content Server software is always kept up to date.
Using the server logs to help solve a problem
You can use the server logs to produce debugging information to assist customer support in solving issues. From the Management tab, go to Diagnostics > Server logs to access the Content Server logs.
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.