Virtualizing Your Datacenter

8/9/2019 Virtualizing Your Datacenter

1/160

Virtualizing your Datacenterwith Windows Server 2012 R2 & System Center 2012 R2

Hands‐On

Lab

| Step

‐by

‐Step

Guide

For the VMs the following credentials:

Username: Contoso\Administrator

Password: Passw0rd!

Lab version: 2.0.1

Last updated:

November

6,

2013

Important: these VMs were built using evaluation software. To ensure that the labs continue to

function after the evaluation period has expired, hosters will start the VMs from a saved state and so

the VMs will not resync their time unless they are rebooted. Avoid rebooting any VMs during this lab.

Please share any feedback with the IT Camps Planning Team: [email protected]

Copyright © 2013 by Microsoft Corporation. All rights reserved.


2/160

2

CONTENTS

LAB TIMING ......................................................................................... 4

LAB 1: VIRTUAL MACHINE STORAGE ............................................. 5

EXERCISE 1.1: CONFIGURE A STORAGE POOL ............................ 5

EXERCISE 1.2: CONFIGURE A STORAGE SPACE .......................... 8

EXERCISE 1.3: MANAGE A FILE SERVER ...................................... 13

EXERCISE 1.4: MANAGE A STORAGE AREA NETWORK ............. 19

LAB 2: VIRTUAL MACHINE NETWORKING ................................... 23

EXERCISE 2.1: CONFIGURE A HOST NIC TEAM ........................... 23

EXERCISE 2.2: MANAGE HYPER-V HOSTS ................................... 26

EXERCISE 2.3: CREATING A VIRTUAL SWITCH ............................ 30

LAB 3: ADVANCED VIRTUAL MACHINE NETWORKING .............. 33

EXERCISE 3.1: CREATE A LOGICAL NETWORK ........................... 33

EXERCISE 3.2: APPLY A LOGICAL NETWORKS ............................ 37

EXERCISE 3.3: CREATE A PORT PROFILE & CLASSIFICATION.. 40

EXERCISE 3.4: CREATE & APPLY A LOGICAL SWITCH ............... 44

LAB 4: VIRTUAL MACHINE CLUSTERING & RESILIENCY ........... 49

EXERCISE 4.1: CREATE SHARED STORAGE OVER SMB ............ 49

EXERCISE 4.2: BUILD A HYPER-V CLUSTER ................................ 51

EXERCISE 4.3: ASSIGN SHARED STORAGE USING ISCSI .......... 57

EXERCISE 4.4: OPTIMIZE A CLUSTER ........................................... 62

EXERCISE 4.5: CONFIGURE CLUSTER PATCHING ...................... 65

LAB 5: VIRTUAL MACHINE CONFIGURATION .............................. 71

EXERCISE 5.1: CREATE A GENERATION 1 VM ............................. 71

EXERCISE 5.2: CREATE A VM WITH POWERSHELL .................... 77

EXERCISE 5.3: CREATE A GENERATION 2 VM ............................. 81

LAB 6: VIRTUAL MACHINE MOBILITY ........................................... 86

EXERCISE 6.1: CONFIGURE HOSTS FOR MIGRATION ................ 86

EXERCISE 6.2: TEST A VM MIGRATION ......................................... 88

EXERCISE 6.3: TEST A STORAGE MIGRATION ............................ 90

EXERCISE 6.4: TEST A SHARED NOTHING LIVE MIGRATION..... 92


3/160

3

LAB 7: VIRTUAL MACHINE REPLICATION & PROTECTION ........ 99

EXERCISE 7.1: CONFIGURE A HYPER-V REPLICA ....................... 99

EXERCISE 7.2: CONFIGURE A HYPER-V REPLICA BROKER .... 101

EXERCISE 7.3: REPLICATE A VM ................................................. 104

LAB 8: NETWORK VIRTUALIZATION ........................................... 109

EXERCISE 8.1: CREATE A VM NETWORK ................................... 109

EXERCISE 8.2: ASSIGN A VM NETWORK .................................... 113

LAB 9: VIRTUAL MACHINE TEMPLATES ..................................... 116

EXERCISE 9.1: CREATE A VM TEMPLATE ................................... 116

EXERCISE 9.2: REVIEW A SQL SERVER PROFILE ..................... 124

EXERCISE 9.3: REVIEW A WEB APPLICATION PROFILE ........... 130

EXERCISE 9.4: CREATE A VM FROM A TEMPLATE .................... 134

LAB 10: SERVICE TEMPLATES .................................................... 137

EXERCISE 10.1: CREATE A SERVICE TEMPLATE ...................... 137

EXERCISE 10.2: DEPLOY A SERVICE TEMPLATE ...................... 144

LAB 11: PRIVATE CLOUDS & USER ROLES ............................... 146

EXERCISE 11.1: CREATE A USER ROLE ..................................... 146

EXERCISE 11.2: CREATE A PRIVATE CLOUD ............................. 151

EXERCISE 11.3: DELEGATE ACCESS TO A CLOUD ................... 154


4/160

4

Lab Timing The following table shows the estimated time to complete each lab and task.

Title Estimated Time (V 2.0)

Lab 1: Virtual Machine Storage

Exercise 1.1: Configure a Storage Pool 5

Exercise 1.2: Configure a Storage Space 5

Exercise 1.3:

Manage

a File

Server

10

Exercise 1.4: Manage a Storage Area Network 5

Lab 2: Virtual Machine Networking

Exercise 2.1: Configure a Host NIC Team 5

Exercise 2.2: Manage Hyper‐V Hosts 5

Exercise 2.3: Creating a Virtual Switch 5

Lab 3: Advanced Virtual Machine Networking

Exercise 3.1: Create a Logical Network 5

Exercise 3.2: Apply a Logical Networks 5

Exercise 3.3: Create a Port Profile & Classification 5

Exercise 3.4: Create & Apply a Logical Switch 10

Lab 4: Virtual Machine Clustering & Resiliency

Exercise

4.1:

Create

Shared

Storage

over

SMB

5

Exercise 4.2: Build a Hyper‐V Cluster 10

Exercise 4.3: Assign Shared Storage using iSCSI 10

Exercise 4.4: Optimize a Cluster 5

Exercise 4.5: Configure Cluster Patching 10

Lab 5: Virtual Machine Configuration

Exercise 5.1: Create a Generation 1 VM 5

Exercise 5.2: Create a VM with PowerShell 5

Exercise 5.3: Create a Generation 2 VM 5

Lab 6: Virtual Machine Mobility

Exercise 6.1: Configure Hosts for Migration 5

Exercise 6.2: Test a VM Migration 5

Exercise 6.3: Test a Storage Migration 5

Exercise 6.4:

Test

a Shared

Nothing

Live

Migration

5

Lab 7: Virtual Machine Replication & Protection

Exercise 7.1: Configure a Hyper‐V Replica 5

Exercise 7.2: Configure a Hyper‐V Replica Broker 5

Exercise 7.3: Replicate a VM 5

Lab 8: Network Virtualization

Exercise 8.1: Create a VM Network 10

Exercise 8.2: Assign a VM Network 5

Lab 9: Virtual Machine Templates

Exercise 9.1: Create a VM Template 10

Exercise 9.2: Review a SQL Server Profile 5

Exercise 9.3: Review a Web Application Profile 5

Exercise 9.4: Create a VM from a Template 5

Lab 10: Service Templates

Exercise 10.1: Create a Service Template 10

Exercise 10.2: Deploy a Service Template 5

Lab 11: Private Clouds & User Roles

Exercise 11.1: Create a User Role 5

Exercise 11.2: Create a Private Cloud 5

Exercise 11.3: Delegate Access to a Cloud 5

Total 225 minutes (3:45 hours)


5/160

5

Lab

1:

Virtual

Machine

Storage

Estimated time to complete Lab 1: 25 minutes

Exercise 1.1: Configure a Storage Pool

In

this

exercise

Windows

Server

2012

R2

Server

Manager

will

be

used

to

create

a

new

Storage

Pool.

A

Storage

Pool

aggregates individual physical disks that have been presented to the operating system. This enables the creation of

Storage Spaces, which is done in the next exercise.

Estimated time to complete: 5 minutes

Perform the following on SCVMM01

1. On SCVMM01, open Server Manager.

2. Click All Servers.

3. Right click All Servers, and select Add Servers.


6/160

6

4. Click Find Now, select FS01, and click the add arrow, and then click OK.

5. When FS01 has been imported the IP addresses will be displayed, and under Manageability ‘Online’ will be

listed.

6. Click File and Storage Services.

7. Ensure that FS01 is selected in main window, and then click Storage Pools.

8. Notice that there are 2 pools, Primordial and POOL1 (TIERED). POOL1 (TIERED) has been created in advance.

9. Click the Primordial pool, and look at the four 500GB disks that are available for use in the Physical Disks pane.

The primordial pool simply aggregates spare, unallocated physical disks.


7/160

7

10. Within the Storage Pools pane Primordial selected, click Tasks and then New Storage Pool.

11. In the New Storage Pool Wizard, then click Next.

12. In the Name field, type POOL2, and then click Next.

13. Select all 4 physical disks then mark the bottom disk as a hot spare by selecting Hot Spare in the Allocation

dropdown, and then click Next.

14. Click Create.

15. Leave the Create a virtual disk when this wizard closes checkbox unselected, and then click Close.

16. Click on POOL1 (TIERED), and scroll down the page to view the Physical Disks.

17. Scroll to the right in the Physical Disks pane, to view the Media Type. Notice that the pool consists of a mixture

of 126GB SSDs and 2TB HDDs.


8/160

8

Exercise 1.2: Configure a Storage SpaceIn this exercise a Tiered Storage Space will be created. A Tiered Storage Space will take advantage of a Storage Pool

that contains a mix of high‐speed SSD and HDD physical disks. The wizard will provide guidance through the creation,

allocation of capacity, resiliency and more. After the Storage Spaces are configured they can be store data.

Estimated time

to

complete:

5 minutes


1. On SCVMM01, Open Server Manager

2. In File and Storage Services | Volumes | Storage Pools, in the Virtual Disks pane, click Tasks and select New

Virtual Disk.

3. Click Next.

4.

On the

Select

the

storage

pool

page,

select

POOL1

(TIERED),

and

then

click

Next.

5. On the Specify the virtual disk name page, type Tiered Space 1 in the Name field. Check the Create storage

tiers on this virtual disk checkbox, and then click Next.

6. On the Select the storage layout page, select each of the layout choices to view the description, select Mirror,

and then click Next.


9/160

9

7. On the Configure the resiliency settings page, select Two‐way mirror, and then click Next.

8. On the Specify the provisioning type page, select the default Fixed, then click Next.

9. On the Specify the size of the virtual disk page, select Maximum Size for the SSD Tier and the HDD Tier, and

then click Next.

10. On the Confirm selections page, ensure that the settings match those in the image below, and then click Create.


10/160

10

11. On the View results page, ensure that the Create a volume when this wizard closes checkbox is selected, and

then click Close. The New Volume Wizard starts automatically and this is expected.

12. On

the

Before

you

begin

page,

click

Next.

13. On the Select server and disk page, ensure that FS01 is selected, and then click Next.

14. On the Specify the size of the volume page, review the volume size information. Change the Volume size

increment to GB and type 4344 in the Volume size field, and then click Next.

15. On the Assign to a drive letter or folder page, select V from the Drive letter dropdown, and then click Next.


11/160

11

16. On the Select file system settings page, type VMs in the Volume label field, and then click Next.

17. On the

Confirm

selections

page,

ensure

that

the

settings

match

those

in

the

image.

Once

confirmed,

click

Create.

18. On the Completion page, click Close.

19. In Server Manager on the dashboard pane, select File and Storage Services | Volumes.

20. In the Volumes pane under FS01 (3), ensure that volume V: with the File System Label VMs is present.


12/160

12

21. In Server Manager on the dashboard pane, select File and Storage Services | Shares. Notice that FS01 is not

listed, because there are no shares associated with FS01 at this time.

22. Minimize Server Manager.


13/160

13

Exercise 1.3: Manage a File ServerIn this exercise System Center 2012 R2 Virtual Machine Manager will be used to manage file servers and SMB shares

which can be used to store Hyper‐V VMs. First the file server FS01 is added under management, then VMM can

provision new file‐based storage from FS01. Additionally the ‘View Script’ button will be used which shows the

underlying PowerShell script for a wizard or template. This makes it easier to learn PowerShell, and these scripts can

be saved and updated to enable automating repetitive tasks. Click on this button throughout different labs to see the

output from

other

wizards.



1. Open the Virtual Machine Manager Console. If the Connect to Server window appears, ensure Use current

Microsoft Windows session identity is selected, and click Connect.

2. Select the Fabric workspace.

3. On the navigation pane, expand Storage and click File Servers.


14/160

14

4. On the ribbon, click Add Resources, and then click Storage Devices.

5. The Add Storage Devices Wizard will open.

6. On the Select Provider Type page, select Windows‐based file server, and then click Next.

7. On the Specify Discovery Scope page, in the Provider IP address or FQDN field, type FS01.contoso.com, and

leave the

This

computer

is

in

an

untrusted

Active

Directory

domain

box

unchecked.


15/160

15

8. For the Run As account, click Browse.

9. In the Select a Run As Account window, click Create Run As Account.

10. In the Create Run As Account window, ensure that Validate domain credentials is selected, type the following,

then click OK:

Name: Storage Admin

User Name: Contoso\Administrator

Password: Passw0rd!

Confirm

password:

Passw0rd!

11. On the Select a Run As Account window, select Storage Admin and click OK.


16/160

16

12. After returning to the Specify Discovery Scope page, click Next.

13. VMM will automatically scan FS01 and return the results below. On the Gather Information page, review the

results, and then click Next.

14. On the Select Storage Devices page, click Next.

15. On the Summary page, ensure the settings match the image below, and then click Finish.

16. The Jobs window will appear. Select Adds Storage Provider, review the results, and then close the Jobs screen.

There should be no File Shares listed.


17/160

17

17. On the Fabric navigation pane, select Providers.

18. Select FS01.contoso.com and, on the ribbon, click Create File Share.

19. In the Name field, type in VMShare1.

20. Next to the Classification dropdown, click New.

21. In the New Classification window, type Gold Tier in the Name field, and then click Add.


18/160

18

22. In the Local path field, type V:\Shares\VMShare1.

23. Click View Script at the bottom. Notepad will open displaying the PowerShell script that will be used to execute

these actions. This can be saved as a PowerShell script (.ps1) that can be edited and reused to help automate

repetitive tasks.

24. Click Create. If the jobs window does not appear, click the Jobs workspace and then click either Running or

History to see this new job which may already have finished. Observe the job through to completion.

25. Return to the Fabric workspace.

26. Repeat steps 17‐24 with the following information:

Name: VMShare2

New Classification Name: Silver Tier

Local Path: V:\Shares\VMShare2

27. Minimize the

Virtual

Machine

Manager

Console,

and

maximize

Server

Manager.

28. VMShare1 and VMShare2 should now appear in the list of shares on FS01. The Shares pane may need to be

refreshed to see the newly created file shares. Minimize Server Manager.


19/160

19

Exercise 1.4: Manage a Storage Area NetworkIn this exercise VMM’s storage management capabilities will be explored using an iSCSI SAN. First an iSCSI SAN will be

brought under VMM’s management. Next VMM will apply a classification, then provision a new LUN from the iSCSI

SAN showing VMM’s powerful storage integration capabilities for the virtualized infrastructure.

Estimated time

to

complete:

5 minutes


1. From the Virtual Machine Manager Console, select the Fabric workspace.

2. On the navigation pane, expand Storage and click Arrays.

3. Right‐click Arrays and select Add Storage Devices.

4. On the Select Provider Type page, select SAN and NAS devices discovered and managed by a SMI‐S provider,

and click then Next.


20/160

20

5. On the Specify Discovery Scope page, in the Protocol dropdown select SMI‐S WMI, and in the Provider IP

address or FQDN field, type DC01.contoso.com.

6. Next to

the

Run

As

Account

field,

click

Browse.

7. Select Storage Admin, and then click OK.

8. After returning to the Specify Discovery Scope page, click Next.

9. Discovery against the target will now take place. On the Gather Information page, select DC01 when discovery

has completed, and then click Next.

10. On the Select Storage Devices page, click Create classification.

11. In the Name field, type Bronze Tier, and then click Add.


21/160

21

12. Back on the Select Storage Devices page, select the box next to iSCSITarget: DC01: C:, then select Bronze Tier

from the Classification dropdown, and then click Next.

13. On the Summary page, ensure the settings match those in the screenshot below, and then click Finish.

14. The Jobs window will open. Review the job, then close the Jobs window when it has finished.

15. On the navigation pane, under Storage, select Arrays.

16. In the detail pane, select DC01.


22/160

22

17. On the ribbon, click Create Logical Unit.

18. In the Create Logical Unit window, leave the default Storage Pool, in the Name field, type CSV01, leave the

default 1GB size, and then click OK.

19. On the navigation pane, under Storage, select Classifications and Pools.

20. In the detail pane, expand Bronze Tier| iSCSI Target: DC01: C:, and observe the newly created Storage LUN that

was created

on

the

iSCSI

SAN.

21. Minimize the Virtual Machine manager console.

‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐END OF LAB 1‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐


23/160

23

Lab

2:

Virtual

Machine

Networking


Exercise 2.1: Configure a Host NIC Team

In

this

exercise

Windows

Server

2012

R2

Server

Manager

will

be

used

to

create

a

new

NIC

Team

on

the

two

Hyper‐

V

hosts. This task will be executed remotely from SCVMM01, against both Hyper‐V hosts on the network. VMM can

also be used to create NIC Teams on Hyper‐V hosts, however due to limitations of this virtualized lab environment, it

is not possible to complete this task using VMM.



1. From SCVMM01 open Server Manager.

2. From the navigation pane, select All Servers.

3. Right‐click All Servers, and click Add Servers.

4. In the Add Servers window, click Find Now.

5. Select HYPER‐V01 and HYPER‐V02, click the right arrow, and then click OK. It will take a few moments to add

HYPER‐V01 and HYPER‐V02.


24/160

24

6. Once the list of IP addresses appears next to HYPER‐V01 and HYPER‐V02, navigate to Server Manager | All

Servers, right‐click HYPER‐V01 and click Configure NIC Teaming to start the NIC Teaming work pane.

7. In the Teams pane, select Tasks, then New Team.

8. In the NIC Teaming window, type VMTEAM1 in the Team name field.

9. In the Member adapters box, select VMNIC1 and VMNIC2 and click Additional properties to expand the

window.


25/160


26/160

26

Exercise 2.2: Manage Hyper‐V HostsIn this exercise the two Hyper‐V hosts will be brought under the management of VMM through the deployment of an

agent.



1. Open the Virtual Machine Manager Console. If the Connect to Server window appear, ensure Use current



3. Expand Servers, and click All Hosts.

4. On the ribbon, click Add Resources and select Hyper‐V Hosts and Clusters.


27/160

27

5. In the Add Resource Wizard, on the Resource Location page, leave the default selection of Windows Server

computers in a trusted Active Directory domain, and then click Next.

6. On the Credentials page, ensure that Use an existing Run As account is selected, and then click Browse.


8. In the Create Run As Account window, ensure that Validate domain credentials is selected, type the following,

and then click OK:

Name: VMM Admin

User Name: contoso\vmmadmin

Password: Passw0rd!

Confirm password: Passw0rd!

9. In the Select a Run As Account window, select VMM Admin, and then click OK.


28/160


29/160

29

14. On the Host Settings page, accept the defaults, and then click Next.

15. On the Summary page, ensure the settings match those of the screenshot below, and then click Finish.

16. The Jobs window will automatically open and the Add virtual machine host process will begin. This will take

several moments to complete. A warning will appear about a restart, but this can be safely ignored. Do not

restart the VMs. Close the Jobs window.


30/160

30

Exercise 2.3: Creating a Virtual SwitchIn this exercise VMM will be used to create a Hyper‐V Extensible vSwitch, and this virtual switch will be bound to the

NIC team that was created earlier. This will convert that NIC team into a vSwitch, which will later allow VMs to

communicate through the physical host to other networks.

Estimated time

to

complete:

5 minutes





3.

Expand Servers, and click All Hosts.

4. In the main detail pane, right‐click HYPER‐V01, and select Properties.

5. On the General tab, review the details about this Hyper‐V host. Note that the Operating System is Microsoft

Hyper‐V Server 2012 R2, a free SKU for Hyper‐V hosts.


31/160

31

6. Click Hardware, and review the hardware on this particular Hyper‐V host. Note that this host has a number of

network adapters.

7. Within the Hardware tab, scroll down to Advanced, and click BMC Settings. Review the BMC options available

for Out of band Management.

8. Click the Virtual Switches tab, click New Virtual Switch, and select New Standard Switch. Note the option to

select a regular Hyper‐V vSwitch, or a VMM‐specific Logical Switch. Logical Switches will be covered in later labs

9. In the Name field, type vSwitch1.

Note: It is important to match the case for this vSwitch, so type the name exactly.

10. Select the External radio button, and, from the Network adapter dropdown, select VMTEAM1 – Microsoft

Network Adapter Multiplexor Driver. This will bind the vSwitch to this physical adapter. Click OK.


32/160


33/160

33

Lab

3:

Advanced

Virtual

Machine

Networking


Exercise 3.1: Create a Logical NetworkIn this exercise System Center 2012 R2 Virtual Machine Manager will create a Logical Network which represents a

specific network

in

this

lab

environment.

A

logical

network,

together

with

one

or

more

associated

network

sites,

is

a

user‐defined named grouping of IP subnets, VLANs, or IP subnet/VLAN pairs that are used to organize and simplify

network assignments. Some possible examples include “BACKEND,” “FRONTEND,” “LAB,” “MANAGEMENT,”

“LIVEMIGRATION” and “BACKUP”. Since logical networks represent an abstraction of the underlying physical network

infrastructure, they enable administrators to model the network based on business needs and connectivity

properties.






3. On the navigation pane, expand Networking, and click Logical Networks.

4. In the upper left hand corner of the ribbon navigation, click Create | Create Logical Network.

5. In the Create Logical Network Wizard window, in the Name page, type Contoso LAN in the Name field.


34/160

34

6. Ensure that the One connected network radio button is selected, check the boxes for Allow new VM networks

created on this logical network to use network virtualization and Create a VM network with the same name to

allow virtual machines to access this logical network directly, and then click Next.

7. On the Network Site page, under Network sites click Add.

8. Contoso LAN_0 populates in the pane. Under Host groups that can use this network site select All Hosts.

9. Under Associated

VLANs

and

IP

subnets

click

Insert

row,

type

the

following

settings,

and

then

click

Next:

VLAN: 0

IP subnet: 192.168.1.0/24

10. On the Summary page, review the settings, and then click Finish.

11. Review the completed jobs in the Jobs window, and then close the window.


35/160

35

12. In the Logical Networks and IP Pools pane, right‐click Contoso LAN, and click Create IP Pool.

13. In the Create Static IP Address Pool Wizard, on the Name page, type Contoso LAN IP Pool in the Name field,

ensure that the Logical Network selected is Contoso LAN, and then click Next.

14. On the Network Site page, ensure that the Use an existing network site radio button is selected, and then click

Next.

15. On the IP address range page, change the Starting IP address to 192.168.1.10 and the Ending IP address to

192.168.1.100, and then click Next.

16. On the Gateway page, click Insert, enter 192.168.1.254, and then click Next.


36/160


37/160

37

Exercise 3.2: Apply a Logical NetworksIn this exercise the Logical Network which was created earlier, along with other pre‐created Logical Networks, will be

applied. VMM will not apply new IP addresses to the NICs that are being attached to the Logical Networks, but it will

help VMM to map the existing IP assignments to the Logical Networks. This prevents those IP addresses from being

deployed to other hosts in order to avoid network conflicts.




Microsoft Windows

session

identity

is

selected,

and

click

Connect.





38/160

38

5. Click the Hardware tab, scroll down to the NIC labeled VMTEAM1, and select Logical Network.

6. In the results pane, click the box for Contoso LAN.

7. Scroll to the NIC labeled Live Migration, select the Logical network connectivity tab, then select the box for Live

Migration.


39/160

39

8. Scroll to the NIC labeled Heartbeat, select the Logical network connectivity tab, then click the box for

Heartbeat.

9. Scroll to the NIC labeled Storage 1, select the Logical network connectivity tab, then click the box for Storage 1.

10. Scroll to the NIC labeled Storage 2, select the Logical network connectivity tab, then click the box for Storage 2.

11. Click OK in HYPER‐V01 Properties.

12. Repeat steps 4 to 10 with Hyper‐V02.


40/160

40

Exercise 3.3: Create a Port Profile & ClassificationIn this exercise Hyper‐V Port Profiles and Port Classifications will be created. The first port profile will enable physical

network adaptor settings to be defined, and the second will enable specific types of virtual network adaptors to be

defined. These port profiles are similar to templates, and after they are configured and applied to a particular NIC,

they automatically configure that NIC with those port profile settings. A port classification provides a name and

abstraction for a particular type of network adaptor. This becomes more powerful when combined with a particular

port profile

during

a Logical

Switch

deployment,

which

is

done

in

the

next

exercise.



1. Open SCVMM01 then open the Virtual Machine Manager Console. If the Connect to Server window appear,

ensure Use current Microsoft Windows session identity is selected, and click Connect.


3. On the navigation pane, expand Networking, and click Port Profiles.

4. Right‐click Port Profiles, and select Create Hyper‐V Port Profile.

5. In the Create Hyper‐V Port Profile Wizard, on the General page, type Contoso‐Uplink in the Name field.

6. Select the Uplink port profile radio button, select Address Hash from the Load balancing algorithm dropdown,



41/160


42/160

42

13. On the Security Settings page, select Enable DHCP guard, Allow router guard, and Allow guest specified IP

addresses, and then click Next.

14. On the Bandwidth Settings page, change the Maximum bandwidth (Mbps) to 100, and then click Next.

15. On the Summary page, ensure the settings match the screenshot below, and then click Finish.

16. Review the

completed

jobs

on

the

Jobs

screen,

and

then

close

the

window.



43/160

43

18. On the navigation pane, expand Networking, right‐click Port Classifications and select Create Port

Classification.

19. In the

Create

Port

Classification

Wizard,

type

Contoso

Standard

Port

in

the

Name

field,

and

then

click

OK.


44/160

44

Exercise 3.4: Create & Apply a Logical SwitchIn this exercise the Logical Networks, Port Profiles, and Port Classifications will be used in order to provide a more

standardized, controlled, and granular vSwitch that can be deployed across multiple hosts, known as a Logical Switch.

