Installation and Upgrade Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.4
Upgrading to Web Conferencing Release 5.4
Downloads: This chapterpdf (PDF - 155.0KB) The complete bookPDF (PDF - 1.85MB) | Feedback

Upgrading to Web Conferencing Release 5.4

Table Of Contents

Upgrading to Web Conferencing Release 5.4

Restrictions on Upgrading to Web Conferencing Release 5.4

Before You Upgrade to Web Conferencing Release 5.4

User Authentication Methods in Release 5.4

Load Balancing in Release 5.4

Backing Up Before the Upgrade

Backing Up the MPWEB Database and MPWEB-Slave Database

Backing Up Critical Web Conferencing Application Files

Backing Up Cisco Unified MeetingPlace Registry Information

Upgrading the Web Conferencing Software

Preparing for the Web Conferencing Software Upgrade

Upgrading the Web Conferencing Software on a Standalone Web Server

Upgrading a Standalone Web Server to a Shared Database Configuration

Upgrading the Web Conferencing Software on Web Servers That Share the Same Database

Uninstalling Web Conferencing, SQL Server, or MSDE Software

Uninstalling Web Conferencing Software

Removing SQL Server or MSDE Software


Upgrading to Web Conferencing Release 5.4


This chapter contains the following sections:

Restrictions on Upgrading to Web Conferencing Release 5.4

Before You Upgrade to Web Conferencing Release 5.4

Backing Up Before the Upgrade

Upgrading the Web Conferencing Software

Uninstalling Web Conferencing, SQL Server, or MSDE Software


Note Before reviewing this chapter, read 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.


Restrictions on Upgrading to Web Conferencing Release 5.4

For a list of versions that are supported for upgrade to Release 5.4, refer to "Upgrade Requirements" in 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.

Upgrading by using Terminal Services is not supported.

You cannot delete the SQL Server database if you want to maintain your current click-to-attend links, attachments, and meeting recordings. Deleting or rebuilding your current database will delete all of this information.

Upgrading to Release 5.4 is supported only from a supported Cisco MCS or exact HP or IBM equivalent. If you are not using a supported Cisco MCS or exact HP or IBM equivalent, you must install Release 5.4 as a new installation on a supported Cisco MCS.

If you are upgrading Web Conferencing load balancing clusters, every web server in a cluster must be upgraded to the exact same release and build number (for example, Release 5.4.x).

If you have any customizations that you made in a supported earlier release, they will be lost when you upgrade to Release 5.4. You will have to reimplement your customizations through the Web Conferencing Administrative pages as part of the overall system configuration.

Customizations of the user interface (such as hide/show fields and display custom strings) are stored in the SQL database as part of the Web Conferencing configuration and, thus, are maintained during an upgrade from Release 5.3.

Since Release 5.3, we no longer honor customization requests for Customer Premise Equipment (CPE) customers, and Cisco TAC no longer supports CPE systems that are customized beyond the built-in configuration capabilities of the product, or beyond the documented configuration settings, procedures or instructions. Examples of such customizations include, but are not limited to, the following: modifying web page templates, changing HTML or JavaScript 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.

Before You Upgrade to Web Conferencing Release 5.4

This section contains the following information that you may need to know before upgrading:

User Authentication Methods in Release 5.4

Load Balancing in Release 5.4

User Authentication Methods in Release 5.4

Cisco Unified MeetingPlace Web Conferencing Release 5.4 supports multiple authentication methods. For an upgrade from a supported release earlier than Release 5.3(235), you must reconfigure your web server to use the desired authentication method.

See the "Configuring User Authentication in Cisco Unified MeetingPlace Web Conferencing" chapter in the Configuration Guide for Cisco Unified MeetingPlace Web Conferencing at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.

Load Balancing in Release 5.4

For an upgrade to Release 5.4 when Cisco Unified MeetingPlace Web Conferencing is installed in a load balancing configuration, you must configure the Cisco MeetingPlace Web Conferencing service to log on as Administrator. If you do not configure the Cisco MeetingPlace Web Conferencing service to log on as Administrator, Web Conferencing will not start.

Backing Up Before the Upgrade

Before you upgrade any existing Cisco Unified MeetingPlace Web Conferencing installation, you must back up critical application files. The backup files enable you to revert to your previous environment if the upgrade or installation fails.

The following backup tasks are required for all upgrade scenarios (full and patch upgrades):

1. Backing Up the MPWEB Database and MPWEB-Slave Database

2. Backing Up Critical Web Conferencing Application Files

3. Backing Up Cisco Unified MeetingPlace Registry Information

Backing Up the MPWEB Database and MPWEB-Slave Database

The procedure in this section uses Enterprise Manager to back up the databases. Back up the MPWEB database first, then the MPWEB-Slave database.

To use osql commands, see the "Cisco Unified MeetingPlace Web Conferencing and SQL Server" appendix in the Configuration Guide for Cisco Unified MeetingPlace Web Conferencing at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.

To Back Up the MPWEB Database and MPWEB-Slave Database


Step 1 Open Enterprise Manager.

Step 2 Expand the database folder.

Step 3 Right-click the database name—MPWEB or MPWEB-Slave—then choose All Tasks > Backup Database.

The SQL Server Backup - MPWeb window appears.

Step 4 Specify the destination where the backup file will be created, then click OK to initiate the backup operation.

The Backup Progress window appears, then disappears when the backup process is complete.

Step 5 Repeat Step 1 through Step 4 to back up the MPWEB-Slave-#### database.


Note If you see multiple MPWEB-Slave databases, you have a load balancing cluster, in which multiple Web Conferencing servers work together to provide data conferencing load balancing. All members in the cluster share the same MPWEB database, but each member has its own MPWEB-Slave database. Back up all valid databases.


Step 6 Continue with the "Backing Up Critical Web Conferencing Application Files" section.


Backing Up Critical Web Conferencing Application Files

Before You Begin

Complete the "Backing Up the MPWEB Database and MPWEB-Slave Database" section.

To Back Up Critical Web Conferencing Application Files


Step 1 Open Explorer.

Step 2 Browse to the folder in which the Cisco Unified MeetingPlace Web Conferencing application is installed.

Step 3 Open the MPWeb folder.

Step 4 Back up all folders except for the Diagnostics and Meetings folders.

Step 5 Continue with the "Backing Up Cisco Unified MeetingPlace Registry Information" section.


Backing Up Cisco Unified MeetingPlace Registry Information

Before You Begin

Complete the "Backing Up Critical Web Conferencing Application Files" section.

To Back Up Cisco Unified MeetingPlace Registry Information


Step 1 Open Registry Editor.

Step 2 Navigate to and select HKEY_LOCAL_MACHINE\SOFTWARE\Latitude.

Step 3 From the menu bar, choose Registry > Export Registry File.

Step 4 Save the file.


Tip When saving your backup files, add information that will help you manage the backup. For example, including 4.3.0.246 and 5.4.x in the folder name means that the folder contains the Release 4.3(0.246) backup files, which were created before you upgraded to Release 5.4.(x).


Step 5 Save all backup files to a safe location.


Upgrading the Web Conferencing Software

This section contains the following information:

Preparing for the Web Conferencing Software Upgrade

Upgrading the Web Conferencing Software on a Standalone Web Server

Upgrading a Standalone Web Server to a Shared Database Configuration

Upgrading the Web Conferencing Software on Web Servers That Share the Same Database

Preparing for the Web Conferencing Software Upgrade

Before You Begin

Read the "Restrictions on Upgrading to Web Conferencing Release 5.4" section.

Read the "Before You Upgrade to Web Conferencing Release 5.4" section.

Complete the "Backing Up Before the Upgrade" section.


Caution Cisco Unified MeetingPlace Web Conferencing overwrites all customizations when upgrading from Release 4.3(0. x). Ensure that you back up your customizations as indicated in the upgrade procedures so they are available for future retrieval.

To Prepare to Upgrade the Web Conferencing Software


Step 1 Ensure that your system meets the requirements for upgrading.

See "Upgrade Requirements" in 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.

Step 2 Confirm that the Cisco Unified MeetingPlace 8100 series server to which the web server is connecting has Cisco Unified MeetingPlace Audio Server Release 5.4 installed.

If it does not, do one of the following tasks:

Upgrade the 8100 series server to Audio Server Release 5.4. See the Installation and Upgrade Guide for Cisco Unified MeetingPlace Audio Server at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html.

Attach the web server to a different 8100 series server that is already running Audio Server Release 5.4. See the "Changing the Cisco Unified MeetingPlace Audio Server Connection" section in the "Configuring Cisco Unified MeetingPlace Web Conferencing" chapter of the Configuration Guide for Cisco Unified MeetingPlace Web Conferencing at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.

Step 3 (Optional) Upgrade the Cisco MCS server or non-Cisco MCS server to the latest OS requirements:

Cisco MCS server

We recommend upgrading to the latest Cisco MCS Server OS release or patch.

Non-Cisco MCS server

We recommend upgrading to the latest Windows 2000 Server service pack and installing any additional critical security hot fixes, as reported by the Windows Update utility.


Step 4 Continue with the applicable upgrade, depending on the configuration:

Upgrading the Web Conferencing Software on a Standalone Web Server.

Upgrading a Standalone Web Server to a Shared Database Configuration.

Upgrading the Web Conferencing Software on Web Servers That Share the Same Database


Upgrading the Web Conferencing Software on a Standalone Web Server


Caution Cisco Unified MeetingPlace Web Conferencing overwrites all customizations when upgrading from Release 4.3(0. x). Ensure that you back up your customizations as indicated in the upgrade procedures so they are available for future retrieval.

Before You Begin

Obtain the "Installing Web Conferencing" chapter to assist you with the upgrade.

Complete the "Preparing for the Web Conferencing Software Upgrade" section.

