Server virtualization in Windows Server 2012 R2 is based on a module called a hypervisor. Sometimes called a virtual machine monitor (VMM), the hypervisor is responsible for abstracting the computer’s physical hardware and creating multiple virtualized hardware environments, called VMs. Each VM has its own (virtual) hardware configuration and can run a separate copy of an operating system (OS). Therefore, with sufficient physical hardware and the correct licensing, a single computer running Windows Server 2012 R2 with the Hyper-V role installed can support multiple VMs, which administrators can manage as if they were standalone computers.

——————

NOTE: REMOTEFX
RemoteFX enables remote computers to connect Hyper-V guest VMs with an enhanced desktop experience, including graphics adapter virtualization, USB redirection, and intelligent encoding and decoding. Don’t expect many questions about RemoteFX on the exam.

—————–

Following are points which will cover in coming sections

Virtualization architectures

Virtualization products can use several different architectures to share a computer’s hardware resources among VMs. The earlier type of virtualization ...
Read More

Hyper-V implementations

Windows Server 2012 R2 includes the Hyper-V role only in the Standard and Datacenter editions. The Hyper-V role is required ...
Read More

Installing Hyper-V

Once you have the appropriate hardware, you can add the Hyper-V role to Windows Server 2012 R2 by using Server ...
Read More

Using Hyper-V Manager

Once you have installed the Hyper-V role and restarted the computer, you can begin to create VMs and deploy OSs ...
Read More

Configuring resource metering

Resource metering is a Windows PowerShell–based feature in Windows Server 2012 R2 Hyper-V that enables administrators to document VM usage ...
Read More