The logical switch also has compliance capabilities, such as detecting unplanned switch configuration changes, and

offering remediation capabilities to return it to its desired configuration. First a logical switch is created, then it is

deployed on a spare network adaptor on each of the Hyper‐V hosts. This will reconfigure that particular physical

adaptor into

a vSwitch,

using

the

settings

defined

by

that

Logical

Switch.

In

this

lab

the

logical

switch

is

applied

to

a single NIC, however VMM could also deploy it across multiple NICs on a host while automatically configuring teaming.






3. On the navigation pane, expand Networking, right‐click Logical Switches, and click Create Logical Switch.

4. On the Getting Started page, read the information, and then click Next.


45/160

45

5. On the General page, type Contoso‐LS in the Name field, and then click Next.

6. On the Extensions page, review the currently installed Extensions, note that one of them is already enabled, and

then click Next.

7. On the Uplink page, ensure that in the Uplink mode dropdown No Uplink Team is selected, and click Add.

8. The Add Uplink Port Profile window opens. Ensure that the Contoso‐Uplink is selected. This already has the

information about the Network sites it will support, and that Network virtualization support is enabled. Click

OK.

9. After returning to the Uplink page, review the selection, and then click Next.

10. On the Virtual Port page, it is possible to specify which vNIC configurations can be used with this particular

logical switch. Click Add.

11. The Add Virtual Port window will open. Next to Port Classification, click Browse.

12. On the Select a Port Profile Classification window, select Contoso Standard Port, and then click OK.


46/160

46

13. Back in the Add Virtual Port window, at the bottom, select the Include a virtual network adapter port profile in

this virtual port box, and select Contoso‐vNIC from the drop‐down list, and then click OK.

14. After returning to the Create Logical Switch Wizard page, select the Contoso Standard Port, click Set Default,


15. Repeat steps 10 to 13 with the following information:

a. Classification: Bandwidth ‐ Low | Include a virtual network adapter port profile: Bandwidth ‐ Low

b. Classification: Bandwidth ‐ Medium | Include a virtual network adapter port profile: Bandwidth ‐

Medium

c. Classification: Bandwidth ‐ High | Include a virtual network adapter port profile: Bandwidth ‐ High

16. Back on the Create Logical Switch Wizard page, ensure the settings match those below, and then click Next.


47/160

47

17. On the Summary screen, ensure the settings match the screenshot below, and click Finish.

18. Review the completed jobs on the Jobs screen, and then close the window.

19. Return to the Fabric workspace, expand Servers, and click All Hosts.


21. Click the Virtual Switches tab.

22. Click New Virtual Switch and select New Logical Switch. Note that the Contoso‐LS is automatically selected as

the logical switch.

23. Under Physical Adapters, select VMNIC3. Note that the Contoso‐Uplink is automatically selected as the Uplink

Port Profile.


48/160

48

24. Click OK.

25. At the prompt click OK.

26. Repeat steps 19 to 25 for HYPER‐V02.

‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐END OF LAB 3‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐


49/160

49

Lab

4:

Virtual

Machine

Clustering

&

ResiliencyEstimated time to complete Lab 4: 40 minutes

Exercise 4.1: Create Shared Storage over SMBIn this exercise System Center 2012 R2 Virtual Machine Manager will use the File Server storage to assign file shares

to Hyper

‐V

hosts.

The

hosts

can

store

the

virtual

machine

on

this

shared

storage

using

the

SMB

file

sharing

protocol.


Perform

the

following

on

SCVMM01

1. Open the Virtual Machine Manager Console. If the Conect to Server window appear, ensure Use current




4. In the main detail pane, right‐click HYPER‐V01 and select Properties.

5. Click the Storage tab.

6. Click Add, and select Add File Share.

7. From the File share path dropdown, select \\FS01.contoso.com\VMShare1.

8. Click Add, and select Add File Share.

9. From the File share path dropdown, select \\FS01.contoso.com\VMShare2.


50/160

50

10. Click OK.

11. Repeat steps 4 to 10 for HYPER‐V02.


51/160

51

Exercise 4.2: Build a Hyper‐V ClusterIn this exercise VMM will create a Windows Server 2012 R2 Failover Cluster using the Hyper‐V hosts. Any VMs that

are deployed on the cluster will be made highly available, so after a host failure the VMs would automatically restart

on another node in that cluster, providing resiliency to both planned and unplanned downtime.

Estimated time

to

complete:

10

minutes




2.

Select the Fabric workspace.

3. Select the Home tab above the ribbon.

4. Click Create, and select Hyper‐V Cluster.

5. In the Create Cluster Wizard, on the General page, type CLUSTER1 in the Name field.


52/160

52

6. Next to Use an existing Run As account, click Browse, select VMM Admin, and then click OK. Click Next.

7. On the Nodes page, multi‐select HYPER‐V01 and HYPER‐V02, click Add, and then click Next.

8. On the IP Address page, check the box next to 192.168.1.0/24, select Contoso LAN IP Pool from the Static IP

Pool

dropdown.

VMM

will

automatically

allocate

an

IP

address

to

the

Cluster

from

that

pool

of

IP

Addresses.

Click Next.

9. On the Storage page, click Next. A SAN does not need to be selected as this cluster will use the storage on the

File Server.

10. On the Networks page, click Next. The Virtual Switches and Logical Switches for these hosts were already

created.


53/160

53

11. On the Summary page, ensure the settings match below, and then click Finish.

12. Observe the running job in the Jobs window. Maximize the Jobs window. In the results pane at the bottom,

select the Validate Cluster job, and click the Details tab. Observe the job through to completion.

13. This will take a few minutes to complete. Once complete, in the jobs window, click the Summary tab. Observe

there is a warning with the configuration. Close the jobs window.

14. In the Fabric workspace, expand All Hosts, right‐click CLUSTER1, and select Properties.


54/160

54

15. On the General tab, type 0 in the Cluster reserve (nodes) field.

16. Click the Status tab and, in the detail pane, click the link for the cluster validation report.

17. The validation report opens in IE. Maximize the window.

18. Notice there is a warning for Network and Storage. A warning means that the cluster is supported and will

function correctly, however a best practice is not being followed.


55/160

55

19. Click Network, then click Validate IP Configuration.

20. Scroll down until the yellow warnings about the APIPA address are displayed and review the information.

21. Press the Back Arrow twice to return to the top of the report.

22. Click Storage.

23. Select Validate Disk Access Latency. Note that no disks were found. This warning occurs because there is no

SAN storage attached to the cluster. The cluster uses the SMB 3.0 File Shares created earlier for shared storage

because these provide shared access and are often cheaper and easier to configure.

24. Close Internet Explorer window.

25. From the CLUSTER1.contoso.com Properties click the File Share Storage tab.


56/160

56

26. In the detail pane, click Add. From the File share path dropdown, select \\FS01.contoso.com\VMShare1, and

