Implementing Server Virtualization with Hyper-V 20410D 13: Implementing Server Virtualization with Hyper-V Presentation: 60 minutes Lab: 70 minutes After completing this module, students should be able to: Describe the Microsoft® virtualization technologies. Implement Hyper‑V®. Manage virtual machine storage. Manage virtual networks. Required Materials To teach this module, you need the Microsoft Office PowerPoint® file 20410D_13.pptx. Important: We recommend that you use Office PowerPoint 2007 or a newer version to display the slides for this course. If you use PowerPoint Viewer or an earlier version of Office PowerPoint, all the features of the slides might not display correctly. Module 13 Implementing Server Virtualization with Hyper-V

Managing Virtual Networks 20410D Module Overview 13: Implementing Server Virtualization with Hyper-V Managing Virtual Networks Provide a brief overview of the module content. If the labs are hosted rather than being run on classroom machines, you will be able to perform only “Exercise 3: Creating and Configuring a Virtual Machine.” Hyper-V does not support nested virtual machines, so students cannot perform exercises 1, 2, and 4. As part of your preparation, you might consider using a screen-recording app to record exercises 1, 2, and 4, while running the labs on your own equipment. You then can show these videos to the students.

Lesson 1: Overview of Virtualization Technologies 20410D Lesson 1: Overview of Virtualization Technologies 13: Implementing Server Virtualization with Hyper-V What Is Microsoft Application Virtualization? Briefly describe the lesson content.

Server Virtualization 20410D Server Virtualization 13: Implementing Server Virtualization with Hyper-V Benefits of server virtualization with Hyper-V include: Invisible to users Guest machines can use different operating systems More efficient use of hardware Service and application isolation Workload consolidation Simplifies server deployment by using: Virtual machine templates App-Controller virtual machine self-service portal Students likely are familiar with server virtualization. Many students probably use a non-Microsoft virtualization solution in their environment. Ask students if they have deployed server virtualization, and talk about non-Microsoft products, such as VMware, Citrix XenServer, and VirtualBox.

20410D What Is Windows Azure? 13: Implementing Server Virtualization with Hyper-V Windows Azure is a cloud-based platform for hosting virtual machines and applications You pay only for the resources that you use You can increase and decrease capacity automatically and swiftly You can use Windows Azure to: Host websites Host production applications Host virtual machines Test proof-of-concept solutions Discuss cloud providers such as Amazon EC2. Ask students if they are using either a public cloud or a private cloud in their organization. If they are, ask them what led them to this decision. Point out to students that they can sign up for a 30-day trial of Windows Azure by going to http://www.windowsazure.com.

Desktop Virtualization 13: Implementing Server Virtualization with Hyper-V Desktop virtualization includes the following technologies: Client (Local) Hyper-V VDI RemoteFX allow virtual machines to display rich graphics and video capabilities RemoteFX requires: GPU that supports DirectX 9.0c or newer CPU that supports SLAT Discuss the use of desktop virtualization and the differences between Virtual PC on Windows® 7 and Client Hyper‑V on Windows 8 and Windows 8.1 Virtual PC can run only x86 virtual machines. Client Hyper‑V supports almost all features available in Hyper‑V on Windows Server 2012. Discuss why administrators might want to run demonstration labs on Windows 8 or Windows 8.1 clients, rather than deploying them on production servers. This method allows a less formal proof-of-concept phase before dedicating organizational resources to a test.

Presentation Virtualization 20410D Presentation Virtualization 13: Implementing Server Virtualization with Hyper-V Differences between desktop virtualization and presentation virtualization Presentation virtualization technologies include: Remote Desktop Services Full Desktop with RDC Applications using RemoteApp Remote Access through RD Gateway Desktop virtualization: Presentation virtualization: Users are assigned their own virtual machines that are running a client operating system Users sign in and run separate sessions on the server The desktop and apps run on the host server The desktop and apps run within virtual machines Discuss the architecture of presentation virtualization: Apps run on the server. Apps display on the client. Ask students if they have deployed Remote Desktop Services or Terminal Services in their organization. Some students may use Citrix XenServer in their organization, and will not be using Remote Desktop Services. Discuss the use of RemoteApp as a type of self-service portal for programs.

