HOTSPOT
You have a Hyper-V host named Server1 that runs Windows Server 2008 R2. All of the virtual machines on
Server1 use VHDs.
You install the Hyper-V server role on a server named Server2 that runs Windows Server 2012. Server2 has
the same hardware configurations as Server1.
You plan to migrate the Hyper-V host from Server1 to Server2 by using the Windows Server Migration Tools.
In the table below, identify what can be migrated by using the Windows Server Migration Tools. Make only one
selection in each row. Each correct selection is worth one point.
Answer: 
Explanation:
I think all of them can be migrated. Anyone can explain the answer ?
I hear some are saying only the floppy disks cannot be migrated.
http://technet.microsoft.com/library/ee849855(v=ws.10)
The answer is correct as is..
Connections to physical disks directly attached to virtual machines cannot be migrated with the tools.
I think only floppy disks cannot be migrated. I think VHD files should migrate too.
And what part of a “V”hd is physical to you? You do realize vhd stands for “virtual” hard disk?
Correct answer is YYYN.
Virtual Machines (configuration and data), Hyper-V settings, and VHDs attached to VMs are migrated. VHD files would migrate although VFD (Virtual Floppy Disks) will not.
I think the answer is “Can, Can, Can, Cannot”.
http://technet.microsoft.com/en-us/library/jj574113.aspx
VHDs are files, not disks and so therefore can be migrated.
Answer is correct as is.
http://technet.microsoft.com/en-us/library/ee849855(WS.10).aspx
Incorrect, your link proves that everything in the list apart from VFD (virtual floppy disks) can be migrated.
Correct answer is: Can, Can, Can, Cannot.
If you can’t migrate VHDs, how is the VM supposed to boot?
This should settle it. from http://technet.microsoft.com/en-us/library/ee849855(WS.10):
Estimated duration
The length of time it takes to migrate the Hyper-V role depends on the size of the data to be transferred. Of the various types of files to be transferred, the .vhd files have the largest file sizes (from a few gigabytes to many gigabytes in size). The length of time is affected by the size of the .vhd files and by the network bandwidth.
…so its CAN CAN CAN CANNOT. The only thing that cannot be migrated is the VFD.
I really cannot understand why virtual floppy disks cannot be migrated.It’s bloody files, like VHDs. And all these links above don’t mention virtual floppy drives at all…
In my understanding answer should be all Yes.
Actually, it is right, floppy is not migrated, because they don’t needed…
“VFD and ISO files. These files are not migrated..”
So, answers YYYN
I think they meant VFD in the question and not VHD
I don’t think the migration tool will migrate the VHD’s, they have to be done manually, will have to check this in my lab.
For sure you can migrate VHD files bc Microsoft states:
“VFD and ISO files. These files are not migrated because they are not required for the virtual machine to operate and are not supported by the Import and Export cmdlets”.
Key phrase is:”because they are not required for the virtual machine to operate and are not supported by the Import and Export cmdlets”
VHD files can be imported by cmdlets AND are required for the VM to operate.
Answer: YYYN
https://technet.microsoft.com/en-us/library/jj574113.aspx
The length of time it takes to migrate the Hyper-V role depends on the size of the data to be transferred. Of the various types of files to be transferred, the .vhd files have the largest file sizes (from a few gigabytes to many gigabytes in size). The length of time is affected by the size of the .vhd files and by the network bandwidth.
And then there’s this which is specifically for migrating from 2008R2 to 2012:
https://technet.microsoft.com/en-us/library/jj574226.aspx
Which clearly has a manual step to copy data using Robocopy.. which makes me lean back to the YYNN anser given in the example.
answer:
can, can, can, cannot.
the vhd file can be migrated, the VFD cannot be migrated.
VFD cannot be migrated. They are not present in 2012 R2
http://windowsitpro.com/site-files/windowsitpro.com/files/uploads/2014/03/Savill%20WIN2806%20Server%202012%20R2%20Hyper-V_Figure1.jpg
CAN, CAN, CAN, CAN’T …
From link provided above: https://technet.microsoft.com/library/ee849855(v=ws.10)
*********************************
Hyper-V migration overview
…
The migration tools include cmdlets that you use to perform some of the tasks required to migrate the Hyper-V role. The Export cmdlet captures the majority of the Hyper-V settings that are required to perform a successful migration, including the virtual machine configurations, virtual networks, and virtual hard disks. The DCOM and WMI namespace security settings must be migrated separately. The instructions for this are provided later in the guide. On the destination server, the import cmdlets will recreate the virtual machines.
*********************************