Your network contains two servers named HV1 and HV2. Both servers run Windows Server
2012 R2 and have the Hyper-V server role installed.
HV1 hosts 25 virtual machines. The virtual machine configuration files and the virtual hard
disks are stored in D:\VM.
You shut down all of the virtual machines on HV1.
You copy D:\VM to D:\VM on HV2.
You need to start all of the virtual machines on HV2. You want to achieve this goal by using
the minimum amount of administrative effort.
What should you do?
A.
Run the Import-VMInitialReplication cmdlet.
B.
From HV1, export all virtual machines to D:\VM. Copy D:\VM to D:\VM on HV2 and
overwrite the existing files. On HV2, run the Import Virtual Machine wizard.
C.
From HV1, export all virtual machines to D:\VM. Copy D:\VM to D:\VM on HV2 and
overwrite the existing files. On HV2, run the New Virtual Machine wizard.
D.
Run the Import-VM cmdlet.
Explanation:
Wouldn’t this be B?
You need to export them first, not just copy them over?
copy will work just fine, tried it myself
Thanks mina, you are an active student.
Strange question
I think it is B:
http://technet.microsoft.com/en-us/library/hh831535.aspx
Starting in Windows Server 2012, you no longer need to export a virtual machine to be able to import it. You can simply copy a virtual machine and its associated files to the new host, and then use the Import Virtual Machine WIZARD to specify the location of the files. This registers the virtual machine with Hyper-V and makes it available for use.
In addition to the wizard, the Hyper-V module for Windows PowerShell includes cmdlets for importing virtual machines. For more information, see Import-VM
During the import process, you can choose how to import the virtual machine:
The question states that you’ve already copied the files to the other server, so all you need to do is import them. If you select B as your answer then you’re just copying the VMs a second time for no reason.
Tell the correct answer plzz???
hi hassan, 7cham 3la 3aradak i guess the answer
Hassan f**k off posting this on every question
The answer is B. The Import-VM cmdlet should be combined with the -register switch in this instance. The config files and vhdx have already been copied to new server.
https://technet.microsoft.com/en-us/library/hh848495.aspx
D
https://technet.microsoft.com/en-gb/library/hh831535.aspx
Starting in Windows Server 2012, you no longer need to export a virtual machine to be able to import it. You can simply copy a virtual machine and its associated files to the new host, and then use the Import Virtual Machine wizard to specify the location of the files. This registers the virtual machine with Hyper-V and makes it available for use.
The Import-VM cmdlet imports a virtual machine from a file.
https://technet.microsoft.com/en-us/library/hh848495.aspx
^ There you have it. If there’s ambiguity, always go with the answer that demonstrates new features.
D
D. import directly, no syntethic driver conversion needed
agree with D, not B as you have already copied the files so this would just copy them again. All you need to do is import it.
Brad and Joe, I would suggest you should not use language like this, cos the we use shows how our parents brought up us and our company. If someone asks some question, we should reply him/her patiently.
Hina
I’m gonna have to agree with D to because…
1. Minimal amount of administrative effort(This Matters ALOT!!!)
2. The VM files have already been copied which would automatically go against 1, because of the redundancy
3. You are already doing answer D in answer B, but B is overwriting what you have already copied, which is literally the same thing.
Technet isn’t even needed for this one…