Implementing Hyper-V® 20687B 12: Implementing Hyper-V Presentation: 60 minutes After completing this module, students will be able to: Describe Client Hyper-V® in Windows® 8. Explain the process for creating and working with virtual machines. Identify key aspects of working with virtual disks. Understand and manage snapshots with Hyper-V. Required materials To teach this module, you need the Microsoft® Office PowerPoint® file 20687B_12.pptx. Important: We recommend that you use PowerPoint 2007 or a newer version to display the slides for this course. If you use PowerPoint Viewer or an earlier version of PowerPoint, some features of the slides might not display correctly. Preparation tasks To prepare for this module: Read all of the materials for this module. Practice performing the demonstrations. Work through the Module Review and Takeaways section, and determine how you will use this section to reinforce student learning and promote knowledge transfer to on-the-job performance. Module 12 Implementing Hyper-V®

20687B Module Overview 12: Implementing Hyper-V Managing Snapshots  

Lesson 1: Overview of Hyper-V 20687B Lesson 1: Overview of Hyper-V 12: Implementing Hyper-V Scenarios for Using Client Hyper-V  

20687B What Is Client Hyper-V? 12: Implementing Hyper-V Hardware and software requirements: Management Tools: Client Hyper-V is a feature that enables virtualization within the Windows 8 environment Introduce Hyper-V first in the context of general virtualization. The example in the student handbook may provide a frame of reference if any students are unfamiliar with virtualization. Then, introduce Client Hyper-Vas the Windows 8 component for virtualization. Point out the differences between Client Hyper-V and Hyper-V on Windows Server® 2012, with special emphasis on the features that are not available in Windows Server 2012, such as sleep and hibernate, and virtual wireless networking. Windows 8 64-bit version SLAT supported processor 4 GB RAM Hyper-V Manager Hyper-V Virtual Machine Connection tool Hyper-V Module for Windows PowerShell

Scenarios for Using Client Hyper-V 20687B Scenarios for Using Client Hyper-V 12: Implementing Hyper-V Scenarios for using Client Hyper-V can include: Using self-contained, multinode test labs Testing Windows versions Troubleshooting production Hyper-V virtual machines Working with existing production Hyper-V files by using familiar tools Creating isolated networks for testing Loading VHDs from a USB drive for mobility Using preconfigured trial VHDs from Microsoft for trial-testing a potential new application The goal of this topic is to get students thinking about how they can use Hyper-V and how they can stretch the boundaries of what is possible within a traditional IT infrastructure. Situations such as multinode test labs, and immediate recovery from fatal errors by using snapshots, will offer a new way of thinking about the Windows computer infrastructure. Discussion Prompt: See if any of the students can add to this list. The point of this questions (and topic) is to get them thinking differently. Even ideas that are not possible now, from a technical standpoint, should be put in a frame of reference, as virtualization technology is continuing to evolve and change. Client Hyper-V on Windows 8 is such an example.

Lesson 2: Creating Virtual Machines 20687B Lesson 2: Creating Virtual Machines 12: Implementing Hyper-V Running Virtual Machines  

Creating a Virtual Machine 20687B Creating a Virtual Machine 12: Implementing Hyper-V Important information required to create a virtual machine: Virtual machine name Virtual machine location Network connection Virtual hard disk location Operating system installation media Explain to students the critical information necessary for creating a virtual machine. Provide reference to the steps necessary for creating a new virtual machine in Hyper-V Manager.

Configuring Virtual Machines 20687B Configuring Virtual Machines 12: Implementing Hyper-V Default configuration options: Virtual Machine components include: Name: New Virtual Machine Memory Processor Network adapters Virtual disks List the available settings and describe each to the students. Location: The default location configured for Client Hyper-V Memory: 512 MB Network connection: Not connected Virtual hard disk: Dynamically expanding hard disk with a storage capacity of 127 GB Operating system: No media specified

Running Virtual Machines 20687B Running Virtual Machines 12: Implementing Hyper-V A virtual machine can be in one of the following states: Stopped Started Running Paused Saved Identify the various states of virtual machines. Review the export/import process with students, and explain that export/import is a vital part of testing and troubleshooting in the virtual machine environment, and that this was an area precisely for which Client Hyper-V was designed. Virtual machines can be exported and imported between Client Hyper-V and Hyper-V environments

Lesson 3: Managing Virtual Hard Disks 20687B Lesson 3: Managing Virtual Hard Disks 12: Implementing Hyper-V Configuring a Virtual Hard Disk  

What Is a Virtual Hard Disk? 20687B What Is a Virtual Hard Disk? 12: Implementing Hyper-V A VHD provides storage for a virtual machine, and is represented and used just like a physical disk within the virtual machine Introduce students to the virtual hard disk (VHD) format, explaining its significance in the virtual machine environment. Point out the important aspects of a VHD, and draw students’ attention to the new VHDX format that Windows 8 and Windows Server 2012 support. Explain dynamic and fixed capacity drives, the differences between the two, and where you might use each option. VHDs in Windows 8: Are available in two types: IDE and SCSI Support the VHDX format Can be created as fixed-size or dynamically expanding drives

Configuring a Virtual Hard Disk 20687B Configuring a Virtual Hard Disk 12: Implementing Hyper-V When planning virtual hard disks: Implement storage solutions with multiple hard drives to distribute disk I/O Explain how to configure VHDs in Hyper-V, and why you might use standalone VHD files. Take students through the steps of creating VHDs. Use fast hard drives Consider deploying a SAN for VHD storage Implement iSCSI SANs for a less expensive storage solution Avoid scanning virtual hard disk files with antivirus software, or use virtualization-aware anti-virus software

