Professional Documents
Culture Documents
-0-
Windows Platform - CH 13
-1-
Windows Platform I CH 13
Module Overview
Overview of Virtualization Technologies
Implementing Hyper-V
Managing Virtual Machine Storage
Managing Virtual Networks
-2-
Windows Platform - CH 13
-3-
Windows Platform I CH 13
Desktop Virtualization
Desktop virtualization includes the following technologies:
Client (Local) Hyper-V
MED-V
VDI
-4-
Windows Platform - CH 13
Presentation Virtualization
Differences between desktop virtualization and presentation virtualization
Application Virtualization
Benefits of App-V
Application isolation
Applications that are not compatible with the server’s operating system or with
one another can be run on the same server
Application streaming
Application deployment is quicker because only those parts of the application
that are being used are transmitted across the network to the client computer
Application portability
Applications can follow users across multiple computers, without requiring a
traditional installation on those client computers
-5-
Windows Platform I CH 13
-6-
Windows Platform - CH 13
About Hyper-V
Hyper-V
Is the hardware virtualization role in Windows Server 2012
Gives virtual machine guests direct access to the host's hardware
Terminology
Server also known as parent partition
Virtual machines also known as child partitions
Compatible server operating systems
Windows Server 2012 Full GUI
Windows Server 2012 Server Core
Windows Server 2012 Server Hyper Core
-7-
Windows Platform I CH 13
COM 1
COM 2
Diskette Drive
You can add the following hardware to a virtual machine:
SCSI Controller (up to 4)
Network Adapter
Legacy Network Adapter
Fibre Channel adapter.
RemoteFX 3D video adapter
-8-
Windows Platform - CH 13
-9-
Windows Platform I CH 13
- 10 -
Windows Platform - CH 13
- 11 -
Windows Platform I CH 13
Using Snapshots
Point-in-time copy of a virtual machine
Does not affect running state of a virtual machine
Snapshot files:
Virtual machine configuration .xml file
Saved-state files
Differencing disk (.avhd)
- 12 -
Windows Platform - CH 13
- 13 -
Windows Platform I CH 13
- 14 -
Windows Platform - CH 13
- 15 -
Windows Platform I CH 13
- 16 -
Windows Platform - CH 13
Module_13
Question: Ask the students why they might consider using fixed virtual hard disks
instead of dynamic virtual hard disks.
Answer:
They want to ensure that they retain control over the growth of virtual hard
disks.
They want to pre-allocate storage.
Question: Ask the students in what types of situations they might encounter
difficulties if they used dynamically expanding disks.
Answer: With dynamically expanding disks, it is easy to place multiple dynamically
expanding disks on the same volume, and then have them grow to consume the
volume. You do not have to plan volume use.
Question: What type of virtual network switch would you create if you wanted to
allow the virtual machine to communicate with the local area network connected to
the Hyper-V host?
Answer: You would create an External virtual network switch.
Question: How can you ensure that no one single virtual machine uses all available
bandwidth provided by the Hyper-V host?
Answer: You would configure maximum and minimum bandwidth settings on virtual
network adapters.
Question: What dynamic memory configuration task can you perform on a virtual
machine hosted on Hyper-V 3.0 that was not possible on Hyper-V 2.0?
Answer: You can modify dynamic memory settings while the virtual machine is
running on Hyper-V 3.0. You could not do this on previous versions of Hyper-V.
- 17 -
Windows Platform I CH 13
Question: In which situations should you use a fixed memory allocation rather than
dynamic memory?
Answer: You should use fixed memory allocation in the following situations:
When the guest operating system does not support dynamic memory.
When the host operating system has limited memory resources, and you need
to ensure that operating systems are allocated memory fairly.
Question: In which situations must you use VHDX format virtual hard disks as
opposed to VHD format virtual hard disks?
Answer: You should use VHDX rather than VHD in the following situations:
You need to support virtual hard disks larger than 2 TB. VHDX files can be a
maximum of 64 TB , while VHD files are limited to 2 TB.
You need to protect against data corruption caused by power failures. VHDX
files are less likely to become corrupted in the event of unexpected power
failure because of the way that the file format processes updates.
You need to deploy a virtual hard disk to a large sector disk.
Question: You want to deploy a Windows Server 2012 Hyper-V virtual machine's
virtual hard disk on a file share. What operating system must the file server be
running to support this configuration?
Answer: You can only deploy virtual hard disks to file shares that support SMB 3.0,
and only the Windows Server 2012 operating system supports hosting SMB 3.0 file
shares.
- 18 -