DRAG DROP
You have two servers named Server1 and Server2 thatrun Windows Server 2012. Server1 has the Hyper-V
server role installed. Server1 hosts a virtual machine named VM1.
VM1 is currently running. VM1 has a snapshot that was created two weeks ago.
You plan to use Server2 to perform a forensic analysis of the contents of the disk of VM1 from two weeks ago.
You need to ensure that you can view the contents of the disk of VM1 from two weeks ago from Server2.
Which three actions should you perform in sequence?(To answer, move the appropriate three actions from the
list of actions to the answer area and arrange themin the correct order.)
Answer: 
Explanation:
I think the last step should mount the vhdx disk on server2
Correct.
1. On Server1, right-click VM1, and then click shutdown
2. On Server1, right-click the snapshot of VM1, and then click Export
3. On Server2, run the Mount-Vhd cmdlet
step 1: Shutdown vm1
steo 2: export vm1
step 3: export snapshot vm1
Hi Bean ,
Could you please help to verify on this
Step1: Shutdown VM1
Step2: export VM1 => (include all snapshot into VHD file)
“In addition to virtual machine configuration and virtual disk image files, the Import/Export process will also transfer any existing snapshots for the virtual machine” – http://www.virtuatopia.com/index.php/Migrating_Hyper-V_Virtual_Machines_Using_Import/Export
Step3: Mount-VHD
http://technet.microsoft.com/en-us/library/hh848551.aspx
So you have answer for,” You need to ensure that you can view the contents of the disk of VM1 from two weeks ago from Server2.” => just my opinion
perfect !
I think it is:
On Server1, right-click VM1, and then clich Shutdown
On Server1, right-click VM1, and then click Export
On Server2, run the Mound-vhd cmdlet
I agree with Rafik.
I seems like the snapshot was already taken (“two weeks ago”), so no need to shutdown VM and retake it. I just tried running a VM, and you can’t export snapshot while running. The solution should ensure you can view image from Server2, so it needs to get there. Snapshot already exists.
On Server1, right-click VM1, and then click Shutdown.
On Server1, right-click the snapshot of VM1, and then click Export …
On Server2, run the Mount-Vhd cmdlet.
dism.exe /append-image consolidates images to one .wim file.
http://technet.microsoft.com/en-us/library/hh824916.aspx
I just tested this scenario in vm.
When you export the VM it exports all the Snapshots along with it.
When you right click on a particular snapshot and export it then only the image of the drive when snapshot was taken is exported. which is the requirement of this question.
also in order to export a particular snapshot we have to first shutdown the VM
so the tested results are:
1. On Server1, right-click VM1, and then click shutdown
2. On Server1, right-click the snapshot of VM1, and then click Export
3. On Server2, run the Mount-Vhd cmdlet
note : the snapshot should be exported to a shared drive so that it can be accessed by server2.
I had snapshot of currently running VM. Then I right-click VM1, click SAVE, and then exported snapshot.
So below answer also could be correct. Am I right?
1. On Server1, right-click VM1, and then click SAVE
2. On Server1, right-click the snapshot of VM1, and then click Export
3. On Server2, run the Mount-Vhd cmdlet
It is wrong to chose SAVE because this creates the latest snapshot which is not required.
The required snapshot is that the two week back.
Step1: On Server1, right-click VM1, and then click Shutdown.
Step2: On Server1, right-click the snapshot of VM1, and then click Export (You should not export VM1 because it will export all snapshots if any other that the two weeks back required snapthot which is not necessary)
http://www.virtuatopia.com/index.php/Migrating_Hyper-V_Virtual_Machines_Using_Import/Export
Step3: On Server2, run the Mound-vhd cmdlet
http://technet.microsoft.com/en-us/library/hh848551.aspx
FOR R2:
Step1: On Server1, right-click the snapshot of VM1, and then click Export (You should not export VM1 because it will export all snapshots if any other that the two weeks back required snapthot which is not necessary)
Step2: On Server2, run the Mound-vhd cmdlet
Whay would you just export the snapshot as it would be pointless without the actual VM being exported. If you export the VM the snapshot go with.
On Server1, right-click VM1, and then clich Shutdown
On Server1, right-click VM1, and then click Export
On Server2, run the Mound-vhd cmdlet
In addition to virtual machine configuration and virtual disk image files, the Import/Export process will also transfer any existing snapshots for the virtual machine” – http://www.virtuatopia.com/index.php/Migrating_Hyper-V_Virtual_Machines_Using_Import/Export
I’m i mad or did i miss somewhere in the question that the VM has already been imported?
Does anyone else find this question a bit thin on details? Why the need to shut it down when there is Live Migration?
yes. also my q. I did it witout shudown
But, what about the new options that Hyper-v 2012 came up with:
“Hyper-V is updated to support exporting a virtual machine or a virtual machine checkpoint while the virtual machine is running. You no longer need to shut down a virtual machine before exporting.”
“The Export option is now available as an action for a running virtual machine from Hyper-V Manager. The following Windows PowerShell cmdlets can be used on a running virtual machine, Export-VM and Export-VMSnapshot”
http://technet.microsoft.com/en-us/library/dn282278.aspx
So, for me answer must be:
1. On Server1, right-click the snapshot of VM1, and then click Export
2. On Server2, run the Mount-Vhd cmdlet
wrong, live export became available in hyper-v 2012 R2. This question doesn’t mention r2, so shutdown first.
I think
1. Export VN snapshot
2. Save VM
3. Mount Diskt on server2
what you tink ?
we can export Snapshot withour shutdown the VM
David’s answer looks to be correct.
thanks a tonn david..