then click OK.

27. In the detail pane, click Add. From the File share path dropdown, select \\FS01.contoso.com\VMShare2, and

then click OK.

28. Click the Virtual Switches tab. Note that the standard and logical switches that were created earlier are

attached to this node.

29. Click OK to close the CLUSTER1 Properties.


57/160

57

Exercise 4.3: Assign Shared Storage using iSCSIIn this exercise VMM assigns an iSCSI LUN that was created earlier to the cluster nodes to provide shared storage.

VMM manages the iSCSI connectivity between the hosts and the iSCSI SAN through multiple sessions, as well as

configuring the LUN correctly. The files of a clustered VM would be hosted on this SAN and accessible by both node.

Estimated time

to

complete:

10

minutes




2.


3. In the Storage node, select Classification and Pools.

4. From the central pane, expand Bronze Tier, then expand iSCSITarget: DC01: C:, then select CSV01.

5.

On the

upper

ribbon,

select

Allocate

Capacity.

6. In the Allocate Storage Capacity window, click Allocate Storage Pools.


58/160


59/160


60/160

60

14. In the Create New iSCSI Session window, select DC01 from the Array dropdown, and then click Create.

15. In the Hyper‐V01 Properties window, click OK.

16. Repeat steps 12 to 15 for Hyper‐V02.

17. Under All Hosts, right click CLUSTER1, and select Properties.

18. Click the Shared Volumes tab, and then click Add.


61/160

61

19. In the Add Cluster Shared Volume window, select CSV01. In the Volume Label field, type CSV01, click the boxes

for Quick Format and Force Format, and then click OK.

20. In the

CLUSTER1.contoso.com

Properties

window,

click

OK.

VMM

will

then

assign

the

LUN

to

both

nodes

in

the

cluster, format the volume, convert it to a Cluster Shared Volume, and make it available for placement of virtual

machines.


62/160

62

Exercise 4.4: Optimize a ClusterIn this exercise VMM will be used to make a number of configuration changes to the cluster. These include optimizing

the hosts for VM load balancing and power usage. This helps to ensure that the VMs will use the host resources

efficiently.

Estimated time

to

complete:

5 minutes




2.


3. Expand Servers, right‐click All Hosts, and select Properties.

4. In the All Hosts Properties window, click the Host Reserves tab.


63/160

63

5. On the Host Reserves tab, ensure that the Use the host reserve settings from the parent host group box is

unchecked, and change the Memory settings for Unit to % and for Amount to 5. Since the Hyper‐V hosts in this

lab environment only have 2GB RAM, the Memory setting needs to be set lower to ensure that a VM can be

deployed.

6. Click the Dynamic Optimization tab.

7. On the Dynamic Optimization tab, slide the Aggressiveness slider to High. Aggressiveness affects how evenly

distributed the VMs are across the different hosts. An aggressively balanced cluster will live migrate VMs more

frequently to

ensure

that

a similar

amount

of

host

resources

are

used

on

each

cluster

node.

8. Select the box for Automatically migrate virtual machines to balance load at this frequency (minutes) and type

5 in the box.

9. Select the Enable power optimization box, and then click Settings.


64/160

64

10. Review the default threshold values. Under Schedule click one of the blue squares between 8am and 6pm and

Monday to Friday. The square will turn white when clicked, to indicate no power optimization will operate

during those times. By pressing the keyboard arrow keys and the space bar, the squares can be changed.

Change a few of these squares, and then click OK.

11. Back on the All Hosts Properties window, click OK to close the window.


65/160

65

Exercise 4.5: Configure Cluster PatchingIn this exercise VMM will be used to review patching compliance for the cluster nodes. After VMM is integrated with

WSUS a baseline will be created which defines which patches are needed for the different hosts. Next the hosts will

be scanned and compliance will be reported. VMM’s integrated patching can also be used to secure other types of

infrastructure servers that VMM can manage.




Microsoft Windows

session

identity

is

selected,

and

click

Connect.


3. In the navigation pane, expand Infrastructure, and select Update Server.

4. Right‐click Update Server, and click Add Update Server.


66/160

66

5. In the Add Windows Server Update Services Server window, enter the following information:

Computer name: SCVMM01.contoso.com

TCP/IP Port: 8530

6. Next to Use an Existing Run As Account, click Browse.


8. In the Create Run As Account window, enter the following details, and then click OK:

Name: WSUS Admin

Username: contoso\administrator

Password: Passw0rd!

9. In the Select a Run As Account window, ensure that WSUS Admin is selected, and then click OK.

10. Ensure that the Use Secure Sockets Layer (SSL) to communicate with WSUS server and clients box is

unchecked, and then click Add.


67/160

67

11. The Jobs window will open. Review the details then move on to the next step. The job will take a few moments

because VMM will trigger a WSUS synchronization.

Note: The synchronization may fail and this is expected. This is because the WSUS server in this lab may

not have a connection to an upstream source, such as Windows Update.

12. Minimize the Jobs window.

13. Select the Library workspace.

14. Expand Update Catalog and Baselines, right‐click Update Baselines, and then click Create Baseline.

15. In the

Update

Baseline

Wizard,

on

the

General

page,

type

HYPER

‐V

in

the

Name

field,

and

then

click

Next.

16. On the Updates page, click Add.


68/160

68

17. Multi‐select both updates beginning with Update for Windows Server 2012 R2, and then click Add.

18. On the Updates page, click Next.

19. On the Assignment Scope page, click the box next to CLUSTER1.contoso.com, and then click Next.

20. On the Summary page, ensure the settings match those in the image below, and then click Finish.

21. The Jobs window opens. Observe the completed job, and then close the Jobs window.


23. Under Servers | All Hosts, select CLUSTER1.

24. On the

ribbon,

click

Compliance.


69/160

69

25. In the detail pane, expand CLUSTER1, then expand both HYPER‐V01 and HYPER‐V02, and then select

CLUSTER1.contoso.com.

26. On the ribbon, click Scan. This process scans the cluster nodes and compare them with the baseline that was

created earlier. This process will take a few moments.

When the scan completes, the report indicates that both Hyper‐V hosts have the necessary updates to be in

compliance. If one of the cluster nodes was missing an update, VMM would have performed the following

steps.

A. Place a host into maintenance mode

B. Live migrate virtual machines off the host

C. Update the host

D. Restart the host (if necessary)

E. Check that the patch installed successfully and the node rejoined the cluster

F. Remove the

host

from

maintenance

mode

G. Live migrate the virtual machines back to the host (optional)

H. Repeat steps A ‐ H on the other nodes in the cluster

27. Within the Hosts pane, right‐click CLUSTER1.contoso.com, and select Compliance Properties.


70/160

70

28. The Compliance Properties tool allows exemptions to be made for select updates on specific Hyper‐V host

