You have a Hyper-V host named Server1 that runs Windows Server 2012 R2 Datacenter. Server1 is located in
an isolated network that cannot access the Internet.
On Server1, you install a new virtual machine named VM1. VM1 runs Windows Server 2012 R2 Essentials and
connects to a private virtual network.
After 30 days, you discover that VM1 shuts down every 60 minutes.
You need to resolve the issue that causes VM1 to shut down every 60 minutes.
What should you do?
A.
OnVM1, run slmgr.exe and specify the /ipk parameter.
B.
OnServer1, run slmgr.exe and specify the /rearm-sku parameter.
C.
Create a new internal virtual network and attach VM1 to the new virtual network.
D.
On Server1, run Add-WindowsFeatureVolumeActivation.
Now you have the capability with Automatic Virtual Machine Activation (AVMA) to confi gure the Windows Server 2012 R2 Datacenter edition Hyper-V host to automatically activate any guest VMs that are running on it. All you need to do to use this handy new feature is to first deploy a guest VM with a Windows Server 2012 R2 Datacenter, Standard, or Essentials edition (any operating system below 2012 R2 won’t work with AVMA) and then install the AVMA key
inside the guest VM using the following command:
slmgr /ipk
Once you run this command (substituting the option with the actual key you get with your Windows Server 2012 R2 Datacenter purchase), the guest VM automatically activates itself against its host. If you’re deploying your VMs using an unattended setup file, then adding the AVMA key to it will give you the hands-free approach to activation.
2
0
Thanks, that one I did not know
0
0