Re-Registering a Virtual Appliance
If you clone a virtual appliance, each cloned instance must be re-registered before you can use it in live production mode.
Re-registration is necessary to take advantage of reporting and clustering features. If you do not re-register a cloned appliance, it cannot be distinguished from the parent appliance (the virtual machine it was cloned from) if both are used on the same network; properties such as the hostname and static IP address are identical to that of the parent virtual machine.
You can re-register a virtual appliance on the page. Alternatively, you can use the command-line interface of the virtual appliance, which is available via the Console tab of your VMware client. See the Virtual Email Appliance Setup Guide for more information.
If the appliance you plan to clone belongs to an existing cluster of appliances, you must remove it from the cluster before cloning. Once you have cloned an appliance and re-registered it according to the steps that follow, you can join one or both of the appliances to the cluster.
Before re-registering, ensure that you have configured unique network and hostname settings for the cloned virtual appliance. See the Virtual Appliance Setup Guide for more information.
If you have configured certificates for the appliance on the page, you must upload new certificates that bear the hostname of the cloned appliance. This is not necessary if you are using the default self-signed certificate.
To re-register a virtual appliance: