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.
Looks correct answer
https://technet.microsoft.com/en-GB/library/dn502540.aspx
0
0
slmgr.exe /ipk will then allow you to enter the product key. Validating the license info without connecting to domain.
0
0
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.
0
0
A rearm would reset the activation timers, temporarily solving the issue, so B is the least stupid response here. In the context of the question, it would be slmgr.vbs /rearm-sku [WINDOWS SERVER 2012 R2 ESSENTIALS SKU]
0
0