computers. Under HYPER‐V01.contoso.com, select the top‐most update, and then click Create.

29. In

the

Create

Exemption

window,

enter

Not

Applicable,

and

then

click

Create.

In

a

production

environment

it

isimportant to always apply the latest updates.

30. The State

of

the

update

has

been

changed

to

Exempt.

Click

OK.

‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐END OF LAB 4‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐


71/160


72/160

72

4. On the Select Source page, select Create the new virtual machine with a blank virtual hard disk, and then click

Next.

5. On the Identity page, type VM01 in the Virtual machine name field, select Generation 1 from the Generation

dropdown, and then click Next.

6. On the Configure Hardware page, scroll down to review the configuration options, including Processor, SCSI

Adapter 0, CPU Priority, Virtual NUMA and Memory Weight.

7. Select Memory

under

General

in

the

navigation

tree,

in

the

details

pane,

then

in

the

select

the

Dynamic

radio

button. Enter 128 in the Startup memory field, type 64 in the Minimum memory field, and type 192 in the

Maximum memory field.


73/160

73

8. On the Configure Hardware page, select VM01_disk_1 under Bus Configuration | IDE Devices in the navigation

tree. Change the Size (GB) value to 5 GB. Leave all other default settings.

9. On the Configure Hardware page, scroll down in the navigation pane and select Network Adapter 1 under

Network Adapters.

10. In the results pane, under Connectivity, select the Connect to a VM network radio button, and click Browse.

11. In the Select a VM Network window, select Contoso LAN, and then click OK.

12. In the Network Adapter 1 details pane, under Port Profile, select Contoso Standard Port from the Classification

dropdown.

13. On the Configure Hardware page, select Availability under Advanced in the navigation pane.


74/160

74

14. In the Availability detail pane, click the Make this virtual machine highly available check box.

15. In the Availability detail pane, click Manage availability sets. An Availability Set is a group of VMs that

distribute themselves across different hosts as evenly as possible. This type of anti‐affinity can be used to keep

VMs with identical server roles (such as virtualized DCs or guest cluster nodes) on different hosts to avoid a

single point of failure.

16. In the

Manage

Availability

Sets

window,

click

Create.

17. In the Create Availability Set window, type Lab Availability Set in the Name field, and then click OK.


75/160

75

18. In the Manage Availability Sets window, click OK.

19. On the Configure Hardware page, click Next.

20. On the Select Destination page, ensure that the Destination is All Hosts, and then click Next.

21. VMM

scans

each

host

for

its

current

resource

usage

across

CPU,

Memory,

Disk

and

Network,

and

ranks

each

host based on these factors and the expected needs of the VM, using a feature called Intelligent Placement. On

the Select Host page, select HYPER‐V01, and then click Next.

22. On the Configure Settings page, accept the defaults, and then click Next.

23. On the

Add

Properties

page,

make

the

following

changes

using

the

drop

down

lists

and

entry

boxes,

then

click

Next:

Select an action to perform automatically when the virtualization server starts: Turn on the virtual

machine if it was running when the physical server stopped

Delay start up (seconds): 10

Action to take when the virtualization server stops: Shut down guest OS

Specify the operating system you will install in the virtual machine: Windows Server 2012 R2 Datacenter


76/160

76

24. On the Summary page, review the settings. They should match those in the screenshot below.

25. Ensure that the Start the virtual machine after deploying it is not selected, then click View Script.

26. Click File and select Save As.

27. Change the file name to DeployVM.ps1, using the Save as type dropdown, select All Files.

28. Navigate so that location to save the file is E:\VMMLibrary, and then click Save.

29. Close Notepad and click Create.

30. In the Jobs window, select the running Create virtual machine job and review the job details at the bottom of

the page.

31. When the Job finishes running, close the Jobs window.


77/160


78/160

78

4. Select Edit | Replace in Script.

5. In the

Find

What

field,

type

VM01,

in

the

Replace

with

field,

type

VM02,

and

then

click

Replace

All.

6. Save the file.

7. Click Run

(green

triangle)

from

the

upper

ribbon.

The

PowerShell

script

will

run,

but

it

may

take

a few

moments

to start.

8. Once the script is complete a new PowerShell prompt will appear. Close PowerShell ISE.


79/160

79



10. Select the VMs and Services workspace, and then select CLUSTER1.

11. Note that VM02 is being created with an identical configuration as VM01. Since both VMs are in the same

availability set called Lab Availability Set they will be distributed across different hosts.

12. Select the Library workspace.

13. Expand Library Servers, and click on SCVMM01.contoso.com.

14. Right‐click SCVMM01.contoso.com, and select Refresh. DeployVM.ps1 should appear in the Physical Library

Objects details pane.


80/160

80

15. Select DeployVM.ps1, on the ribbon, click View File. Notepad will open.

16. Close Notepad.


81/160

81

Exercise 5.3: Create a Generation 2 VMIn this exercise a new VM will be deployed as a “Generation 2” Hyper‐V virtual machine. The process is similar to

deploying a traditional VM, however there are differences which will be noted, specifically with the VM hardware.

Generation 2 VMs also have unique features such as supporting UEFI firmware and Secure Boot.

Estimated time

to

complete:

5 minutes




2.

Select the VMs and Services workspace.

3. On the ribbon, click Create Virtual Machine, and then select Create Virtual Machine.

4.

On the

Select

Source

page,

click

Create

the

new

virtual

machine

with

a blank

virtual

hard

disk,

and

then

click

Next.


82/160

82

5. On the Identity page, type VM03 in the Virtual machine name field, from the Generation dropdown select

Generation 2, and read the information at the bottom of the page. Click Next.

6. On the Configure Hardware page, scroll down to review the reduced number of configuration options available

with a Generation 2 Virtual Machine. This is because Generation 2 Virtual Machines have standardized the

virtualized hardware, removing such components as legacy NICs.

7. Select Memory under General in the navigation tree, in the details pane, select the Dynamic radio button, type

128 in the Startup memory field, type 64 in the Minimum memory field, and type 192 in the Maximum

memory field.

8. On the Configure Hardware page, select VM03_disk_1 under Bus Configuration | SCSI Adapter 0 in the

navigation tree. Change the Size (GB) value to 5 GB. Leave all other default settings.


83/160

83

9. On the Configure Hardware page, select Availability under Advanced in the navigation pane.

10. In the Availability detail pane, click the Make this virtual machine highly available check box.

11. In the Availability detail pane, click Manage availability sets.

12. In the Manage availability sets window, under Available Properties, select Lab Availability Set, click Add, and

then click OK.


84/160

84

13. In the Availability detail pane, change the Virtual machine priority to High.

14. On the Configure Hardware page, under Advanced in the navigation pane, select Firmware. Note that

Generation 2 virtual machines boot from UEFI firmware, which supports Secure Boot. Secure Boot helps to

