Installation and Upgrade Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.3
Upgrading to Cisco Unified MeetingPlace Web Conferencing Release 5.3

Table Of Contents

Upgrading to Cisco Unified MeetingPlace Web Conferencing Release 5.3

Restrictions for Upgrading to Cisco Unified MeetingPlace Web Conferencing Release 5.3

About Upgrading to Cisco Unified MeetingPlace Web Conferencing Release 5.3(235) and Later Releases

User Authentication Methods in Release 5.3(235) and Later

Load Balancing in Release 5.3(333) and Later

How to Back Up Before Upgrading to Cisco Unified MeetingPlace Web Conferencing Release 5.3

Backing Up the MPWEB Database and MPWEB-Slave Database

Backing Up Critical Cisco Unified MeetingPlace Web Conferencing Application Files

Backing Up Cisco Unified MeetingPlace Registry Information

How to Upgrade to Cisco Unified MeetingPlace Web Conferencing Release 5.3

Preparing to Upgrade Cisco Unified MeetingPlace Web Conferencing

Upgrading a Standalone Web Server

Upgrading a Standalone Web Server to a Shared Database Configuration

Upgrading Web Servers Sharing the Same Database

How to Uninstall Cisco Unified MeetingPlace Web Conferencing, SQL Server, or MSDE

Uninstalling Cisco Unified MeetingPlace Web Conferencing

Removing SQL Server or MSDE


Upgrading to Cisco Unified MeetingPlace Web Conferencing Release 5.3


Topics in this section include:

Restrictions for Upgrading to Cisco Unified MeetingPlace Web Conferencing Release 5.3

About Upgrading to Cisco Unified MeetingPlace Web Conferencing Release 5.3(235) and Later Releases

How to Back Up Before Upgrading to Cisco Unified MeetingPlace Web Conferencing Release 5.3

How to Upgrade to Cisco Unified MeetingPlace Web Conferencing Release 5.3

How to Uninstall Cisco Unified MeetingPlace Web Conferencing, SQL Server, or MSDE

Restrictions for Upgrading to Cisco Unified MeetingPlace Web Conferencing Release 5.3

We do not support upgrading to Release 5.3 by using Terminal Services.

You can upgrade to Release 5.3 only from Release 4.2.7.x or 4.3.0.x.

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.

We support upgrading to Release 5.3 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.3 as a new installation on a supported Cisco MCS.

If you are upgrading Cisco Unified MeetingPlace 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.3.x.

If you have any customizations that you made in Release 4.2.7.x or 4.3.0.x, they will be lost when you upgrade to Release 5.3. You will have to re-implement your customizations through the Cisco Unified MeetingPlace Web Conferencing Administrative pages as part of the overall system configuration.

One of the many improvements in the Release 5.3 feature set is the ability to customize the user interface, such as hide/show fields or display custom strings, through web-based administrative pages. Unlike earlier releases, these customizations are stored in the SQL database as part of the Cisco Unified MeetingPlace Web Conferencing configuration. Therefore, customizations are maintained between software release upgrades.

With the introduction of the self-customization capability in Release 5.3, Cisco Systems no longer honors 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, modifying Windows OS security through IPSec policies and NTFS ACL, and so on.

About Upgrading to Cisco Unified MeetingPlace Web Conferencing Release 5.3(235) and Later Releases

This section provides information that you may need to know before upgrading to Release 5.3(235) and later releases.

Topics in this section include:

User Authentication Methods in Release 5.3(235) and Later

Load Balancing in Release 5.3(333) and Later

User Authentication Methods in Release 5.3(235) and Later

Before Release 5.3(235), Cisco Unified MeetingPlace Web Conferencing supported three authentication methods:

MeetingPlace Authentication

HTTP Basic Authentication

Windows Integrated Authentication

In Release 5.3(235) and later releases, Cisco Unified MeetingPlace Web Conferencing now supports additional authentication methods and has a redesigned configuration interface. Consequently, when you upgrade an earlier release of Cisco Unified MeetingPlace Web Conferencing to Release 5.3(235) and later, you must reconfigure your web server to use the desired authentication method.

For instructions, see Chapter 5, "Configuring User Authentication in Cisco Unified MeetingPlace Web Conferencing Release 5.3(235) and Later Releases" in the Configuration Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.3.

Load Balancing in Release 5.3(333) and Later

If you have Cisco Unified MeetingPlace load balancing configured and plan to upgrade to Cisco Unified MeetingPlace Web Conferencing Release 5.3(333) and later, be aware of the following update:

When configuring services for your load balancing deployment, Release 5.3(333) and later requires that you configure the Cisco MeetingPlace Web Conferencing service to log on as Administrator. This is in addition to the five other services required for Release 5.3(235). If you do not configure the Cisco MeetingPlace Web Conferencing service to log on as Administrator, web conferencing will not start.

For more information, see Step 4 in the following sections:

Configuring Services for the First Internal Web Server, page 4-12

Configuring Services for the First External Web Server, page 4-16

How to Back Up Before Upgrading to Cisco Unified MeetingPlace Web Conferencing Release 5.3


