Do i need to re-install cnMaestro on-Premises for each new release?

There are two types of releases that exist.  Some releases will be a OVA release.  Other releases will simply be Package releases that can be imported into the existing cnMaestro instance.  Technically, the reason there are two different types is because it depends on the type of changes that were made.  If the change touches more parts of the application, it’s likely to require a full OVA upgrade. 

For example, in cnMaestro On-Premises User Guide 1.2.2

Package Types

cnMaestro On-Premises software will be released in two forms:

OVA Image

The OVA image contains all software needed to run the cnMaestro application. It is installed on a virtual machine and will be released intermittently to update system software. Moving to a new OVA image requires one to export the configuration/data from the old cnMaestro instance and import it into the new. The OVA tends to run about 2.5 GB in size.


The package file can be installed on top of an OVA image and will only update the cnMaestro application. Packages

will be released more frequently, and they won’t require one to export/import existing data. Packages can be installed by downloading them from Cambium and uploading them through the UI (at Manage > Server > Operations).

The general update flow will be an OVA file followed by package releases. For significant system-level updates, a new OVA file will be generated.

Exporting/Importing Data

With an OVA software update, the current system data needs to be exported from the old cnMaestro instance and

imported to the new. This can be done through the Manage > Server > Operations page.

OVA Update Process

Updating an OVA image can be managed through the following process (which assumes the hardware has enough

hard disk space for two instances of cnMaestro.

  1. Export the cnMaestro Server data from the old instance.
  2. Stop the old instance.
  3. Start the new instance (using the directions presented above).
  4. Import the data into the new instance.
  5. Set the IP address of the new instance to that of the old instance.