FortiManager 7.6 Deployment Patterns: Centralized Management
FortiManager centralizes configuration and policy management for multiple FortiGate devices, but a centralized tool can also concentrate deployment risk. Choose an architecture that allows teams to identify the intended configuration, review differences and recover when a push fails. Fortinet’s current FortiManager 7.6 Administrator exam is named NSE 6, not the former NSE 5/FCP 7.6 exam. The product concepts remain useful independent of the older exam label.
On this page
Choose a realistic central-management topology
Document where FortiManager runs, its administrative domains, which FortiGate devices it manages and how administrative traffic reaches them. Consider availability, backups, management network isolation and monitoring before choosing a deployment size. A remote branch may lose its management path while continuing to forward production traffic; design the response accordingly. Avoid making the FortiManager reachable from untrusted networks merely to simplify device onboarding.
Decide how devices are registered and trusted
Define discovery, device identity validation, certificate or administrator trust, onboarding approvers and naming standards. Group devices based on operational ownership, software version and the policies they should receive. A discovered device must not automatically receive a broad production package. Maintain an asset record tying each managed device to a change owner, environment and recovery contact.
Separate intent from deployed state
The device database, policy package and installed configuration can differ. A useful workflow detects and reconciles those differences before installation. If an emergency firewall change occurs locally, record it, review whether it should become managed intent, and avoid overwriting it blindly during the next deployment. Approvals need a preview of impacted objects, policy changes, affected targets and a rollback plan.
Handle version changes deliberately
Firmware upgrades, feature additions and ADOM version settings must be planned together. A management tool cannot be assumed to understand every feature from every FortiOS release. Read the compatibility notes before changing versions. Stage representative devices and verify policy installation, monitoring and backups before extending a rollout to the rest of the estate. Document how to restore management if an upgrade breaks device communication.
Observe deployments and failures
Capture successful baseline synchronization, a test package installation, policy install logs, and device-reported configuration state. Simulate an installation rejection or network interruption in a lab and identify whether the error is in connectivity, authorization, object validation or device capabilities. Validate traffic behavior after policy installation; a successful install response is not equivalent to business acceptance. See Fortinet’s current exam description for product-version context.