Lotus Notes Standard Fix Pack 1 Cumulative Client Hotfix 1 (FP1 CCH1) for 8.0.2

 Fix readme

 

AbstractThis file contains information you need for installing and running Lotus Notes Fix Pack 1 Cumulative Client Hotfix 1 (FP1 CCH1) for the 8.0.2 build. This file also contains information about the SPRs included in this build.

The hotfix is available for download at Fix Central: http://www.ibm.com/support/fixcentral/.

This hotfix ALSO includes all fixes from Notes 8.0.2 Fix Pack 1 (FP1). This Client Cumulative Hotfix replaces Client Cumulative Hotfixes 1 , 2 and 3 for the Notes 8.0.2 build.

Note also that there are no plans to develop an 8.0.2 CCH4. For the Notes 8.0.2 build, customers should install FP1 and/or CCHs on top of FP1.

You can install this FP1 CCH1 on top of 8.0.2, or 8.0.2FP1. (You can go directly from 8.0.2 to 8.0.2FP1 CCHx without installing the FP1 first.)  

Content

Table of Contents

1.0 Files Included2.0 Getting Help3.0 Installing4.0 SPRs Included in this CCH

1.0 Files Included

The files included in this CCH are:

802FP1CCH1_W32.exe - installation file

2.0 Getting Help

Go to http://www.ibm.com/software/lotus/support/notes/support.html

3.0 Installing

This Help document is divided into the following sections:

SECTION 1 – General InformationSECTION 2 – Performing a Cumulative Client Hotfix installSECTION 3 – Removing a Hotfix InstallationSECTION 4 – Applying a Hotfix to a Client that Already has a Hotfix AppliedSECTION 5 – Using the Cumulative Client Hotfix Installer with Domino’s Smart Upgrade FeatureSECTION 6 – Important Note

SECTION 1 – General informationA Cumulative Client Hotfix (CCH) is a bundle of hotfixes for the Lotus Notes Client. CCHs are intended to address the more critical problems that have been identified in a shipping maintenance release. Defects addressed in the CCH have gone through a limited test cycle.

The Cumulative Client Hotfix Installer is packaged as a single executable. This executable's name is comprised of the base version of the Notes client for which the hotfix was created, followed by the CCH version, and then followed by the platform for which it is built. In most cases the platform will be W32. For example, the first CCH for an 8.0.2 Notes client will be named: 802CCH1_W32.exe

SECTION 2 – Performing a Cumulative Client Hotfix installThe executable for the Hotfix Installer can be run either through the Windows GUI by double-clicking the executable or via a command line to start the install with GUI input requiring user input.

NOTE 1: If running on 802IFR1, a prior CCH was installed. This CCH may be installed on the existing configuration without any additional action.

NOTE 2: Please note that if you un-install this FP1 CCH1 hotfix, the Notes Client will revert back to 8.0.2. This is despite if you install FP1 CCH1 on top of 8.0.2, or 8.0.2FP1.

For 8.x HotfixesBeginning with 8.x, the installer now uses the Microsoft Installer and therefore command line options that are available for use with MSI are now available with the Cumulative Client Hotfix Installer. Starting with 8.0.2 Hotfixes, the silent parameter (/s) may be used. This will allow administrators to use Smart Upgrade and enable the correct parameters to silently install hotfixes on users machines.

For all Hotfixes:When the Cumulative Client Hotfix Installer is run for the first time on a base version (for example, an 8.0.2 Notes client with no previous hotfixes applied) it will:

Identify the current release of the product

Create a backup directory called RCHBackup

Update version information of the client. This can be verified through the Help -> About Notes menu item (e.g., the string would change from Release 8.0.2 to Release 8.0.2 CCH3).

Move the files that are being "replaced" by the installer to the RCHBackup after they have been compressed into a file called "undo.db"

Create a HOTFIX.INI file in the root of the Notes Program directory (typically the "Notes" directory), which documents information about the hotfix that has been applied

Place a copy of the installer itself into the RCHBackup directory

Create the file LotusInstall.log which is located in the C:\Documents and Settings\%USERNAME%\My Documents directory

ADDITIONAL NOTES: It is imperative that the HOTFIX.INI and RCHBackup directory (and its contents)

remain intact and unchanged. Tampering with either may result in undesirable outcomes when it comes time to remove a CCH or apply a new CCH on top of the currently installed CCH.

SECTION 3 – Removing a Hotfix installationTo remove a hotfix and return the client to the base release, the Hotfix installer should be run a second time. The installer should not be run from the RCHBackup directory for reversion. Instead it should either be copied from its original source to the local machine on which the reversion is desired into a directory other than RCHBackup, or a copy of the installer from the RCHBackup directory should be placed into a different local directory where it can then be run from. This is important so that during the removal process the RCHBackup directory can be cleaned up properly. The same command line options still apply.

IMPORTANT NOTE: Please note that if you un-install this FP1 CCH1 hotfix, the Notes Client will revert back to 8.0.2. This is despite if you install FP1 CCH1 on top of 8.0.2, or 8.0.2FP1.

