[LMStone]

Originally Posted by abhi.datt

We have a licensed Network edition v 5 for 175 users which we intended to upgrade to 6.0.4.
After following the standard upgrade procedure we are facing following problems:
1. Logger services not starting because of which Admin cannot monitor services

2. At the time of upgradation, install.sh script correctly identified our license file for 175 users but after the upgradation is completed and restarting the services several features are missing:
A: Zimlets are not appearing in users area
B: License, HSM, Backup/restore is not appearing in global configuration of administration console( the 6.0.4 documentation and previous version have these features under the same navigation area)
C: Search Mail – option is not appearing under tools in administration console (the 6.0.4 documentation and previous version shows this features are available)
D: Move Mailbox feature is also not appearing anywhere as it was appearing in last version as well as in the documentation of 6.0.4.

So it looks like it has lost functionality or has become equivalent to Opensource edition.

What is wrong??

We saw pretty much the same thing on a few of our upgrades. If your situation is like ours was, there are two things going on here.

First, we had to reinstall the zimlets manually after the upgrade. Some zimlets were upgraded, so were not. You can check the log from the install to see which ones failed to be upgraded.

Second, the "missing" bits of the admin console in our case was due to the upgrade installer script not upgrading the rights of the global and domain admins correctly. The good news about 6.0 is that there is now much more flexibility and control for customizing what users can see and manipulate in the admin console. The bad news is that, like customizing Views in Lotus Notes applications and/or managing GPOs in Windows one GPO at a time (without using any of the wizards), getting things the way you want them isn't intuitive (at least to me!)

To "fix" the "missing" console bits, first let's do a test:

1. Create a new user account and make the user a Global Admin.
2. Log in to the Admin Console with this new Global Admin account you just created and see if all of the "missing" bits of the console now appear.
3. If the Admin Console is still missing bits when viewed by the brand new Global Admin, I'd open a support ticket with Zimbra straightaway.
4. If the new Global Admin user can see everything in the Admin Console, then we just need to fix the permissions of the Global Admin accounts existing prior to the upgrade.

To fix the Admin Console permissions of the Global Admin user accounts existing prior to the upgrade easily, we need to use the Admin Console, so log in to the Admin Console with that new, fully functional Global Admin user account you just created and do the following:

1. Browse to and press Edit to administer the settings of the old Global Admin account
2. Once in Edit mode, browse to the Admin Views tab and press the Select All button under the Directly Assigned Admin Views pane on the left, assuming none of these views are already checked. If these views are already checked, press the Deselect All button. Basically, we want to toggle and save the state of all of these Directly Assigned Admin Views. Press Save to commit the account settings and exit fully from editing the account.
3. Go back in and redit the account. Unselect the Global Administrator tickbox on the General Information tab, press Save to commit this change and exit fully from editing the account.
4. Once more, open the account in editing mode and mark the Global Administrator tickbox. Save the settings and exit from editing the account.
5. Try logging in to the Admin Console with the old account you just fussed with and see if the "missing" bits of the Admin Console now reappear.
6. If so, you are done. If not, I'd open a support ticket with Zimbra.

Zimbra initially advised us that toggling the Global Administrator tickbox on the General Information tab would be enough to "fix" the old Global Admin accounts, but we found at least in our case that this wasn't enough. Forcing some changes to the Directly Assigned Admin Views was required first to enable the re-checking of the Global Administrator tickbox to work.

Hope that helps,
Mark