Create a Gen 2 virtual machine on Windows Server 2012 R2

The second generation of virtual machines has the following improvements:

• Boot time and support x64-based processor: faster boot time and support for virtual machines running 64bits operating systems
• Faster Deployment: Legacy Network Adapter is removed in 2nd generation version, using SCSI controller instead of Legacy IDE Controller allows deployment of Gen 2 virtual machines half the time of Gen 1
• Legacy free: the “legacy” drivers emulating the virtual machine’s hardware are now removed and replaced by drivers detected in the form of synthetic or software-based drivers.
• UEFI-Based: When you start virtual machines, they use UEFI (BIOS) and Software-based drivers. Generation 2 virtual machines will boot in UEFI mode instead of BIOS
• Secure boot: Secure boot support (Windows 8 and Windows 8.1) for virtual machines if the physical server supports UEFI (next generation BIOS platform).
• Network boot: support network boot in IPv4 and IPv6 environments, simple processing and less error.
• Boot from a SCSI CD/DVD: the built-in CD/DVD drive is now emulated running the SCSI engine. Simultaneously support hot-add (hot plug) and hot-remove (hot remove)
• Boot from a SCSI-attached virtual hard disk: VHD hard drives now run SCSI, allowing faster booting than the IDE standard, the IDE standard is removed. Support for new hard drive standard VHDX (allows up to 64TB and supports Online-resizing)
• Additional: In addition, generation 2 virtual machines also inherit old features such as Snapshots, State Transition (Paused or Saved), import/export, backup/restore, Failover replication, Clustering and QoS.

B) Lab creates 2nd generation virtual machine on Windows Server 2012 R2 :

The deployment model is as follows:

• Configure the IP address and join the domain to the AD machine:

• Authenticate with Administrator rights to join the domain

• Install the Hyper-V feature on the Hyper-V1 physical machine. Go to Server Manager -> Add roles and features

• As for the Network (Adapter Network) part of the virtual machine managed by Virtual Switches, this step allows us to declare the Hyper-V host’s physical network card to Virtual Switches so that the virtual machines can use this card to communicate. with the outside.

• Right-click Hyper-V1 -> Select Virtual Switch Manager -> Select the Virtual Switch you just created during the Role installation process -> set the Name to: “Internet”

• This step is the step to configure the Live Migration feature (convert virtual machines from one physical Hyper-V host to another Hyper-V host in the Domain). Usually use the Kerberos protocol to authenticate and manage the live migration process.

• Create virtual machines on Hyper-V Host

• Name the virtual machine and choose the path to save the virtual machine

• Microsoft lets you create Gen 1 or Gen 2 virtual machines

• Configure memory for virtual machines

• Declare Network in Virtual Switches for virtual machines

• Configure the VHD file size of the virtual machine and the location to save the virtual machine in the Hyper-V Host

• Select the Windows installation ISO file for the virtual machine (here I install Windows 8.1)

• Now we have a virtual machine

• Then start the virtual machine up, now by default it boots under the Secure Boot mechanism (But the mainboard in my Hyper-V Host machine does not support UEFI BIOS, so it gives an error)

• Right-click the newly created virtual machine and select Settings -> FirmWare -> uncheck “Enable Secure Boot” and select the boot mode that prioritizes the ISO file.

• Now we start the virtual machine up

• Join domain for virtual machine to Domain : Huypd.com and set the IP address.