What Is Microsoft Application Virtualization? 20410D What Is Microsoft Application Virtualization? 13: Implementing Server Virtualization with Hyper-V Benefits of App-V App isolation Incompatible programs can run on the same server App streaming App deployment is quicker App portability Apps can follow users across multiple computers UE-V App and operating system settings follow users across multiple computers Discuss the benefits of application virtualization, not just in terms of compatibility, but also in terms of allowing apps to be deployed to a client computer without requiring a full local installation. Ask students if they use application virtualization in their own environments. If so, ask them which app they most often virtualize. Discuss the benefits of deploying User Experience Virtualization (UE-V) with Microsoft Application Virtualization (App-V).

Lesson 2: Implementing Hyper-V 20410D Lesson 2: Implementing Hyper-V 13: Implementing Server Virtualization with Hyper-V What’s New with Hyper-V in Windows Server 2012 R2 Provide a brief overview of the lesson content.

Compatible Windows Server operating systems: What Is Hyper-V? 13: Implementing Server Virtualization with Hyper-V Hyper-V: Is the hardware virtualization role in Windows Server 2012 Gives virtual machine guests direct access to the host’s hardware Compatible Windows Server operating systems: Windows Server 2012 Microsoft Hyper-V Server 2012 Describe the history of Hyper‑V, which includes that it was: Released with Windows Server 2008. Improved in Windows Server 2008 R2 Service Pack 1 (SP1). Is included in Windows Server 2012 as Hyper‑V 3. Compare Hyper‑V to products such as Virtual PC, Virtual Server, and non-Microsoft virtualization solutions.

Hardware Requirements for Hyper-V 13: Implementing Server Virtualization with Hyper-V Factors to consider when planning hardware for servers running Hyper-V: Processor characteristics Must have an x64 platform that supports hardware assisted virtualization and Data Execution Protection Processing capacity Memory Storage subsystem performance Network throughput (typically multiple network interface cards) Remind students that they need a processor that supports hardware assisted virtualization, and that this is not always enabled in the BIOS.

Virtual Machine Hardware 13: Implementing Server Virtualization with Hyper-V Virtual machines have the following simulated hardware by default: BIOS Memory Processor IDE Controller 0 and 1 SCSI Controller Synthetic Network Adapter COM 1 and 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 When presenting this slide, explain the different hardware components that virtual machines can include. Additionally, explain the limitations of Integrated Drive Electronics (IDE) and SCSI devices.

Generation 2 Virtual Machines 20410D Generation 2 Virtual Machines 13: Implementing Server Virtualization with Hyper-V Generation 2 virtual machines differ from generation 1 virtual machines: Emulated devices are removed UEFI firmware instead of BIOS Secure Boot Boots from SCSI controller PXE boot uses a standard network adapter Faster boot and operating system installation Can run side-by-side with generation 1 Generation 1 must be used for legacy systems Supported guest operating systems: Windows Server 2012 and Windows Server 2012 R2 64-bit versions of Windows 8 and Windows 8.1 Introduce the generation 2 virtual machine. Point out that virtual machines that were used before Windows Server 2012 R2 are all generation 1, and that generation 2 virtual machines are available only with Hyper- V on Windows Server 2012 R2. Explain that unlike with generation 1 virtual machines, emulated hardware components are not present in generation 2 virtual machines. Conversely, new features, such as Secure Boot and boot from SCSI controller, are present in generation 2 virtual machines. Point out that generation 2 virtual machines do not have better performance, except when starting and installing operating systems. Emphasize that you can install only supported operating systems on generation 2 virtual machines, which are: Windows Server 2012. 64-bit versions of Windows 8 and newer operating systems.

Dynamic Memory settings for a virtual machine What Is Dynamic Memory? 13: Implementing Server Virtualization with Hyper-V Dynamic Memory settings for a virtual machine Explain to students that you can access the virtual machine Settings dialog box by right-clicking the virtual machine, and then clicking Settings. Discuss the benefits of using Dynamic Memory over statically allocated memory. Explain how in Windows Server 2012, you can change Dynamic Memory settings while the virtual machine operating system is running. Discuss this new feature, and explain in what scenarios it is most useful.

Configuring Virtual Machine Integration Services 20410D Configuring Virtual Machine Integration Services 13: Implementing Server Virtualization with Hyper-V Possible integration services include: Operating system shutdown Time synchronization Data exchange Heartbeat Backup (volume snapshot) Enhanced session mode allows a connection to a virtual machine that is similar to remote desktop because it: Enables device redirection Uses a shared clipboard Enables folder redirection The parameters on the slide are listed in the virtual machine’s Settings dialog box. This dialog box is accessible by right-clicking on a virtual machine, and then clicking Settings. Describe each virtual machine integration services component. Describe the supported operating systems. Mention that it is not necessary to install virtual machine components, but that it does make managing virtual machines substantially easier.

