Installation, Upgrade, and Migration Guide for Cisco Unified MeetingPlace Release 8.6
Migrating to Cisco Unifed MeetingPlace Release 8.6 from Release 6.1 MR1
Downloads: This chapterpdf (PDF - 432.0KB) The complete bookPDF (PDF - 5.68MB) | Feedback

Migrating to an Audio-Only Deployment from Release 6.1

Table Of Contents

Migrating to an Audio-Only Deployment from Release 6.1

About Migration

Migration Process

Migration Path Matrix

About Migration Paths

Web Servers

Audio and Application Servers

Video Systems

Prerequisites for the Migration

Migrating to a Virtual Machine

Preserved Data

Lost Data

Retaining Recordings

Setting Up a Trial System

How to Prepare for a Migration

Migration Considerations

Migration Best Practices

General Migration Errors and Troubleshooting

Migrating Data from a Cisco Unified MeetingPlace Release 6.1 MR1 System to a Cisco Unified MeetingPlace Release 8.6 System

Migrating Data from a Cisco Unified MeetingPlace Release 6.1 MR1 Audio Server to a Cisco Unified MeetingPlace Release 8.6 Application Server

Ensuring There is Sufficient Disk Space

Exporting Data from the Cisco Unified MeetingPlace Release 6.1 MR1 Audio Server

Importing the Data to the Cisco Unified MeetingPlace Release 8.6 Application Server

Troubleshooting the Application Server Data Migration

Migrating Cisco Unified MeetingPlace Release 6.1 MR1 Directory Services to Cisco Unified MeetingPlace Release 8.6 Directory Service

About Migrating Non-Local Users from Cisco Unified MeetingPlace Release 6.1 MR1 to Cisco Unified MeetingPlace Release 8.6

Restoring the Local and Non-Local Status for Users

Troubleshooting the Directory Service Migration

Migrating Data from a Cisco Unified MeetingPlace Release 6.1 MR1 Web Conferencing Server to a Cisco Unified MeetingPlace Release 8.6 Web Server

Exporting the ICalendarMeetings table from the Cisco Unified MeetingPlace 6.1 MR1 Web Conferencing Server Database to a Text File

Backing Up the Web Conferencing Data Before a Migration

Installing the Cisco Unified MeetingPlace 8.6 Web Server

Synchronizing Meeting Data Between the Cisco Unified MeetingPlace Web Conferencing Server and the Cisco Unified MeetingPlace Application Server

Migrating Your Microsoft Outlook Plug-In

Migrating the Microsoft Outlook Users Who Schedule Meetings From Outlook

Migrating the Microsoft Outlook Users Who Schedule Meetings from Cisco Unified MeetingPlace

Testing the Outlook Migration

Post-Migration Steps

Testing that the Migrated System Works Correctly


Migrating to an Audio-Only Deployment from Release 6.1


Release 8.6
Revised: 11/7/13

About Migration

How to Prepare for a Migration

Migrating Data from a Cisco Unified MeetingPlace Release 6.1 MR1 System to a Cisco Unified MeetingPlace Release 8.6 System

Post-Migration Steps

Testing that the Migrated System Works Correctly

About Migration

Because of the different system architectures between Cisco Unified MeetingPlace Release 8.6 and previous releases of Cisco Unified MeetingPlace, you cannot upgrade to this release of Cisco Unified MeetingPlace from a previous Release 6.1 system. However, you can migrate to this release from a previous release. Migration preserves some of the existing customer and system data while installing a new system.


Note This process supports a migration from a Release 6.1 system to a Release 8.6 system, in an audio-only deployment. If you want to migrate to a deployment with Cisco WebEx scheduling, then see the Migrating Using the MPtoWebEx CSV Converter module. Migrations to Release 8.6 with Cisco Unified MeetingPlace scheduling are not supported.



Note This migration module covers the migration or installation of the following Release 8.6 components (Application Server, Web Server and Microsoft Outlook plug-in). If your system includes any Cisco Unified MeetingPlace integration, then refer to the specific integration module for your release. See the Configuration Guide for Cisco Unified MeetingPlace Release 8.6.



Note If you have Adobe Connect (Adobe Breeze) meetings, then only audio and video recordings are migrated. Web recordings and attachments are not migrated. We recommend you keep your legacy Cisco Unified MeetingPlace system intact (to access legacy Web recordings and attachments), and install a new Release 8.6 system.


Migration Process

Migration Path Matrix

About Migration Paths

Prerequisites for the Migration

Migrating to a Virtual Machine

Preserved Data

Lost Data

Retaining Recordings

Setting Up a Trial System

Migration Process

The following table presents an overview of the major steps required to migrate a Cisco Unified MeetingPlace Release 6.1 system to Cisco Unified MeetingPlace Release 8.6. If you are using an earlier version of Cisco Unified MeetingPlace Release 6.0 and want to migrate to Release 8.6, then you must first upgrade to Cisco Unified MeetingPlace Release 6.1 MR1.


Note Before you begin the migration process, make sure you have the Cisco Unified MeetingPlace Release 8.6 DVD available for the installation.


The following table presents an overview of the major steps required to migrate a Cisco Unified MeetingPlace Release 6.1 system to Cisco Unified MeetingPlace Release 8.6.


Note This table is written in the order in which you should proceed with your migration. We recommend you familiarize yourself with the overall process, as written in the table, before actually proceeding with the migration. You may also want to print a copy of this migration procedure, as a reference.


Step #
Step Description
Related Topics

Step 1 

If your system is earlier than Cisco Unified MeetingPlace 6.1 MR1, then first upgrade your system to this version.

Migration Path Matrix.

Step 2 

Prepare for the migration.

Continue with About Migration Paths through Setting Up a Trial System. Be sure to get the appropriate licenses for your Release 8.6 system. Cisco Unified MeetingPlace 6.1 MR1 licenses do not work with a 8.6 system.

Step 3 

Make sure your system is at Release 6.1 MR1.

For information about upgrading from Cisco Unified MeetingPlace Release 6.1, see http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace_Release_6.1_--_Installing_and_Upgrading_the_Audio_Server_Software.

Step 4 

Read through and complete the necessary migration best practices.

How to Prepare for a Migration.

Note To save time, you can perform these best practices at the same time as the next step (exporting data from the Audio Server).

Step 5 

Migrate existing data from your existing Cisco Unified MeetingPlace Audio Server.

Migrating Data from a Cisco Unified MeetingPlace Release 6.1 MR1 Audio Server to a Cisco Unified MeetingPlace Release 8.6 Application Server.

Note You cannot use a Cisco Unified MeetingPlace Release 6.1 Audio Server with a Release 8.6 system.

Step 6 

Install the Cisco Unified MeetingPlace Release 8.6 Application Server on a new machine.

Installing the Application Server Software module.

Note The migration goes directly to Release 8.6.

Step 7 

Import the existing data from the Release 6.1 MR1 Audio Server to the 8.6 Application Server.

Importing the Data to the Cisco Unified MeetingPlace Release 8.6 Application Server.

Step 8 

Fix any Application Server migration errors.

Troubleshooting the Application Server Data Migration.

Step 9 

Migrate the directory service.

Migrating Cisco Unified MeetingPlace Release 6.1 MR1 Directory Services to Cisco Unified MeetingPlace Release 8.6 Directory Service.

Step 10 

If your Cisco Unified MeetingPlace system includes a Microsoft Outlook plug-in integration and users schedule meetings through Cisco Unified MeetingPlace (back-end integration), then export the ICalendarMeetings table from the Web Conferencing Server Database to a text file.

Exporting the ICalendarMeetings table from the Cisco Unified MeetingPlace 6.1 MR1 Web Conferencing Server Database to a Text File.

Step 11 

Back up the existing Web Conferencing Server database.

Backing Up the Web Conferencing Data Before a Migration.

Step 12 

Install the 8.6 Web Server.

Complete one of the following:

Using the same hardware: Using the Same Hardware for Your Cisco Unified MeetingPlace Release 8.6 Web Server.

Using new hardware

Using New Hardware for Your Cisco Unified MeetingPlace Release 8.6 Web Conferencing Server.

Installing the Cisco Unified MeetingPlace Web Server Software module.

Step 13 

Synchronize data between the 8.6 Application Server and the 8.6 Web Server.

Synchronizing Meeting Data Between the Cisco Unified MeetingPlace Web Conferencing Server and the Cisco Unified MeetingPlace Application Server.

Step 14 

If applicable, migrate your Microsoft Outlook plug-in.

Migrating Your Microsoft Outlook Plug-In.

Depending on your Outlook integration, complete one of the following:

Migrating the Microsoft Outlook Users Who Schedule Meetings From Outlook.

Migrating the Microsoft Outlook Users Who Schedule Meetings from Cisco Unified MeetingPlace.

Step 15 

Complete any post-migration steps.

Post-Migration Steps.

Step 16 

Test your migration to ensure it was successful.

Depending on your company's requirements, test the migration by attending meetings, running reports, testing failover (if applicable), and so on. See General Migration Errors and Troubleshooting.


Caution Be sure to read and complete the post-migration procedures in Testing that the Migrated System Works Correctly, before using your system.

Migration Path Matrix

This is Step 1 of the Migration Process.

The earliest release your system can be running to migrate to Cisco Unified MeetingPlace Release 8.6 is Release 6.1 MR1.


Note If you have various Cisco Unified MeetingPlace system components at different versions, then bring all components to the same Cisco Unified MeetingPlace version, before starting the migration.


Table 1 Cisco Unified MeetingPlace Release Matrix 

MIgrating From
Migrating To 8.6
Then Do This

6.1 MR1

Yes

Continue with Step 2, About Migration Paths through Setting Up a Trial System.


