With Cisco Unified MeetingPlace Release 6.x, Cisco Unified MeetingPlace Web Conferencing and all Cisco Unified MeetingPlace integration components must be installed on a Cisco MCS server running a Microsoft Windows Server 2003-based Cisco MCS operating system. Changing the operating system from the Windows 2000 Server-based version to the Windows 2003-based version requires a new installation. Cisco does not support upgrading the operating system from the Windows 2000-based version to the Windows 2003-based version.

To install Cisco Unified MeetingPlace Web Conferencing Release 6.0 MR1, run the 6.0MR1 installation program. If your system has no version of Web Conferencing, the program installs MR1. If your system currently has Release 6.0, the program upgrades to MR1.

To install Cisco Unified MeetingPlace Web Conferencing Release 6.0 MR2, run the 6.0MR2 installation program. If your system has no version of Web Conferencing, the program installs MR2. If your system currently has Release 6.0 or MR1, the program upgrades to MR2.

Caution! The migration process is complex, so it is imperative that you follow the documentation carefully.

Whether you choose to install new MCS servers or you use existing MCS servers, you must back up customer-specific application data if you want to migrate the data to the server after the installation of the Windows 2003-based version of the operating system.

After the migration, attachments and audio recordings from previous meetings that were backed up and restored by using the Cisco Unified MeetingPlace Web Conferencing Backup/Restore Wizard will be available on the migrated Web Conferencing server; however, synchronized audio/web recordings will not be available for playback on the Release 6.0 server. If users need to access these recordings, you must retain the original pre-6.0 Web Conferencing server. Therefore, before doing the migration, you must choose one of the following three approaches for the Web Conferencing migration:

Replace the pre- Release 6.x Web Conferencing server with the Release 6.x version (either by using the same hardware or by replacing the hardware and decommissioning the old hardware during the migration)

Users will be able to access existing attachments and audio recordings on the Release 6.0 server, but will no longer have access to existing synchronized audio/web recordings.

If you are replacing the hardware, we recommend that you use the DNS host name of the original server on the new hardware. Keeping the same name allows you to migrate the configuration settings and customizations seamlessly. Also, in some deployments, users launch a web-sharing session by clicking a URL on a meeting that was previously scheduled. By preserving the DNS host name you ensure that those URLs function as before.

Build a new Release 6.0 Web Conferencing server; run the new server alongside the original server temporarily, and decommission the original server when users no longer need access to existing synchronized audio/web recordings

Users have access to synchronized audio/web recordings until they are purged or until you decommission the original server.

The new server does not use the IP address or host name of the original server.

Caution! The migration process for Cisco Unified MeetingPlace for Outlook, Cisco Unified MeetingPlace for Lotus Notes, Cisco Unified MeetingPlace SMTP E-Mail Gateway, Cisco Unified MeetingPlace H.323/SIP Gateway, and Cisco Unified MeetingPlace Directory Services requires that you restore the software on a machine with same IP address or host name used to back up data. If you choose this approach for a server on which any of these integrations are installed, you will have to do a new installation of the integration(s) on the server.

Do the tasks in the Migration Task List for Cisco Unified MeetingPlace Release 6.0. For this scenario, you do not need to run the Cisco Unified MeetingPlace Web Conferencing Backup/Restore wizard. You will manually migrate any customizations and configuration settings to the new Release 6.0 Web Conferencing server.

During the transition period, both Web Conferencing servers connect to and share the same Audio Server.

Migrate the Web Conferencing files, settings, and host name to a new Release 6.0 server, but keep the original server running with a different hostname so users can access existing synchronized audio/web recordings

Users have access to synchronized audio/web recordings until they are purged from the original server.

Do the tasks in the Migration Task List for Cisco Unified MeetingPlace Release 6.0. For this scenario, after you run the Cisco Unified MeetingPlace Web Conferencing Backup/Restore Wizard, you will change the DNS host name of the original server, and use the original DNS host name when building the new Release 6.0 server.

Both Web Conferencing servers connect to and share the same Audio Server.