Configuring Virtual Machine Start and Stop Actions 13: Implementing Server Virtualization with Hyper-V Possible automatic start actions: Nothing Automatically start if it was running when the service stopped Always start this virtual machine automatically Possible automatic stop actions: Save the virtual machine state Turn off the virtual machine Shut down the guest operating system Discuss the different virtual machine start and stop actions, and ask the students in what scenarios they would configure a virtual machine to start automatically. Additionally, ask them to determine what start delay they would apply to different virtual machines on a host virtualization server that is running Hyper‑V.

Hyper-V Resource Metering 20410D Hyper-V Resource Metering 13: Implementing Server Virtualization with Hyper-V Parameters that you can measure with resource metering: Average CPU use Average physical memory use, including: Minimum memory use Maximum memory use Maximum disk space allocation Incoming network traffic for a network adapter Outgoing network traffic for a network adapter Remind students that they can only perform Resource Metering from a Windows PowerShell® command- line interface. Discuss the likelihood that future versions of Windows Server 2012 and Microsoft System Center 2012 - Virtual Machine Manager (VMM) should have a method for using Microsoft SQL Server® Reporting Services to display this data in graphical format.

What’s New with Hyper-V in Windows Server 2012 R2 13: Implementing Server Virtualization with Hyper-V New or Improved Feature New to Windows Server 2012 R2 Shared virtual hard disk Automatic virtual machine activation Enhanced session mode Storage quality of service Virtual machine generation Improved in Windows Server 2012 R2 Resize virtual hard disk Live migration Failover Clustering Integration services Export Replica Linux support Management Before beginning this topic, determine how to cover the improved features in Windows Server 2012 R2. In some cases, you might want to explain the features in both Windows Server 2012 and Windows Server 2012 R2. For example, if your students are not familiar with the features of Live Migration, explain it in terms of both the Windows Server 2012 and Windows Server 2012 R2 features. Spend less time presenting the differences between Windows Server 2012 and Windows Server 2012 R2 if students are only going to use or deploy Windows Server 2012 R2 in their environment.

Lesson 3: Managing Virtual Machine Storage 20410D Lesson 3: Managing Virtual Machine Storage 13: Implementing Server Virtualization with Hyper-V Using Checkpoints Provide a brief description of the lesson content.

What Is a Virtual Hard Disk? 13: Implementing Server Virtualization with Hyper-V .vhdx format provides several benefits compared to the .vhd format, including that the: Disks can be larger (64 TB versus 2 TB) Disk corruption is less likely to occur Format supports better alignment when deployed to a large sector disk Format supports larger block size for dynamic and differencing disks Multiple virtual machines can use shared virtual hard disks Storage QoS allows you to limit virtual hard disk IOPS Ask students in what format their backups from Windows Server Backup (a feature of Windows Server 2008) are written. Many students are not aware that backups are written to virtual hard disk. Remind students that using .vhdx files limits a virtual machine to running on Hyper‑V on Windows Server 2012, and that Server Message Block (SMB) 3.0 has limitations when using virtual hard disks on shared folders.

Creating Virtual Disk Types 13: Implementing Server Virtualization with Hyper-V Fixed-size virtual hard disks vs. dynamic virtual hard disks Discuss the benefits and drawbacks of using direct-attached storage. One drawback in particular is that it makes it more complicated to perform consistent backups of the virtual machine because the physical disk drive is not contained within a virtual hard disk file. Question Why might you consider using fixed virtual hard disks instead of dynamically expanding virtual hard disks? Answer You might want to use fixed virtual hard disks instead of dynamically expanding virtual hard disks when: You want to maintain control over the growth of virtual hard disks. You want to pre-allocate storage. In what situations might you encounter difficulties if you use dynamically expanding disks? It is easy to place multiple dynamically expanding disks on the same volume. They can then grow and consume the volume. 100 GB used 600 GB allocated 600 GB fixed-size disk 100 GB allocated 600 GB dynamic disk