Note You must perform this backup procedure before every Cisco Unified MeetingPlace Web Conferencing upgrade, whether it is a full or patch upgrade.


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

This backup procedure applies to the following:

Upgrading Cisco Unified MeetingPlace Web Conferencing from one major release to another, such as upgrading from Release 4.3 to Release 5.3.

Applying a patch to a major release, such as upgrading from Release 5.3(104.0) to Release 5.3(104.3).

To back up before you upgrade, perform the following tasks in the order shown:

Backing Up the MPWEB Database and MPWEB-Slave Database

Backing Up Critical Cisco Unified MeetingPlace Web Conferencing Application Files

Backing Up Cisco Unified MeetingPlace Registry Information

Backing Up the MPWEB Database and MPWEB-Slave Database

This procedure uses Enterprise Manager to back up the database. To use osql commands, see Appendix A in the Configuration Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.3.

Procedure


Step 1 Open Enterprise Manager.

Step 2 Expand the database folder.

Step 3 Right-click MPWEB and 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, to initiate the backup operation, click OK.

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

Step 5 To Backup the MPWEB-Slave-#### database, repeat Step 1 through Step 4.


Note If you see multiple MPWEB-Slave databases, you have a load-balancing cluster, where multiple Cisco Unified MeetingPlace 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 Proceed to the "Backing Up Critical Cisco Unified MeetingPlace Web Conferencing Application Files" section.


Backing Up Critical Cisco Unified MeetingPlace Web Conferencing Application Files

Before You Begin

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

Procedure


Step 1 Open Explorer.

Step 2 Navigate to where the Cisco Unified MeetingPlace Web Conferencing application is installed.

Step 3 Open the \MPWeb folder.

Step 4 Backup all folders except for the \Diagnostics and \Meetings folders.

Step 5 Proceed to the "Backing Up Cisco Unified MeetingPlace Registry Information" section.


Backing Up Cisco Unified MeetingPlace Registry Information

Before You Begin

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

Procedure


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 to 5.3.104.0 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.3.104.0.


Step 5 Save all backup files to a safe location.


How to Upgrade to Cisco Unified MeetingPlace Web Conferencing Release 5.3

This section contains the following procedures:

Preparing to Upgrade Cisco Unified MeetingPlace Web Conferencing

Upgrading a Standalone Web Server

Upgrading a Standalone Web Server to a Shared Database Configuration

Upgrading Web Servers Sharing the Same Database

Preparing to Upgrade Cisco Unified MeetingPlace Web Conferencing

Before You Begin

Read the "Restrictions for Upgrading to Cisco Unified MeetingPlace Web Conferencing Release 5.3" section.

If you are upgrading to Release 5.3(235) or a later release, read the "About Upgrading to Cisco Unified MeetingPlace Web Conferencing Release 5.3(235) and Later Releases" section.

Procedure


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

Review the "Upgrading to Release 5.3" section in the Release Notes for your release of Cisco Unified MeetingPlace Web Conferencing.

Step 2 Back up your system.

Complete the "How to Back Up Before Upgrading to Cisco Unified MeetingPlace Web Conferencing Release 5.3" section.


Caution Cisco Unified MeetingPlace Web Conferencing overwrites all customizations when upgrading from Release 4.2.7.x or 4.3.0.x. Ensure that you back up your customizations as indicated in the upgrade procedures if you want them available for future retrieval.

Step 3 Make sure that the Cisco Unified MeetingPlace 8100 series server that the web server is connecting to has Cisco Unified MeetingPlace Audio Server Release 5.3 installed by doing one of the following:

Upgrade your Cisco Unified MeetingPlace 8100 series server to Cisco Unified MeetingPlace Audio Server Release 5.3 by complete the instructions in the Installation and Upgrade Guide for Cisco Unified MeetingPlace Audio Server Release 5.3.

Attach your web server to a new Cisco Unified MeetingPlace 8100 series server already loaded with Cisco Unified MeetingPlace Audio Server Release 5.3 by completing the instructions in the "Changing the Cisco Unified MeetingPlace Audio Server Connection" section in Chapter 2 of the Configuration Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.3.

Step 4 (Optional) Upgrade your Cisco MCS server or non-Cisco MCS server to the latest OS requirements by doing one of the following.

If you are using a Cisco MCS server, we recommend that you upgrade your server to the latest Cisco MCS Server OS Release or Patch.

If you are using a non-Cisco MCS server, we recommend that you upgrade to the latest Windows 2000 Server Service Pack and install any additional Critical Security Hotfixes, as reported by the Windows Update utility.

Step 5 Proceed to the next task in your upgrade procedure as follows:

For a standalone server configuration, see the "Upgrading a Standalone Web Server" section.

For a standalone server to shared database configuration, see the "Upgrading a Standalone Web Server to a Shared Database Configuration" section.

For a shared database configuration, see the "Upgrading Web Servers Sharing the Same Database" section


Upgrading a Standalone Web Server


Caution Cisco Unified MeetingPlace Web Conferencing overwrites all customizations when upgrading from Release 4.2.7.x or 4.3.0.x. Ensure that you back up your customizations as indicated in the upgrade procedures if you want them available for future retrieval.

