Feedback
|
Table Of Contents
Release Notes for Cisco Unified MeetingPlace Web Conferencing Release 5.4(156)
Requirements for Cisco Unified MeetingPlace Web Conferencing 5.4
New and Changed Requirements and Support—Release 5.4(156)
Technical Changes with Release 5.4(156)
Changes on the Web Conferencing Server
Important Note: Java Client-Side Requirements
Web Conferencing 5.4 Documentation Changes
Video Integration Upgrade Required
Web Conferencing Documentation
Compatibility Matrix for Cisco Unified MeetingPlace Components
New Functionality—Release 5.4(156)
Changed Functionality—Release 5.4(x)
Installation and Upgrade Information
Installing Cisco Unified MeetingPlace Web Conferencing Release 5.4 for the First Time
Upgrading to Cisco Unified MeetingPlace Web Conferencing Release 5.4
Installation and Upgrade Notes
Installing Web Conferencing on an IBM MCS-7835I by Using VNC
Single Sign-On Software Integration Considerations
Terms for Single Sign-On Software Integration
Terms of Support for Single Sign-On Software Integration
Resolved Caveats—Release 5.4(156)
Multiple Guides: Cisco Policy for Use of Third-Party Software and Security Updates
CPU Spikes When Running Services
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco Unified MeetingPlace Web Conferencing Release 5.4(156)
Updated August 10, 2009
These release notes contain information on new and changed support, new and changed functionality, limitations and restrictions, and open and resolved caveats for Cisco Unified MeetingPlace Web Conferencing Release 5.4(156).
You can access the latest software upgrades for all versions of Web Conferencing on the Cisco Software Center website at http://www.cisco.com/public/sw-center/sw-voice.shtml.
Note
To access the software download page, you must be logged on to Cisco.com as a registered user.
Contents
These release notes contain the following sections:
•
New and Changed Requirements and Support—Release 5.4(156)
•
New Functionality—Release 5.4(156)
•
Changed Functionality—Release 5.4(x)
•
Installation and Upgrade Information
•
Obtaining Documentation, Obtaining Support, and Security Guidelines
System Requirements
This section contains the following information:
•
Requirements for Cisco Unified MeetingPlace Web Conferencing 5.4
Requirements for Cisco Unified MeetingPlace Web Conferencing 5.4
System Requirements for Cisco Unified MeetingPlace Release 5.4 contains the most current information on Web Conferencing requirements. The document is available at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html.
Compatibility Information
•
For information about the compatibility of Cisco Unified MeetingPlace Web Conferencing 5.4 with other Cisco Unified MeetingPlace components, refer to Compatibility Matrix: Cisco Unified MeetingPlace Components at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_device_support_tables_list.html.
•
The following third-party software is supported on Web Conferencing servers, provided that the software is configured so as not to disrupt Cisco Unified MeetingPlace operations:
–
McAfee VirusScan Enterprise versions 8.0i and later
–
Microsoft Windows Terminal Services
CautionTerminal Services (WTS) is not supported for installing or upgrading Web Conferencing. If you use WTS, the installation or upgrade process may fail.
–
Virtual Network Computing (VNC is supported for installing and upgrading Web Conferencing.)
The introduction of unsupported third-party products may affect Cisco support for the product.
CautionCisco Unified MeetingPlace Web Conferencing Release 5.4 is not compatible with Cisco Security Agent. We recommend that you do not install Cisco Security Agent on a web server where Cisco Unified MeetingPlace Web Conferencing is installed. If Cisco Security Agent is installed on an end-user system, users will see a security alert when they attempt to use the application-sharing feature. Users can choose to proceed with the feature and use application-sharing without difficulty.
Related Documentation
For descriptions and locations of Cisco Unified MeetingPlace documentation on Cisco.com, refer to the Documentation Guide for Cisco Unified MeetingPlace. The document is shipped with Cisco Unified MeetingPlace and is available at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_documentation_roadmaps_list.html.
New and Changed Requirements and Support—Release 5.4(156)
This section contains information about new and changed requirements and support in the Cisco Unified MeetingPlace Web Conferencing Release 5.4(156) time frame only. Refer to the release notes of the applicable version for information on new and changed support with earlier versions of Web Conferencing. Release notes for all versions of Web Conferencing are available at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_release_notes_list.html.
Technical Changes with Release 5.4(156)
This section describes technical changes introduced by Cisco Unified MeetingPlace Web Conferencing 5.4(156):
•
Changes on the Web Conferencing Server
•
Important Note: Java Client-Side Requirements
•
Web Conferencing 5.4 Documentation Changes
Changes on the Web Conferencing Server
•
The web server (IIS) filter "Jenga" has been removed.
•
The web server (IIS) extension "JengaX" has been removed.
•
The web server Java servlet known as "DCMS master" has been removed.
•
The SQL Server database "MPWEB-Slave-####" has been removed.
•
The ODBC System DSN "DCMS" has been removed.
•
Most of the registry keys under HKEY_LOCAL_MACHINE\Software\Data Connection\Admin have been removed.
•
More than 1,000 unnecessary files including .exe and .dll files have been removed.
Both the Web Conferencing 5.4(156) installer and the Web Conferencing 5.4(156) Master Service (when run the first time) have the appropriate logic to remove the unused components from the system. No features are impacted by these technical changes.
Java Server-Side Change
As a consequence of the structural changes described in the "Changes on the Web Conferencing Server" section, Sun Java 1.4.2_05 is no longer necessary on the Web Conferencing server. During a fresh installation of the Web Conferencing 5.4(156) software, Sun Java 1.4.2_05 is not installed. However, Sun Java 1.4.2_05 will not be removed by the installer when performing an upgrade of a previous version of Web Conferencing. It is possible and allowed to remove the Java 2 Runtime Environment, SE v1.4.2_05 by using the standard Windows Add/Remove Programs control panel.
Important Note: Java Client-Side Requirements
Microsoft or Sun Java associated to a web browser is still required on the client side for end users to participate in web conferences. There is no change of operations or requirements for end users in this area.
Web Conferencing 5.4 Documentation Changes
As a consequence of the structural changes described above, some installation and configuration steps described in the Installation and Upgrade Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.4 and in the Configuration Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.4 no longer apply. See the "Changes" section under "Documentation Updates."
Internet Explorer 7.0
Web Conferencing supports Microsoft Internet Explorer 7.0 on Windows XP and Windows Vista.
Java Runtime Environment
Web Conferencing supports the following Java versions on end-user workstations:
•
Microsoft JVM 3810.
•
Sun Java 1.4.2_04 or later—except versions 1.4.2_10, 1.4.2_11, and 1.5.0_06, which have a defect affecting the Web Meeting Console.
Video Integration Upgrade Required
If the system has Cisco Unified MeetingPlace Video Integration installed, you must upgrade to Video Integration Release 5.4(107).
Web Conferencing Documentation
This section lists new product documentation available with this release.
Compatibility Matrix for Cisco Unified MeetingPlace Components
For the most current list of supported version combinations of Cisco Unified MeetingPlace Audio Server and the Cisco Unified MeetingPlace components, refer to Compatibility Matrix: Cisco Unified MeetingPlace Components at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_device_support_tables_list.html.
The document replaces information in the "Cisco Unified MeetingPlace Component Compatibility Matrix" section in the "Introducing Cisco Unified MeetingPlace" chapter of the Installation and Upgrade Guide for Cisco Unified MeetingPlace.
New Functionality—Release 5.4(156)
There is no new functionality for Cisco Unified MeetingPlace Web Conferencing Release 5.4(156). See the "Resolved Caveats—Release 5.4(156)" section.
Refer to the release notes of the applicable version for information on new functionality in earlier versions of Web Conferencing. Release notes for all versions of Web Conferencing are available at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_release_notes_list.html.
Changed Functionality—Release 5.4(x)
There is no changed functionality for Cisco Unified MeetingPlace Web Conferencing Release 5.4(156). See the "Resolved Caveats—Release 5.4(156)" section.
Refer to the release notes of the applicable version for information on changed functionality in earlier versions of Web Conferencing. Release notes for all versions of Web Conferencing are available at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_release_notes_list.html.
Installation and Upgrade Information
Installing or upgrading to Cisco Unified MeetingPlace Web Conferencing Release 5.4 by using Microsoft Windows Terminal Services is not supported.
This section contains the following information:
•
Installing Cisco Unified MeetingPlace Web Conferencing Release 5.4 for the First Time
•
Upgrading to Cisco Unified MeetingPlace Web Conferencing Release 5.4
•
Installation and Upgrade Notes
Installing Cisco Unified MeetingPlace Web Conferencing Release 5.4 for the First Time
For instructions on installing Web Conferencing, refer to the Installation and Upgrade Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.4 at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html.
Upgrading to Cisco Unified MeetingPlace Web Conferencing Release 5.4
For instructions on upgrading Web Conferencing, refer to the "Upgrading to Web Conferencing Release 5.4" chapter of the Installation and Upgrade Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.4 at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html.
Installation and Upgrade Notes
Installing Web Conferencing on an IBM MCS-7835I by Using VNC
There is a known problem installing Cisco Unified MeetingPlace Web Conferencing on an IBM MCS-7835I by using VNC when Cisco Unified CallManager was installed earlier by using VNC on a server that is running IBM Director version 4.11 or later.
To avoid this problem, we strongly recommend that you do not use VNC for a new installation or an upgrade of Web Conferencing on an IBM MCS-7835I.
For additional information, see the "Using Bug Toolkit" section, and refer to caveat CSCsa39488.
Limitations and Restrictions
•
Single Sign-On Software Integration Considerations
Browser Limitations
We do not support Windows Vista with Aero.
Configuration Restrictions
Cisco Unified MeetingPlace Web Conferencing deployments that are customized beyond the built-in configuration capabilities of the product, or beyond the documented configuration settings, procedures or instructions, are not supported by Cisco Systems. Examples of such customizations include, but are not limited to, the following: modifying web page templates; changing HTML or Javscript code; changing IIS running parameters or applying custom .asp pages or ISAPI filters; modifying SQL server configuration or authentication method; and modifying Windows OS security through IPSec policies and NTFS ACL.
Single Sign-On Software Integration Considerations
•
Terms for Single Sign-On Software Integration
•
Terms of Support for Single Sign-On Software Integration
Terms for Single Sign-On Software Integration
•
Customer Premise Equipment (CPE) customers who implement single sign-on (SSO) software integrations on Cisco Unified MeetingPlace Web Conferencing servers do so at their own risk and are responsible for understanding the technical implementations and feasibility of SSO integrations on the systems.
•
By allowing SSO software integrations, we do not claim support for any SSO software packages or vendors.
•
SSO software integrations require proper configuration of Web Conferencing systems through the Admin pages. If the SSO software integration requires a change in the Web Conferencing product source code, the SSO integration becomes an SSO customization, and we do not support customizations by either customers or any other parties.
•
CPE customers who want to integrate SSO packages can contact Cisco Managed Services to obtain a service request for implementing SSO. The service is offered as a convenience and does not change the scope of the SSO integration; the service is an integration and configuration of the Web Conferencing product, not a customization of the product code.
•
Customers must first implement SSO software integrations on test or lab servers and confirm that the integrated systems work, including Web Conferencing features and operations.
•
Customers are responsible for ensuring stability of integrated Web Conferencing-SSO systems, including communicating with SSO software vendors for the following reasons:
–
To obtain necessary fixes and support.
–
To troubleshoot functional problems and technical problems, including crashes triggered by the SSO package.
•
SSO software often includes a web-server extension, called the IIS ISAPI extension or filter. Web Conferencing installs and uses four IIS extensions. Any incompatibility between an SSO software extension and the Web Conferencing extensions can make IIS non-functional or unstable. Any crash of the SSO IIS extension can cause IIS to crash and can generate a full Web Conferencing outage, resulting in a full system restart, termination of in-progress meetings, and disconnection of web-conferencing users. In addition, any memory leak in the SSO package or module can make IIS or the whole server unstable.
•
Although SSO software integration is productized for the Web Conferencing system, any changes in overall configuration, including Web Conferencing upgrades and SSO package upgrades, can potentially break integrated Web Conferencing-SSO systems.
Terms of Support for Single Sign-On Software Integration
•
Customers must inform Cisco TAC that their Cisco Unified MeetingPlace Web Conferencing servers have third-party single sign-on (SSO) packages installed and configured with Web Conferencing when opening a service request for Web Conferencing, Cisco Unified MeetingPlace for Outlook, or Cisco Unified MeetingPlace for Lotus Notes.
•
Customers must be able to provide SSO integration details upon request. Inability to provide details can result in Cisco TAC not being able to proceed with service requests.
•
If a service request is about troubleshooting the SSO integration, Cisco TAC can review the logs and identify whether the problem is on the SSO side or the Web Conferencing side. If the problem is on the SSO side, information will be provided to customers, so they can further troubleshoot with their SSO vendors.
•
If the service request is about troubleshooting a Web Conferencing problem that does not seem to be connected to the SSO integration, Cisco TAC will proceed per the normal support process. If Cisco TAC discovers that the SSO integration plays a role in the problem, information will be provided to customers, so they can further troubleshoot with their SSO vendors.
•
If Cisco TAC believes the problem is triggered by an SSO package, Cisco TAC can require customers to disable the SSO package to troubleshoot further.
•
Microsoft Debug Diagnostic tool, also called DebugDiag, may be required for troubleshooting IIS crashes and memory leaks to determine whether the problems are produced by the SSO package.
Caveats
This section lists Severity 1, 2, and 3 caveats.
You can find the latest caveat information for Cisco Unified MeetingPlace Web Conferencing version 5.4(156)—in addition to caveats of any severity for any release—by using Bug Toolkit, an online tool available for customers to query defects according to their own needs. Bug Toolkit is available at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. For information on using Bug Toolkit, see the "Using Bug Toolkit" section.
Note
To access Bug Toolkit, you must be logged on to Cisco.com as a registered user.
This section contains caveat information for Web Conferencing Release 5.4(156) only. Refer to the release notes of the applicable version for caveat information for earlier versions of Web Conferencing. Release notes for all versions of Web Conferencing are available at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_release_notes_list.html.
Open Caveats—Release 5.4(156)
(Caveats are listed in order by severity, then by component, then by caveat number.)
Resolved Caveats—Release 5.4(156)
(Caveats are listed in order by severity, then by component, then by caveat number.)
Using Bug Toolkit
To access Bug Toolkit, you need an Internet connection, web browser, and Cisco.com user ID and password. For more detailed information on using Bug Toolkit, click Help in any Bug Toolkit window.
To Use Bug Toolkit
Step 1
Open your web browser and go to http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
Step 2
Click the Launch Bug Toolkit link.
Step 3
To look for information about a specific caveat, enter the ID number in the Enter Known Bug ID field.
To view all caveats for a Cisco Unified MeetingPlace component, go to the "Search for Bugs in Other Cisco Software and Hardware Products" section, and enter meetingplace in the Product Name field.
Step 4
In the list, select Cisco Unified MeetingPlace, then click Next.
Step 5
On the Cisco Unified MeetingPlace search page, set options to limit your search results. You can choose any or all of the available options:
a.
Choose the applicable Cisco Unified MeetingPlace version:
•
Choose the major version for the major releases. A major release contains significant new features, enhancements, architectural changes, and/or defect fixes.
•
Choose the revision for more specific information. A revision (maintenance) release primarily contains defect fixes to address specific problems, but it may also include new features or enhancements.
b.
Choose the applicable features or components. Make your selection from the Available list and click Add to place your selection in the Limit Search To list.
c.
Enter keywords for which to search caveat titles and descriptions.
Note
To make queries less specific, use the All wildcard for the major version/revision, features/components, and keyword options.
d.
Choose the applicable advanced options:
•
Bug Severity—The default specifies severity levels 1 through 3.
•
Bug Status Group—Check the Fixed check box for resolved caveats.
•
Release Note Enclosure—The default specifies Valid Release Note Enclosure.
Step 6
Click Next. Bug Toolkit returns a list of caveats.
Note
You can modify your results by submitting another query and using different criteria. You can also save your query for future use.
Documentation Updates
Errors
This section lists errors in the current Cisco Unified MeetingPlace Web Conferencing documentation and gives corrected information. The correct information will be incorporated in a future documentation release.
Configuration Guide for Cisco Unified MeetingPlace Web Conferencing: Prerequisites for Configuring WebConnect
The sixth bullet in the "Prerequisites for Configuring WebConnect" section in the "Configuring WebConnect" chapter of the Configuration Guide for Cisco Unified MeetingPlace is incorrect. The correct text for the bullet is as follows:
•
If you use Cisco Unified MeetingPlace Video Integration, and a single MCU is shared among sites, the Video Integration can be installed on the web servers at only one site. If each site has its own MCU, the Video Integration can be installed on web servers at each site. In either case, the Cisco Unified MeetingPlace Audio Server at each site must be licensed for video.
In the "Prerequisites for Configuring WebConnect" section in the "Configuring WebConnect" chapter of the Configuration Guide for Cisco Unified MeetingPlace add the following requirement:
•
You must use Cisco Unified MeetingPlace Directory Services for synchronizing user profiles.
Configuration Guide for Cisco Unified MeetingPlace Web Conferencing: Prerequisites for Configuring Cisco Unified MeetingPlace for Cisco Unified IP Phone
The fourth bullet in the "Prerequisites for Configuring Cisco Unified MeetingPlace for Cisco Unified IP Phone" section in the "Configuring Cisco Unified MeetingPlace for Cisco Unified IP Phone" appendix of the Configuration Guide for Cisco Unified MeetingPlace is incorrect. The correct text for the bullet is as follows:
•
The only supported authentication method for Cisco Unified MeetingPlace for Cisco Unified IP Phone is the Cisco Unified MeetingPlace Directory and Web Page Form for login method. See the "About MeetingPlace Authentication" section on page 4-4 for information about authentication methods.
Multiple Guides: Cisco Policy for Use of Third-Party Software and Security Updates
In the "Terms of Use" section in the "Introducing Cisco Unified MeetingPlace Web Conferencing" chapters of the Installation and Upgrade Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.4 and the Configuration Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.4, disregard the policy section titled "Cisco Policy for Use of Third-Party Software and Security Updates."
For information on supported third-party software, see the "Compatibility Information" section.
For system requirements, refer to the "Requirements for Cisco Unified MeetingPlace Web Conferencing 5.4" section of System Requirements for Cisco Unified MeetingPlace Release 5.4 at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html.
CPU Spikes When Running Services
Running some services, such as MPAgent, can use as much as 90 percent of your CPU. Fortunately, these services run at a low priority so the CPU spikes do not impact important system functions.
Changes
This section lists changes to the current Cisco Unified MeetingPlace Web Conferencing documentation. The changed information will be incorporated in a future documentation release.
Installation and Upgrade Guide for Cisco Unified MeetingPlace Web Conferencing and Configuration Guide for Cisco Unified MeetingPlace Web Conferencing: Some Procedure Steps Can Be Ignored
Because of structural changes in Web Conferencing 5.4(156) (see the "Technical Changes with Release 5.4(156)" section), the following steps in procedures throughout the Installation and Upgrade and Configuration guides for Web Conferencing can be ignored:
•
All steps involving the creation, deletion, or modification of the registry keys located in HKEY_LOCAL_MACHINE\Software\Data Connection\Admin. (These keys were used for the connection to the MPWEB-Slave SQL database and for load balancing configuration.)
•
All steps involving the access, configuration, backup and restore of the MPWEB-Slave (also referred to as MPWEB-Slave-#### database), as this database no longer exists. (If the database still exists after Web Conferencing 5.4(156) has been installed and started, the SQL credentials that you are using may not have sufficient privilege for the Web Conferencing master service to drop this database. In that case, a warning message in the log may invite a SQL administrator to drop this database manually.)
•
All steps involving the presence or installation of the Sun Java Runtime Environment on the Web Conferencing server.
•
All steps involving the Jenga, JengaTest, Servlet, or WEBI components.
Troubleshooting Information
Refer to the "Troubleshooting Cisco Unified MeetingPlace Web Conferencing" chapter of the Configuration Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.4 at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flip Video, Flip Video (Design), Flipshare (Design), Flip Ultra, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Store, and Flip Gift Card are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website 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. (0907R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2009 Cisco Systems, Inc. All rights reserved.
Feedback