Managing Virtual Hard Disks 13: Implementing Server Virtualization with Hyper-V The following are maintenance operations that you can perform on virtual hard disks: Convert from fixed to dynamic Convert from dynamic to fixed Convert from .vhd to .vhdx format Convert from .vhdx to .vhd format Shrink a dynamic virtual hard disk Expand a dynamic or fixed virtual hard disk Remind students that they can shrink only dynamically expanding virtual hard disks, and not fixed virtual hard disks. However, point out that there is a workaround. They can convert a fixed virtual hard disk to a dynamically expanding virtual hard disk, shrink the dynamically expanding virtual hard disk, and then convert it back to a fixed virtual hard disk.

Reducing Storage Needs with Differencing Virtual Hard Disks 13: Implementing Server Virtualization with Hyper-V When using differencing disks, you: Can reduce space that is used by storage, but at the cost of performance Can link multiple differencing disks to a single parent disk Cannot modify the parent disk Can use the Inspect Disk tool to reconnect a differencing disk to a missing parent Explain why differencing virtual hard disks reduce storage use. For example, you can create a sysprepped virtual hard disk that has an operating system installed as a parent hard disk. You can deploy new operating systems quickly by creating differencing virtual hard disks off that parent. This process is much faster than performing traditional deployment. Explain why differencing virtual hard disks do not perform as well as traditional virtual hard disks. The primary disadvantage of a differencing virtual hard disk is that you need to ensure that the parent is not modified. Discuss using read-only parents for differencing virtual hard disks. Reinforce that Windows Server 2012 Hyper-V resolves the performance issues that existed with differencing virtual hard disks in earlier Hyper-V versions.

Using Checkpoints Checkpoints: Using checkpoints: 20410D Using Checkpoints 13: Implementing Server Virtualization with Hyper-V Checkpoints: Are static images of the data on a virtual machine at a given moment Are not replacements for backups Were called snapshots in previous versions Using checkpoints: When you create a checkpoint, Hyper-V writes to a differencing virtual hard disk When you apply a checkpoint, the virtual machine reverts to the configuration as it existed at the time the checkpoint was created You can perform a virtual machine export of a checkpoint This topic has five static slides. Use the next four slides to illustrate how the process of creating and reverting checkpoints works. Slide 1 of 5 Explain the difference between a checkpoint and a backup, and ensure that students understand these differences. Remind the students that there is a limit of 50 checkpoints per virtual machine. Once you have 50 checkpoints, you must delete an existing checkpoint manually before you can create another one. Describe how to use branching checkpoint trees. Explain that using checkpoints with domain controllers, SQL Server, and Microsoft Exchange Server servers can lead to unpredictable results.

Using Checkpoints 1. A checkpoint is created every day Original 13: Implementing Server Virtualization with Hyper-V 1. A checkpoint is created every day Original Monday Checkpoint Tuesday Checkpoint Slide 2 of 5 The next four slides show the process of creating and reverting checkpoints. Step 1: A checkpoint is created every day.

Using Checkpoints 1. A checkpoint is created every day 13: Implementing Server Virtualization with Hyper-V 1. A checkpoint is created every day 2. You locate a problem after Tuesday’s checkpoint is created Original Monday Checkpoint Tuesday Checkpoint Slide 3 of 5 Step 2: You locate a problem after Tuesday’s checkpoint is created

Using Checkpoints 1. A checkpoint is created every day 13: Implementing Server Virtualization with Hyper-V 1. A checkpoint is created every day 2. You locate a problem after Tuesday’s checkpoint is created 3. You solve the problem by reverting back to the Monday checkpoint Original Monday Checkpoint Tuesday Checkpoint Slide 4 of 5 Step 3: You solve the problem by reverting to the Monday checkpoint.

Using Checkpoints 1. A checkpoint is created every day 13: Implementing Server Virtualization with Hyper-V 1. A checkpoint is created every day 2. You locate a problem after Tuesday’s checkpoint is created 3. You solve the problem by reverting back to the Monday checkpoint 4. The next checkpoint is created on Wednesday Original Monday Checkpoint Tuesday Checkpoint Wednesday Checkpoint Now Slide 5 of 5 Step 4: The next checkpoint is created on Wednesday.

Lesson 4: Managing Virtual Networks 20410D Lesson 4: Managing Virtual Networks 13: Implementing Server Virtualization with Hyper-V What Is NIC Teaming? Briefly review the lesson content.

