Guest

Cisco Unified MeetingPlace

MeetingPlace Web Patch Installation Package Steps for Deployment

Cisco - MeetingPlace Web Patch Installation Package Deployment Procedure

Document ID: 51040

Updated: Jan 31, 2006

   Print

Introduction

Cisco MeetingPlace Web patches are now distributed through a Patch Installation Package format with a lightweight installer.

The Patch Installation Package is provided in a zip or self-extracting .exe file with this filename pattern:

  • MPWEB<release#>_<build#>_<patch#>.zip

  • MPWEB<release#>_<build#>_<patch#>.exe

Where:

  • release# - The major version of the software (for example, 427 for 4.2.7 or 430 for 4.3.0).

  • build# - The full build / installer number (for example, 106 for 4.2.7.106 or 63 for 4.3.0.63).

  • patch# - The maximum patch level included in this package.

Patches are developed on top of a full installation version and are identified by a fifth number, such as 4.2.7.106.20 (patch level 20 for Cisco MeetingPlace Web version 4.2.7.106) or 4.3.0.63.6 (patch level 6 for Cisco MeetingPlace Web version 4.3.0.63).

The Patch Installation Package is cumulative. For example, 4.2.7.106.20 package contains all patches from 1 to 20. In order to ensure the stability and consistency of the overall installation, installing patch level 5 causes all earlier patches (for example, from 1 to 5) to be installed.

The patch installer also warns you of any incompatibilities due to customizations on your server regarding a database of standard files for your particular Cisco MeetingPlace Web version. If your server has been customized, you need to obtain customized files from Cisco MeetingPlace Customization Services and include them in the standard Patch Installation Package. You will then be able to install the patch while maintaining your customizations. Details are described under the Installation Package Deployment Procedure section.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on Cisco MeetingPlace Web versions 4.2.7.106 and later.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Installer Features

The Patch Installation Package has three main features:

  • File Consistency Check

    Check the consistency of your existing Cisco MeetingPlace Web installation without having to stop the MeetingPlace Web services. This feature verifies the presence, version, size, checksum and timestamp of all the files that are part of a standard Cisco MeetingPlace Web installation, in order to determine if some files have been changed (customized) or are in an inconsistent state (file is missing, version differs, and so forth).

  • Patch-level Compatibility Check

    Test the compatibility of your existing Cisco MeetingPlace Web installation with all the patch levels included in this Patch Installation Package, without having to stop the MeetingPlace Web services. This is required to make sure that installing a specific patch level is not going to break the customizations already deployed on the server. If the server has no customizations, this feature confirms that the server is compatible with all patch levels included in the installation package.

  • Patch Installation

    Install a specific patch level on your server. This option requires that you stop the Cisco MeetingPlace Web and IIS services first. The installer upgrades the Cisco MeetingPlace Web installation to the desired patch level, and re-applies your customizations if the standard package was extended with the Customization Package from the Cisco MeetingPlace Customization Services.

Utilization Scenarios

Server with No Customizations

Use the latest standard Patch Installation Package compatible with your Cisco MeetingPlace Web release.

  • Option 1 – Verifies the consistency of your installation.

  • Option 2 – Confirms that you can upgrade to any patch level.

  • Option 3 – Allows you to upgrade to any patch level.

Server with Customizations

You can use the latest standard Patch Installation Package compatible with your Cisco MeetingPlace Web release.

  • Option 1 – Verifies the consistency of your installation and analyzes which files have been customized.

  • Option 2 – Determines which patch levels require an update of your customizations. If the installer determines that a particular patch level cannot be safely applied because of customizations, contact Cisco MeetingPlace Customization Services to request an updated customization appropriate for your server.

  • Option 3 – Allows you to upgrade to a desired patch level and reapply the appropriate customizations, provided that you have extended the standard package with the Customization Package that you received from Cisco MeetingPlace Customization Services.

Installation Package Deployment Procedure

Follow this procedure.