Before You Begin

Obtain Chapter 2, "Installing Cisco Unified MeetingPlace Web Conferencing Release 5.3" to assist you with your upgrade.

Complete the "Preparing to Upgrade Cisco Unified MeetingPlace Web Conferencing" section.

Procedure


Step 1 Stop all Cisco Unified MeetingPlace 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 Cisco Unified MeetingPlace 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 folders from drive:\Latitude\mpweb to drive:\Latitude\mpweb_backup.

Step 3 Run the Cisco Unified MeetingPlace Web Conferencing Setup program and follow the installation process described in Chapter 2, "Installing Cisco Unified MeetingPlace Web Conferencing Release 5.3".


Upgrading a Standalone Web Server to a Shared Database Configuration

To upgrade a standalone web server to a shared database configuration, you must first uninstall the web-conferencing software and then reinstall it. For information about uninstalling Cisco Unified MeetingPlace Web Conferencing, see the "Uninstalling Cisco Unified MeetingPlace Web Conferencing" section.

Before You Begin

See Chapter 2, "Installing Cisco Unified MeetingPlace Web Conferencing Release 5.3" to assist you with configuration.

Complete the "Preparing to Upgrade Cisco Unified MeetingPlace Web Conferencing" section.

Restrictions

You cannot modify a standalone web server with a local SQL Server database to access a remote SQL Server database.

Procedure


Step 1 Stop all Cisco Unified MeetingPlace 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 Cisco Unified MeetingPlace 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 folders from drive:\Latitude\mpweb to drive:\Latitude\mpweb_backup.

Step 3 Run the setup program and choose the Remove option.

Step 4 Reboot the computer.

Step 5 Modify the AppName value.

a. Go to drive:\Program Files\InstallShield Installation Information\.

Several folders are revealed.

b. Open a folder.

c. From the folder, open the setup.ini file in Notepad and locate the AppName value.

d. Do one of the following:

If AppName equals anything other than Cisco MeetingPlace Web Conferencing, close Notepad and move onto the next folder. Do not do anything to this folder.

If AppName equals Cisco MeetingPlace Web Conferencing, close Notepad, delete this entire folder, and proceed to Step 6.

e. Repeat Step 5b. to Step 5d. for each folder in the InstallShield Installation Information directory.

Step 6 If you have Microsoft SQL Desktop Engine (MSDE) installed, remove it.

a. Open your Windows control panel and choose Add/Remove Programs.

b. Click Microsoft SQL Desktop Engine (MSDE) and click Change/Remove.

Step 7 Run the Cisco Unified MeetingPlace Web Conferencing Setup program and follow the installation process as described in Chapter 2, "Installing Cisco Unified MeetingPlace Web Conferencing Release 5.3".

For Database Location, choose Existing Remote Server.

Update both the username and password to correspond to those of the existing remote SQL Server whose database you wish to share.

For Database Server, enter the hostname or static IP address of the existing remote SQL Server database you wish to share.


Upgrading Web Servers Sharing the Same Database


Note 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.


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.

Before You Begin

See Chapter 2, "Installing Cisco Unified MeetingPlace Web Conferencing Release 5.3" to assist you with your configuration.

Read the "Load Balancing in Release 5.3(333) and Later" section.

Complete the "Preparing to Upgrade Cisco Unified MeetingPlace Web Conferencing" 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, for example to Release 5.3.x, where x is the same amongst all web servers.

Procedure


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

For example, if you have three web servers in this cluster, leave the first web server on, but shut down the second and third servers.

Step 2 To upgrade the first web server, back up the files.

For instructions, see Step 2 in the "Upgrading a Standalone Web Server" section.

Step 3 Run the Cisco Unified MeetingPlace Web Conferencing Setup program to upgrade.

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

Step 4 Reboot the server and verify your Cisco Unified MeetingPlace 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 5 Verify Cisco Unified MeetingPlace Web Conferencing functionality.

Step 6 Leave the web server running.

Step 7 Turn on the second web server and upgrade it as outlined in Step 2 through Step 6.

Step 8 Continue with each web server in this cluster until all servers are upgraded to the exact same release.


How to Uninstall Cisco Unified MeetingPlace Web Conferencing, SQL Server, or MSDE

This section includes the following procedures:

Uninstalling Cisco Unified MeetingPlace Web Conferencing

Removing SQL Server or MSDE

Uninstalling Cisco Unified MeetingPlace Web Conferencing

Procedure


Step 1 From your 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 Cisco MeetingPlace Web Conferencing and all its components, click Yes.

This action deletes the entire Cisco MeetingPlace Web Conferencing directory, DSN, and so on.

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


Removing SQL Server or MSDE

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.

Procedure


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

Step 2 Stop the Microsoft SQL Server Service.

Step 3 From Start > Settings > Control Panel > Add/Remove Programs, choose either Microsoft SQL Server or Microsoft SQL Server Desktop Engine.

Step 4 Click Remove.

Step 5 Reboot your server.