Zimbra Releases/8.8.8/P3

Zimbra Collaboration 8.8.8 Patch 3 GA Release

Check out the "Fixed Issues", "Zimbra NG, Chat, Talk Changelog" and "Known Issues" for this version of Zimbra Collaboration. Please refer "Patch Installation" section for Patch Installation instructions. As always, you’re encouraged to tell us what you think in the Forums, or file a bug in Bugzilla.

Software changes

Fixed Issues (Bugzilla query)
108948	Admin console shows chat service as "Stopped" and if admin starts the service chat become unusable
108506	Different date shown for Recurring Appointment Instance

Zimbra NG, Chat, Talk Changelog
Mobile NG: Removed parameter of DeleteItemAction to move item to trash in favor of MoveItemsAction. This will correctly synchronize Deletion of shared appointments on iPhone. DeleteAsMove is also taken in care from Sync Collection
HSM NG: Reviewed MailboxMoveOperation error threshold and corrected. Worked on single account level and skip the account when (1) any errors occur during account stage (2) more than 5% errors in blobs stage for the specific account. No failure in case of errors in backup stage. Added read_error_threshold parameter to doMailboxMove command to handle error notification when mailboxmoveoperation fails due to too many errors
Admin: Added OperationGroup.SKIP_LICENSE_CHECK so now ModuleLicensedPolicy.canBeQueued() can enqueue operation even if module is not licensed. Added DeleteAllDelegatedRightsOperation to OperationGroup.SKIP_LICENSE_CHECK group.
Admin Zimlet: Replaced teamChatGroupLimit attribute label in domain and global modifier with "Max no. of users in groups" Backup module: Fixed Undelete Account Wizard on last step to popdown wizard on clicking finish on last step. Import Wizard - there are no accounts to import even if there should be HSM Module - “doMoveBlobsRequest” Request(that triggered clicking apply HSM policy now) response is correctly handled avoiding access to undefined objects and showing the correct dialog HSM Module - Added "Cancel" button in HSM Primary Volumes editing dialog. HSM Volume - DoDeleteVolumeRequest response is correctly handled avoiding access to undefined objects and showing the correct dialog HSM Module - fixed doDeduplicateRequest creation and response menagement restoring the expected behavior HSM Module -> Added "Cancel" button in HSM policy editing dialog

Known Issues
[TBD ]	TBD

Patch Installation

8.8.8 Patch 3 Change: Please read! 8.8.8 Patch3 (zimbra-patch) checks if your system is Network Edition and if so adds a new Network Edition-only package repository. As a result, after 8.8.8 Patch3 installation is completed, Network edition customers will need to run another package update/upgrade process to obtain the updated Network Edition only packages available from newly added package repository.

Before Installing the Patch

Before installing the patch, consider the following:

• Patches are cumulative.
• A full backup should be performed before any patch is applied. There is no automated roll-back.
• Zimlet patches can include removing existing Zimlets and redeploying the patched Zimlet.
• Only files or Zimlets associated with installed packages will be installed from the patch.
• Switch to user zimbra before using ZCS CLI commands.
• Important! You cannot revert to the previous ZCS release after you upgrade to the patch.
• Important Note for ZCS Setup with Local ZCS repository: Customers who have setup local ZCS repository should first update the local repository by following instructions in wiki

Install the Patch

Note: This patch should be installed only on all mailbox nodes running in your environment.

With 8.8.8 Patches, customers would not need to download any ZCS Patch builds. Patch packages can be installed by using Linux package management commands.

• Please make note that, installing zimbra-patch package only updates the Zimbra core packages. administrator would need to upgrade other applicable packages like zimbra-chat, zimbra-network-modules-ng, zimbra-talk.

• Note regarding Chat and Talk package conflict
  • zimbra-chat and zimbra-talk packages conflict each other.
  • Ubuntu will ask user's confirmation before removing already installed package and installing the conflicting package.
  • Redhat will give error if conflict found and user will have to remove installed package before installing conflicting package.

Please refer below steps for 8.8.8 Patch3 installation on Redhat and Ubuntu platforms:

Redhat

Installing zimbra packages individually

Install/Upgrade zimbra-patch for FOSS and NETWORK

• As root, install the patch. Type

yum clean metadata 
yum check-update 
yum install zimbra-patch

• Switch to user zimbra

su – zimbra

• ZCS must be restarted to changes to take effect. Type

zmcontrol restart

Install/Upgrade zimbra-chat for FOSS and NETWORK

• Make sure you already installed/upgraded zimbra-patch before this step. Please see 8.8.8 Patch 3 Change
• As root, Type below command.

yum install zimbra-chat 

• Switch to user zimbra

su – zimbra

• Zimbra mailbox service must be restarted to changes to take effect. Type

zmmailboxdctl restart

Install/Upgrade zimbra-talk and zimbra-network-modules-ng (NETWORK Only)

• Make sure you already installed/upgraded zimbra-patch before this step. Please see 8.8.8 Patch 3 Change
• As root, Type below command.

yum clean metadata 
yum check-update 
yum install zimbra-network-modules-ng
yum install zimbra-talk

• Switch to user zimbra

su – zimbra

• Zimbra mailbox service must be restarted to changes to take effect. Type

zmmailboxdctl restart

Installing zimbra packages with system package upgrades

• As root, type below command to clear yum cache

yum clean metadata

• As root, type below command first time so the server sees there is a new zimbra-patch package in the 888patch repository (and any other available operating system and Zimbra common package updates)

yum check-update

• As root, type below command to allow the patch, if necessary, to add the new Network Edition patch repository.

yum install zimbra-patch 

• As root, type below command to update most available packages.

yum update

• Switch to user zimbra

su – zimbra

• ZCS must be restarted to changes to take effect. Type

zmcontrol restart

Ubuntu

Installing zimbra packages individually

Install/Upgrade zimbra-patch for FOSS and NETWORK

• As root, install the patch. Type

apt-get update
apt-get install zimbra-patch

• Switch to user zimbra

su – zimbra

• ZCS must be restarted to changes to take effect. Type

zmcontrol restart

Install/Upgrade zimbra-chat for FOSS and NETWORK

• Make sure you already installed/upgraded zimbra-patch before this step. Please see 8.8.8 Patch 3 Change
• As root, Type below command.

apt-get install zimbra-chat 

• Switch to user zimbra

su – zimbra

• Zimbra mailbox service must be restarted to changes to take effect. Type

zmmailboxdctl restart

Install/Upgrade zimbra-talk and zimbra-network-modules-ng (NETWORK Only)

• Make sure you already installed/upgraded zimbra-patch before this step. Please see 8.8.8 Patch 3 Change
• As root. Type below command.

apt-get update
apt-get install zimbra-network-modules-ng
apt-get install zimbra-talk

• Switch to user zimbra

su – zimbra

• Zimbra mailbox service must be restarted to changes to take effect. Type

zmmailboxdctl restart

Installing zimbra packages with system package upgrades

• As root, type below command first time so the server sees there is a new zimbra-patch package in the 888patch repository (and any other available operating system and Zimbra common package updates)

apt-get update

• As root, type below command to allow the patch, if necessary, to add the new Network Edition patch repository.

apt-get install zimbra-patch

• Network Edition Only: As root, type below command second time so the server sees the packages available in the new Network Edition repository added by Patch3

apt-get update

• As root, type below command to update most available packages

apt-get upgrade

OR

• As root, type below command to update all available packages plus any kernel updates.

apt-get dist-upgrade

• Switch to user zimbra

su – zimbra

• ZCS must be restarted to changes to take effect. Type

zmcontrol restart