Re: Hyper-v 2016 vs vSphere 6.5

MY 2 CENTS!!!

If you're interested in learning how the latest releases of Hyper-V and VMware vSphere compare, this is the session for you!

If you're interested in Hyper-V vs. vSphere: Understanding the differences, this is the session for you!

If you're interested in Migrating to Microsoft: VMware to Hyper-V, this is the session for you!

"Edited Highlights:

The Microsoft Firewall is your enemy. It can cause things to stop working in all places where Windows is used – SCVMM, Windows Hyper-V and then source VM – whether that source VM is running in VMware vSphere and/or Windows Hyper-V

VMware Convertor works with or without VMware Multi-Hypervisor Manager – and generally presents more options/features. However, if you want to have simple/quick method of converting from Windows Hyper-V to VMware vSphere then MHM is your man, if you want the fancy options then VMware Convertor is what you should focus on IMHO.

VMware Convertor can convert both physical and virtual machines – on the fly without a power down of the source Windows Hyper-V VM. Remember VMware has been doing conversions like this ever since the P2V product which I first started using in 2003.

The time to convert from M2V is considerably shorter than the time convert from V2M (5-6mins compared 30-40mins).

VMware Convertor can do a “final sync” between the source (Windows Hyper-V) and the destination (VMware vSphere) which gives you an consistent copy of the VM.

If you’re serious about (or forced against your will into) a multi-hypervisor strategy – I think neither VMware MHM or Microsoft SCVMM, where one vendor manages another, is a serious proposition. I think if your serious about this approach then you should be looking at a provisioning tool like VMware vCloud Automation Center.

Adding VMware into SCVMM requires – adding vCenter, adding vSphere hosts AND retrieving/authentication to each and every host to get full functionality. Neither SCVMM or MVMC (Microsoft Virtual Machine Convertor) allow you to convert a vSphere VM to a Windows Hyper-V without some sort of power down in the process, and as consequence a maintenance window

Using SCVMM to convert V2M is fraught with authentication/communications problems, using “Convert Physical Machine” might work better and quicker (around 10mins compared to 30-40mins with MVMC/SCVMM V2M). I understand that SCVMM R2 removes “Convert Physical Machine” from SCVMM. This in the release notes for SCVMM R2 – http://technet.microsoft.com/en-us/library/dn303329.aspx

After any successful conversion from vSphere to Hyper-V I’ve yet to see any method that successfully allowed for Microsoft Intregration Services to be installed – that means no mouse control, and in some case no network capabilities."

"Multi-Hypervisor Management and VM Conversion"

Raul.

VMware VDI Administrator.

Stay Connected: Like > Share > Comment > Reply > Helpful > Answered