I recently used the MS VMConverter tool to move half a dozen VM’s from an ESXi 4.x infrastructure to Hyper-V.
The GUI tool didn’t like the thin-provisioned disks, so I didn’t get the actual machine definition to convert as it choked and backed out. But the associated Powershell cmdlets converted the vmdk’s to vhdx’s just fine. Added them as disks to newly provisioned Hyper-V VMs and they booted right up. A little network tweaking as a result of the VMWare tools removal, and I was in business. -sc From: [email protected] [mailto:[email protected]] On Behalf Of Jameel Sarangi Sent: Thursday, June 8, 2017 4:04 PM To: [email protected] Subject: [NTSysADM] RE: VMware to Hyper-V transition Use the Starwinds v2v converter. Works awesome to move from ESXi to Hyper-V Jameel Sarangi / VP Operations [email protected]<mailto:[email protected]> [www.netsmart.ca]<http://www.netsmart.ca> Direct: (780) 784-3323 / TF: (877) 452-5811 9922 - 111 St NW Edmonton AB T5K 1K2 www.netsmart.ca<http://www.netsmart.ca> [cid:[email protected]] <https://www.facebook.com/netsmartinc> [cid:[email protected]] <https://www.twitter.com/netsmartinc> [cid:[email protected]] <https://www.linkedin.com/company/netsmart-inc-> [cid:[email protected]] <https://plus.google.com/117724164920144786754/about> The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error please contact the sender and destroy any copies of this information. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Webster Sent: Thursday, June 8, 2017 11:12 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: VMware to Hyper-V transition You left out Emergent Online, then Provision Networks, then Quest, then Dell and Wyse is in there somewhere. Webster From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Melvin Backus Sent: Thursday, June 8, 2017 12:01 PM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: VMware to Hyper-V transition vWorkspace, formerly Quest, then Dell, and now Quest again. ☺ -- There are 10 kinds of people in the world... those who understand binary and those who don't. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Webster Sent: Thursday, June 8, 2017 11:56 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: VMware to Hyper-V transition What is your VDI solution? Webster From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Melvin Backus Sent: Thursday, June 8, 2017 10:48 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] VMware to Hyper-V transition Anyone out there proficient in both VMware and Hyper-V who can point me at any good docs on doing a migration? I’ve got a specific application I’m considering moving to Hyper-V to help stretch the life of our VDI solution. We will eventually have to change I’m sure, but migrating it may be a stopgap and I’ve got the extra hardware at the moment. In particular I’m weak on the networking aspects of Hyper-V. -------------------- Service Desk | 404-497-1599 | https://servicedesk.byers.com<https://servicedesk.byers.com/> Melvin Backus | Sr. Systems Engineer | Byers Engineering Company | 404.497.1565 -- There are 10 kinds of people in the world... those who understand binary and those who don't.