To Upgrade the Web Conferencing Software on a Standalone Web Server


Step 1 Stop all Web Conferencing services:

a. From the Windows Service control panel, right-click Cisco MeetingPlace Web Conferencing.

b. Choose Stop.

Step 2 Back up any customized Web Conferencing pages in the Template, Html, Images, Jslib, and Scripts directories, and any images, if applicable:

a. Locate the directory where the previous version of Cisco Unified MeetingPlace Web Conferencing is installed. Typically, this is drive:\Latitude\mpweb.

b. Create a new directory called mpweb_backup (for example drive:\Latitude\mpweb_backup).

c. Copy the Template, Html, Images, Jslib, and Scripts directories, and any images, from drive:\Latitude\mpweb to drive:\Latitude\mpweb_backup.

Step 3 Run the Web Conferencing Setup program and follow the installation process described in the "Installing Web Conferencing" chapter.


Upgrading a Standalone Web Server to a Shared Database Configuration

To upgrade a standalone web server to a shared database configuration, first upgrade the Web Conferencing software on the server by using the instructions in the "Upgrading the Web Conferencing Software on a Standalone Web Server" section, then refer to the "How to Migrate from a Local SQL Server Database to a Remote SQL Server Database" section in the "Cisco Unified MeetingPlace Web Conferencing and SQL Server" appendix of the Configuration Guide for Cisco Unified MeetingPlace Web Conferencing at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.

Upgrading the Web Conferencing Software on Web Servers That Share the Same Database

Web servers share the same database in the following circumstances:

They are deployed as part of a Cisco Unified MeetingPlace Web Conferencing load balancing cluster.

They are deployed as part of a WebConnect configuration.

Although it is possible to upgrade both an internal cluster and an external cluster at the same time, we recommend that you complete the upgrade of one cluster before you proceed to the next cluster to reduce confusion and the potential for error.

Before You Begin

See the "Installing Web Conferencing" chapter to assist you with your configuration.

Read the "Load Balancing in Release 5.4" section.

Complete the "Preparing for the Web Conferencing Software Upgrade" section.

Restrictions

You must upgrade every web server in an internal cluster, external cluster, or WebConnect configuration to the exact same release and build number.

To Upgrade the Web Conferencing Software on Web Servers Sharing the Same Database


Step 1 From a group of web servers sharing a database, shut down all the web servers except one.

Step 2 Back up any customized Web Conferencing pages in the Template, Html, Images, Jslib, and Scripts directories, and any images, if applicable:

a. Locate the directory where the previous version of Cisco Unified MeetingPlace Web Conferencing is installed. Typically, this is drive:\Latitude\mpweb.

b. Create a new directory called mpweb_backup (for example drive:\Latitude\mpweb_backup).

c. Copy the Template, Html, Images, Jslib, and Scripts directories, and any images, from drive:\Latitude\mpweb to drive:\Latitude\mpweb_backup.

Step 3 Run the Web Conferencing Setup program to upgrade.

Most installation and configuration settings remain from your previous installation of Web Conferencing.

Step 4 Reboot the server.

Step 5 Verify the Web Conferencing configuration based on the type of server you are deploying, such as part of an internal cluster, part of an external cluster, or part of a WebConnect configuration.

Step 6 Verify Web Conferencing functionality.

Step 7 Leave the web server running.

Step 8 Turn on the second web server and repeat Step 2 through Step 7.

Step 9 Repeat Step 2 through Step 7 on all subsequent web servers in this cluster until all are upgraded to the exact same release.


Uninstalling Web Conferencing, SQL Server, or MSDE Software

This section contains the following information:

Uninstalling Web Conferencing Software

Removing SQL Server or MSDE Software

Uninstalling Web Conferencing Software

To Uninstall Web Conferencing Software


Step 1 From the Windows Start menu, choose Settings > Control Panel > Add/Remove Programs.

Step 2 From the Add/Remove Programs window, click Cisco MeetingPlace Web Conferencing.

Step 3 Click Change/Remove.

Step 4 When prompted to completely remove Web Conferencing and all its components, click Yes.

Step 5 From Windows Explorer, manually delete the storage locations for converted audio files (for example, drive:\wma_files).


Removing SQL Server or MSDE Software

If you are no longer using SQL Server or MSDE for any other applications, you can uninstall it manually.

Restrictions

Uninstalling SQL Server or MSDE does not remove the MPWEB SQL database files. To completely remove all database files associated with Cisco Unified MeetingPlace Web Conferencing, you must manually locate and delete the files.

To Remove SQL Server or MSDE Software


Step 1 From the Windows Start menu, choose Settings > Control Panel > Administrative Tools > Services.

Step 2 Stop the Microsoft SQL Server service.

Step 3 From the Start menu, choose Settings > Control Panel > Add/Remove Programs, then choose the applicable software: Microsoft SQL Server or Microsoft SQL Server Desktop Engine.

Step 4 Click Remove.

Step 5 Reboot the server.