Micetro notifies you when a new version becomes available and allows administrators to update to a new version. Versions may contain updates for any number of components, such as Micetro Central and the Micetro Agents.
Micetro uses a calendar-based versioning model, in which releases are numbered according to the year in which they are released, along with two rolling numbers that indicate the major and minor release numbers within a calendar year. In this versioning model, version numbers are structured as <Year>.<Major release>.<Minor/Patch release>.
For example, in the version 25.1.1:
-
Year indicates the last two digits of the calendar year, e.g., 25 means the version was released in the year 2025.
-
Major release indicates the sequence of major releases in the year, e.g., 1 indicates that it’s the first major release of the year.
-
Minor/Patch release indicates the minor/patch release on top of the major version, starting from 0, e.g., 25.1.1 is the first patch after the release of 25.1.0.
Calendar-based versioning will not be applied retroactively to existing versions, e.g., 11.1.0.
Each release builds on top of the previous version, so any new release contains fixes for bugs and issues that were resolved in previous versions. Patches are only used when specific issues in a particular version need to be addressed. Any fixes applied in a patch will also be part of the next release and any releases in the future.
Version support
Versions are supported for two years from their original release dates. Any patches applied on top of a version do not reset this timeframe, which always refers to the release date for which .0 is the patch number.
If you have any questions, please contact BlueCat Support at support@bluecatnetworks.com.
Update paths
A direct update path is supported for all Micetro versions from 7.x and greater. If you are on a version below 7.x, please update first to version 9.3 before updating to the target version, e.g., 25.1.x.
Important notes for updating:- If you have a Kea DHCP server on a version below 1.6.0, it must be updated to 1.6.0 or 1.8.0 before you can update to Micetro version 10.0.0 or greater. For more information, refer to the Kea update notice.
- If you’re running Micetro Central on Windows on a version between 7.x and
10.x, and want to update directly to 25.1.x, follow these
instructions:
- Run the installer executable manually to upgrade Micetro Central to version 25.1.x.
- Download only the Micetro Central installer file from the Micetro downloads server and run the installer with "Run as Administrator" on the machine running Micetro Central.
- Update Micetro Central in the High Availability setup, if applicable.
- Shut down the Micetro Central service on each secondary server.
- Update the primary server manually using an installer, which can be downloaded from the downloads server.
- Manually update each secondary server using an installer.
When the update is successfully completed, the service will be started again. Both servers should be updated and returned to High Availability mode.