Lesson 4: Managing Snapshots 20687B Lesson 4: Managing Snapshots 12: Implementing Hyper-V Considerations for Working with Snapshots  

What Is a Snapshot? Snapshots: Snapshot files: 20687B What Is a Snapshot? 12: Implementing Hyper-V Snapshots: Snapshot files: Virtual machine configuration .XML file Are a point-in-time copy of a virtual machine Do not affect the running state of a virtual machine Provide an overview of snapshots, as outlined in the student handbook. Relate any practical examples of using snapshots that you have experienced to the students. Save state files Differencing disk (.AVHD)

Creating and Managing Snapshots 20687B Creating and Managing Snapshots 12: Implementing Hyper-V Manage snapshot options: Create a snapshot View a snapshot Snapshot settings Apply a snapshot Rename a snapshot Delete a snapshot Subtree Revert Explain the various ways of interacting with Client Hyper-V snapshots. Ensure students understand that while snapshots can be a quick and easy way to mitigate lost data and provide recovery from error or failure, they should not be considered as an alternative to backup or an intentional plan for business continuity and disaster recovery.

Considerations for Working with Snapshots 20687B Considerations for Working with Snapshots 12: Implementing Hyper-V Snapshots: Should not be used in production environments Should be used in testing and training environments May consume a significant amount of hard disk space Outline the considerations on the slide. Can have unexpected results when deleted

Lab: Implementing Hyper-V Exercise 2: Creating a Virtual Network and Virtual Machine Exercise 1: Installing Client Hyper-V You have been asked to install the Client Hyper-V feature on LON-CL5, a standalone Windows 8 computer in the IT department. In order to ensure that the IT department has access to all options in the virtual environment, you have been asked to install all of the management tools available for Client Hyper-V. Exercise 2: Creating a Virtual Network and Virtual Machine You have been asked to create a virtual network and virtual machine to accommodate application testing and demonstrate the Hyper-V environment for the application testing team. The virtual network and virtual machine should adhere to the following specifications: Virtual Network: Network type: Private Network name: Private Network Virtual Machine Name: Windows 8 Test Memory: 1024 megabytes (MBs) Storage location: Default Network connection: Private Network Installation media: None Logon Information No virtual machines are required for this exercise Estimated time: 60 minutes To perform this lab, you must boot the host computer to 20687B-LON-CL5. To do this, restart the host computer and choose 208678B-LON-CL5 from the boot menu. Sign in as Adatum\Administrator and the password Pa$$w0rd.

20687B Lab Setup 12: Implementing Hyper-V The IT department at A. Datum wants to test several applications in different operating system environments prior to certifying the applications for the environment. Several members of the application testing team have expressed interest in creating virtual environments on their Windows 8 desktops where they can create and configure virtual machines. You have been asked to demonstrate the process of creating an environment where the applications can be tested.

20687B Lab Review 12: Implementing Hyper-V In the lab, you configured created a private virtual network to connect the virtual machine to. Would a private network type be the logical choice if you were using the virtual machine for testing Windows Updates? Why or why not? Question Why did you have to boot from a Windows 8 VHD file in order to complete this lab? Answer An operating system that performs virtualization needs to run directly on the computer’s hardware. The Windows Server 2008 R2 virtual environment that hosts the A. Datum virtual machines will not support one of those virtual machines to host virtualization itself. In the lab, you configured created a private virtual network to connect the virtual machine to. Would a private network type be the logical choice if you were using the virtual machine for testing Windows Updates? Why or why not? A private network type would limit the virtual machine to connectivity with other virtual machines only. This would not be a good choice for Windows Updates, because the computer will need Internet connectivity to download the updates. The external network type would be best suited for a virtual machine that you are using to test Windows Updates.

Module Review and Takeaways 20687B Module Review and Takeaways 12: Implementing Hyper-V Tools Review Questions Question Why would you deploy Client Hyper-V to a Windows client computer in a corporate environment? Answer Users can use Client Hyper-V to work with Hyper-V-based virtual machines for troubleshooting and testing purposes. You also can use it as an isolated test environment, or for running multiple operating systems on the same computer. When using the Hyper-V Virtual Machine Connection tool to connect to virtual machines hosted on a Windows 8 computer in your environment, often the tool cannot connect to the virtual machines. When you check the host computer, you notice in Event Viewer that the virtual machines are going in and out of the Saved state. What might be the problem, and how could you solve it? The power-management features likely are turned on for the host machine, and it is going into sleep mode. To solve the problem, you could configure the host computer so that it does not go into sleep mode. Why should you not use virtual machine snapshots for backup and disaster recovery? Snapshots are still dependent on the virtual machine’s availability in order to take and apply the snapshots. Typically, snapshots also reside in the same directory as the rest of the virtual machine. Therefore, if the virtual machine fails in some way, or if the disk that houses the virtual machine and snapshot files fails, the snapshots will not be able to aid you in recovering the virtual machine. (More notes on the next slide)

12: Implementing Hyper-V 20687B 12: Implementing Hyper-V Tools Tool Description Where to Find It Hyper-V Manager Management console for Client Hyper-V Start screen Hyper-V Virtual Machine Connection Tool Connect directly to local or remote virtual machines without opening Hyper-V Manager