5GHz DFS channels on AP Profile were not supported for FAP U231F.

FortiManager may try to delete default wtp 11ac-only profile on FortiWiFi-60F causing install to fail.

User may not be able to access AP Manager with a custom read-only admin profile.

After added FortiManager fabric ADOM to FortiManager, Device Manager's log status, Log Rate, or Device Storage column cannot get data from FortiAnalyzer.

SD-WAN monitor may stuck loading when admin user belongs to device group.

The Client Address Range setting should allow users to configure assign-IPs from firewall address or group.

FortiManager does "auto-retrieve" causing all policy package status to go "unknown" after a new VDOM is created on FortiGate.

When editing device in HA cluster, admin password change is not applied to secondary unit.

Importing policy package shows ngfw-mode policy-based with the inspection-mode set to proxy.

FortiManager is missing peer options with dial up user configuration with VPN IPSec Phase 1.

Device & Groups > VPN Phase1/Phase2 does not show the proposal column when using FGT-VM type "FGVMIB".

Provisioning template with empty name cannot be deleted or edited.

Zero-touch provisioning with script installation may fail due to duplicated snmp-index.

User may not be able to click on the check box to import configuration with 6.2 ADOM.

The Provisioning Template 's status on Summary Dashboard always displays "Modified".

Installation fails due to configuring forward-error-correction on FortiGate's interfaces.

Certificates CN information may be invalid when FortiGate is registered by Zero-Touch-Provisioning.

FortiManager is unable to use secondary IP as source IP in DNS database.

FortiManager is unable to install the Switch Controller > VLAN interface configuration during the ZTP process.

When a device uses IPsec Tunnel Provisioning template with enable value for aggregate member, FortiManager may create a new system interface with the same name which is not expected behavior.

FortiToken provision button is greyed out in Device Manager while it is enabled on FortiGate with the same token.

Editing provisioning CLI template without any modification may cause device status changed to Modified.

When sdwan-monitor-history is enabled, replace last 5 minutes with last 10 minutes.

FortiManager cannot install TCP-connect using Random port for SD-WAN.

Administrative user gui-dashboard information should be deleted upon VDOM deletion.

FortiManager cannot use space to set location under SNMP configuration.

Input-Device under CLI Configuration > System > SD-WAN > Service displays loading for a long time.

When optional meta fields are being used, users cannot edit the devices.

Threat feeds global objects are not installed to destination ADOM when using the assign all object option.

Global database may be locked when viewing Workflow Session Diff.

FortiManager should be able to assign VLAN interface to FortiExtender.

Under some conditions, disk usage may reach 100% after a few days.

There is a Criteria Latency field which is different between FortiGate and FortiManager when creating the manual interface option for SD-WAN rules.

System NPU values may be different between FortiManager and FortiGate-1801F.

FortiManager's lock/commit operation is very slow when FortiManager-HA is enabled.

"Push Update" does not work for pending device under the FGuard > License Status.

FortiManager displays "failed to copy BRANCH_BGP_Recommended" error when performing the "check adom-integrity" test.

During the installation, FortiManager displays Policy Consistency Check failure.

Hit count, first used, and last used may not get updated on FortiManager.

The App Control set to Monitor in FortiManager causes the App to be disappeared from FortiGate.

Where Used may not be reporting used objects properly.

FortiManager displays error when using "push to install" for objects utilized by policy blocks.

FortiManager is unable to import or create virtual server with real servers using the same IP but different "http-host".

Right-click menu to add object may return an error: "cgn-resource-quote:out of range".

Policy lookup may not work if the managed devices are in Transparent mode.

There may be slowness when using Find Duplicate Objects with Merge tools.

Copy fail error due to external-resource used in webfilter profile.

Removing the objects from Device Level DB did not delete the object's reference from ADOM Level DB.

When creating a Central DNAT policy in FortiManager, more services may not be added to policy with error: can't assign to property "from" on NaN: not an object.

Address group changes for per-device mapping does not apply to FortiGate when Address group is used in policy route.

6.4 version ADOM policy package failed to enable policy NAT from GUI.

IPv4 & IPv6's ACLs are not available when Policy Offload Level is set to "Full Offload".

Moving a policy by dragging may not work properly.

There may not be empty lines in "IPS Signature and Filters".

Consolidated policy NAT is always disabled on the GUI.

Installation fails because the virtual-wan-link did not exist.

FortiManager displays Install failure due to adding "g-" prefix to the external-resource objects.

Created time doesn't indicate AM or PM on the Tools > Find Unused Policies.

After upgrade, installation may fail due to mcast-session-counting.

Install fails when new transparent mode VDOM is added directly via FortiGate CLI and imported into FortiManager.

Failed to run the Post-Run CLI Template due to the "datasrc invalid" error.

When creating a new phase1 interface, dpd=on-idle settings may not be saved.

FortiManager should have the CA Identifier as configurable for SCEP server request.

Setting a Cluster ID for a model HA cluster results in an invalid group ID under config system HA.

Two factor authentication fails when special characters are used in CN.

FortiManager may not generate event logs for meta field changes.

Script Groups should be copied with their members when cloning an ADOM.

FortiManager may not be able to upgrade ADOM from 6.2 to 6.4: err=-2,Policy ippool (ippool6) name cannot be empty.

The number of FortiGate devices registered is in the upper limit of the license count may causes HA becomes asynchronized.

Webfiltering HTTPS 8888 is not working after FortiManager is upgraded from 6.4.7 to 7.0.4.