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.
Correct.
slmgr /ipk
Attempts to install a 5×5 product key. The product key provided by the parameter is confirmed valid and applicable to the installed operating system.
If not, an error is returned.
If the key is valid and applicable, the key is installed. If a key is already installed, it is silently replaced.
To prevent instability in the license service, the system should be restarted or the Software Protection Service should be restarted.
This operation must be run from an elevated command prompt, or the Standard User Operations registry value must be set to allow unprivileged users extra access to the Software Protection Service.
http://technet.microsoft.com/en-us/library/dn502540.aspx
yes this is correct
Server reboots every hour because it requires license activation.
http://windowsitpro.com/blog/windows-server-2012-r2-evaluation-edition-shuts-down-every-hour
Since it is on private network, online activation is not possible.
For disconnected activation, Datacenter server has a feature to provide automatic virtual machine activation
https://technet.microsoft.com/en-au/library/dn303421.aspx
Above feature need to be installed on the host server. Once done, the following command needs to be run on Essential server to be activated via AVMA service
slmgr /ipk K2XGM-NMBT3-2R6Q8-WF2FK-P36R2
Answer A,D
If you have to choose one answer only, I would go for D.
Is the command not “Install-WindowsFeature VolumeActivation”? As in the D command will not work..?
Answer should therefore be A?
D is wrong, the command is
Install-WindowsFeature VolumeActivation
There isn’t a correct answer here.
Automatic Virtual Machine Activation (AVMA) would ensure this didn’t happen (this is built into Windows Server 2012 R2 DATACENTER Edition).
D refers to KMS – if you want your server to activate others (not necessarily VMs) and clients, then you would configure this.
The problem is caused by licensing though; and slmgr.vbs /ipk won’t fix it as you will need to activate it – to do this, you would need slmgr.vbs /ato, BUT due to there being no Internet connection, this isn’t an option.
Therefore, the only way to fix is to activate by phone (although in real life, you wouldn’t have this issue due to AVMA on Server 2012 R2 Datacenter). Badly written question with no correct answer.
B is the least stupid answer as a rearm would reset the activation timers, thus temporarily fixing the issue.