Cisco Unified MeetingPlace, Release 6.x -- How to Replace a Web Server and Retain the SQL Database

From DocWiki

Jump to: navigation, search

Cisco Unified MeetingPlace, Release 6.x > Web Conferencing > Configuring > Web Conferencing and SQL Server




During installation, a MPWEB database is tied to a specific Cisco Unified MeetingPlace web server through a unique GUIDWebID that is generated by the Cisco Unified MeetingPlace Web Conferencing installer and stored in the registry and SQL database. Therefore, if you want to transfer the MPWEB SQL database and all attachments from the old server to a new server, the new server must use the same GUIDWebID as the old server. This requires preparing the following three components from the old server to the new server:

  • The whole \MPWEB\Meetings folder (including all sub-folders) in zipped or unzipped format.
  • The GUIDS.reg file with modifications to add the GUIDWebID and the mpweb slave database filename information. The GUIDS.reg file, as well as the GUIDWebID and DBName registry values, come from the old server.
  • A backup of the MPWEB database and mpweb slave database(s) from the old server.


To replace an existing Cisco Unified MeetingPlace web server with a new server and retain the attachments of past meetings so that they are accessible from the new server, do the following procedures in the order shown:

To Prepare the Current Cisco Unified MeetingPlace Web Server
  1. Stop all Cisco Unified MeetingPlace Web Conferencing services, including the Gateway SIM service.
    For instructions, see the Stopping All Cisco Unified MeetingPlace Web Conferencing Services.
  2. Detach this Cisco Unified MeetingPlace web server from the Cisco Unified MeetingPlace Audio Server.
    1. Open the Gateway SIM Agent.
      For instructions, see the Opening the MeetingPlace Gateway Configurations Utility.
    2. From the Gateway SIM tab, write down the hostname or IP address of the Cisco Unified MeetingPlace Audio Server for future reference.
      Note: You must use the same server reference when you install the new Cisco Unified MeetingPlace web server. If the Audio Server is specified as a hostname, you will enter that same hostname; if it is specified as an IP address, you will use an IP address later.
    3. Detach this Cisco Unified MeetingPlace web server from the Audio Server by clicking Delete Unit .
  3. Make a copy of the entire \MPWEB\Meetings folder and its contents.
  4. Make a copy of the GUIDS.reg file.
    You can find this file where Cisco Unified MeetingPlace Web Conferencing application files are stored.
  5. Open regedit and obtain the registry values for GUIDWebID and DBName.
    Caution! Ensure that the registry values are correct. Compare the values that you obtained in Step 5 against what you enter in Step 6.
  6. Open GUIDS.reg in a text editor and add the GUIDWebID and DBName registry paths and key values.
  7. Save the file with these changes.
  8. Make a backup of the MPWEB database and the mpweb slave database(s).
    For instructions, see the How to Back Up and Restore MPWEB SQL Database.
  9. Copy the attachments, GUIDS.reg and the MPWEB backup, to the new server.
  10. Continue with the To Install the Replacement Cisco Unified MeetingPlace Web Server.
To Install the Replacement Cisco Unified MeetingPlace Web Server

You must install the same release of Cisco Unified MeetingPlace Web Conferencing or later on the new server as is running on the old server. For example, if you are running Release 6.0 on the old server, you must install Release 6.0 or a later release on the new server.


Before you install Web Conferencing on the new server, you must run GUIDS.reg on the new server to add the following four keys in to the registry: GUID IDs for Site, System, Web, and mpweb slave db filename. To run GUIDS.reg, right-click GUIDS.reg, then choose merge .


  1. Install Cisco Unified MeetingPlace Web Conferencing.
    For instructions, see Installing and Upgrading Web Conferencing.
  2. When you are prompted at the end of the installation, reboot the server.
    After the initial reboot, the installation program continues and may reboot a few more times to complete the installation.
  3. When you are prompted for the Cisco Unified MeetingPlace Audio Server information, enter the value that you wrote down in Step 2 of the To Prepare the Current Cisco Unified MeetingPlace Web Server.
  4. After the installation completes, verify that Cisco Unified MeetingPlace Web Conferencing is functional.
  5. Continue with the To Build the Replacement Cisco Unified MeetingPlace Web Server.
To Build the Replacement Cisco Unified MeetingPlace Web Server

Verify that the release of Cisco Unified MeetingPlace Web Conferencing that is installed on the new server is either the same or later than the release installed on the old server. For example, if you are running Release 6.x on the old server, you must be running Release 6.x or a later release on the new server.


  1. Stop all Cisco Unified MeetingPlace Web Conferencing services.
  2. Delete the MPWEB SQL database that is created automatically during the Cisco Unified MeetingPlace Web Conferencing installation by using either Enterprise Manager or the osql drop database command.
    For more information about this osql command, see the To Restore the Database.
  3. Restore the old MPWEB database on to the new server by using either Enterprise Manager or the osql restore database command.
    For more information about this osql command, see the To Restore the Database.
  4. Delete all contents in the \MPWeb\Meetings\ folder.
  5. Restore all the files and attachments from the old server in to \MPWeb\Meetings folder.
  6. Reboot the server.
    or
    Restart the Cisco Unified MeetingPlace Web Conferencing service.
  7. Access the home page and log in with a System Manager profile to make the appropriate changes in the Web Server administrative pages, such as the web server Hostname.

Rating: 0.0/5 (0 votes cast)

Personal tools