Since the existing synchronized web/audio recordings are tracked by the Audio Server, we recommend that you use MeetingTime to change the Days Until Meetings Stats Purged setting on the Audio Server to a sufficiently large number, and also increase the value of the Purge Meetings Held Before (Days) setting on the original Web Conferencing server. This will ensure that the existing recordings are available to users for as long as the original and new servers are running side-by-side.

Use the following task list to do the applicable tasks for your deployment in the correct order.

Migration Task List for Cisco Unified MeetingPlace Release 6.0

Caution! The migration process is complex, so it is imperative that you follow the documentation carefully.

Note: Migrating to Release 6.0 by using Terminal Services is not supported.

Verify that your Cisco MCS server model is supported for use by Release 6.0 components by checking the System Requirements. If your server hardware is no longer supported, you must upgrade to new MCS hardware.

Back up customer-specific application data. If you are migrating to a new server or if you are installing a new operating system on an existing server, you must back up customer-specific data that will be restored after the installation of Windows 2003.

Follow the backup procedures for the following components as applicable to your deployment:

Cisco Unified MeetingPlace Network Backup Gateway-Back up all files in the backup directory. This location can vary based on customer configuration. The following registry setting stores the directory location: HKLM/Software/Latitude/MeetingPlace Backup/MPBackup_Dir

Cisco Unified MeetingPlace H.323/SIP Gateway-Back up the following files from the C:\Latitude\MeetingPlace IP Gateway directory: config-ras.val, config.val, and dialgroups.txt. If it exists, back up rvtele.ini from <WINDOWS>\system32.

Cisco Unified MeetingPlace for Outlook-Back up customized files in C:\Program Files\Cisco Systems\MPWeb\mpoutlook (mpmessage.rtf, mpMsgRsvl.rtf, and mpMsgVideoNot.rtf) and in each language sub-folder. Also, back up customized files in C:\Program Files\Cisco Systems\Shared Components\MeetingPlace Notification Gateway\ (NotifySchedule.tpl, NotifyScheduleVideo.tpl, NotifyReSchedule.tpl, NotifyReScheduleVideo.tpl, NotifyCancel.tpl, NotifyNoShow.tpl, and NotifyRenewRecur.tpl) and each language sub-folder. Note the Windows domain that the server is joined to, and the Windows administrator account and password that was created for the default Microsoft Outlook mailbox on the server.

Cisco Unified MeetingPlace for Lotus Notes-Back up the user.id file (the default location for this file is C:\Program Files\Lotus\Notes\Data) and the notification.tpl file (the default location for this file is C:\Program Files\Cisco Systems\Cisco MeetingPlace for Notes).

Cisco Unified MeetingPlace Gateway SIM-The Gateway SIM is backed up and installed with Cisco Unified MeetingPlace Web Conferencing. From your system tray, right-click the Cisco Unified MeetingPlace (orange door) icon, click Properties, and note the hostname, FQDN or IP address of the Audio Server as it appears in the box in the lower left corner. You will need to enter this information exactly as it appears here when reinstalling Web Conferencing.

Note: Cisco Unified MeetingPlace for Jabber is not installed on an MCS server, and there is no customer-specific data to back up.

Back up customer specific data on the Cisco Unified MeetingPlace Web Conferencing server(s), if applicable, depending on the decision you made about retaining user access to existing synchronized audio/web recordings.

Follow the backup procedures for the following situations as applicable to your deployment:

Manually back up Web Conferencing in case you need to revert to the previous release (5.3 or 5.4). This task is optional, but strongly recommended. (If you have a cluster of Web Conferencing servers, do this task on each server.) See Manually Backing Up Web Conferencing.

If your deployment includes a shared external database (in other words, the database is not installed on a Web Conferencing server), and you did not already back up the database as part of the manual backup in Task 5.1, back up the external database. See Backing Up a Shared External Database.

If your deployment includes shared or external storage (in other words, multiple Web Conferencing servers store MeetingNotes in a single location, or MeetingNotes are stored in an external storage location), back up the storage location. See Backing Up Shared or External Storage.

If you are replacing the original Web Conferencing server with new server hardware and not retaining user access to synchronized audio/web recordings: Decommission the original Web Conferencing server.

If you are migrating the Web Conferencing files, settings, and host name to a new Release 6.0 server and retaining user access to synchronized audio/web recordings: Change the DNS host name of the original server to something other than its original name.

Install Web Conferencing Release 6.0. (If you have a cluster of Web Conferencing servers, do this task on each server.) Follow the procedures described in Installing Web Conferencing.

Note: If you use the restore executable to restore Web Conferencing data, enter the exact Audio Server value that you noted in Task 4.9 for the Hostname of MeetingPlace Server parameter when installing Web Conferencing Release 6.0.

If the server was restored from a backup done on a member of a Web Conferencing cluster, configure the shared storage authentication information. (If you have a cluster of Web Conferencing servers, do this task on each server.) See Configuring Shared Storage Authentication Settings.

If a standalone server is restored from a backup that previously had shared storage configured, or if you would like to configure shared storage on a server that did not previously have it configured, see Configuring Shared Storage.

If you are running the new Release 6.0 Web Conferencing server alongside the original server temporarily:

Manually migrate the customizations and configuration settings on the original Web Conferencing server to the new server.

Inform your users that the original server will be decommissioned after a certain date and that they should schedule new meetings on the new server moving forward. They will still be able to access previously scheduled meetings and recordings on the original server.

If you are migrating the Web Conferencing files, settings, and host name to a new Release 6.0 server and retaining user access to synchronized audio/web recordings: In order for users to access existing synchronized audio/web recordings, we recommend that you create a custom URL on the Welcome page of the new Release 6.0 server, directing users to the original server for these recordings. (For example, "Click here to access your previously recorded meetings.") See About Web Conferencing Templates.

Updating the Number of Full Web Conferencing Ports Configured on the Audio Server

In previous releases, the Full Web Conferencing Ports value on the Audio Server was set to either 0 (no Web Conferencing licensed) or 1 (Web Conferencing licensed). When you upgrade the Audio Server to Release 6.0, you must manually update the number of Full Web Conferencing Ports to match the number of licensed Web Conferencing ports for your deployment.

Procedure

Open MeetingTime.

Click Administration > Configure.

In the Views box, under System Configuration, click Server Configuration.

Click Query.

Check the value for Full Web Conferencing Ports. If it does not match the number of licensed ports for your deployment, click on the value, change it, and click OK. Then click Save Changes.

Manually Backing Up Web Conferencing

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):

Procedure

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.

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.

Backing Up Cisco Unified MeetingPlace Registry Information

Before You Begin

Procedure

Open Registry Editor.

Navigate to and select HKEY_LOCAL_MACHINE\SOFTWARE\Latitude.

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

Save the file.

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

Save all backup files to a safe location where you will be able to access them after installing the Windows 2003 operating system on the MCS server(s).

Backing Up Web Conferencing by Using the Cisco Unified MeetingPlace Web Conferencing Backup or Restore Wizard

The Cisco Unified MeetingPlace Web Conferencing Backup or Restore Wizard generates an executable that migrates configuration settings and meeting information from Web Conferencing Release 5.3 or 5.4 to Release 6.0 on the Windows 2003 operating system. If you plan to migrate server configuration and settings to Release 6.0, you must do this procedure even if you already did a manual backup. If you have a load-balancing cluster of Web Conferencing servers, do this procedure on each server in the cluster.

Note: The restore file generated by the Cisco Unified MeetingPlace Web Conferencing Backup or Restore Wizard cannot be used to revert to Release 5.3 or 5.4 if the migration fails. You will need to have a manual backup created by using the Manually Backing Up Web Conferencing if you need to revert to the original release.

The Backup or Restore Wizard creates a restore file to be used after upgrading the MCS operating system.

When the backup completes, note the location of the restore file, and click OK.

Click Close.

Copy the restore file from the location you noted in Step 4 to an external location where you can access it after the new version of the operating system is installed.

Note: If you are planning to keep the original Web Conferencing server running alongside the new Release 6.0 server, you do not need to copy the restore file to another location; when restoring settings to the new server, you can access the restore file by browsing to the URL of the location you noted in Step 4.

Backing Up a Shared External Database

The procedure in this section uses Enterprise Manager to back up an MPWEB database that is shared between multiple Web Conferencing servers in a cluster. Do this procedure if you need to migrate the database to a new machine (for example, because you plan to run a cluster of Release 6.0 servers with a new database server alongside a Release 5.4 machine that accesses the original database server) and you have not backed up the database already.

