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 R2.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:
* The following configurations and settings can be migrated automatically include:
/ Most virtual machine configurations. Virtual machines and their data are moved as part of
the migration, but some configurations require manual intervention
/ Hyper-V settings. These include the system-wide settings and the authorization store.
References:
http://technet.microsoft.com/en-us/library/ee849855%28v=WS.10%29.aspx
Can someone explain this one to me? I can’t really find any information that VHD files aren’t migrated.
0
0
The following link will help you, to understand the migration process:
https://technet.microsoft.com/library/jj574113
0
0
I’m still really not following. I see on there that VFD (Virtual Floppy Disk) is mentioned and that one I know is correct in the question but I don’t see any mention of VHD files not getting moved. I see a mention of pass-through disks but in that case they aren’t VHD files then at that point correct? I need someone to show me the light on this because I’m just not getting it for some reason :/.
0
0
The problem with that link is that it is for “2012” and not “2012 R2”. Server 2012 R2 has other issues… I’ll post a reply to describe it below.
0
0
I don’t really found any direct clue in this technet article aswel as other articles, but what it does indicate for what the duration concerns is:
“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.”
Also, under role config en settings, it states that “Virtual machine (configuration AND data)” is migrated.
So I think we can assume VHD’s can be migrated, and the answer should be:
Can, Can, Can, Cannot
Correct me if I’m wrong
0
0
I have to agree. I can’t find any documentation that states that VHD files attached to a machine do not get migrated. It states in the link you are referring to that virtual machine configurations AND data can be migrated and Hyper-V settings as well. As you mentioned it does state about VHDs possibly taking a long amount of time to migrate (which to me says right there that VHDs attached to the machine DO get migrated). It states specifically that Virtual Floppy Disks (VFDs) can not. So to me it looks like can, can, can, cannot is correct.
0
0
This got my attention so I did more research and found this link interesting: http://blog.bruteforcetech.com/archives/955
“The only catch here could be if the second host runs 2012 R2 and not just 2012. Hyper-V Manager of Windows Server 2012 R2 cannot import virtual machines exported from Windows Server 2012 or earlier. In that case, you will have to create a new VM by using the existing VHD/VHDX files.” – See more at: http://blog.bruteforcetech.com/archives/955#sthash.xXbA84Xv.dpuf
0
0
Also from here: http://blogs.technet.com/b/rmilne/archive/2013/10/22/windows-hyper-v-2012-amp-8-1-hyper-v-did-not-find-virtual-machine-to-import.aspx
“VM’s that are exported from Windows Server 2008 or 2008 R2 utilized the version 1 WMI namespace which resulted in an .exp file to represent the exported virtual machine. In Windows Server 2012 we introduced a new WMI namespace (version 2 or root\virtualization\v2) which implemented a much better import/export model – allowing you to effectively just copy the virtual machine folder (with the VM’s XML configuration file inside it) as well as the VM’s VHDs and then import that directly. For Windows Server 2012 we maintained the version 1 WMI namespace which allowed for importing of Windows Server 2008/R2 VM’s on 2012.
In Windows Server 2012 R2 we have removed the old version 1 namespace which means we can’t import virtual machines that where exported from Windows Server 2008/R2.”
0
0
So it is YYYN.
0
0
No, according to this post by grande, it’s YYNN, the answer is correct:
“The only catch here could be if the second host runs 2012 R2 and not just 2012. Hyper-V Manager of Windows Server 2012 R2 cannot import virtual machines exported from Windows Server 2012 or earlier. In that case, you will have to create a new VM by using the existing VHD/VHDX files.” – See more at: http://blog.bruteforcetech.com/archives/955#sthash.xXbA84Xv.Tm9QA2qb.dpuf.
According to the question, Server1 has Server 2008 R2 installed and Server2 has Server 2012 R2, you won’t be able to import.
So it’s YYNN.
0
0
Correct.
I passed my exam with a score of 928 about 3 weeks ago. Got 100% in Hyper-V section.
0
0
Congratulations for this very high score. I will pass my exam in few days but I’m afraid to lose.
To success did you train a lot with this dump exam or more read books ?
Thank you
0
0
What dumps did you use?thank you
0
0
This question has been updated on the latest exam. It now has 5 options to select from, including “Virtual machine queue (VMQ) networking settings”
0
0
Although this article is about Server 2008 and 2008 R2, VMQ networking settings can be automatically migrated.
Reference:
https://technet.microsoft.com/pt-pt/library/Ee849855(v=WS.10).aspx
0
0
VMQ came up in my question as well and yes you can migrate.
0
0
I believe this is only matter of no entirely clear definition. it says “VHD files attached to VM” so I´d say this counts as another disks. The vhd file that serves as system drive for the virtual machine is getting transfered. But if you add another volumes, iSCSI volumes backed by VHD etc, these don´t get transfered.
0
0
it’s very simple regarding the VHD(X) and the VM Configuration files
These Files are not migrated automatically !!
No matter if you follow the Migration Guide from W2k8R2 to W2k12R2, which doesn’t use Migration tools:
https://technet.microsoft.com/en-us/library/dn872560.aspx
nor if you follow the Guide to Migrate from W2k8 R2 to W2k12:
https://technet.microsoft.com/de-de/library/jj574226.aspx>
both tell you to copy the VM folders manually or with a script
thanx to Hugh Jorgan for the update
0
0
if you uses only “Windows Server Migration Tools” feature, vhd will not migrated. VHD should be migrated by robocopy, not by WSMT.
yes,yes,no,no
0
0
https://technet.microsoft.com/en-us/library/jj574113.aspx
yes yes no no
0
0
Based on the URL referenced above many times (https://technet.microsoft.com/en-us/library/jj574113.aspx) there is NO mention of VHD or VHDX files whatsoever besides the section titled “Estimated Duration”, wherein it describes the impact of migration completion time resulting from larger .vhd files. Therefore, I have to disagree with Y Y N N. I say Y Y Y N.
0
0