Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Ok Here is my problem I have 1 ESXi 3.5 server that has 3 vm's on it. I have decided to move over to Hyper-V Server R2 since I like what they are doing on the free side of things. (Free Clustering and Live Migration seal the deal for me) we are a small shop and don't have a real iscsi setup yet (but it's coming, soon I hope) so I'm just running my storage locally (tho I do have a starwind/ms server iscsi box if I need it for the conversion) And I need to get my vm's off the exsi box on to my hyper-v r2 box. I have SCVMM but it appears that it won't connect to my esxi box to move them. And I'm not sure how to do it.

I've read a lot about manual conversions (the vmdk to vhd tool) but I'd like to do something more automated if I can. Space is a concern as one vm is our storage drive and it's close to 1TB.

So I guess my actual question is what's the best way to get my stuff from vmware to hyper-v?

Thanks everyone.

share|improve this question
    
Hmmmm, Hyper-V also has a terrible track record on security (see imgur.com/xZW77.png). Are you sure you really want to migrate? –  wazoox Jul 13 '09 at 18:37
2  
Whatever you do, I'd suggest investing a couple hundred bucks in a 1.5TB drive and copy your VMDK+VMX to it using FastSCP or another utility and work on it there. This will cover you in case you do something horribly wrong and probably give you the best way to physically migrate the data. –  Kevin Kuphal Jul 13 '09 at 19:07
    
Yeah that was my plan. I'm not pulling down the esxi server until I have all its vm's running on the new hyper-v server. As for security like all MS products you have to be smart about deployment, keep up with your patches and firewall whenever you can. –  Barden Jul 13 '09 at 22:31
    
What security? the link mostly shows the admin was an idiot to allow access to hyper-v to start with. –  TomTom Aug 12 '10 at 12:35
1  
@Wazoox, sounds like they've got the worlds worst security if they allow the Internet to access their Hyper-V hosts; which should be totally isolated from everyone except appropriate admin staff. –  Chris S Aug 12 '10 at 13:01

4 Answers 4

up vote 2 down vote accepted

Copy the .vmx and any VMDK files from the ESX console to a Windows folder. Then you should be able to point SCVMM at the .vmx and it should work. If it fails at that point you can edit the .vmx to make sure the vmdk paths in it are OK (ie just remove any paths from them if they are there). Veeam FastSCP will do the trick if you need something to handle the copy. It would be a good idea to remove any snapshots first if you have any before you start.

The files will most likely all be under /vmfs/datastore/virtualmachine-name but some of them may be elsewhere if you've chosen to put the VMDK's in other locations. If they are spread around you will have to edit the .vmx

share|improve this answer
    
I'm happy to report it worked like a champ, at least on my smaller image (I have no reason to belive a bigger one wont work) thanks for the help! –  Barden Jul 16 '09 at 1:36
    
+1, Copy the files over to Windows, open the SCVMM PowerShell, run new-v2v and answer all the questions. Done. –  Chris S Aug 12 '10 at 12:58

I've used SCVMM to import VMs from VMWare Server (v1). As far as SCVMM is concerned the VM is just a physical server and it imports with no problems. Uninstall the VMWare Tools first or you'll get harmless but annoying warnings when you start the VM in Hyper-V.

JR

share|improve this answer

http://www.adopenstatic.com/cs/blogs/ken/archive/2008/03/23/16710.aspx

The difference is that he was migrating from VMware Server. but the article can guide you an help you.

share|improve this answer

Remove VMware tools on the server you want to migrate to HyperV Install disk2vhd en start it up. This copys your entire disks/partitions to a VHD file. Create a new virtual server on HyperV, using the VHD files you created before. 'Insert' integrations services disk and install integration services. Boot your virtual machine on HyperV (make sure VMware virtual server is off to avoid conflicts.

share|improve this answer
    
This is a messy way to do the conversion when he's got SCVMM that will do a very clean conversion; and you don't mess with the existing VMs on the ESX server (a good failsafe). –  Chris S Aug 12 '10 at 12:59

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.