This completes Step 1 of the Migration Process.

About Migration Paths

This is Step 2 of the Migration Process. Be sure you have completed Step 1 (Migration Path Matrix) before starting this step.

We currently only support migrations from Cisco Unified MeetingPlace Release 6.1 MR1 and later to Release 8.6. If you are using an earlier version of Cisco Unified MeetingPlace and want to migrate to Release 8.6, then you must first upgrade to Cisco Unified MeetingPlace Release 6.1 MR1.

For more information on supported migrations, see Migration Path Matrix.

Web Servers

Audio and Application Servers

Video Systems

Web Servers

The Release 8.6 Web Server is installed on a Cisco MCS running the Cisco Unified MeetingPlace Windows operating system. You may install the Release 8.6 Web Server on a Cisco MCS or a virtual machine (on a VMware ESXi 4.1 host on a UCS B-Series or C-Series Server) running the Cisco Unified MeetingPlace Windows operating system.

For more information on installing on a virtual machine, see Installing on a Virtual Machine.

You can either reuse an existing Cisco MCS for the Web Server or you can install a newer Cisco MCS. We recommend using new hardware for the Release 8.6 Web Server and keeping the old Web Server as a contingency until the Release 8.6 deployment is complete and operational.


Caution If you choose to continue using the same hardware for your Web Server, make sure that it meets the minimum requirements for the Cisco Unified MeetingPlace Web Server. For more information, see the System Requirements for Cisco Unified MeetingPlace Release 8.6 at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_device_support_tables_list.html


Note If you are installing on an Cisco MCS 7835-I2 or 7845-I2, then you may need to upgrade or downgrade the firmware before installing the Cisco Unified MeetingPlace Windows operating system. For the steps to correct this problem, see Updating the Firmware on a Cisco MCS 7835-I2 or 7845-I2. For background information about the problem, see http://www.cisco.com/en/US/products/ps6509/products_tech_note09186a008059a81d.shtml.


Before the Web Server migration, you should backup your Web Server data.

If you are installing the Cisco Unified MeetingPlace Release 8.6 Web Server on a new machine, then restore your existing Web Server data on the new machine.

If you are retaining the same hardware for the Cisco Unified MeetingPlace Release 8.6 Web Server, then temporarily use another machine to back up your existing Web Server data.

For more information on supported Cisco MCS, see System Requirements for Cisco Unified MeetingPlace Release 8.6 at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_device_support_tables_list.html

Click-to-attend (CTA) links can only be migrated if the Cisco Unified MeetingPlace Release 8.6 Web Server has the same hostname (FQDN) as the Cisco Unified MeetingPlace Release 6.1 Web Server. If the hostname is changed, then a CNAME with the old FQDN can be added in DNS to point to the new primary Web Server. This enables CTA links to function correctly when the hostname is changed.

Audio and Application Servers

Cisco Unified MeetingPlace Release 6.1 uses an Audio Server 8100 series. Cisco Unified MeetingPlace Release 8.6 no longer uses an Audio Server but instead uses an Application Server. The Application Server is installed on a new Cisco MCS or on a virtual machine on a Cisco UCS B-Series or C-Series Server. This component must be installed new and cannot be upgraded from Cisco Unified MeetingPlace Release 6.1. You can migrate data from the Audio Server to the Application Server.

Video Systems

If you currently use a Cisco Unified MeetingPlace 3545 Media Server for Cisco Unified MeetingPlace Release 6.1 MR1 you can reuse the chassis and the Video Blade. However, you must upgrade the software for the video blade.

Cisco Unified MeetingPlace Release 8.6:

http://www.cisco.com/cisco/software/navigator.html and select Products > Voice and Unified Communications > Unified Communications Applications > Conferencing Software > Cisco Unified MeetingPlace > Cisco Unified MeetingPlace 8.6.

Because of the different configurations, you cannot reuse any part of the Cisco Unified MeetingPlace 3515 Media Server nor can you reuse the Audio Blade of the Cisco Unified MeetingPlace 3545 Media Server.

You cannot reuse the Cisco Unified MeetingPlace Release 6.1 MR1 video software or video configurations.

Prerequisites for the Migration

Read System Requirements for Cisco Unified MeetingPlace Release 8.6 at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html.

(Release 6.1 MR1 only) If you have not done so already, download the Cisco Unified MeetingPlace Release 8.6 Prerequisite Package to obtain the hotfixes and patches for the migration at http://www.cisco.com/cisco/software/navigator.html and select Products > Voice and Unified Communications > Unified Communications Applications > Conferencing Software > Cisco Unified MeetingPlace > Cisco Unified MeetingPlace 8.6. Select Unified MeetingPlace Application Server Release 8.6 Extract the files on your local system.

Obtain the Cisco Unified MeetingPlace Release 8.6 software DVDs from the Cisco Global Price List (GPL) or with a valid Cisco Unified Communications Software Subscription (UCSS). You will use the DVDs during the migration. Contact Cisco customer support for additional information.

Obtain the Cisco Unified MeetingPlace Release 8.6 binaries from http://www.cisco.com/cisco/software/navigator.html. Select Products > Voice and Unified Communications > Unified Communications Applications > Conferencing Software > Cisco Unified MeetingPlace > Cisco Unified MeetingPlace 8.6.

Familiarize yourself with the configuration of the Cisco Unified MeetingPlace Release 8.6 system. See the previous chapters in this guide, as well as the Configuration Guide for Cisco Unified MeetingPlace Release 8.6.

Get new licenses for your Cisco Unified MeetingPlace Release 8.6 system. Licenses for Cisco Unified MeetingPlace Release 6.1 MR1 do not work with a Cisco Unified MeetingPlace Release 8.6 system.

See Planning Guide for Cisco Unified MeetingPlace Release 8.6 for more information about Cisco Unified MeetingPlace Release 8.6 licenses. See "Obtaining Your License After Migration" section of theConfiguration Guide for Cisco Unified MeetingPlace for the exact procedure.

Do not run backups during the migration process. If you have scheduled automatic backups, ensure that you suspend them.

If your deployment includes a Hardware Media Server, then be sure to write down the IP address for each MCU before you start the migration. You will need to configure your audio and video blades on Cisco Unified MeetingPlace Release 8.6, following the migration.

Both the Release 6.1 Application Server and the Release 8.6 Application Server must be in the same time zone during the migration. Once the migration is complete, you can change the time zone on the new Release 8.6 Application Server.

If you have not run the vfptrfix command within the last 2-3 months, we highly recommend running it to fix voice pointer errors, before exporting data from the Cisco Unified MeetingPlace 6.1 MR1 Audio Server (Step 5 of the Migration Process.) (Although this command may take several hours to complete, it helps prevent the MigrateData Capture tool from failing, due to too many voice pointer errors.)


Note Before running the vfptrfix command, make sure there is sufficient disk space on your system. See Ensuring There is Sufficient Disk Space.


Using telnet, sign in to the CLI in Cisco Unified MeetingPlace as the admin user. Then, sign in as the CSC user (su), and enter the password of the day (contact Cisco TAC to obtain the password). Run the vfptrfix -f -v command.

If you are using the Cisco Unified MeetingPlace Microsoft Outlook plug-in, then make sure that you export the ICalendarMeetings table before upgrading your Web Server to Release 8.6. Complete this export as Step 11 of the Migration Process.

Migrating to a Virtual Machine

You can migrate your Web Server to a virtual machine, from a physical machine, with the following considerations:

The virtual machine must have the following requirements:

(Cisco UCS C210 M2 Server or UCS B-Series Server) Application Server and Cisco WebEx Node for MCS: 8 vCPU, 8 GB RAM, and a 300GB hard drive.

(Cisco UCS C200 M2 Server) Application Server and Cisco WebEx Node for MCS: The virtual machine must have 4 vCPU, 8 GB RAM, and a 300GB hard drive.

Web Server: 4 vCPU, 4 GB RAM, and a 250GB hard drive.

Install one virtual machine, per blade, on a Cisco UCS B-Series or C-Series Server.

Be sure your LAN connection supports at least 1 Gb/s (gigabits per second) connection.

Be sure your vSphere Client has supports at least 1 Gb/s (gigabits per second) connection.

One virtual NIC is required.


Note The Cisco Unified MeetingPlace system does not support snapshots on virtual machines.


For complete details on installing on a virtual machine, see the Installing on a Virtual Machine module.

Preserved Data

Meeting and user passwords.

Future meetings, including recurring meetings and invited participants (except for video terminals).

Audio deployments—attachments are migrated.

Deployments with MeetingPlace scheduling and Cisco WebEx conferencing—attachments are migrated.

Adobe Connect (Adobe Breeze) meetings—No attachments are migrated.