What Is a Virtual Switch? 20410D What Is a Virtual Switch? 13: Implementing Server Virtualization with Hyper-V Hyper-V on Windows Server 2012 supports the following three types of virtual switches: External Used to map a network to a specific network adapter or network adapter team Internal Used to communicate between the virtual machines on the host and between the virtual machines and the host itself Private Used to communicate between virtual machines, but not between the virtual machines and the host itself Describe the three different types of virtual switches, and ask the students to determine scenarios in which it would be appropriate to use an internal virtual switch, but not a private virtual switch. Ask students whether they would configure virtual local area networks (VLANs) at the network adapter level or at the virtual switch level, and why.

What Are Virtual Local Area Networks? 20410D What Are Virtual Local Area Networks? 13: Implementing Server Virtualization with Hyper-V When you use VLANs, you can: Logically segment network traffic running on the same physical and virtual networks Configure tagging on each virtual switch Configure tagging on each virtual network adapter Note that host network interface cards must support VLAN tagging VLAN IDs extend VLANs within the host’s network switch to VLANS on the external network Describe the process of configuring VLANs on Hyper-V network switches and virtual network adapters. For more information, refer to the following Microsoft Consulting Services blogs about VLANs and Hyper-V: http://go.microsoft.com/fwlink/?LinkID=331082 http://go.microsoft.com/fwlink/?LinkID=331083

Virtual Switch Extensions 20410D Virtual Switch Extensions 13: Implementing Server Virtualization with Hyper-V Virtual switch extensions enable third-party vendors to create virtual switches You can manage virtual switches by using the same toolset that you use to manage physical switches Several networking vendors have already used Hyper-V virtual switch extensions extensibility to implement virtual versions of hardware switches. Prior to teaching this course, you may want to investigate vendors that have produced virtual versions of hardware switches, and then ask the students if they use any of this equipment in their own organizational environments. Virtual switches Physical switches

Managing Virtual Machine MAC Addresses 13: Implementing Server Virtualization with Hyper-V Virtual Switch Manager Window Reinforce the circumstances when it is necessary for administrators to configure separate media access control (MAC) address pools, such as in environments that have multiple servers running Hyper‑V. Ask students who have deployed virtualization in their production environments how they ensured that virtual machines are never assigned the same MAC address.

Configuring Virtual Network Adapters 13: Implementing Server Virtualization with Hyper-V Properties of a network adapter: Virtual Switch VLAN ID Bandwidth Management Features of a virtual network adapter: MAC address allocation DHCP Guard Router Guard Port Mirroring NIC Teaming Discuss the situations where you would want to use Dynamic Host Configuration Protocol (DHCP) Guard and Router Guard. Describe the scenarios where you might configure bandwidth management on a virtual machine, such as ensuring that no one particular virtual machine monopolizes all of the host’s available network bandwidth.

Network Adapter Advanced Features 13: Implementing Server Virtualization with Hyper-V Virtual Machine Queue delivers network traffic directly to the guest IPsec task offloading enables the host’s network adapter to perform calculation-intensive security association tasks SR‑IOV enables multiple virtual machines to share the same PCI Express physical hardware resources vRSS balances the network processing across multiple virtual processor cores in a virtual machine Discuss each of the advanced network adapter features and explain how each can improve the network performance of virtual machines. Many of these features enable virtual machines to handle high-capacity bandwidth tasks. Explain the hardware requirements for vRSS. Ask students to describe a virtual workload that they need to support that requires extensive bandwidth resources.

NIC Teaming in virtual machines: 20410D What Is NIC Teaming? 13: Implementing Server Virtualization with Hyper-V NIC Teaming: Provides redundancy and aggregates bandwidth Is supported at the host and virtual machine level NIC Teaming in virtual machines: Requires multiple virtual network adapters Must be enabled on virtual network adapters Can then be implemented in the virtual machine’s operating system (if supported) Explain why you would want to configure virtual NIC Teaming for virtual machines. Discuss how you can use multiple NIC Teams on the host connected to multiple virtual switches, and then use NIC Teaming that you configure through the virtual machine’s host operating system, to add another layer of performance and redundancy.

