Devices not visible after migrating FortiManager VM from VMware to Hyper-V
Confirmed 7/20/2026
Problem
After migrating a FortiManager VM from VMware to Hyper-V by installing the same version and restoring a backup, Device Manager showed no devices even though License Information still showed the expected ADOMs and registered devices.
Symptoms
Devices and ADOMs are to be seen in the cli but not in the GUI. CLI commands such as diagnose dvm device list and diagnose dvm adom list confirmed that the devices and ADOMs were present.
Environment
FortiManager
FortiOS version
7.6.4
Solution
The issue was resolved by going to System Settings > ADOMs, enabling ADOMs, then logging out and back in so the correct ADOMs and devices became visible.
based on the test, the devices and ADOMs were never lost. The FortiManager database still contained them, confirmed by:
diagnose dvm device list
diagnose dvm adom list
The issue was that ADOM mode was not enabled/active in the GUI after the restore, so Device Manager did not show the expected ADOM/device structure.
Confirmed solution
GUI
Go to:
System Settings > ADOMs
Enable ADOMs, then:
Log out > Log back in
After logging back in, the ADOM selector becomes available and the correct ADOMs/devices are visible under:
Device Manager
CLI equivalent
If needed, ADOM mode can also be enabled from CLI:
config system global
set adom-status enable
end
Then log out/in, or reboot if the GUI does not refresh correctly:
execute reboot
Key takeaway
This was not a VMware-to-Hyper-V device database loss issue. The restore succeeded, but the GUI was effectively showing the system as if ADOM mode was disabled. Since the DVM commands showed the correct inventory, no device re-add was required.
Verification
ADOMs and Devices will appear again in the GUI
Tags
No tags yet.
Community rating
— / 5 (0)