protect against the booting of unauthorized or compromised operating systems. Click Next.

15. On the Select Destination page, ensure that the Destination is All Hosts, and click Next.


85/160

85

16. On the Select Host page, notice there is a warning next to the hosts. Select HYPER‐V01, and click the Rating

Explanation tab. This recommends that the VM is not placed on HYPER‐V01 because another VM that it is part

of the Lab Availability Set is already on that same host. VMM will actively move running virtual machines to

different hosts to maintain availability sets.

17. Select HYPER

‐V02,

and

click

Next.

18. On the Configure Settings page, accept the defaults, and click Next.

19. On the Select Networks page, accept the defaults, and click Next.

20. On the Add Properties page, click Next.

21. On the Summary page, review the settings. They should match those in the screenshot below.

22. Ensure that Start the virtual machine after deploying it is not selected, and click Create.

23. In the Jobs window, select the running Create virtual machine job and review the job details at the bottom of

the page.

24. When the Job finishes running, close the Jobs window.

‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐END OF LAB 5‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐


86/160

86

Lab

6:

Virtual

Machine

Mobility


Exercise 6.1: Configure Hosts for Migration

Estimated

time

to

complete:

5

minutes

In this exercise System Center 2012 R2 Virtual Machine Manager will prepare the Hyper‐V hosts to support virtual

machine live migration, which moves running VMs between hosts with no downtime. This includes enabling the

hosts for migrations, setting authentication protocols, and configuring the maximum numbers of migrations.





2. Select the VMs and Services workspace.

3. Expand All Hosts | CLUSTER1, and select HYPER‐V01.

4. Right‐click HYPER‐V01, and select Properties.

5. In the HYPER‐V01.contoso.com Properties window, click the Migration Settings tab.

6. Under Live storage migration, change the Maximum numbers of simultaneous live storage migrations to 4.


87/160

87

7. Under Live migration settings, ensure that Turn on incoming and outgoing live migrations is enabled, and

change the Maximum numbers of simultaneous live migrations value to 10.

8. Under Performance option, review the options, and ensure that Use compression is selected.

9. Under Authentication protocol, select Use Kerberos.

10. Under Incoming live migration settings, ensure the Use the following IP subnets is selected. In the list of IP

subnets, select 15.15.15.4/32, and click Move up until this IP subnet is at the top of the list. This ensures this

network is prioritized for Live Migration. Click OK.

11. Repeat steps 4 to 10 with HYPER‐V02.


88/160

88

Exercise 6.2: Test a VM MigrationIn this exercise VMM will perform a migration. Since the Hyper‐V hosts are already virtualized, it is not possible to

start the VMs so they are not actually running “live”, however the steps that would be performed are identical. This

lab migrates the memory of the VM from one host to another host.

Estimated time

to

complete:

5 minutes




2.


3. Expand All Hosts | CLUSTER1, and select HYPER‐V01.

4. In the detail pane, right‐click any of the VMs on that host and select Migrate Virtual Machine.

5. The Migrate VM Wizard opens and automatically assess the target hosts available for migration.


89/160

89

6. Since the VM is currently on HYPER‐V01, select HYPER‐V02 from the list of hosts. Notice the warning about the

Lab Availability Set, as VM03 resides on HYPER‐V02 already. Click Next.

7. On the Summary page, ensure the settings match those in the image below, and then click Move.

8. The Jobs window opens. Observe the migration of the virtual machine from HYPER‐V01 to HYPER‐V02. Close

the Jobs window.

9. Return to the VMs and Services workspace and select HYPER‐V02. Note that the VM which was migrated is

now on this host.


90/160

90

Exercise 6.3: Test a Storage MigrationIn this exercise the VM will remain on the same host, but VMM will move the VM’s storage components (virtual disk,

configuration files, etc.) from one location to another. Storage Migration helps with SAN management and

maintenance.

Estimated time

to

complete:

5 minutes




2.


3. Expand All Hosts, and select CLUSTER1.

4. Right‐click VM01, and select Migrate Storage. The Migrate Storage wizard will open.


91/160


92/160

92

Exercise 6.4: Test a Shared Nothing Live MigrationIn this exercise a VM that running on a cluster will be live migrated to a standalone, including moving its related disks

and files on an iSCSI SAN to the host’s locally attached storage. This is known as a Shared Nothing Live Migration, and

enables IT admins to have complete flexibility for moving VMs around from location to location. The VM’s memory

state and storage are both moved with no interruption to the running virtual machine.




Microsoft Windows

session

identity

is

selected,

and

click

Connect.


3. Right‐click All Hosts and select Add Hyper‐V Hosts and Clusters.

4. In the Add Resource Wizard, on the Resource Location page, leave the default selection of Windows Server

computers in a trusted Active Directory domain, and then click Next.

5. On the Credentials page, ensure that Use an existing Run As account is selected, and then click Browse.


93/160

93

6. In the Select a Run As Account window, select VMM Admin, and then click OK.

7. On the Credentials page, click Next.

8. On the Discovery Scope page, ensure that Specify Windows Server computers by names is selected, and type

SCVMM01 in the Computer names box. Ensure that Skip AD verification box is not selected, and then click

Next.

9. The wizard

will

scan

for

SCVMM01.

If

the

computer

is

not

discovered,

click

OK,

then

click

Refresh.

10. On the Target resources page, select SCVMM01, and then click Next.


94/160

94

11. If a warning appears, click OK, this is safe to ignore.

12. On the Host Settings page, accept the defaults, and then click Next.

13. On the Summary page, ensure the settings match those of the screenshot below, and then click Finish.

14. The Jobs window opens and the Add virtual machine host job begins. This will take several moments to

complete. The job will complete with a warning. This is expected. When the job completes, close the Jobs

window.

15. Close the Virtual Machine Manager Console, then open the Virtual Machine Manager Console. If the Connect

to Server window appear, ensure Use current Microsoft Windows session identity is selected, and click

Connect. Since

VMM

is

add

itself

under

management,

the

management

server

needs

to

be

refreshed.


17. Expand Servers and click on All Hosts.

18. Right‐click SCVMM01 and select Properties.


95/160

95

19. In the SCVMM01.contoso.com Properties window, click the Storage tab.

20. Under Disk, select PHYSICALDRIVE1, which should be 40 GB.

21. Under Logical unit, for Classification, select Gold Tier from the dropdown.

22. Select the Migration Settings tab.

23. Check the box for Turn on incoming and outgoing live migrations.

24. Under Authentication protocol, select Use Kerberos, and then click OK.


96/160


97/160

97

28. Notice that of the 3 available hosts, only 2 have star ratings. Click SCVMM01 and click the Rating Explanation

tab to

Date post:	01-Jun-2018
Category:	Documents
Upload:	valentin-iurea
View:	227 times
Download:	0 times

Virtualizing Your Datacenter

Documents