In order for this process to run properly, it is imperative that the HOTFIX.INI and RCHBackup directory (and its contents) remain intact and unchanged. If either have been removed or modified removal of the hotfix will fail and/or have other undesirable side effects.

When the Hotfix Installer is run a second time in order to revert the client back to its base version, it will:

Identify the current release of the product (e.g., 802FP1 CCH1)

Verify the existence of "undo.db" in the RCHBackup directory and HOTFIX.INI in the Notes program directory

Revert version information of the client. This can be verified through the Help ->

About Notes menu item. (e.g., the base release string will appear once again instead of the hotfix string; that is, the string could change from Release 8.0.2 FP1 CCH1 to Release 8.0.2)

Decompress the files in the "undo.nb" and verify their checksums against the values stored in the HOTFIX.ini

Replace the decompressed files in the Notes Program directory

Delete the HOTFIX.ini and RCHBackup directory including its contents

Log informational messages and/or errors in the UPGRADE.LOG (this file is not cleaned up, it will contain previous log information)

SECTION 4 – Applying a Hotfix to a client that already has a Hotfix appliedIf a subsequent hotfix needs to be applied to a client that already has a hotfix applied, the original fix must be combined with the new fix and a new hotfix installer containing all of the fixes (hence the name Cumulative Client Hotfix) will be distributed.* When the new Hotfix installer is run, the original hotfix will be detected and the Installer will restore the client back to its base version. Similarly to when a hotfix is removed, in order for this process to run properly, it is imperative that the HOTFIX.INI, and RCHBackup directory (and its contents) remain intact and unchanged. It will then apply itself by backing-up and applying files as described earlier. When applying a new CCH on top of an already existing CCH, the same command line options can be utilized if desired.

*It is not guaranteed that a subsequent hotfix will be combined with an already existing hotfix.

SECTION 5 – Using the Cumulative Client Hotfix Installer with Domino’s Smart Upgrade FeatureThis Cumulative Client Hotfix Installer can be used with Domino's Smart Upgrade Feature. The same procedures should be followed for this Installer as is documented in the Administrator Help database. For all 8.x hotfixes and above, you can use the MSI options.

To remove a CCH using SmartUpgrade the hotfix version should be specified as the "Source Version" in the kit document. The "hotfix version" can be found on the Help->About Notes splash screen. (e.g., Release 8.0.2FP1 CCH1) The "Destination Version" can either be specified as the base release (e.g., Release 8.0.2) or as a wildcard (*). These settings also apply if you are attempting to apply a subsequent Hotfix to clients which already have a Hotfix applied.

SECTION 6 – Important NoteInstallation by any method other than with the installer in which a Cumulative Client Hotfix is packaged is not supported.

4.0 SPRs Included in this CCH The first table lists SPRs fixed in 802FP1 CCH1 that impact both the Basic Client and

Standard Client The second table lists SPRs fixed in 802FP1 CCH1 that impact only the Standard

Client Important Note

This table lists SPRs fixed in 802FP1 CCH1 that impact both the Basic and Standard Client

SPR Description

JMAN7K3RDN Forces the local mail file preferred server to be the current home server

DDES7KPR9M Fix a client crash when deleting workspace icon

RBOD7GVSMS Mail file owner field changed when switching locations/IDs w/synchronize contacts enabled

KKOO7D6DQ3 Fix the text that is being cut off when printing or previewing Monthly calendar

LMAN7JAHPG Should be able to archive folders, then remove them from mail file

This table lists SPRs fixed in 802FP1 CCH1 that impact only the Standard Client

SPR Description

SKIN7KFQG5 Fix a Client crash

LMAU7KVQGC Fix crash when trying to accept a meeting invite or update

RBEO7GVLCJ Crash cancelling a meeting from the calendar sidebar

CMAS7LKPD7 Fixed general instability caused by memory corruption when reading PAB data

AGUD7DSU3Q Queryclose cannot prevent user closing document

TBOO7J7GH2 Fix error reported when opening repeating calendar entries

AEDS7P4KD5 8.02CCH3 and later hotfixes notes.jar fails to authenticate where rcpinstall.properties settings missing/being misread

SRAO7P6S8M 8.02CCH3 and later hotfixes notes.jar fails to authenticate on first launch if the workspace does not exist

DMOE7KXQ6F Trash icon missing from Inbox view

RPAS7KPPZ8 Activities in sideshelf - Activity gets Tuned Out when tag is edited

LFOS7K9SVF Hotfix on an existing 8.0.2 client breaks RSS Feeds

DBRK7LXE6V Hebrew words in reverse order in 'Day-At-A-Glance' for meeting

XLZG7KTSML Error an internal error occurred during buddyListPolicyJob

CJKE7M8KWD Embedded Sametime brokerbridge feature (Office Integration channel) stops on machine hibernate

KRED7CAPZW Location popup not appearing over VPN