1. Do not use you own login info (it's checked by default) even if you're an Admin. Login with the Administrator account.
2. You don't have to share the VM folders on the Hyper-V server or SAN. You can just access them with their UNC paths (Example: \\servername\d$\VHDX). I'd suggest not sharing them and having to mess with permissions.
3. 512MB minimum ram (again - this is the idiotic default) is WAY TO LOW - set it to a gig for ALL WINDOWS MACHINES and you'll hate yourself less.
4. The PC doing the conversion needs a temp space with the amount of storage that the VM will need free.
5. This is kinda related... You need a minimum of 3 NICs in your Hyper-V server to even attempt this with a SAN. NIC1 - Management Traffic | NIC2 - HYPER-V Switch | NIC3 - SAN Traffic (hopefully 10gbe and ISCSI). No SAN? Well than, you only need 2 unless you're planning on teaming.
If you do that; you should get through the conversion. Now on to the fun / horrible part. After conversion; the machine will not run and it'll give you 4.5 billion errors in the Hyper-V server log telling you why it's sitting there with the cursor blinking. Unfortunately I had a real problem getting a solution to this error:
'VMNAME' was faulted because the guest executed an intercepting instruction not supported by Hyper-V instruction emulation. If the problem persists, contact Product Support. (Virtual machine ID RANDOM -NUMBERSANDLETTERS)
FYI - THIS HAS NOTHING TO DO WITH VMWARE TOOLS! The spiffy Microsoft tool is supposed to remove them. I've tried removing them B4 conversion and just leaving them in - it made no difference! I believe this happens because it nerfs the boot code when it converts it from the VMWare SCSI to the Hyper-V IDE. That's my personal theory anyway. But Phil you ask; How do we fix this? Here's what you do:
1. Add a Legacy NIC to the hardware and adjust the boot order if you're using WDS. If you don't have a WDS server at your disposal then, youll need to adjust the boot order so it adds the network boot 1st then CD boot. The reason I did this was so that you have enough time to mount the CD ISO before it jams up. Then, start up the VM.
2. I used WDS with a repair image but, the ISO process is almost the same. Load up your repair environment and pull up a command prompt. Then, follow Attempt 1 & 2 from here.
3. Reboot and it should work like a champ. If not you might need to Fix_HDC it to deal with controller driver issues. Just download Fix_HDC and store it on a flash drive or integrate it into your recovery image.
That process worked for me to convert (2) 2008R2's and a 2003 legacy server so far. I hope this helps - I haven't found much around the net covering Hyper-V random weirdness so I thought I'd throw in my 2 cents.
