StarWind Software

Looking to see if anyone has migrated TPM-enabled Hyper-V VMs from Hyper-V to ESXi. The "Enable Secure Boot" is checked, as well as the "Enable Trusted Platform Module" and "Encrypt state and virtual machine migration traffic" options. On they Hyper-V host, when running "tpm.msc" it comes back with "Compatible TPM cannot be found", so I'm trying to determine if the settings under the VM are "just for show". However, in the VM itself (or one of them), there is a TPM 2.0 device listed in Device Manager, and "tpm.msc" shows one and the manufacturer name is "MSFT".

Can I actually migrate this guy over to ESXi and have it work? Trying to determine this before rabbit-holing a bunch of time.

Thanks!

Welcome to StarWind Forum! I think that this request is not quite related to the StarWind V2V converter. It is more related to the VM configuration and hypervisor or host hardware.
From my experience, you can turn off the TPM and try booting up the VM.

You can turn it off TPM but this depends on your environment's security and compliance requirement.

That's a good point. But to make that VM up, it might be necessary to temporarily disable it.
Again, that's something that is not related to StarWind's software.

To update this thread ...

I had some hardware to work with so I lab'd it up. Set up a machine has a Hyper-V host and created a VM on it. No domain, no certs, etc.
I enabled the security features on the VM and went through the conversion process on it without changing anything. No surprise, but the converted VM didn't boot. So I shut down the source VM and disabled everything under "Security" ("Enable Secure Boot", "Enable Trusted Platform Module", "Encrypt state and virtual machine migration traffic"; "Enable Shielding" was never checked). Powered it up; made sure it still came up (and it did). Ran through the conversion, and after making the normal changes on the ESXi side (install tools, etc.), the VM came right up.

One thing that hadn't occurred to me is that, when I had the security features enabled for the Hyper-V VM, I never did anything with it - so removing it never really had any consequences to it. So now I'm re-enabling it on the Hyper-V VM, and enabing BitLocker to see where this is going to go.

Thanks for sharing your experience! That's a very good point.