History of past meetings and meeting participants (preceding 38 days or the number of days until the meeting statistics are purged.

Recordings and attachments for past meetings (preceding 38 days or the number of days until the meeting statistics are purged)

Audio deployments—recordings and attachments are migrated.

Deployments with MeetingPlace scheduling and Cisco WebEx conferencing—recordings and attachments are migrated.

Adobe Connect (Adobe Breeze) meetings—Only audio and video recordings are migrated. Web recordings and attachments are not migrated.

Continuous meetings that are still active (ongoing)

Recorded user names

Users and groups

Web customizations

Click-to-attend links in previous e-mail notifications (only if the Cisco Unified MeetingPlace Release 8.6 Web Server has the same hostname (FQDN) as the Cisco Unified MeetingPlace Release 6.1 MR1 Web Server).

If the hostname is changed, then a CNAME with the old FQDN can be added in DNS to point to the new primary Web Server. This enables CTA links to function correctly when the hostname is changed.

Old Microsoft Outlook notifications

Old IBM Lotus Notes notifications

Old e-mail notifications

Meeting categories (user profiles and scheduled meetings that use custom categories will revert to using the standard meeting category)

Lost Data

During the migration process, the following will be lost:

History of past meetings and meeting participants (greater than 38 days or the value you set) in MeetingTime before the migration.

Existing meeting recordings and attachments (older than 38 days or the number of days until the meeting statistics are purged).

You may be able to access older recordings. See Retaining Recordings for more information.

Adobe Connect (Adobe Breeze) meetings—Web recordings and attachments are not migrated.

The ability to use most of your current hardware.

Video reservations, including any video terminals that were invited, for all meetings

Video terminal information. You must recreate all video terminal accounts after the migration.

Meeting statistics, meeting capacity, and billing information

System configuration for the existing Audio Server

Team information (no concept of teams in Cisco Unified MeetingPlace Release 8.6)

Audio customizations such as voice prompts and flex fields

Customizations for Cisco Unified MeetingPlace integrations (for example, Microsoft Outlook templates)

Related Topics

About Migration Paths

Retaining Recordings

If you want to retain historical recordings, you may chose one of the following options.

You can keep the legacy Cisco Unified MeetingPlace system for historical data.

We recommend you restrict users from starting new meetings on the legacy system. You can rename the legacy Cisco Unified MeetingPlace system with a new name, and retain the existing name on the new Cisco Unified MeetingPlace 8.6 system for an easier transition.

Retain the existing Cisco Unified MeetingPlace system for a specified period, and ask meeting hosts and participants to download historical meetings and attachments on to their own machine.

After the specified time, you can bring down the legacy system.

Setting Up a Trial System

If you are unsure if you want to migrate to Cisco Unified MeetingPlace Release 8.6, you can first set up a Cisco Unified MeetingPlace Release 8.6 trial system.

To set up a trial system, you will need new hardware. You can either temporarily install a Cisco Unified MeetingPlace Web Server or you can permanently install a new Cisco Unified MeetingPlace Web Server to replace your older Cisco Unified MeetingPlace Web Server.

With the trial system, you can import groups and user profiles. However, you cannot import meetings, due to the risk of sending out conflicting or invalid notifications.

If you decide to convert your trial system to a Cisco Unified MeetingPlace Release 8.6 production system, you must first clear out the trial data and then import the actual data from the older system.


Note All recordings made between when you import the data to the trial system to when you import the data again before converting the trial system to production are lost.


This completes Step 2 of the Migration Process.


Caution Do not complete Step 3 if you are at Release 6.1.

How to Prepare for a Migration

This is Step 4 of the Migration Process. Be sure you have completed Step 3 (applying the latest hotfixes and patches to your 6.1 MR1 Audio Server and Meeting) before starting this step.

During a migration, many errors can occur. We strongly recommend that you thoroughly review this section before you begin a migration.

Migration Considerations

Migration Best Practices

General Migration Errors and Troubleshooting

Migration Considerations


Caution Do not run any other processes or tasks on your Cisco Unified MeetingPlace Release 6.1 MR1 system during a migration, especially during the data backup process. This can potentially affect the data that is being transferred from one system to another.

MeetingTime is no longer available

The system migrates Cisco Unified MeetingPlace Release 6.1 MR1 meetings with passwords but problems can arise if the Cisco Unified MeetingPlace Release 6.1 MR1 password is less than the minimum password length required in Cisco Unified MeetingPlace Release 8.6. Therefore, we suggest that you set the value for the "Minimum meeting password length" parameter in Cisco Unified MeetingPlace Release 8.6 to the same value as or a smaller value than the parameter value in Cisco Unified MeetingPlace Release 6.1.

Following migration, you will get the default Release 8.6 video settings.

E-mail formats are mapped as follows:

Table 2 E-Mail Type Mappings

E-Mail Type (Release 6.1 MR1)
E-Mail Type and Format (Release 8.6)

none

SMTP (HTML)

cc:Mail

SMTP (HTML)

Lotus Notes

IBM Lotus Notes (Plain text)

Microsoft Mail

SMTP (HTML)

Microsoft Exchange

Microsoft Exchange (HTML)

Qualcomm Eudora

SMTP (HTML)

Netscape Messenger

SMTP (HTML)

Other

SMTP (HTML)


Migration Best Practices

Following migration, custom prompts need to be recreated in Release 8.6.


Note We recommend you do the migration during the weekend or during a low latency period. The Cisco Unified MeetingPlace system does a full profile synchronization early Sunday morning, so we recommend that you start the migration and complete the database backup before this synchronization occurs.



Caution Make sure that you back up your existing Cisco Unified MeetingPlace 6.1 MR1 system. It is important to have a backup of your data should the migration fail, or you need to cancel the migration.

To avoid multiple errors when importing data from the Cisco Unified MeetingPlace Release 6.1 MR1 system to the Cisco Unified MeetingPlace Release 8.6 system, follow these tips. To save time, you may choose to complete these best practices while exporting data from the Audio Server (Exporting Data from the Cisco Unified MeetingPlace Release 6.1 MR1 Audio Server).

Back up your SQL Server database before the migration. This reduces the transaction log, which makes the SQL Server database smaller and easier to migrate. See How to Back Up and Restore MPWEB SQL Database in the "Configuring the SQL Server for the Cisco Unified MeetingPlace Web Server" section of the Configuration Guide for Cisco Unified MeetingPlace.

Ensure that you have installed the Cisco Unified MeetingPlace Release 8.6 licenses on the system.

Ensure that the values for the system, meeting, and user configuration parameters for the Cisco Unified MeetingPlace Release 8.6 system are as close as possible to those values for the same parameters on the Cisco Unified MeetingPlace Release 6.1 MR1 system.


Note These are critical initial settings for the Cisco Unified MeetingPlace Release 8.6 system. After the migration is complete, you can change these system parameters with no repercussions.


Both systems must have the same values for the following fields:

Minimum profile password (PIN in Release 8.6) length

Minimum user password length

Maximum meeting length (minutes)

Meeting ID start guard time (minutes)

Meeting ID end guard time (minutes)

Maximum advance days to schedule (MeetingPlace scheduling only)

Minimum meeting ID (password in Release 8.6) length

Ensure that the Cisco Unified MeetingPlace Release 8.6 system has enough ports for the largest meeting scheduled on the Cisco Unified MeetingPlace Release 6.1 MR1 system.

During the migration, you will need to transfer files between servers. Be sure to have a file transfer application, such as WinSCP, available to transfer these files.

When installing the Cisco Unified MeetingPlace system remotely, be sure your LAN connection supports at least 1 Gb/s (gigabits per second).

If you are planning to change the name of your Application Server or Web Server following migration, then consider the following:

If the Web Server hostname is changed, then a CNAME with the old FQDN can be added in DNS to point to the new primary Web Server. This enables CTA links to function correctly when the hostname is changed.

Update the DNS server with the information for your new Release 8.6 Web Server and Application Server

Have a valid DNS service configuration. This is mandatory for correct operation of the Cisco Unified MeetingPlace system.

You need to enter a valid IP address for a DNS service during the installation of the Release 8.6 Application Server. Without this, your migration may fail.

You can test your DNS service by entering on the command-line interface, ping <DNS_IP_Address>. You should get a response in under 200 milliseconds.

General Migration Errors and Troubleshooting

If there are errors (for example, with a user or meeting record) the migration does not stop, but skips those records.

If you see the following error, it is because a password is required for the meeting in Cisco Unified MeetingPlace Release 8.6 but there was no password for the meeting in Cisco Unified MeetingPlace Release 6.1 MR1. The system has automatically set the meeting password to 12345 and imported the meeting:

Error in record 1, meeting id "xxxx": Password is configured to be mandatory, but none was provided.

You must have the Cisco Unified MeetingPlace Release 8.6 licenses before the migration. If you did not install the lotusnotes or the msft_int license and you migrate a meeting that uses that license, the system maps the meeting to the generic SMTP (HTML) format (see Table 2) and displays the following error message:

Changing email format to RTF for group xxx.
Import line: "",87,"","4353","xxx","Yes","No","Yes","Beep","BeepName

To prevent file corruption, edit the migration files with a text editor. Turn off the word wrap option to improve readability. When finished, save the file with a .csv extension.

Experienced users can use Microsoft Excel to edit the migration files. If you use Microsoft Excel, then reopen the saved file with a text editor and remove all the commas in the first line. When finished, save the file with a .csv extension.


Note If you use Microsoft Excel to edit migration files, you might experience the file formats changing or invisible hex characters being added to the header. We recommend only experienced users should use Microsoft Excel.


This completes Step 4 of the Migration Process.

Migrating Data from a Cisco Unified MeetingPlace Release 6.1 MR1 System to a Cisco Unified MeetingPlace Release 8.6 System

Migrating Data from a Cisco Unified MeetingPlace Release 6.1 MR1 Audio Server to a Cisco Unified MeetingPlace Release 8.6 Application Server

Migrating Cisco Unified MeetingPlace Release 6.1 MR1 Directory Services to Cisco Unified MeetingPlace Release 8.6 Directory Service

Migrating Data from a Cisco Unified MeetingPlace Release 6.1 MR1 Web Conferencing Server to a Cisco Unified MeetingPlace Release 8.6 Web Server

Migrating Your Microsoft Outlook Plug-In

Migrating Data from a Cisco Unified MeetingPlace Release 6.1 MR1 Audio Server to a Cisco Unified MeetingPlace Release 8.6 Application Server

This is Step 5 of the Migration Process. Be sure you have completed Step 4 (How to Prepare for a Migration) and Prerequisites for the Migration, before starting this step.

Because of the hardware differences, you must migrate from a Cisco Unified MeetingPlace Release 6.1 MR1 Audio Server to a Cisco Unified MeetingPlace Release 8.6 Application Server. You cannot use a Cisco Unified MeetingPlace Release 6.1 MR1 Audio Server with a Cisco Unified MeetingPlace Release 8.6 system and you cannot upgrade from a Cisco Unified MeetingPlace Release 6.1 MR1 Audio Server to a Cisco Unified MeetingPlace Release 8.6 Application Server.


Note Both the Release 6.1 MR1 Application Server and the Release 8.6 Application Server must be in the same time zone during the migration. Once the migration is complete, you can change the time zone on the new Release 8.6 Application Server.



Note Plan accordingly, as the Audio Server data migration may take 24 to 48 hours to complete. The time depends on multiple factors including the database, the number of recordings, the number of meetings, number of users, number of notifications, and so on.


To migrate data from an Audio Server to an Application Server, perform the following tasks in this order:

1. Check free disk space. See Ensuring There is Sufficient Disk Space.

2. Export data from the old system. See Exporting Data from the Cisco Unified MeetingPlace Release 6.1 MR1 Audio Server.

3. Install the Cisco Unified MeetingPlace Release 8.6 Application Server. See the Installing the Application Server Software module.

4. Import the data to the new system. See Importing the Data to the Cisco Unified MeetingPlace Release 8.6 Application Server.

Ensuring There is Sufficient Disk Space

Make sure that you have sufficient free disk space on the Cisco Unified MeetingPlace Release 6.1 MR1 Audio Server for certain file systems.

Procedure


Step 1 Sign in to the Cisco Unified MeetingPlace Audio Server command-line interface as the CSC user (contact Cisco TAC to obtain the password of the day).

Step 2 Enter the df command to check the space utilization on the root, db, and tmp file systems.

The root file system should have less than 65 percent utilization.

mtgplace# df /
Filesystem    BlkSize  Blocks    Used    Free    %
/dev/sdncr.1a   16384   31999   19569   12430  61%
 
   

If the root file system utilization is higher than 65 percent, then check /usr/users/csc for old case log files and remove them. If you still cannot find enough free space, then contact Cisco TAC for further assistance.

The DB filesystem should have less than 60 percent utilization:

mtgplace# df /lat/db
Filesystem    BlkSize  Blocks    Used    Free    %
/dev/sdncr.0c   16384  320000  138058  181942  43%
 
   

If the db file system utilization is higher than 60 percent, then contact Cisco TAC for further assistance.

The tmp file system should have less than 80 percent utilization.

mtgplace# df /tmp
Filesystem    BlkSize  Blocks    Used    Free    %
/dev/sdncr.1b   16384   51200   24633   26567  48%
 
   

If the tmp file system utilization is higher than 80 percent, then check /tmp/update for old update files and remove them.

Exporting Data from the Cisco Unified MeetingPlace Release 6.1 MR1 Audio Server

Before You Begin

You must have the following software installed before starting your Release 6.1 Audio Server migration:

Cisco Unified MeetingPlace MeetingTime Release 6.1 MR1

Cisco Unified MeetingPlace Audio Server Release 6.1 MR1

Restriction

Do not run any other processes or tasks on your systems during a migration. This can potentially affect the data that is being transferred from one system to another.

Procedure


Step 1 Stop the Web Conferencing services and then stop the Gateway SIM. See "How to Use the Cisco Unified MeetingPlace Web Conferencing Service" in the Configuration Guide for Cisco Unified MeetingPlace Release 8.6 or the online help in the administrator interface.

Step 2 Use MeetingTime and sign in, as a system administrator, to the Cisco Unified MeetingPlace 6.1 MR1 Audio Server.

Step 3 Go to Options > Edit Settings.

Step 4 Use the arrows to set the Minutes to wait for report results to 300.

Setting this value to the maximum value of 300, effectively results in no timeout limit.

Step 5 Telnet to the Cisco Unified MeetingPlace 6.1 MR1 Audio Server CLI as the admin user. Enter restart enable on the command-line interface to reboot the Cisco Unified MeetingPlace Audio Server.

Complete this command immediately before capturing the migration data.

Step 6 Use MeetingTime to sign in, as a system administrator, to the Cisco Unified MeetingPlace 6.1 MR1 Audio Server.

Step 7 Go to Administration > Report.

Step 8 Click MigrateData Capture from the left panel.

Step 9 Select the time period for retaining the history of completed meetings and meeting participants. Click 38 from the right panel and use the arrows, if you want to select a shorter time period. Then click OK.

The maximum time period is 38 days.

Step 10 Click migratedata.zip from the right panel. Click OK to save the file to the default location, or click Browse to navigate to the directory where you want to save this file. Click Save.

Step 11 Click Generate Report.

The system displays a message stating that this report can generate a high data transfer load on the Audio Server and is intended only as a migration tool to Cisco Unified MeetingPlace Release 8.6. It should not be run during periods of active utilization.

Step 12 Click Yes to acknowledge the message, then click Yes again, when the system asks if you want to continue.

When complete, the system returns you to the Report tab.

The migratedata.zip file contains the following:

mpweb_purge_mtgs.sql

MtgCat.xml

mtversion.txt

RawGroup.txt

RawMeetings.txt

RawMtgCat.txt

RawPartAtt.txt

RawProfile.txt

RecordedNames.zip

The MigrateData Capture report exports all the .wav files (for recorded names) to the Reports folder in the directory in which Cisco Unified MeetingPlace MeetingTime is installed.


Note The system does not remove these files after creating the RecordedNames.zip file. Therefore, if you want to capture migration data from another Cisco Unified MeetingPlace Release 6.1 MR1 Audio Server, or redo the migration data capture by using the current Audio Server, then remove all of the .wav files from the Reports folder.



This completes Step 5 of the Migration Process.

What To Do Next

1. Complete Step 6 of the Migration Process, by installing the Cisco Unified MeetingPlace Release 8.6 Application Server. See the Installing the Application Server Software module.


Note The migrate goes directly to Release 8.6. Make sure you have installed Cisco Unified MeetingPlace Application Server before continuing to Step 7 of the Migration Process.


Be sure you have completed Step 5 (Migrating Data from a Cisco Unified MeetingPlace Release 6.1 MR1 Audio Server to a Cisco Unified MeetingPlace Release 8.6 Application Server) before starting this step.

2. When finished with the installation, proceed to Importing the Data to the Cisco Unified MeetingPlace Release 8.6 Application Server.

Importing the Data to the Cisco Unified MeetingPlace Release 8.6 Application Server

This is Step 7 of the Migration Process. Be sure you have completed Step 6 (Installing the Application Server Software module) before starting this step.

Use Migration Import from MeetingPlace 6 in the Cisco Unified MeetingPlace Release 8.6 Administration Center to import the data from the Cisco Unified MeetingPlace Release 6.1 MR1 Audio Server to the Cisco Unified MeetingPlace Release 8.6 Application Server.

Restriction

Ensure that the Cisco Unified MeetingPlace Release 8.6 Application Server has been installed prior to starting the restore process. See the Installing the Application Server Software module.

Do not run any other processes or tasks on your systems during a migration. This can potentially affect the data that is being transferred from one system to another.

If you plan to have a failover deployment (audio-only or a deployment with MeetingPlace scheduling), then be sure to build, configure, and complete migration on your primary server (Node1) before you configure the standby server (Node2) and enable replication.

Procedure


Step 1 Sign in to the Application Server command-line interface as the root user.

Step 2 Navigate to the /tmp directory and use the touch command to create a file, .migrate (an empty file).

[root@<server_name> tmp]# touch .migrate

Step 3 Verify that an empty .migrate file has been created.

find . -empty -exec ls {} \;

This command returns a list of all empty files. For example:

[root@<server_name> tmp]# find . -empty -exec ls {} \;

./dbtasklocks/TRIGGER_WATCH

./.migrate

./brassd.log

Step 4 Sign in to the Application Server command-line interface by entering su - informix.

Step 5 Navigate to the appropriate directory by entering cd /opt/cisco/meetingplace/database/db-maintenance/.

Step 6 Enter ./update_statistics.sh, then wait until the command completes (in approximately 5 minutes).Sign in to the Administration Center on the Application Server.

Step 7 Put the Application Server in Maintenance Mode by selecting Maintenance > Migration configuration and then selecting Start Maintenance Mode.

Step 8 Choose Maintenance > Migration Import from MeetingPlace 6.

Step 9 Click Browse to navigate to the data file that contains the import data.

Step 10 Click Execute.

After starting the import of migratedata.zip, a separate browser tab is opened, showing the status of the date import. At any time, you can select '''See Result''' to view a detailed migration import. (A separate browser window is opened.)

After the import is completed, the system displays a new tab stating that the import has finished.

Step 11 Click See Result to confirm the status.

This popup window displays the detailed status.

Step 12 Restart the Application Server when the data migration is complete.


This completes Step 7 of the Migration Process.

Troubleshooting the Application Server Data Migration

This is Step 8 of the Migration Process. Be sure you have completed Step 7 (Importing the Data to the Cisco Unified MeetingPlace Release 8.6 Application Server) before starting this step.

The system always generates the following error messages during the data migration, due to the differences in system profile designs between Cisco Unified MeetingPlace Release 6.1 MR1 and Cisco Unified MeetingPlace Release 8.6. These messages can be ignored:

Error importing record 2: Profile number 0001 already exists.
Import line: "Sales","Engineer","salesengineer","0001","","gd","System","
Error importing record 3: Profile number 0002 already exists.
Import line: "Tech","Engineer","technician","0002","","gd","System","0","

If the migration import fails, scan the output file for the failure reasons. Fix any errors manually or by using Cisco Unified MeetingPlace MeetingTime. If you use Cisco Unified MeetingPlace MeetingTime, you must export the migrate file again from the Cisco Unified MeetingPlace Release 6.1 MR1 Audio Server.

Always scan the results of the migration import on the Cisco Unified MeetingPlace Release 8.6 system. The most common problems occur when importing the first records from user groups and user profiles. If you see problems, cancel the migration and correct the errors.

Sign in as root on the Cisco Unified MeetingPlace 8.6 Application Server command-line interface, and enter mpx_sys restart to cancel the migration.

Clean up the database on the Cisco Unified MeetingPlace Release 8.6 Application Server command-line interface by entering /opt/cisco/meetingplace/application/current/bin/cleardb.

If more than 5000 errors occur during a migration, then the migration terminates with an error message:

Maximum errors reached. Aborting action.

Contact Cisco TAC for further assistance.

If you see the following error message when importing migratedata.zip from the Administration Center on the Application Server, then check the following:

Migration import is not allowed. Check version of meetingtime used for creating migrate.zip.

Make sure the correct version of MeetingTime and the Audio Server are being used to export the database.

Make sure there is no existing data in the Application Server by running the dbsize command as the root user. If there is any data, then run the cleardb command to clean up the data, followed by a reboot of the Application Server.

Check the migration logs located at migrate*.log in the /tmp folder and at migrate*.html.info in the /mpx-record/migrate folder.

Check the mpx-record/migrate folder and see if all the contents of migratedata.zip are unzipped.

If the contents of migratedata.zip are not completely unzipped or are missing, then manually unzip migratedata.zip by running unzip migratedata.zip from the mpx-record/migrate folder through the command-line interface.

Fixing Migration Data Errors

Problem   If there are errors during a migration (for example, with a user or meeting record), then the migration skips those records. Depending on the number of errors, there are two solutions.

Solution   If there aren't too many errors for users or meetings, then we recommend you recreate the user profiles and meetings.

Solution   If the number of errors is higher, then complete the following steps.


Step 1 Run raw profile and raw meeting export reports from the Cisco Unified MeetingPlace Release 6.1 MR1 system.

Step 2 Fix the problems in the .csv file.

If you use Microsoft Excel to make your changes, then reopen the saved file with a text editor and remove all the commas in the first line. When finished, save the file with a .csv extension.

Step 3 Import this file into the Cisco Unified MeetingPlace Release 8.6 system.

See Importing Meetings Page in the "Administration Center Page References fo Cisco Unified MeetingPlace" section of the Configuration Guide for Cisco Unified MeetingPlace.


Note With this process, no recorded name gets migrated. If a failed meeting record includes recurrence, then the recurrence is broken at that meeting instance. Manually cancel, then reschedule the meeting with recurrence.


This completes Step 8 of the Migration Process.

Related Topics

See General Migration Errors and Troubleshooting.

Migrating Cisco Unified MeetingPlace Release 6.1 MR1 Directory Services to Cisco Unified MeetingPlace Release 8.6 Directory Service

This is Step 9 of the Migration Process. Be sure you have completed Step 8 (Troubleshooting the Application Server Data Migration) before starting this step.

About Migrating Non-Local Users from Cisco Unified MeetingPlace Release 6.1 MR1 to Cisco Unified MeetingPlace Release 8.6

Restoring the Local and Non-Local Status for Users

Troubleshooting the Directory Service Migration

About Migrating Non-Local Users from Cisco Unified MeetingPlace Release 6.1 MR1 to Cisco Unified MeetingPlace Release 8.6

The Cisco Unified MeetingPlace Release 6.1 MR1 database contains two types of users: local and non-local. Local users were manually created using Cisco Unified MeetingPlace and non-local users were imported into Cisco Unified MeetingPlace from an external directory by Cisco Unified MeetingPlace Directory Services.

The migration process imports all users as local users. Cisco Unified MeetingPlace Release 8.6 cannot modify the user profiles for user who had non-local status before but that now have local status.

The following process restores the local or non-local status for users to the original value.

Restoring the Local and Non-Local Status for Users

Before You Begin

You have installed the Cisco Unified MeetingPlace Release 8.6 Application Server.

You have migrated data from the Cisco Unified MeetingPlace Release 6.1 MR1 Audio Server to the Cisco Unified MeetingPlace Release 8.6 Application Server.

Procedure


Step 1 Sign in as the administrator to the Cisco Unified MeetingPlace Release 6.1 MR1 Web Server and as a superuser to the Cisco Unified MeetingPlace Release 8.6 Application Server.

Step 2 On the Cisco Unified MeetingPlace Release 8.6 Application Server, navigate to the following directory: /opt/cisco/meetingplace/migrationtools/current/directoryservice/etc. This directory contains two files: SunOne_ldaptools.zip and MP6.0_MPDSMigrationHelper.bat.

Step 3 Copy those two files to a local directory on the Cisco Unified MeetingPlace Release 6.1 MR1 Web Server where Cisco Unified MeetingPlace Directory Services is running.

Step 4 Navigate to the directory to which you just copied the files.

Step 5 Unzip the SunOne_ldaptools.zip file to a new directory.

Step 6 Copy the MP6.0_MPDSMigrationHelper.bat file to the same new directory.

Step 7 Navigate to the new directory that you just created.

Step 8 Enter MP6.0_MPDSMigrationHelper.bat <FQDN of machine where MPDS is running> <LDAP port> <MPDS admin password> to run the Directory Services migration script.

An example is:

MP6.0_MPDSMigrationHelper.bat MP6mpds.cisco.com 389 mpds123

The system writes the output to a file called LocalMPUsers.txt in the current directory.

Step 9 Copy the output file called LocalMPUsers.txt to the \tmp directory on the Cisco Unified MeetingPlace Release 8.6 Application Server.

Step 10 Sign in as a superuser to the Release 8.6 Application Server.

Step 11 Navigate to the /opt/cisco/meetingplace/migrationtools/current/directoryservice/bin directory.

Step 12 Enter the following to run the MPDSMigrationHelper script:

./ MPDSMigrationHelper.sh <input file location> <update | getStatus>

An example is:

./ MPDSMigrationHelper.sh /tmp/LocalMPUsers.txt update

The system writes the log file to the console and to this location: /tmp/MPDSMigrationToMP8.6.log.

Step 13 Enter the following to verify that the migration worked:

./ MPDSMigrationHelper.sh /tmp/LocalMPUsers.txt getStatus

This command writes the local and non-local status of the user to the migration log file and to the console. The output looks like the following:

User user1 isLocalUser? true
 
   

Troubleshooting the Directory Service Migration

If you did not restore the local and non-local user status for users, the system generates the following error message when you try to manage the user profiles:

Validation exception: The user ID xxxx is already being used.

The Cisco Unified MeetingPlace Release 8.6 version of Directory Service tries to create the same users on Cisco Unified MeetingPlace Release 8.6 and cannot get user updates from Active Directory or Cisco Unified Communications Manager.

To trigger a full synchronization from Active Directory or Cisco Unified Communications Manager and to update the users, follow the steps in this procedure.

Procedure


Step 1 Sign in to the Administration Center.

Step 2 Click User Configuration > Directory Service > Directory Service Configuration.

Step 3 Enter values for the AXL username, AXL password, and AXL URL fields.

Step 4 Check the boxes next to Update Now and Perform full sync with Cisco Unified Communications Manager.

Step 5 Click Save.


This completes Step 9 of the Migration Process.

Related Topics

See the online help in the administrator interface for more information about the Directory Service Configuration page.

Migrating Data from a Cisco Unified MeetingPlace Release 6.1 MR1 Web Conferencing Server to a Cisco Unified MeetingPlace Release 8.6 Web Server

To migrate Web Server data, complete the following procedures, in this order:

1. (Only if you are using the Microsoft Outlook plug-in as a front-end integration.) Exporting the ICalendarMeetings table from the Cisco Unified MeetingPlace 6.1 MR1 Web Conferencing Server Database to a Text File.

2. Backing Up the Web Conferencing Data Before a Migration.

3. Installing the Cisco Unified MeetingPlace 8.6 Web Server. Complete one of the following:

Using the Same Hardware for Your Cisco Unified MeetingPlace Release 8.6 Web Server.

Using New Hardware for Your Cisco Unified MeetingPlace Release 8.6 Web Conferencing Server.

4. Synchronizing Meeting Data Between the Cisco Unified MeetingPlace Web Conferencing Server and the Cisco Unified MeetingPlace Application Server.


Note The backup and restore of Cisco Unified MeetingPlace Web Server conferencing data takes approximately 15-30 minutes for each phase.


Exporting the ICalendarMeetings table from the Cisco Unified MeetingPlace 6.1 MR1 Web Conferencing Server Database to a Text File

This is Step 10 of the Migration Process. Be sure you have completed Step 9 (Migrating Cisco Unified MeetingPlace Release 6.1 MR1 Directory Services to Cisco Unified MeetingPlace Release 8.6 Directory Service) before starting this step.


Note Only complete this procedure if your Cisco Unified MeetingPlace system has a Microsoft Outlook plug-in with a back-end integration (users schedule meetings through Cisco Unified MeetingPlace). If you do not utilize the Microsoft Outlook plug-in, or you have a front-end integration (users schedule Outlook meetings through Microsoft Outlook), then do not complete this procedure.



Caution Complete this procedure before migrating your Cisco Unified MeetingPlace 6.1 MR1 Web Server.

This process takes approximately a few minutes.

Procedure


Step 1 As an administrative user, sign in to a Microsoft Windows machine that can access the Cisco Unified MeetingPlace 6.1 MR1 Web Conferencing Server database.

Step 2 Start the DTS Import/Export Wizard. Go to Start > All Programs > Microsoft SQL Server > Import and Export Data. Click Next.

Step 3 Choose a Data Source from the drop-down list. Then, enter the Server name, choose the Authentication, and enter the username and password for the MPWEB database. Click Next.

Step 4 Choose the Destination, Text File, from the drop-down list. Enter the path and the name of the text file, for example, ICalendarMeetings.txt. Click Next.

Step 5 Select Copy table(s) and view(s) from the source database. Click Next.

Step 6 Select the destination file format. Click Next.

Source: ICalendarMeetings table

Delimited

File type: ANSI

Row delimiter: {CR}{LF}

Column delimiter: Comma

Text qualifier: Double Quote {"}

Step 7 Check the Run Immediately check box. Click Next.

Step 8 Click Finish to complete the DTS Import/Export Wizard.

You will import the ICalendarMeetings.txt file to the Cisco Unified MeetingPlace 8.6 Application Server.


Note Save the ICalendar generated file to your computer. This file will be imported later.



This completes Step 10 of the Migration Process.

Backing Up the Web Conferencing Data Before a Migration

This is Step 11 of the Migration Process.

If your Cisco Unified MeetingPlace system includes a Microsoft Outlook plug-in integration and users schedule meetings through Cisco Unified MeetingPlace (back-end integration), then complete Exporting the ICalendarMeetings table from the Cisco Unified MeetingPlace 6.1 MR1 Web Conferencing Server Database to a Text File (Step 10) before starting this step.

The Cisco Unified MeetingPlace Web Conferencing Backup or Restore Wizard generates an executable that migrates configuration settings and meeting information from one Web Server to another. If you have a load-balancing cluster of Web Servers, complete the following procedures on each server in the cluster.

Cisco Unified MeetingPlace Web Conferencing Backup Utility

Specifying a Different Backup Destination Folder

Backing Up Data from the Source Web Server


Note The restore file generated by the Cisco Unified MeetingPlace Web Conferencing Backup or Restore Wizard cannot be used to revert to Release 6.1 MR1 if the migration fails. You will need to have a manual backup created if you need to revert to the original release. For more information, see How to Back Up and Restore MPWEB SQL Database in the "Configuring the SQL Server for the Cisco Unified MeetingPlace Web Server" section of the Configuration Guide for Cisco Unified MeetingPlace.



Note If you are planning to install the Cisco Unified MeetingPlace Release 8.6 Web Server on the same hardware as the legacy Cisco Unified MeetingPlace Release 6.1 MR1 Web Conferencing Server, then back up your Web conferencing data on a different server.


Cisco Unified MeetingPlace Web Conferencing Backup Utility

The Cisco Unified MeetingPlace web conferencing backup utility is included in the Cisco Unified MeetingPlace 8.6 Web Server download package. Copy it to the Cisco Unified MeetingPlace 6.1 MR1 Web Server to execute your backup.

The Web Conferencing backup utility uses the Microsoft Windows backup tool as its underlying backup engine. Since the Windows backup tool does not perform any compression, the total size of your projected backup equals the total data size of the files and folders that you want to back up. You may use the Properties function in Windows Explorer to get the size of each folder and add them together to get the total size of back up data.

By default, the backup utility backs up data from the following folders:

C:\Program Files\Microsoft SQL Server\MSSQL\Data

C:\Program Files\Cisco Systems\MPWeb\Meetings

C:\Program Files\Cisco Systems\MPWeb\WebConf\content\7

The \MPWeb\WebConf\content\7 folder contains an extremely large number of folders and files.

These folders are based on the default set up of the local SQL Server database on the Cisco MCS server and on the lack of a shared storage location.


Note The Web Conferencing backup utility cannot back up data from a shared storage location. To back up such data, manually navigate to the location of your shared storage location, copy the contents of the entire folder, then paste them into another location.


The utility then stores the backed up data in the following folder by default:

C:\Program Files\Cisco Systems\MPWeb\MPBackup

If you run the backup utility in command line mode, you can specify a different location. See Specifying a Different Backup Destination Folder.

Specifying a Different Backup Destination Folder

Complete this procedure if you want to set up your own destination backup folder, where your backed up data will be stored. If you do not do this procedure, the Web Conferencing backup utility will store its backed up data in C:\Program Files\Cisco Systems\MPWeb\MPBackup by default.

If you choose to use the default destination folder, go to Backing Up Data from the Source Web Server.

Procedure


Step 1 Open a DOS command window.

a. Select Start > Run.

b. Enter cmd.

Step 2 Navigate to the folder where the backup utility is located. Example: C:\Temp\mpweb_software>

Step 3 Enter the location of your backup destination folder by reviewing the following examples:

Example 1: 

If you enter ciscounifiedmeetingplacewebconferencingbackup.exe f:

the backup utility will create a folder called f:\MPBackup and use it as the destination folder for your backed up data.

Example 2: 

`If you enter ciscounifiedmeetingplacewebconferencingbackup.exe f:\backup

the backup utility will create a folder called f:\backup\MPBackup and use it as the destination folder for your backed up data.


Note If you specify f:\ instead of f:, or f:\backup\ instead of f:\backup, the backup utility will fail and abort. In other words, do not include the \ as the last character in your path specification.


Example 3: 

Specify your destination backup folder by using a UNC path:

Enter ciscounifiedmeetingplacewebconferencingbackup.exe \\hostname\temp


Backing Up Data from the Source Web Server

As a precaution, complete this procedure even if you will be using the same hardware for the Cisco Unified MeetingPlace 8.6 Web Server.

Before You Begin

Manually estimate the total data size of your backup operation to ensure that your destination has enough disk space to hold the backed up data files.

Manually stop the MSSQLSERVER service and disable the service until the backup is done.


Note This backup takes 15-30 minutes, depending on the number of users, meetings, attachments, and recordings. For example, the backup takes about 10 minutes for a system with about 300,000 profile users and 400,000 meetings, with a small number of attachments and recordings.


Procedure


Step 1 On the original Cisco Unified MeetingPlace 6.1 MR1 Web Conferencing Server, exit any open applications.

Step 2 Copy CiscoUnifiedMeetingPlaceWebConferencingBackup.exe from the Cisco Unified MeetingPlace 8.6 Web Server download package and copy it to the Cisco Unified MeetingPlace 6.1 MR1 Web Server.


Note Be sure to use CiscoUnifiedMeetingPlaceWebConferencingBackup.exe for the release to which you are migrating. If you are migrating to Release 8.6, then go to http://www.cisco.com/cisco/software/navigator.html and select Products > Voice and Unified Communications > Unified Communications Applications > Conferencing Software > Cisco Unified MeetingPlace > Cisco Unified MeetingPlace 8.6. Obtain CiscoUnifiedMeetingPlaceWebConferencingBackup.exe file for Release 8.6.


Step 3 Double-click CiscoUnifiedMeetingPlaceWebConferencingBackup.exe.


Note To store the backup data in a different location, run the following from the command prompt: CiscoUnifiedMeetingPlaceWebConferencingBackup <location>



Note The backup file is originally saved on this destination C:\Program Files\Cisco Systems\MPWeb\MPBackup\ and is named MeetingPlacebackup.bkf.


Step 4 Click Next in the first dialog box of the Backup or Restore Wizard and follow the prompts.

The Backup or Restore Wizard creates a restore file called CiscoUnifiedMeetingPlaceWebConferencingRestore.exe that you can use on a separate Web Server.

Step 5 Set the MSSQLSERVER service back to its original settings. Starting this service also turns on the Cisco MeetingPlace services on the Web Server.


This completes Step 11 of the Migration Process.

Installing the Cisco Unified MeetingPlace 8.6 Web Server

This is Step 12 of the Migration Process. Complete only one of the two bulleted procedures below, depending on whether you are using existing hardware, or new hardware, for the 8.6 Web Server.


Note If any of the fields or strings were customized on the Web Server, see Configuring User Interface Text, especially steps 4 and 10, for information about saving the customization for migration purposes.


Be sure you have completed Step 11 (Backing Up the Web Conferencing Data Before a Migration) before starting this step.

(Only if you are using existing hardware for the 8.6 Web Server.) See Using the Same Hardware for Your Cisco Unified MeetingPlace Release 8.6 Web Server.

This section describes how to set up and install the Cisco Unified MeetingPlace 8.6 Web Server on your existing hardware.

Using New Hardware for Your Cisco Unified MeetingPlace Release 8.6 Web Conferencing Server.

This section describes how to migrate data, such as meeting recordings, attachments, custom strings, and MPWEB database information from the Cisco Unified MeetingPlace 6.1 MR1 Web Server to the Cisco Unified MeetingPlace 8.6 Web Server on new hardware.


Note If you are installing on an Cisco MCS 7835-I2 or 7845-I2, then you may need to upgrade or downgrade the firmware before installing the Cisco Unified MeetingPlace Windows operating system. For the steps to correct this problem, see Updating the Firmware on a Cisco MCS 7835-I2 or 7845-I2. For background information about the problem, see http://www.cisco.com/en/US/products/ps6509/products_tech_note09186a008059a81d.shtml.


Using the Same Hardware for Your Cisco Unified MeetingPlace Release 8.6 Web Server

This is Step 12 of the Migration Process.

Only perform this procedure if you are using the same hardware for both the Cisco Unified MeetingPlace Release 6.1 MR1 and Cisco Unified MeetingPlace Release 8.6 Web Servers. If you are using new hardware, then go to the instructions in Using New Hardware for Your Cisco Unified MeetingPlace Release 8.6 Web Conferencing Server.

Restrictions

Do not run any other processes or tasks on your systems during a migration. This can potentially affect the data that is being transferred from one system to another.

You cannot migrate the Cisco Unified MeetingPlace Web Server when the Application Server is being rebooted. The 8.6 Application Server must be running before you can migrate the Web Server.

To ensure that the Application Server is running, sign in to the CLI as mpxadmin and enter swstatus. For more information about using the CLI, see the Configuration Guide for Cisco Unified MeetingPlace Release 8.6 or the online help in the administrator interface.

Click-to-attend (CTA) links can only be migrated if the Cisco Unified MeetingPlace Release 8.6 Web Server has the same hostname (FQDN) as the Cisco Unified MeetingPlace Release 6.1 MR1 Web Conferencing Server. If the hostname is changed, then a CNAME with the old FQDN can be added in DNS to point to the new primary Web Server. This enables CTA links to function correctly when the hostname is changed.

Before You Begin

Migrate data from a Cisco Unified MeetingPlace Release 6.1 MR1 Audio Server to a Cisco Unified MeetingPlace Release 8.6 Application Server.

Look up the value of the "Hostname [Home Page]" parameter for the Cisco Unified MeetingPlace Release 6.1 MR1 Web Server and resolve it to obtain the IP address of the NIC that is used during the installation of the Cisco Unified MeetingPlace 8.6 Web Server. Enter this value when prompted for the local IP address during the Web Server installation.


Note The correct IP address is not necessarily that of NIC 1; therefore, we recommend that you look at the administrator interface for the value of the "Hostname [Home Page]" parameter.


If your Cisco Unified MeetingPlace Release 6.1 MR1 system was enabled for video, use the Add/Remove Programs function to remove the video program from the Web Server. The video program that worked in Cisco Unified MeetingPlace Release 6.1 MR1 does not work in Cisco Unified MeetingPlace Release 8.6.

Verify that the Cisco Unified MeetingPlace Release 6.1 MR1 Web Server has network connectivity to the Cisco Unified MeetingPlace Release 8.6 Application Server by running the nslookup hostname and then pinging the hostname (FQDN).

Detach the Cisco Unified MeetingPlace Release 6.1 MR1 Web Server from the Cisco Unified MeetingPlace Release 6.1 MR1 Audio Server.

Procedure


Step 1 On the original Cisco Unified MeetingPlace 6.1 MR1 Web Server, exit any open applications.

Step 2 Although it is not mandatory, we recommend you clean up old files and applications on your existing hardware, before installing the Cisco Unified MeetingPlace 8.6 Web Server. After cleaning up your system, it should be a clean Cisco MCS.

a. Using Microsoft Add/Remove Programs, remove Cisco Unified MeetingPlace Web Conferencing. For additional information, see http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_6.1_--_Uninstalling_Web_Conferencing_Software#Uninstalling_Web_Conferencing_Software.

b. Delete the C:\Program Files\Cisco Systems folder.

c. Using Microsoft Add/Remove Programs, remove Microsoft SQL Server. For additional information, see http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_6.1_--_Uninstalling_SQL_Server_Software_and_Removing_MPWEB_SQL_Database_Files.

Step 3 Use Microsoft Management Console and ensure that no Cisco Unified MeetingPlace services are running.

Step 4 Install the Cisco Unified MeetingPlace Windows operating system on the Release 8.6 Web Server.

Step 5 Restore the Web Server conferencing data.

a. Copy CiscoUnifiedMeetingPlaceWebConferencingRestore.exe to the destination computer and double-click this file.

The Backup or Restore Wizard window displays.

b. Click Next. Select Restore files and settings, then click Next.

c. Click Browse and navigate to your MeetingPlacebackup.bkf file. Click Next.

d. Double-click an item in the left pane to see its contents. Check the items you want to restore. Then click Next.

Ensure that all drives and multiple folder options are checked.

e. Click Finish to close the Wizard.

The restore operation proceeds.

f. Click Close to close the Cisco Unified MeetingPlace Restore window.

Step 6 Install the Cisco Unified MeetingPlace Release 8.6 Web Conferencing software. See the Installing the Cisco Unified MeetingPlace Web Server Software module.

Step 7 Enter the hostname (FQDN) of the Cisco Unified MeetingPlace Release 8.6 Application Server when the system prompts you for the hostname of the Primary Server.

Step 8 Enter the IP address associated with the "Hostname [Home Page]" value when the system prompts you for the local IP address.

The system continues the installation.

Step 9 Follow the screen prompts to reboot the Web Server.

The system reboots and continues the installation.


This completes Step 12 of the Migration Process.

What to Do Next

Synchronizing Meeting Data Between the Cisco Unified MeetingPlace Web Conferencing Server and the Cisco Unified MeetingPlace Application Server

Using New Hardware for Your Cisco Unified MeetingPlace Release 8.6 Web Conferencing Server

This is Step 12 of the Migration Process.

Only perform this procedure if you are using new hardware for Cisco Unified MeetingPlace Release 8.6 Web Server. If you are using existing hardware, then go to the instructions in Using the Same Hardware for Your Cisco Unified MeetingPlace Release 8.6 Web Server.

Restrictions

Do not run any other processes or tasks on your systems during a migration. This can potentially affect the data that is being transferred from one system to another.

You cannot upgrade the Cisco Unified MeetingPlace Web Server when the Application Server is being rebooted. The 8.6 Application Server must be running before you can migrate the Web Server.

To ensure that the Application Server is running, sign in to the CLI as mpxadmin and enter swstatus. For more information about using the CLI, see the Configuration Guide for Cisco Unified MeetingPlace Release 8.6 or the online help in the administrator interface.

Click-to-attend (CTA) links can only be migrated if the Cisco Unified MeetingPlace Release 8.6 Web Server has the same hostname (FQDN) as the Cisco Unified MeetingPlace Release 6.1 MR1 Web Conferencing Server. If the hostname is changed, then a CNAME with the old FQDN can be added in DNS to point to the new primary Web Server. This enables CTA links to function correctly when the hostname is changed.

Before You Begin

Ensure that you completed Backing Up Data from the Source Web Server.

Copy the backup directory from the source web server to the destination web server where you want to restore the data.

This backup directory includes MeetingPlacebackup.bkf and CiscoUnifiedMeetingPlaceWebConferencingRestore.exe.

Ensure that the migration to the new 8.6 Application Server has already been completed.

Ensure that the Microsoft SQL Server account on the new Web Server uses the same username and password as the SQL Server account on the source Web Conferencing Server.

Install the Cisco Unified MeetingPlace Windows operating system on the Release 8.6 Web Server MCS or virtual machine.


Note This restore process takes approximately the same amount of time as the backup.


Procedure


Step 1 Copy CiscoUnifiedMeetingPlaceWebConferencingRestore.exe to the destination computer.

Step 2 Double-click this file.

The Backup or Restore Wizard window displays.

Step 3 Click Next.

Step 4 Select Restore files and settings. Click Next.

Step 5 Click Browse and navigate to your MeetingPlacebackup.bkf file. Click Next.

Step 6 Double-click an item in the left pane to see its contents.

Step 7 Check the items you want to restore. Click Next.

Ensure that all drives and multiple folder options are checked.

Step 8 Click Finish to close the Wizard.

The restore operation proceeds.

Step 9 Click Close to close the Cisco Unified MeetingPlace Restore window.


This completes Step 12 of the Migration Process.

What to Do Next

1. Install the Cisco Unified MeetingPlace Release 8.6 Web Server software on a new Cisco MCS or virtual machine by following the instructions in the Installing the Cisco Unified MeetingPlace Web Server Software module.

2. Synchronizing Meeting Data Between the Cisco Unified MeetingPlace Web Conferencing Server and the Cisco Unified MeetingPlace Application Server.

Synchronizing Meeting Data Between the Cisco Unified MeetingPlace Web Conferencing Server and the Cisco Unified MeetingPlace Application Server

This is Step 13 of the Migration Process. Be sure you have completed Step 12 (Installing the Cisco Unified MeetingPlace 8.6 Web Server) before starting this step.

When you migrated your Cisco Unified MeetingPlace Audio Server data, you selected the historical time period for retaining the history of completed meetings and the meeting participants. Run the mpweb_purge_mtgs.sql script to delete all meetings data (including CTA links) from the Web Server database, that are older than the time period you specified when creating migratedata.zip. See Exporting Data from the Cisco Unified MeetingPlace Release 6.1 MR1 Audio Server.


Note Although synchronization between the Application Server and the Web Server happens automatically, we recommend that you execute this script before starting the Web Server.



Note The script execution takes 15 to 30 minutes, depending on the number of users, meetings, attachments, and recordings. For example, it takes about 5 minutes for a system with about 300,000 profile users and 400,000 meetings with minimal attachments and recordings.


Procedure


Step 1 Stop the Web Server.

a. Choose Settings > Control Panel > Administrative Tools > Services from the Windows Start menu.

b. Stop the Cisco Unified MeetingPlace Web Server and Gateway SIM service.

Step 2 Sign in to the Cisco Unified MeetingPlace Application Server command-line interface as the mpxadmin user.

Step 3 Navigate to the /mpx-record/migrate directory.

Step 4 Run the mpweb_purge_mtgs.sql script. Complete one of the following

Copy mpweb_purge_mtgs.sql to the Cisco Unified MeetingPlace Release 8.6 Web Server. Using SQL Server Management Studio, open and execute mpweb_purge_mtgs.sql against the newly restored Web Server 8.6 database.

Run the following command on the CLI on the Release 8.6 Web Server:

osql -E - S <name_of_8.6_Web_Server>\MPWEBSQL -i <location of mpweb_purge_mtgs.sql_script>

Step 5 Restart the Cisco Unified MeetingPlaceWeb Server and Gateway SIM services (refer to Step 1 and start the services). You can now sign into your Web Server, after completing the migration.


This completes Step 13 of the Migration Process.

Migrating Your Microsoft Outlook Plug-In

This is Step 14 of the Migration Process. Be sure you have completed Step 13 (Synchronizing Meeting Data Between the Cisco Unified MeetingPlace Web Conferencing Server and the Cisco Unified MeetingPlace Application Server) before starting this step.

In Cisco Unified MeetingPlace Release 6.1 MR1, the Microsoft Outlook for Cisco Unified MeetingPlace integration resides on the Web Server. For Cisco Unified MeetingPlace Release 8.6, the Microsoft Outlook for Cisco Unified MeetingPlace integration resides on the Application Server.


Note You can migrate your deployment from Cisco Unified MeetingPlace Release 6.1 MR1 Release 8.6 only. Migrations from other Cisco Unified MeetingPlace 6.x releases to 8.6 are not supported.



Note If you did any web customization on user fields prior to migration, see Configuring User Interface Text for information about reloading these changes after migration. Make sure Cisco Unified MeetingPlace 8.6 Web Server is installed and replication is finished before reloading customization changes (see steps 5 and 11).


This section describes how to migrate Microsoft Outlook users so that users can attend meetings that were scheduled before the migration.

Users can schedule meetings either from Microsoft Outlook (front-end integration), or from Cisco Unified MeetingPlace, through the Cisco Unified MeetingPlace web scheduling interface, Conference Manager, or MeetingTime (back-end integration).

Select the appropriate migration procedure for your deployment, then test your deployment.

Migrating the Microsoft Outlook Users Who Schedule Meetings From Outlook

Migrating the Microsoft Outlook Users Who Schedule Meetings from Cisco Unified MeetingPlace

Testing the Outlook Migration

When the migration is complete, the system will automatically replace all future meeting requests that contain the URL of the Cisco Unified MeetingPlace Release 6.1 MR1 system with the URL of the Cisco Unified MeetingPlace Release 8.6 system.

Before You Begin

Make sure that you have migrated meeting data from Cisco Unified MeetingPlace Release 6.1 MR1 to Cisco Unified MeetingPlace Release 8.6. See Migrating Data from a Cisco Unified MeetingPlace Release 6.1 MR1 System to a Cisco Unified MeetingPlace Release 8.6 System for information.

Ensure that all end users have installed the most recent version of the Microsoft Outlook for Cisco Unified MeetingPlace integration. See the Integration Note for Installing and Configuring Microsoft Outlook with Cisco Unified MeetingPlace Release 8.6 or the online help in the administrator interface for more information.

Manually back up your Outlook notification templates, as these are not migrated.

Migrating the Microsoft Outlook Users Who Schedule Meetings From Outlook

Complete this procedure if your Cisco Unified MeetingPlace system has a front-end integration with the Microsoft Outlook plug-in


Note Ensure that you have already migrated your Cisco Unified MeetingPlace Application Server and Web Server to version 8.6.


Procedure


Step 1 Navigate to the /opt/cisco/meetingplace/migrationtools/current/outlook directory on the Cisco Unified MeetingPlace Release 8.6 Application Server.

This directory contains two files:

mpoutlook.asp—The asp file used to redirect users to the Cisco Unified MeetingPlace Release 8.6 Application Server.

mpolhost.tpl—The template file used to get the hostname (FQDN) of the Cisco Unified MeetingPlace Release 8.6 Application Server.

Step 2 Copy (and overwrite if it exists) the file called mpoutlook.asp to the C:\Program Files\Cisco Systems\MPWeb\Scripts directory on the Cisco Unified MeetingPlace Release 8.6 Web Server.


Note This must replace the previous file with the same name.


Step 3 Copy (and overwrite if it exists) the file called mpolhost.tpl to the C:\Program Files\Cisco Systems\MPWeb\Template directory on the Cisco Unified MeetingPlace 8.6 Web Server.

Step 4 Open the new mpoutlook.asp file.

Step 5 Find the following lines:

Force overwrite of server
strAppServer = http://<new MP8.6 server>
 
   

Step 6 Replace <new MP8.6server> with the fully qualified domain name (FQDN) hostname of the Cisco Unified MeetingPlace Release 8.6 Application Server. Then uncomment this line by removing the single quote.

Step 7 Save and close the file.

Step 8 If your Release 8.6 Web Server has a different IP address (than the legacy Release 6.1 MR1 Web Server), then add the IP address of the new Web Server to the DNS server (so the new IP address is also mapped to the hostname of the old Release 6.1 MR1 Web Server).

By making the change on the DNS server, all requests to this hostname is directed to the new IP address on the Release 8.6 Web Server. No change is required in the Microsoft Outlook plug-in on the client, and users can access both legacy and new meetings.



Note If you re-used the DNS name of your Cisco Unified MeetingPlace Release 6.1 MR1 Web Server for the 8.6 Web Server you will need to perform the following additional steps on the 8.6 Web Server:


1. Open the Internet Information Services (IIS) Manager snap-in.

2. Create a new virtual directory under the Default Web Site.

Set the alias to cgi-bin.

Set the path to the C:\Program Files\Cisco Systems\MPWeb\Scripts directory.

Allow the Read and Run Scripts Permissions.

What to Do Next

Testing the Outlook Migration

Migrating the Microsoft Outlook Users Who Schedule Meetings from Cisco Unified MeetingPlace

This procedure is for users who schedule meetings through the Cisco Unified MeetingPlace web scheduling interface, Conference Manager, or MeetingTime (back-end integration).

Complete these procedures, in this order:

1. Exporting the ICalendarMeetings table from the Cisco Unified MeetingPlace 6.1 MR1 Web Conferencing Server Database to a Text File.

2. Copying the ICalendarMeetings Text File to a Cisco Unified MeetingPlace 8.6 Application Server.

3. Executing the migrateFromMP6MR5.sh Script.

Copying the ICalendarMeetings Text File to a Cisco Unified MeetingPlace 8.6 Application Server

Procedure


Step 1 Using an SSH client, sign in to the Application Server command-line interface as the mpxadmin user.

Step 2 By using SCP file transfer, copy the exported ICalendarMeetings.txt file to the /opt/cisco/meetingplace/migrationtools/current/notifications directory.

Step 3 Continue to the next procedure, Executing the migrateFromMP6MR5.sh Script.


Executing the migrateFromMP6MR5.sh Script


Caution Only execute the migrateFromMP6MR5.sh script as part of the Microsoft Outlook plug-in migration from Cisco Unified MeetingPlace 6.1 MR1 to Cisco Unified MeetingPlace 8.6. Do not execute this script on a live Cisco Unified MeetingPlace 8.6 system, or you will overwrite Outlook meetings data.


Note Ensure that you have created the ICalendarMeetings.txt file and copied it to the Cisco Unified MeetingPlace 8.6 Application Server.


The time to complete this procedure depends on the size of your ICalendarMeetings table. For example, an ICalendarMeetings table with 12,500 records and a file size of approximately 1.5 MB takes approximately 10 minutes.

Procedure


Step 1 Change to the root user by entering su - and enter the root password.

Step 2 Navigate to the /opt/cisco/meetingplace/migrationtools/current/notifications directory.

The migrateFromMP6MR5.sh script and the ICalendarMeetings.txt file should be in this directory.

Step 3 Execute the migrateFromMP6MR5.sh script.

>./ migrateFromMP6MR5.sh ICalendarMeetings

After execution, the script reports the total number of inserted, updated, and skipped NotifItemInfo records. The script also creates the migrateFromMP6MR5.log file in the same folder.


What to Do Next

Testing the Outlook Migration

Testing the Outlook Migration


Note Ensure that you have already upgraded your Cisco Unified MeetingPlace Web Server to Release 8.6, before completing this procedure.


Procedure


Step 1 On the server with the Microsoft Outlook client, enter the URL of the executable file to download the new MeetingPlace 8.6 Outlook plugin.The URL has the format:

http://<App server host name>/outlook/public/setup.exe

Step 2 When prompted, download the new plugin and install it.

Post-Migration Steps

This is Step 15 of the Migration Process. Be sure you have completed Step 14 (Migrating Your Microsoft Outlook Plug-In) before starting this step.

If you are using a Hardware Media Server in your deployment, then you need to configure your audio and video blades on Cisco Unified MeetingPlace Release 8.6. Use the same IP address, as before the migration, for each MCU.

This completes Step 15 of the Migration Process.

Testing that the Migrated System Works Correctly

This is Step 16 of the Migration Process. Be sure you have completed Step 15 (Post-Migration Steps) before starting this step.

Once your migration to Cisco Unified MeetingPlace 8.6 is complete, we suggest you run some functional tests on the new system, tailored to your system configuration.

Before turning off maintenance mode on your Release 8.6 Application Server

Confirm that all the users' recorded names have been copied into their respective user profile subdirectories. There must be no wav or refcnt files in the /opt/cisco/meetingplace/afs/custom/userprofile directory.


Caution If a user attempts to start a meeting before the user's recorded name has been copied to the subdirectory, than the user profile becomes unusable, and cannot be repaired.

On the command-line interface:

Check that all the appropriate services are running.

On the Administration Center:

Add a new user.

Edit an existing user.

Delete an existing user.

Add a new group.

Delete an existing group.

On the Cisco Unified MeetingPlace web scheduling interface:

Schedule a meeting.

Attend a meeting.

Reschedule a series of recurring meetings.

Reschedule a single meeting.

Delete a single meeting.

Delete a series of recurring meetings.

Delete a single future meeting.

Open the attachment of a future meeting.

Play an audio and web recording.

On the phone user interface:

Play recorded usernames.

This completes Step 16 of the Migration Process.