The ‘VMC to Hyper-V import tool’ in short ‘VMC to Hyper-V’ supports any VMC which is my goal but not yet true. The initial goal was to support import of Virtual Server VMC files as Hyper-V is a server product. But I intend to do some testing with VPC2007 VMC files as well.
The name also contains ‘import’ instead of ‘migrate’. With importing you can repeat the step as often as you like and nothing in the original VMC file gets changed. With migrate there is usually some form of conversion and sometimes it is a no-way-back process. I think import better reflects the nature of the tool.
There are a couple of small things on the todo list but they may not get into the first release. Things like Guest OS verification with regards to logical processor support or startup and shutdown behavior of the VM. I wonder if people often used the startup/shutdown behavior setting of the VM. If you do, let me know and I may try to add support for those settings.