FortiManager can do more than manage configuration. It can also act as a local FortiGuard Distribution Server (FDS), receiving FortiGuard update packages from the FortiGuard […]

The FortiManager Global Database exists for policies and objects that must be governed above an individual ADOM. Ordinary ADOMs let organizations separate customers, business units, […]

FortiManager can become a critical dependency even though it is not normally in the packet-forwarding path. If the primary management system fails during an incident […]

FortiManager can centralize policy and configuration only after it has a trusted management relationship with the FortiGate it is meant to control. Device registration is […]

FortiManager can show a FortiGate as connected while still reporting that its configuration is out of sync. The reason is that FortiManager does not manage […]

Administrative domains, or ADOMs, are one of the most important FortiManager design concepts because they decide where devices, policy packages, objects, administrators, and operational responsibility […]

FortiManager separates centralized policy management from device-specific configuration. That separation is why a change can exist in Policy & Objects without immediately changing a FortiGate, […]

A failed FortiManager install is rarely solved by pressing Install again. The useful question is where the installation failed: target selection, policy validation, device database […]

FortiManager can allow administrators to edit without locking, or it can require explicit locks before changes are made. Workspace mode exists to solve a coordination […]

FortiManager’s JSON API allows centralized network-management workflows to be automated without reproducing every operation through the GUI. The API can retrieve managed objects, change configuration, […]