Licensing 3.2 Beta 2 NE
NOTE - This applies to 3.2 Beta 2 or LATER releases of the Zimbra Collaboration Suite, and only applies to the NETWORK EDITION. The open source version requires no license file.
Zimbra Licensing is for the Network versions. Its purpose is to enforce agreements we have with our customers.
Licenses are files that are installed once per deployment. The license constrains the number of users that are allowed to be in use and an expiration time after which some network features are lost and no users can be created.
3.2beta2 and 4.0RC1 shipped with trial licenses embedded in them. 4.0.0GA did not embed a trial license, but does require a license to run.
Obtaining a license
For trial users, a license will be mailed to you after registration at www.zimbra.com. Trial users upgrading from 3.1.x releases should fill out the registration form again to get the 4.0.0 binaries and a license key.
Paid customers and trial users with sales contact (and thus a support portal login) should log in to the support portal at http://www.zimbra.com/support. From that page there is a button to click to have a license mailed to you. This will also take you to a page with links for the binaries.
For upgrades from 3.1.x to 4.0.0GA the license MUST first be placed in /opt/zimbra/conf/ZCSLicense.xml. If the license is not present the upgrade will exit. The upgrade will pick up and install the license file as part of the upgrade.
Make sure the license is owned and readable by the zimbra user:
chown zimbra:zimbra /opt/zimbra/conf/ZCSLicense.xml chmod 440 /opt/zimbra/conf/ZCSLicense.xml
For upgrades from 3.2beta2 or 4.0RC1 to 4.0.0GA no action is required for the license.
For new installations of 4.0.0GA, the license should be installed after the install completes. This can be done via either CLI with "zmlicense -i <file>" or via the admin UI at GlobalSettings' License tab.
If you have an existing installation and receive a license (e.g. you move from being a trial installation to a paid customer), you will receive a new license via e-mail. This license can be installed with either the zmlicense tool or the admin UI as in the preceding paragraph.
Note that a tomcat restart (zmcontrol start/stop) should be done after the license is installed.
The license should be installed only once, but all tomcat servers in a multinode deployment must be restarted.
Displaying a License
The currently installed license can be viewed with either the CLI tool "zmlicense -p" or with the admin UI, in GlobalSettings' License tab.
Licenses are XML files, so you can just look in them to see the parameters if desired.