But I don't have a lot of experience. Microsoft have made some efforts to get Linux to run, but it's not really in their interests to support their biggest competitor in the server space - hence from my understanding it's sub-optimal.
Personally what I did in a similar situation a few years ago was buy a new HDD, install Proxmox to the hardware and migrate the physical Win server into Proxmox as a KVM VM. I then offloaded as much funtionality from the Win VMs as I could to Linux VMs running under OVZ (Proxmox has much lower resource overheads than Win and Linux VMs running under OVZ are so resource friendly it's not funny). I then migrated the remaining Win VM (there was only one) to run on the PVE host. My whole system runs so much better now - even the Win server runs better as a dedicated VM now that it doesn't have to support all the other VMs. So now I only have 2 Win VMs running (the original physical server + 1) and everything else is handled by Linux VMs (mostly TKL ones). Admittedly it was a huge hassle to do at the time, but I have absolutely no regrets. It runs so much smoother and is far more scalable. Especially now that TKL is incorporated into PVE, it takes all of about 5 minutes to provision a new TKL server VM (running under OVZ).
Anyway, that may not be the answer you are after... So to answer your question more explicitly...
I would suggest that you install the TKL v12.0 MediaWiki appliance to your Hyper-V host and ensure that you can get that running ok. From what I understand it will require some tweaking but it should run ok. Once you have that set up then run TKLBAM on your old appliance and restore it into your new v12.0 appliance. You may need to do some additional tweaking there to get that all working, but hopefully shouldn't take too much effort...
AFAIK Hyper-V support for Linux is not great...
But I don't have a lot of experience. Microsoft have made some efforts to get Linux to run, but it's not really in their interests to support their biggest competitor in the server space - hence from my understanding it's sub-optimal.
Personally what I did in a similar situation a few years ago was buy a new HDD, install Proxmox to the hardware and migrate the physical Win server into Proxmox as a KVM VM. I then offloaded as much funtionality from the Win VMs as I could to Linux VMs running under OVZ (Proxmox has much lower resource overheads than Win and Linux VMs running under OVZ are so resource friendly it's not funny). I then migrated the remaining Win VM (there was only one) to run on the PVE host. My whole system runs so much better now - even the Win server runs better as a dedicated VM now that it doesn't have to support all the other VMs. So now I only have 2 Win VMs running (the original physical server + 1) and everything else is handled by Linux VMs (mostly TKL ones). Admittedly it was a huge hassle to do at the time, but I have absolutely no regrets. It runs so much smoother and is far more scalable. Especially now that TKL is incorporated into PVE, it takes all of about 5 minutes to provision a new TKL server VM (running under OVZ).
Anyway, that may not be the answer you are after... So to answer your question more explicitly...
I would suggest that you install the TKL v12.0 MediaWiki appliance to your Hyper-V host and ensure that you can get that running ok. From what I understand it will require some tweaking but it should run ok. Once you have that set up then run TKLBAM on your old appliance and restore it into your new v12.0 appliance. You may need to do some additional tweaking there to get that all working, but hopefully shouldn't take too much effort...