Note: See the Introduction section above for details on the files contained within the Patch Installation Package.

  1. Download the latest version of the Patch Installation Package (registered customers only) to your Cisco MeetingPlace Web server.

    Note: Verify what MeetingPlace Web release is running on your server so that you download the correct package for your MeetingPlace Web release.

    Note: If WinZip is not installed on your server, be sure to download the self-extracting .exe version of the package.

  2. Create a temporary folder on the server, such as C:\Temp\Patch. Make sure this folder is empty.

  3. Extract the standard Patch Installation Package into this temporary folder.

    Extract the package into a temp folder. You cannot run the installer directly from the WinZip application window.

  4. Double-click on the installer.exe program.

    The installer is text-based and launched in a command prompt on your Windows desktop.

  5. Wait for the installer to gather information about your system (initialization step).

    When finished, a menu option appears:

    Latitude Communications Patch Installer V1.0
    
    ============================================
    
    Product detected: MeetingPlace Web Conferencing.
    
    Install location: C:\Latitude\MPWeb
    
    Version: 4.2.7.106.3
    
    Patch Installation Package level: 20
    
    1) Check system files consistency
    
    0) Exit
    
    Select:

    In the example above, the installer has detected Cisco MeetingPlace Web installed in folder C:\Latitude\MPWEB. The main version is 4.2.7.106 and the current patch level is 3. The Patch Installation Package used here contains all patches up to level 20.

  6. Select 1 and hit Enter to start the installation consistency check.

    The installer verifies every file in your installation and outputs a message for each file that does not correspond to the official version stored in the master file list.

    If the installer detects an inconsistency, it displays one of the following messages:

    • <file_name> is missing.

      The <file_name> file is not present in your Cisco MeetingPlace Web installation. Certain files are not installed depending on the installation options you chose. For example, "audio service" related files are not installed if you chose basic installation, or files in the Templates folder are not installed on an external server in a DMZ-C configuration. The list of missing files can be reviewed to ensure that your installation is not corrupted.

    • <file_name> is at patch level <x> (instead of <y>).

      The patch level for the file <file_name> is not the one that was expected. This can indicate an inconsistent patch installation on your system. Note that the first time you run the installer, it is not known what patch level is installed and it is assumed patch level 0 (no patches installed). If a patch level has been installed before, you will receive numerous "<file_name> is at patch level X (instead of 0)" messages. This is normal.

    • <file_name> is customized.

      The <file_name> file content does not match the content of the original file and its timestamp value is higher than one of the original files. The installer therefore assumes this file has been customized.

    • <file_name> is customized (overwritten by file <other_file_name>).

      The <file_name> file content does not match the content of the original file but corresponds to another file that is part of the Cisco MeetingPlace Web distribution. The installer therefore assumes that this file has been customized by replacement with another file (typical context: templates for internal / external servers in DMZ configurations, mpagent.exe and mpagentext.exe - the secure version of mpagent.exe for external sites – in the DataSvc folder, and so forth).

    • <file_name> is customized with incorrect timestamp (<= <ts_value>). Possible version mismatch.

      The <file_name> file is detected as a customized file but its timestamp value is too low and indicates a possible version mismatch. This occurs when the Cisco MeetingPlace Web installation is supposed to be at patch level <x> and the customized file timestamp is lower than the timestamp (<ts_value>) of the original file that is compatible with patch level <x>.

    • <file_name> is based on patch level <x> or below.

      This is an extension of the previous message that gives more details about the possible version mismatch. Based on its incorrect timestamp, it appears that <file_name> has been customized based on patch level <x> of the original file (or even below, the installer cannot figure out). If the Cisco MeetingPlace Web installation is supposed to be at patch level <y>, this gives you an indication of the possible discrepancy for this specific customized file.

    • <file_name> is based on an earlier release of the product (according to its timestamp).

      The <file_name> file does not correspond to any official version in this release (including all possible patched versions of the file) and its timestamp is lower than one of the base (patch level 0) versions. Therefore, the file appears to come from an earlier release of the product. This is a possible upgrade problem (the file has not been upgraded to the current release).

  7. The installer now displays two options in the menu:

    Latitude Communications Patch Installer V1.0
    
    ============================================
    
    Product detected: MeetingPlace Web Conferencing.
    
    Install location: C:\Latitude\MPWeb
    
    Version: 4.2.7.106.3
    
    Patch Installation Package level: 20
    
    
    1) Check system files consistency
    
    2) Check system compatibility with patch level
    
    0) Exit
    
    Select:
  8. Select 2 and press Enter to start the patch level compatibility check.

    The installer verifies the compatibility of each patch level (higher than the currently installed patch level) with your server based on:

    • Whether you have any customized files.

    • What existing customized files will be overwritten if you upgrade to a particular patch level.

    • Whether you have extended the standard package with new customized files from Customization Services.

    When you select this option, some information is displayed before the actual tests begin:

    Latitude Communications Patch Installer V1.0
    
    ============================================
    
    Option selected: Check system compatibility with patch level.
    
    System current patch level: 3
    
    Patch Installation Package level: 20
    
    Checking files compatibility up to patch level 20
    
    Checking files for compatibility with patch level 4
    

    At this point, the installer is testing compatibility of each patch level higher than the currently installed patch level. For each level x tested, the following messages can be displayed:

    • <file_name> needs to have its customizations updated.

      The <file_name> file has been detected as customized on your system, and upgrading to patch level <x> requires updating this file (among others) with a new version. Therefore the customizations in place on your server are erased by the upgrade.

    • <file_name> needs to be upgraded to current release (and possibly have its customizations re-applied).

      The <file_name> file has been detected as coming from an earlier release (and possibly customized) on your system, and upgrading to patch level <x> requires updating this specific file (among others). To ensure system consistency, you must make sure that the version of this file is compatible with the Cisco MeetingPlace Web release that you are using (and that customizations are applied, if necessary).

    At the end of the verification process, a summary is displayed by the installer. One of these three messages is displayed:

    • This system is not compatible with any patch level.

    • This system is compatible with all patch levels.

    • This system is compatible with the following patch level(s): (list of patch levels you can safely upgrade to without breaking your customizations).

  9. If the installer determines that a particular patch level that you want cannot be safely applied because of customizations, contact Cisco MeetingPlace Customization Services to request updated customizations appropriate for your server.

    1. Send the install.log file generated by the installer to the Cisco MeetingPlace Customization Services and request a Statement of Work (SOW) to have your customizations updated.

      Note: Updated customizations are only provided for the most recent patch release of your customer's current software version.

    2. Cisco MeetingPlace Customization Services will send you a Customization Package that contains updated customizations.

    3. When you receive the Customization Package, extract it into the same temporary folder that you created in step 2. The contents of the Customization Package are extracted into the \Customizations subfolder and the installer is now aware of the available customizations for your server.

    4. Re-run the install.exe program and go through options 1 and 2 again.

  10. The installer now displays three options in the menu:

    Latitude Communications Patch Installer V1.0
    
    ============================================
    
    Product detected: MeetingPlace Web Conferencing.
    
    Install location: C:\Latitude\MPWeb
    
    Version: 4.2.7.106.9
    
    Patch Installation Package level: 20
    
    1) Check system files consistency
    
    2) Check system compatibility with patch level
    
    3) Upgrade to higher patch level
    
    0) Exit
    
    Select:
  11. Select 3 and press Enter if you want to upgrade your installation to a higher patch level:

    Latitude Communications Patch Installer V1.0
    
    ============================================
    
    Option selected: Upgrade to higher patch level.
    
    System current patch level: 9
    
    Patch Installation Package level: 20
    
    This system is compatible with the following patch level(s): 10,11,12,13,14
    

    Note:  If you want to upgrade to a non-compatible patch level, please contact Cisco Technical Support to have a case opened in order to make arrangements to update the customizations against this specific patch level before you upgrade. NOT DOING SO WILL BREAK SOME OR ALL OF THE CUSTOMIZATIONS CURRENTLY INSTALLED ON THIS SYSTEM.

    Pre-requisite: IIS Admin, World Wide Web Publishing Service 
    and all MeetingPlace Web services need to be stopped before 
    upgrading to a higher patch level.
    
    Enter patch level [10-20] to upgrade to (0 to exit):
  12. Carefully review the information provided before proceeding.

    In the example above, your installation is at patch level 9, and you can safely upgrade only to levels 10 to 14. Upgrading to level 15 through 20 will break some or all of the customizations on your server. Before upgrading, you must also ensure that Cisco MeetingPlace Web services and IIS related services are stopped. Upgrading while your Cisco MeetingPlace Web system is running is not possible.

  13. Enter the patch level you want to upgrade to and press Enter. The installer upgrades your system:

    Enter patch level [10-20] to upgrade to (0 to exit): 14
    
    Checking services status.
    
    Installing patch level 10
    
    5 file(s) copied.
    
    Installing patch level 11
    
    13 file(s) copied.
    
    Installing patch level 12
    
    1 file(s) copied.
    
    Installing patch level 13
    
    1 file(s) copied.
    
    Installing patch level 14
    
    8 file(s) copied.
    
    Updating customizations by copy over.
    
    8 file(s) copied.
    
    Upgrade completed.
    
    29 file(s) copied.
    
    MPWEB Version registry key set to: 4.2.7.106.14.
    
    Detailed information for this session has been logged to file: Install.log.
    
    Press any key to exit now.
  14. After the upgrade has been completed, the only option remaining is to exit the installer.

    Press any key to exit. The installer has updated a registry key to reflect the new patch level available on this server. This information is displayed when connecting on the home page of your Cisco MeetingPlace Web server. All information related to this installation session has been logged to the file install.log in your temporary folder. Cisco recommends you archive this file in case Cisco Technical Support needs it for further troubleshooting of your system.

  15. You can keep or delete the temporary folder that you used to extract the Patch Installation Package (and Customization Package, if any).

    You may want to keep the standard Patch Installation Package (and Customization Package, if any) in case you need to use them again in the future (for instance, re-installation of the server software, and so forth).

Related Information

Updated: Jan 31, 2006
Document ID: 51040