UTM Migration from Hyper-V to VMware

Hallo Jonas,

I like your idea of using HA as that would retain logs and Reporting.

There's a good chance that the order of the NICs will change, so I would first restore a backup to the VMware instance to check on the NIC order.  Once you know the order is good, do a factory reset and power down the VMware instance and follow the steps below (adapted from my standard recommendation for my clients):

1. On the current UTM in Hyper-V, on the 'Configuration' tab of 'High Availability':
   a. Enable Hot-Standby
   b. Select eth3 as the Sync NIC
   c. Configure it as Node_1
   d. Enter an encryption key (I've never found a need to remember it)
   e. Select 'Enable automatic configuration of new devices'
   f. I prefer to use 'Preferred Master: None' and 'Backup interface: Internal'
2. Cable eth3 to eth3 on the VMware instance.
3. Cable all of the other NICs exactly as they are on the original Hyper-V instance.
4. Power up the VMware instance and wait for the good news. [;)]

Cheers - Bob

Hallo Jonas,

I like your idea of using HA as that would retain logs and Reporting.

There's a good chance that the order of the NICs will change, so I would first restore a backup to the VMware instance to check on the NIC order.  Once you know the order is good, do a factory reset and power down the VMware instance and follow the steps below (adapted from my standard recommendation for my clients):

1. On the current UTM in Hyper-V, on the 'Configuration' tab of 'High Availability':
   a. Enable Hot-Standby
   b. Select eth3 as the Sync NIC
   c. Configure it as Node_1
   d. Enter an encryption key (I've never found a need to remember it)
   e. Select 'Enable automatic configuration of new devices'
   f. I prefer to use 'Preferred Master: None' and 'Backup interface: Internal'
2. Cable eth3 to eth3 on the VMware instance.
3. Cable all of the other NICs exactly as they are on the original Hyper-V instance.
4. Power up the VMware instance and wait for the good news. [;)]

Cheers - Bob