Technical Tip: Configuring startup settings via GUI/CLI

To configure auto-install settings, navigate to System -> Settings -> Start Up Settings, and below are the options via GUI as shown in the screenshot:


Starting from FortiOS v7.4, a new feature was introduced that allows a configuration can be migrated from an older FortiGate device to a new FortiGate directly from the FortiGate GUI, without having to access the FortiConverter portal. 

The target FortiGate must also have a valid FortiConverter license. More information can be found here in this document: FortiConverter in the GUI.

To configure via CLI, execute the following commands:

FGT-A # config sys auto-install

FGT-A (auto-install) # set auto-install-config enable  <----- Enable/disable auto install the config in USB disk.
FGT-A (auto-install) # set auto-install-image   <----- Enable/disable auto install the image on the USB disk.
FGT-A (auto-install) # set default-config-file  <----- Default config file name in USB disk.
FGT-A (auto-install) # set default-image-file   <----- default-image-file Default image file name in USB disk.

If the image used in the above configuration is not signed, the error message 'Installed Firmware is not signed by Fortinet' might be encountered after bootup. More information is covered in this article: Troubleshooting Tip: 'Installed firmware is not signed by Fortinet' error.

When the 'auto file system check' is enabled, and in the event of a power disruption, it will automatically check the file system for any errors during bootup. By default, it is disabled.

The following warning appears when FortiGate boots up:

To enable automatic file system checks using the CLI:

config system global
    set autorun-log-fsck enable
end

Regarding the auto-file system checkup, refer to this document: Run a File System Check Automatically.

For USB auto-install configuration via CLI, refer to this KB article: Technical Tip: Automatic installation of Firmware and system configuration.