Note: For the purpose of migrating to Web Conferencing Release 6.0, you do not need to back up the MPWEB-Slave databases.

Procedure

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.

Save the database backup file to a safe location where you will be able to access it after installing the Windows 2003 operating system on the database server.

Backing Up Shared or External Storage

Each Web Conferencing server cluster requires a common storage location. The common storage location can be on one of the servers in your cluster or on another (external) machine.

Do this procedure if you are using an shared or external storage and you need to migrate the storage to a new machine or location (for example, because you plan to run a cluster of Release 6.0 servers with shared storage alongside a Release 5.4 machine that accesses the original shared storage location). If the storage directory is located on one of the Web Conferencing servers in the default <drive>:\Program Files\Cisco Systems\MPWEB\Meetings directory, it is automatically backed up and restored when you run the Cisco Unified MeetingPlace Backup/Restore Wizard; in this case, you do not need to manually back up the storage location.

Procedure

Locate the storage folder (the folder path may include MPWeb\Meetings). If you do not know the location of the folder, do the following substeps:

Click Start. The wizard extracts and restores files for use in the Web Conferencing upgrade.

When the restore completes, click OK, then click Close.

Restoring a Shared External Database

Do the tasks in this section if you backed up a shared external database to migrate the external database server to a new machine.

Install SQL Server 2000 and any required SQL Server service packs on the database server. For service pack requirements, see the System Requirements.

Restore the MPWEB database from the backup file by performing the following procedure.

Note: When restoring the database for a Web Conferencing Release 6.0 server, you do not need to restore the MPWEB-Slave database(s).

Procedure

Log on to the database server.

Note: If you cannot log on to the database server, log on to any Windows-based workstation or server on the network that has a valid installation of SQL Server Client tools including the osql command, so you can connect remotely to the SQL Server.

If the SQL Server runs locally, you can omit the option -S servername.

If you are not allowed to connect to this SQL Server as SA, connect by using an account with enough privileges to back up a database.

Check if a database called MPWEB exists on this server:

Enter select name from sysdatabases where name like 'MPWEB%', then enter go.

If a MPWEB database exists, verify that no Cisco Unified MeetingPlace Web Conferencing server is currently using this database.

(Optional) If one or multiple Cisco Unified MeetingPlace web servers are using the database, do the following:

Log on as an administrator on each server.

Stop the Cisco Unified MeetingPlace Web Conferencing service.

Wait for all the Cisco Unified MeetingPlace Web Conferencing services, the IIS Admin service, and the World Wide Web publishing service to stop.

To drop the database, enter drop database MPWEB, then enter go.

Before you import your MPWEB database to SQL Server, find out which database physical files are associated with this MPWEB database:

Enter restore filelistonly from disk = ‘fullyqualifiedpath’, where fullyqualifiedpath is the location to which you copied the file in Step 2, then enter go.

Verify the installation folder of the SQL Server where you want to restore this database and check the physical location of the SQL Server master database:

Enter sp_helpfile master, then enter go.

Note: Unless you have a specific reason to restore your MPWEB database to another disk location, such as for performance and tuning or data recovery, we recommend that you restore the MPWEB database to the default Data folder of this SQL Server installation.

Restore your database and relocate the database physical files to the correct location:

Configuring Shared Storage Authentication Settings

Use the procedure in this section if the server was restored from a backup done on a member of a Web Conferencing cluster. In this case, shared storage is already configured and enabled, but the server is not configured with the necessary account information to access the shared storage.

Do this procedure on each server in the cluster.

Procedure

On the Web Conferencing server, open a web browser and browse to http://localhost:8002. When you access this URL on the server, you are automatically signed in to Cisco Unified MeetingPlace Web Conferencing as a technician.

Click Admin, then Shared Storage.

In the appropriate fields, enter a domain, user name, and password for a Windows account that will be used to access the shared storage location. If the account is a local account, enter the machine name in the Domain field.

Note: All Cisco Unified MeetingPlace Web Conferencing services will be configured to "Log On As" the account you choose in this sub-step.

Re-enter the password in the Confirm Password field.

Click Save Changes.

