SMB Live Modernize with Hybrid Cloud Lab 1: Exploring Windows Server 2012 R2 & Hyper-V
Terms of Use 2013 Microsoft Corporation. All rights reserved. Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. For more information, see Microsoft Copyright Permissions at http://www.microsoft.com/permission Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. The Microsoft company name and Microsoft products mentioned herein may be either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. This document reflects current views and assumptions as of the date of development and is subject to change. Actual and future results and trends may differ materially from any forward-looking statements. Microsoft assumes no responsibility for errors or omissions in the materials. THIS DOCUMENT IS FOR INFORMATIONAL AND TRAINING PURPOSES ONLY AND IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. Page 2
Table of Contents LAB 1: PROVISIONING MICROSOFT HYPER-V VMS... 4 Objectives... 4 SYSTEM REQUIREMENTS FOR HOL SYSTEMS STUDENT PORTAL... 5 EXERCISE 1: EXPLORING HYPER-V... 6 Task 1: Exploring Hyper-V... 6 Task 2: Creating a Generation 2 Virtual Machine... 8 Task 3: Explore Gen2-VM Settings... 11 Task 4: Adding Hardware to a VM... 12 Task 5: Resize a Disk on Gen2-VM1... 13 Task 6: Checkpoint Gen2-VM1... 14 EXERCISE 2: CONFIGURING LIVE MIGRATION SETTINGS... 15 Task 1: Prepare Hyper-V for Live Migration... 15 Task 2: Create a Generation 2 VM... 16 Task 3: Configuring Live Migration Settings on Server1... 17 Task 4: Live Migration of a Virtual Machine... 18 Page 3
Lab 1: Provisioning Microsoft Hyper-V VMs During this lab, you will learn how to provision virtual machines, configure Hyper-V host settings, manage storage, manage virtual switches, perform initial configurations, and setup Hyper-V live migration. Estimated time to complete this lab: 30 minutes Objectives The objectives of this exercise are to: Learn to configure Hyper-V Server Settings Learn to configure Virtual Machine Settings Learn to Configure Hardware and Storage Settings for VMs Lean to Configure Live Migration Settings Page 4
System Requirements for HOL Systems Student Portal Please note the labs are only available on the days the course runs. Minimum System Requirements 1. Windows Vista or later recommended (Except Windows 8 RT and 8.1 RT which is not supported) 2. Internet Explorer 8.0 or later 3..NET Framework 3.5 SP1 4. The minimum screen resolution supported is 1280x800 For a complete list of system requirements or to validate that your system meets the minimum system requirements, visit the following link: http://aka.ms/holtest Page 5
Exercise 1: Exploring Hyper-V For this exercise, you will need the following virtual machines: SERVER1 SERVER2 SERVER3 ADMIN DC In this exercise, you will explore and configure Hyper-V Server Setting, create virtual machines, add hardware and storage virtual machines, perform disk resize operations, and perform virtual machine checkpoints. Task 1: Exploring Hyper-V Perform this task on SERVER1 while logged on as Contoso\Administrator Tip: At the start of the lab, you should be logged on automatically to all virtual machines as Contoso\Administrator. If you need to re-logon the password is Passw0rd! 1. Notice that you can switch between lab machines by clicking the machine name in the control panel on the right side of the lab experience window. 2. Switch to machine: Server1. 3. Create a new folder on your C: drive named Hyper-V. 4. Create two new folders in C:\Hyper-V named VM and VHD. 5. Launch Server Manager. Page 6
6. Launch Hyper-V Manager. a. From the Tools menu in Server Manager, select Hyper-V Manager. 7. Right click on Server1 and select Hyper-V Settings. 8. Set the following Hyper-V server settings: a. Default path for Virual Hard Disks: C:\Hyper-V\VHD. b. Default path for Virtual Machines C:\Hyper-V\VM. Page 7
Tip: Be sure to click Apply after each change or they will not be persisted. 9. Click OK. 10. Right click on Server1 and select Virtual Switch Manager. 11. Create a new internal virtual switch named class-internal (sub steps below). Internal switches are used to allow hosted VMs to communicate of the network with the host and each other a. Click Internal and click Create Virtual Switch. b. For the name type Class-Internal and click Apply. 12. Create a new private virtual switch named Class-Private (sub steps below). Internal switches are used to allow hosted VMs to communicate of the network with the host and each other a. Click Private and click Create Virtual Switch. b. For the name type Class-Private and click OK. c. Stay in Hyper-V Manager on Server1 for the next task. Task 2: Creating a Generation 2 Virtual Machine Page 8
Perform this task on SERVER1 while logged on as Contoso\Administrator 1. You should still be logged onto Server1 with Hyper-V Manager open. 2. Right click on Server1 and select New Virtual Machine. 3. Click Next. 4. Name the new VM Gen2-VM1 and notice that the default storage location matches the server setting from the last task. 5. Click Next. 6. Select Generation 2 and click Next. 7. Specify 32 for the memory and select Use Dynamic Memory for this virtual machine. Important: Normally you would select the appropriate level of startup memory for the VM here, but because we're using the TN virtual lab environment, which does not actually run a Hypervisor, you're adding a predefined amount of RAM here to enable the online experience. 8. Click Next. 9. For the connection, select Class-Internal and click Next. 10. Take the default options to create a virtual hard disk with a size of 127 GB dynamcially expanding. Tip: Notice that you can attach a hard drive later, and notice that the default path for the virtual hard disk is the path you specified in the last task. Page 9
11. Click Next to continue 12. Leave the option selected to install an operating system later and click Finish. Page 10
Task 3: Explore Gen2-VM Settings Perform this task on SERVER1 while logged on as Contoso\Administrator 1. Right click Gen2-VM and select Settings. 2. Notice that the new disk is on a SCSI controller and it maps to the VM name with a VHDX file extension, and that is has been created in the default folder that you specified in the Hyper-V Setttings. Generation 1 VMs still use a default of IDE for the OS boot device. This is for compatibility reasons. 3. Notice that the Smart Paging file location is in the same path as the VM. 4. Notice that generation 2 VMs use a firmware boot instead of BIOS. This is to enable modern device boot architectures. 5. Notice that the first and only network adapter is connected to the class-internal switch. 6. Stay in Gen2-VM1 settings for the next task. Page 11
Task 4: Adding Hardware to a VM Perform this task on SERVER1 while logged on as Contoso\Administrator 1. Add an additional Network adapter to Gen2-VM1. a. Click Add Hardware. b. Click Network Adapter. c. Click Add. d. For the virtual switch, select Class-Private and click Apply. e. Notice that Gen2-VM1 now has two NICs, one bound to each virtual switch. 2. Add an additional SCSI disk to Gen2-VM1. a. Click the SCSI Controller, select Hard Drive, and click the Add button. 3. Set the Location to SCSI ID 2 (2), and click the New button 4. Click Next. 5. Select Dynamically expanding and click Next. 6. For the name and path use D-Drive as the name, and take the default path. 7. Click Next. 8. Click Next. 9. Click Finish. Page 12
10. Notice the Gen2-VM1 now has an additional NIC and HDD. 11. Click OK. Task 5: Resize a Disk on Gen2-VM1 Perform this task on SERVER1 while logged on as Contoso\Administrator 1. You should still be logged onto Server1 with Hyper-V Manager open 2. From the Actions Pane, click Inspect Disk. 3. Select D-Drive and click Open. 4. Notice that the current size is 4 MB with the ability to expand to 127 GB if needed. 5. Click Close. 6. Click Edit Disk. 7. Click Next. 8. Click Browse. 9. Click D-Drive and click Open. 10. Click Next. 11. Click Expand and click Next. 12. Change the new size to 150 GB and click Finish. 13. Inspect the disk again. 14. The new size should be expandable to 150 GB. Page 13
Windows Server 2012 R2 supports online VHDX resize. This gives administrators a way to expand the drive capacity of a VM without even shutting it down. Task 6: Checkpoint Gen2-VM1 Perform this task on SERVER1 while logged on as Contoso\Administrator 1. Right click in Gen2-VM1 and select CheckPoint. 2. Notice that a new checkpoint of the VM has been created (middle pane). 3. Right click on the checkpoint and select Rename. 4. Change the name to Pre-Patch. 5. Checkpoint Gen2-VM1 again. 6. Change the name of the second checkpoint to Post-Patch. Assume now that the patching of the server was successful and you now want to remove the two checkpoints.if the patching was unsuccessful, you can revert to the checkpoint that was created before the update, and all changes since that checkpoint will be rolled back. 7. Right click on the Pre-Patch checkpoint and select Delete Checkpoint Subtree to delete all checkpoints in the series. Click Delete. You can also revert to any checkpoint by right clicking on the desired checkpoint and selecting the Revert action. 8. Stay in your lab environment for the next exercise. Page 14
Exercise 2: Configuring Live Migration Settings In this exercise, you attach to your lab environment and perform the necessary steps for Hyper- V live Migration to work across two Hyper-V servers. Task 1: Prepare Hyper-V for Live Migration Perform this task on SERVER2 while logged on as Contoso\Administrator 1. Switch to machine: Server2. 2. Create a new folder on your C: drive named Hyper-V. 3. Create two new folders in C:\Hyper-V named VM and VHD. 4. Launch Server Manager. 5. Launch Hyper-V Manager. a. From the Tools menu in Server Manager, select Hyper-V Manager. 6. Right click on Server1 and select Hyper-V Settings. 7. Set the following Hyper-V server settings: a. Default path for Virual Hard Disks: C:\Hyper-V\VHD b. Default path for Virtual Machines C:\Hyper-V\VM Tip: Be sure to click Apply after each change or they will not be persisted. 8. Click OK. 9. Right click on Server2 and select Virtual Switch Manager. 10. Create a new internal virtual switch named class-internal (sub steps below). a. Click Internal and click Create Virtual Switch. b. For the name type Class-Internal and click OK. Page 15
Task 2: Create a Generation 2 VM Perform this task on SERVER1 while logged on as Contoso\Administrator 1. You should still be logged onto Server1 with Hyper-V Manager open. 2. Right click on Server1 and select New Virtual Machine. 3. Click Next. Name the new VM LiveMig-1 and notice that the default storage locations 3are automatically assigned based on server settings. 4. Click Next. 5. Select Generation 2 and click Next. 6. Specify 32 for the memory and select Use Dynamic Memory for this virtual machine. Important: Normally you would select the appropriate level of startup memory for the VM here, but because we're using the TN virtual lab environment, which does not actually run a Hypervisor, you're adding a predefined amount of RAM here to enable the online experience. 7. Click Next. 8. For the connection, select Class-Internal. 9. Click Next. Take the default options to create a virtual hard disk with a size of 127 GB dynamcially expanding. 10. Click Next to continue. 11. Leave the option selected to install an operating system later and click Finish. 12. Stay in Hyper-V Manager for the next task. Page 16
Task 3: Configuring Live Migration Settings on Server1 Perform this task on SERVER1 while logged on as Contoso\Administrator 1. You should still be in Hyper-V Manager on Server1. 2. Right click on Server1 and select Hyper-V Settings. 3. Click Live Migrations. Tip: Notice that Live Migrations is a Hyper-V Host setting, not a VM setting. Also, notice that Live Migrations are disabled by default. 4. Click the checkbox to Enable incoming and outgoing live migrations. a. Leave Simulaneous Live Migration to set to 2 This setting is to control how many VMs are migrated concurrently. It's to control network traffic and CPU overhead during live migration. The more VMs that are moving at once, the longer the process will take. 5. For the Incoming Live Migrations, you can select a specific network to allow live migrations on, or you can chose to use any connected network. For this exercise, click Use any available network for live migration. In a production environment, you can limit which networks are available for migration traffic by specifying the IP scope. Tip: It's a good idea to have a dedicated NIC and network channel between all the Hyper-V hosts to facilitate live migration traffic. The amount of data going over the network during the storage migration phase of the VM migration can easily saturate a tenant network if no network QoS policies are in place to throttle the bandwidth. 6. Click Apply. 7. Click Storage Migrations from Hyper-V Settings and notice that the number of concurrent live storage migrations has been persisted from the settings you made for live migration. Live storage migrations can be managed idependently of live migrations. 8. Click OK. 1. Connect to Server2 in your lab environment. a. Right click Hyper-V Manager and click Connect to Server. b. Type Server2 and click OK. Page 17
2. Repeat steps 2-6 on Server2. You have now configured both Server1 and Server2 to allow for the live migration of virtual machines between them. Task 4: Live Migration of a Virtual Machine Perform this task on SERVER1 while logged on as Contoso\Administrator In this task you will see where to trigger the live migration of a VM or its storage. 1. Switch back to Hyper-V Manager on Server1. 2. Right click on LiveMig-1 and select Move. 3. Click Next. 4. Notice that you chose to move the entire VM or just its storage to another Hyper-V host. More Information: Both operations are live operations, meaning that the VM stays running and there is never a time that users will need to logoff during the migration. Live storage migration only moves the VHD files. In this case, the VM stays running on the original Hyper-V host, but the VHD files and checkpoints are migrated to the destination Hyper-V host. Once the live storage migration is done, the path to the VHD files changes to the SMB3 UNC path on the destination host. This is very useful when migrating virtual machines into a cluster. 5. Select Move the virtual machine and click Next. 6. On the Specify Destination Computer page, you will type in a server name, or select a server name from AD. The destination Hyper-V host must have already been enabled for live migrations. Type Server2. Page 18
7. Click Next. 8. On the Choose Move Options page, leave the default setting of Move the virtual machine's data to a single location selected. Click Next. Tip: Notice that you can move the VM and all data to single location, or you can move the data to one host and VM to another. You also have the option to leave the VHD files alone and just move the VM (very fast - occurs in seconds). 9. On the Destination Folder page, click Browse. 10. Notice that File Explorer brings up the path on the destination computer (not the local host). This is so that you can control where on the destation host to store the migrated VM files. Browse the C: drive and select C:\Hyper-V\VM. Page 19
11. Click Select folder. This will bring you back to the Destination Folder page with the correct folder listed. 12. Click Next. 13. You will be presented with a summay screen of what you chose for live migration options for LiveMig-1. 14. You will not actually peform a live migration in this lab. 15. Click Cancel to complete the excercise. 16. This concludes the lab. Shut down your lab environment. Page 20