Lab: Implementing Server Virtualization with Hyper-V 20410D Lab: Implementing Server Virtualization with Hyper-V 13: Implementing Server Virtualization with Hyper-V Exercise 4: Using Virtual Machine Checkpoints Before the students begin the lab, read the lab scenario, and display the next slide. Before each exercise, read the scenario associated with the exercise to the class. The scenarios give context to the lab and exercises, and help to facilitate the discussion at the end of the lab. Remind the students to complete the discussion questions after the last lab exercise. Note: If the labs are hosted rather than being run on classroom machines, you will be able to perform only “Exercise 3: Creating and Configuring a Virtual Machine.” Hyper-V does not support nested virtual machines, so students will be unable to perform exercises 1, 2, and 4. As part of your preparation to teach this course, you might consider using a screen-recording app to record exercises 1, 2, and 4, while running the labs on your own equipment. You then could show these videos to the class. Exercise 1: Installing the Hyper-V Role onto a Server The first step in migrating to a virtualized environment for the branch office is installing the Hyper‑V role on a new Windows Server 2012 server. Exercise 2: Configuring Virtual Networking After installing the Hyper‑V role on the new server, you need to configure the virtual network. You need to create a network that connects to the physical network and a private network that you can use only for communication between virtual machines. You will use the private network when you configure the virtual machines for high availability. You also need to configure a specific range of media access control (MAC) addresses for the virtual machines. Exercise 3: Creating and Configuring a Virtual Machine You have been asked to deploy two virtual machines to LON‑HOST1. You have copied a sysprepped virtual hard disk file that hosts a Windows Server 2012 installation. To minimize disk space use at the cost of performance, you are going to create two differencing virtual hard disk files based on the sysprepped virtual hard disk. You then will use these differencing virtual hard disk files as the virtual hard disk files for the new virtual machines. Exercise 4: Using Virtual Machine Checkpoints You are in the process of developing a strategy to mitigate the impact of incorrectly applied change requests. As a part of this strategy development, you are testing the speed and functionality of virtual machine checkpoints to roll back to a previously existing stable configuration. In this exercise, you will deploy Windows Server 2012 in a virtual machine. You then will create a stable configuration for that virtual machine, and create a virtual machine checkpoint. Finally, you will modify the configuration, and roll back to the checkpoint. Logon Information Virtual machine 20410D‑LON‑HOST1 User name Administrator Password Pa$$w0rd Estimated Time: 70 minutes

20410D Lab Scenario 13: Implementing Server Virtualization with Hyper-V Your assignment is to configure the infrastructure service for a new branch office. To use the server hardware that is available currently at branch offices more effectively, your manager has decided that all branch office servers will run as virtual machines. You must now configure a virtual network and a new virtual machine for these branch offices.

20410D Lab Review 13: Implementing Server Virtualization with Hyper-V What Dynamic Memory configuration task was not possible on previous versions of Hyper-V, but which you can now perform on a virtual machine that is hosted on the Hyper-V role on a Windows Server 2012 server? Lab Review Questions Question What type of virtual network switch would you create if you want to allow the virtual machine to communicate with the LAN that is connected to the Hyper‑V virtualization server? Answer You would create an external virtual network switch. How can you ensure that no single virtual machine uses all of the available bandwidth that the Hyper‑V virtualization server provides? You would configure maximum and minimum bandwidth settings on virtual network adapters. What Dynamic Memory configuration task was not possible on previous versions of Hyper‑V, but which you can now perform on a virtual machine that is hosted on the Hyper‑V role on a Windows Server 2012 server? You can modify some Dynamic Memory settings while the virtual machine is running on Hyper‑V. You could not do this in previous Hyper-V versions.

Module Review and Takeaways 13: Implementing Server Virtualization with Hyper-V Best Practices Tools Module Review Questions Point students to the appropriate section in the course, so that they are able to answer the questions that this section presents. Question In which situations should you use a fixed memory allocation instead of Dynamic Memory? Answer You should use fixed memory allocation when the: Guest operating system does not support Dynamic Memory. Management operating system has limited memory resources, and you need to ensure balanced allocation of memory to the operating systems. In which situations must you use virtual hard disks with the new .vhdx format, instead of virtual hard disks with the old .vhd format? You should use virtual hard disks with the new .vhdx format rather than virtual hard disks with the old .vhd format when you need to: Support virtual hard disks larger than 2 TB. Virtual hard disks with the new .vhdx format can be a maximum of 64 TB, while virtual hard disks with the old .vhd format are limited to 2 TB. Protect against data corruption that power failures cause. Virtual hard disks with the new .vhdx format are less likely to become corrupt if an unexpected power failure occurs, because of how the file format processes updates. Deploy a virtual hard disk to a large sector disk. 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? 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 of SMB 3.0 file shares. (More notes on the next slide)

13: Implementing Server Virtualization with Hyper-V 20410D Course Evaluation 13: Implementing Server Virtualization with Hyper-V Remind students to complete the course evaluation.