To put the changes into effect, click Reboot Server, then click OK to confirm the reboot. The server shuts down and restarts.

Configuring Shared Storage

Use the procedure in this section to configure shared storage if it was not configured before backing up and restoring the server, or if it was configured for a standalone (not clustered) Web Conferencing server.

Procedure

Open your web browser to access the Web Conferencing home page.

Use your System Manager-level user ID and password to sign in.

Click Admin, then click Shared Storage.

For Enabled, click Yes.

For Shared Storage Path, enter the path of the shared storage location.

For Content Cache Size, enter a value between 0 and 100 for the percentage of total disk space to use to cache content on the local server.

In the appropriate fields, enter a domain, user name, and password for a Windows account that will be used to access the shared storage location. If the account is a local account, enter the machine name in the Domain field.

Note: All Cisco Unified MeetingPlace Web Conferencing services will be configured to "Log On As" the account you choose in this sub-step.

Re-enter the password in the Confirm Password field.

Click Save Changes.

To put the changes into effect, click Reboot Server, then click OK to confirm the reboot. The server shuts down and restarts.

Installing and Restoring Cisco Unified MeetingPlace for Outlook

Use the following procedure to install Cisco Unified MeetingPlace for Outlook Release 6.0 and restore files from a previous release.

Note: To restore files and settings from a previous installation, the Cisco Unified MeetingPlace for Outlook server must be configured with the same IP address as the original server.

Procedure

Verify that the Cisco Unified MeetingPlace for Outlook server is joined to the same Windows domain that you noted in Task 4.5 of the Migration Task List.

Give local administrative rights to the Windows administrator account on the Cisco Unified MeetingPlace for Outlook server that you noted in Task 4.5 of the Migration Task List.

Sign on to the server by using the Windows administrator account that you noted in Task 4.5of the Migration Task List.

Note: When installing and restoring Cisco Unified MeetingPlace for Outlook, you must be signed on to the server with the same Windows account that was originally used for installing the previous release of Cisco Unified MeetingPlace for Outlook, and Outlook must be configured to open the same Exchange mailbox that was configured on the server for the previous release.

Restore the files that you backed up in Task 4.5 of the Migration Task List.

Installing and Restoring Cisco Unified MeetingPlace for Lotus Notes

Procedure

Verify that you are currently using supported releases of the Domino server and Lotus Notes clients. For system requirements, see the System Requirements.

Install a supported version of the Lotus Notes client on the Cisco Unified MeetingPlace for Lotus Notes server.

Copy the user.id file that you backed up, in Task 4.6 of the Migration Task List, to the Lotus Notes client Data directory on the Cisco Unified MeetingPlace for Lotus Notes server (the default is <drive>:\Program Files\Lotus\Notes\Data).

Run the Lotus Notes client on the Cisco Unified MeetingPlace for Lotus Notes server and browse to the location of the user.id file that you copied to the server in Step 3. The client creates the notes.ini file.

Copy the notification.tpl file that you backed up to the Cisco Unified MeetingPlace for Lotus Notes directory in Task 4.6 of the Migration Task List.

Stop the Domino server and delete the following files from the Domino server Data folder:

mpsa.ntf

mpsa.nsf

mpnotes 5.4 mail template

Run the Cisco Unified MeetingPlace for Lotus Notes Release 6.0 executable (Setup.exe) and complete the InstallShield wizard to upgrade. Maintain all defaults. The installer will automatically upgrade the current Cisco Unified MeetingPlace for Lotus Notes components.

Task List for Migrating an SMA-1S Web Conferencing Deployment

SMA-1S is no longer supported in Release 6.0. To migrate to a Release 6.0 SMA-2S configuration, you must have at least two Cisco MCS servers. In the following task list, you use the original SMA-1S server (or a replacement machine) as the new internal Web Conferencing server, and add an additional Cisco MCS server as the new external Web Conferencing server.

Caution! The migration process is complex, so it is imperative that you follow the documentation carefully.

Note: Migrating to Release 6.0 by using Terminal Services is not supported.

Manually back up Web Conferencing on each server in case you need to revert to the previous release (5.3 or 5.4). This task is optional, but strongly recommended. See Manually Backing Up Web Conferencing.