FortiManager
FortiManager supports network operations use cases for centralized management, best practices compliance, and workflow automation to provide better protection against breaches.
kishizuka_FTNT
Article Id 422239
Description This article describes the FortiManager product behavior where no ADOM upgrade is supported in any major FortiManager 'X.X.0' release.
Scope FortiManager all 'X.X.0' major releases v7.0.0, v7.2.0, v7.4.0, etc, ADOM Upgrade, Global Database Upgrade, Administrators managing FortiManager ADOMs
Solution

Symptoms:

The ADOM 'Upgrade' option does not appear, or the Upgrade button is grayed out; ADOM cannot be upgraded from one major version to another (e.g., v7.0 → v7.2), Global Database upgrade is also not available.

 

Cause:
X.X.0 releases are Base Releases' without ADOM upgrade support:

In all FortiManager major initial releases (.0), ADOM upgrade is not implemented. Only new ADOM creation for that version is supported. This behavior is consistent across all recent major versions (7.0.0, 7.2.0, 7.4.0).

 

ADOM upgrade becomes available starting from X.X.1:

In patch releases such as:

  • v7.0.1.
  • v7.2.1.
  • v7.4.1.

The ADOM upgrade mechanism is added and fully supported. 

 

This reflects the standard release cycle:
The X.X.0 release focuses on introducing support for the new FortiOS major version. ADOM upgrade requires additional development and validation effort. Therefore, it is introduced starting from the X.X.1 release.

 

Global Database upgrade follows the same rule

Global ADOM/Global Database upgrades are aligned with ADOM upgrade behavior. Thus, they are not supported in X.X.0 and become available from X.X.1 onward.

 

Solution:
Upgrade FortiManager to X.X.1 or later.

 

To perform the ADOM upgrade:

  • Upgrade v7.0.0 → v7.0.1+
  • Upgrade v7.2.0 → v7.2.1+
  • Upgrade v7.4.0 → v7.4.1+

After upgrading to a patch release, the ADOM upgrade option becomes available.

 

Alternative: when the ADOM upgrade is not available:

If it is necessary to remain on X.X.0, a new ADOM for the target version (for example, a v7.2 ADOM) should be created, and FortiGates running the new version should be added to that ADOM.


Related document:
Special Notices