Be careful. Default behavior of Hyper-V is dynamic MAC address. The way FreePBX handles licensing means that if your MAC changes your installation (and any commercial modules) will become unregistered and you’ll be doing some cleanup.
You won’t realize this until after you’ve moved the VM and then reboot it. A new MAC address will be assigned to your ethernet adapter due to dynamic MAC being set in hyper-v, eth0 will stop working in CentOS and you will get a new interface (eth1). The web gui will be unreachable until you fix things.
Fixing it can take a bit of work if you don’t know your original MAC address. Luckily you can find the original MAC address after moving it even if you didn’t have it written down (check through your firewall rules config files). If you do have this happen, even after setting the MAC address back and rebooting the VM, you still will have to register FreePBX using the existing Deployment ID. You can do this with the following command;
fwconsole sa a DEPLOYID
If you can’t figure out your original MAC you will have to reactivate the installation. this means you have to login at portal.sangoma.com and “reset your hardware lock” which I believe is still limited to doing this 2 times before you have to contact support.
You probably want to set your MAC to STATIC in Hyper-V (and any hypervisor for that matter) and just make sure you don’t cause a MAC conflict.