You'll learn to run the Install Wizard, read the preview, check the result and respond to a failed install.
The moment configuration reaches the firewall
Everything before this was preparation. The install is the step that changes a production firewall, so it deserves a routine: choose, preview, install, verify.
From package to firewall
On small screens, swipe sideways or focus the diagram and use the arrow keys.
The install is where a mistake becomes an outage.
What the Install Wizard does
On small screens, swipe sideways or focus the diagram and use the arrow keys.
Always read the preview. It shows the difference FortiManager is about to push, including changes that would remove something done locally.
Run the wizard
The install wizard
On small screens, swipe sideways or focus the diagram and use the arrow keys.
Read the preview before confirming.
Open the Install Wizard from Device Manager or the policy package.
Choose what to install: policy package and device settings, or one of them.
Pick the devices. Check the list is only the ones you intend.
Run the validation and open the install preview for each device.
Install. Watch the task until it finishes.
Read the preview
A preview that shows large removals or unfamiliar objects is a stop sign. Common causes are a local change made on the FortiGate, an empty or wrong package, or a missing dynamic mapping.
Verify and read the log
After the install, check that the device status returns to synchronized and the package shows as installed. Then read the install log and test a real flow.
Verify an install
On small screens, swipe sideways or focus the diagram and use the arrow keys.
A success message is not the final check.
Example output · based on Fortinet documentation; exact format varies by model and FortiOS version
FMG1 # diagnose dvm device list
|- STATUS: dev-db: not modified; conf: in sync; cond: pending; dm: installed; conn: up
After a successful install the device database no longer shows pending changes and the device shows as installed. This is an example line; yours will have more columns.
When an install fails
When an install fails
On small screens, swipe sideways or focus the diagram and use the arrow keys.
Read the error before retrying.
Open the task and read the first error line. Later errors often follow from it.
Check the connection status. A device that is down cannot receive an install.
Check for missing objects or mappings the policy needs.
Compare the device and FortiManager configuration for a conflict, such as an object with the same name and different settings.
Check your understanding
Predict · scenario 1
The preview shows many policies being removed from FGT1. What is the most sensible action?
Predict · scenario 2
Which step shows what an install will change?
Predict · scenario 3
An install fails with several errors. Where do you start?
Further reading in Fortinet's documentation
Links open the named page in Fortinet's documentation (checked 19 October 2026). RouteLearn is an independent educational resource, not affiliated with or endorsed by Fortinet. Fortinet, FortiGate, FortiOS, FortiManager and FortiGuard are trademarks of Fortinet, Inc. Example output on this page is illustrative.
FAQ
What is the difference between installing a package and installing device settings?
A policy package install sends policies and objects. A device settings install sends settings from the device database, such as interfaces and routes. The wizard lets you choose either or both.
What if the install is only partly successful?
The install log lists what was sent and what failed. Fix the cause shown in the first error, then install again. Do not keep reinstalling without reading it.
Can I see what will be removed?
Yes. The install preview shows configuration that will be added, changed or removed on the FortiGate.