[LMStone]

Originally Posted by brian

The easiest thing to do when upgrading and installing a new license at the same time is to just drop the license into /opt/zimbra/conf and let the installer take care of installing it for you.

Hi Brian,

In effect, that's what I did.

But consider the case where the license upgrade and a Zimbra version upgrade are separated by weeks or months:

1. Customer uses admin GUI to install higher-capacity license file.

2. Customer over time adds more accounts, totaling a number greater than allowed in the original license file.

3. Customer weeks/months later then performs a Zimbra upgrade; the upgrade process "sees" only the account limit from the preceding license file (but there are more accounts than that!). The sysadmin doing the upgrade doesn't notice that the output from ./install.sh shows the account cap from the older license and allows the upgrade to complete.

Now what happens after the upgrade? There are more accounts than that for which the installed (older) license allows. Are some number of accounts locked out? Will the system even start? And if so, how will the sysadmin look when all of the individual domain admins call to say they can't add any more accounts?

The license upgrade documentation just says to use the Admin console to install the new license file. But upgrading the license this way didn't survive a Zimbra version upgrade in my case. So, then shouldn't either this fact be added to the license upgrade documentation, or shouldn't the middleware behind the admin console be improved to actually copy the new license file to the conf directory?

I appreciate this is a minor item in the grand scheme of things, but thought I should point this out anyway.

All the best,
Mark