The following issues have been identified in 6.0.4. For inquires about a particular bug or to report a bug, please contact Customer Service & Support.
FortiManager cannot detect unauthorized FortiAP units that have been automatically added to managed FortiGate units. As a workaround, perform a manually retrieve operation on the managed FortiGate.
|FortiManager installation always fails on 6.0.x FGT-VMX.
|System Information widget on the slave FortiManager is showing both nodes as master.
|When adding an address via the right-click menu on the policy page, the page is stuck at the loading status.
|FortiManager may not be able to configure full mesh VPN among FortiGate devices with multiple VDOMS, and each VDOM containing an interface within it.
|When creating a Virtual Server, users cannot configure multiple Real Servers or set Real Server Mode for per-device mapping.
|User should not be allowed to delete default Meta fields.
|Unused object window size should be customizable and Column size under unused objects should stay to the set value.
|SSH Profile should not be allowed to enable "Allow Invalid SSL Certificates" when Inspection mode is "SSL Certificate Inspection"
|There should be an option to define the domain name for DHCP Server while configuring the VLANs' per device mappings with FortiSwitch.
|When editing comment/description, FortiManager may display the slash character, "/", as "/".
When promoting at the same time multiple FortiGates that have VDOMs, FortiManager Device Manager might fail to show the FortiGate VDOM name. As a workaround, delete and re-add the FortiGate.