Professional Documents
Culture Documents
20409B
Server Virtualization with Windows Server
Hyper-V® and System Center
Companion Content
ii Server Virtualization with Windows Server Hyper-V® and System Center
Information in this document, including URL and other Internet Web site references, is subject to change
without notice. Unless otherwise noted, the example 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.
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 names of manufacturers, products, or URLs are provided for informational purposes only and
Microsoft makes no representations and warranties, either expressed, implied, or statutory, regarding
these manufacturers or the use of the products with any Microsoft technologies. The inclusion of a
manufacturer or product does not imply endorsement of Microsoft of the manufacturer or product. Links
may be provided to third party sites. Such sites are not under the control of Microsoft and Microsoft is not
responsible for the contents of any linked site or any link contained in a linked site, or any changes or
updates to such sites. Microsoft is not responsible for webcasting or any other form of transmission
received from any linked site. Microsoft is providing these links to you only as a convenience, and the
inclusion of any link does not imply endorsement of Microsoft of the site or the products contained
therein.
These license terms are an agreement between Microsoft Corporation (or based on where you live, one of its
affiliates) and you. Please read them. They apply to your use of the content accompanying this agreement which
includes the media on which you received it, if any. These license terms also apply to Trainer Content and any
updates and supplements for the Licensed Content unless other terms accompany those items. If so, those terms
apply.
BY ACCESSING, DOWNLOADING OR USING THE LICENSED CONTENT, YOU ACCEPT THESE TERMS.
IF YOU DO NOT ACCEPT THEM, DO NOT ACCESS, DOWNLOAD OR USE THE LICENSED CONTENT.
If you comply with these license terms, you have the rights below for each license you acquire.
1. DEFINITIONS.
a. “Authorized Learning Center” means a Microsoft IT Academy Program Member, Microsoft Learning
Competency Member, or such other entity as Microsoft may designate from time to time.
b. “Authorized Training Session” means the instructor-led training class using Microsoft Instructor-Led
Courseware conducted by a Trainer at or through an Authorized Learning Center.
c. “Classroom Device” means one (1) dedicated, secure computer that an Authorized Learning Center owns
or controls that is located at an Authorized Learning Center’s training facilities that meets or exceeds the
hardware level specified for the particular Microsoft Instructor-Led Courseware.
d. “End User” means an individual who is (i) duly enrolled in and attending an Authorized Training Session
or Private Training Session, (ii) an employee of a MPN Member, or (iii) a Microsoft full-time employee.
e. “Licensed Content” means the content accompanying this agreement which may include the Microsoft
Instructor-Led Courseware or Trainer Content.
f. “Microsoft Certified Trainer” or “MCT” means an individual who is (i) engaged to teach a training session
to End Users on behalf of an Authorized Learning Center or MPN Member, and (ii) currently certified as a
Microsoft Certified Trainer under the Microsoft Certification Program.
g. “Microsoft Instructor-Led Courseware” means the Microsoft-branded instructor-led training course that
educates IT professionals and developers on Microsoft technologies. A Microsoft Instructor-Led
Courseware title may be branded as MOC, Microsoft Dynamics or Microsoft Business Group courseware.
h. “Microsoft IT Academy Program Member” means an active member of the Microsoft IT Academy
Program.
i. “Microsoft Learning Competency Member” means an active member of the Microsoft Partner Network
program in good standing that currently holds the Learning Competency status.
j. “MOC” means the “Official Microsoft Learning Product” instructor-led courseware known as Microsoft
Official Course that educates IT professionals and developers on Microsoft technologies.
k. “MPN Member” means an active Microsoft Partner Network program member in good standing.
l. “Personal Device” means one (1) personal computer, device, workstation or other digital electronic device
that you personally own or control that meets or exceeds the hardware level specified for the particular
Microsoft Instructor-Led Courseware.
m. “Private Training Session” means the instructor-led training classes provided by MPN Members for
corporate customers to teach a predefined learning objective using Microsoft Instructor-Led Courseware.
These classes are not advertised or promoted to the general public and class attendance is restricted to
individuals employed by or contracted by the corporate customer.
n. “Trainer” means (i) an academically accredited educator engaged by a Microsoft IT Academy Program
Member to teach an Authorized Training Session, and/or (ii) a MCT.
o. “Trainer Content” means the trainer version of the Microsoft Instructor-Led Courseware and additional
supplemental content designated solely for Trainers’ use to teach a training session using the Microsoft
Instructor-Led Courseware. Trainer Content may include Microsoft PowerPoint presentations, trainer
preparation guide, train the trainer materials, Microsoft One Note packs, classroom setup guide and Pre-
release course feedback form. To clarify, Trainer Content does not include any software, virtual hard
disks or virtual machines.
2. USE RIGHTS. The Licensed Content is licensed not sold. The Licensed Content is licensed on a one copy
per user basis, such that you must acquire a license for each individual that accesses or uses the Licensed
Content.
2.1 Below are five separate sets of use rights. Only one set of rights apply to you.
2.2 Separation of Components. The Licensed Content is licensed as a single unit and you may not
separate their components and install them on different devices.
2.3 Redistribution of Licensed Content. Except as expressly provided in the use rights above, you may
not distribute any Licensed Content or any portion thereof (including any permitted modifications) to any
third parties without the express written permission of Microsoft.
2.4 Third Party Notices. The Licensed Content may include third party code tent that Microsoft, not the
third party, licenses to you under this agreement. Notices, if any, for the third party code ntent are included
for your information only.
2.5 Additional Terms. Some Licensed Content may contain components with additional terms,
conditions, and licenses regarding its use. Any non-conflicting terms in those conditions and licenses also
apply to your use of that respective component and supplements the terms described in this agreement.
a. Pre-Release Licensed Content. This Licensed Content subject matter is on the Pre-release version of
the Microsoft technology. The technology may not work the way a final version of the technology will
and we may change the technology for the final version. We also may not release a final version.
Licensed Content based on the final version of the technology may not contain the same information as
the Licensed Content based on the Pre-release version. Microsoft is under no obligation to provide you
with any further content, including any Licensed Content based on the final version of the technology.
b. Feedback. If you agree to give feedback about the Licensed Content to Microsoft, either directly or
through its third party designee, you give to Microsoft without charge, the right to use, share and
commercialize your feedback in any way and for any purpose. You also give to third parties, without
charge, any patent rights needed for their products, technologies and services to use or interface with
any specific parts of a Microsoft technology, Microsoft product, or service that includes the feedback.
You will not give feedback that is subject to a license that requires Microsoft to license its technology,
technologies, or products to third parties because we include your feedback in them. These rights
survive this agreement.
c. Pre-release Term. If you are an Microsoft IT Academy Program Member, Microsoft Learning
Competency Member, MPN Member or Trainer, you will cease using all copies of the Licensed Content on
the Pre-release technology upon (i) the date which Microsoft informs you is the end date for using the
Licensed Content on the Pre-release technology, or (ii) sixty (60) days after the commercial release of the
technology that is the subject of the Licensed Content, whichever is earliest (“Pre-release term”).
Upon expiration or termination of the Pre-release term, you will irretrievably delete and destroy all copies
of the Licensed Content in your possession or under your control.
4. SCOPE OF LICENSE. The Licensed Content is licensed, not sold. This agreement only gives you some
rights to use the Licensed Content. Microsoft reserves all other rights. Unless applicable law gives you more
rights despite this limitation, you may use the Licensed Content only as expressly permitted in this
agreement. In doing so, you must comply with any technical limitations in the Licensed Content that only
allows you to use it in certain ways. Except as expressly permitted in this agreement, you may not:
• access or allow any individual to access the Licensed Content if they have not acquired a valid license
for the Licensed Content,
• alter, remove or obscure any copyright or other protective notices (including watermarks), branding
or identifications contained in the Licensed Content,
• modify or create a derivative work of any Licensed Content,
• publicly display, or make the Licensed Content available for others to access or use,
• copy, print, install, sell, publish, transmit, lend, adapt, reuse, link to or post, make available or
distribute the Licensed Content to any third party,
• work around any technical limitations in the Licensed Content, or
• reverse engineer, decompile, remove or otherwise thwart any protections or disassemble the
Licensed Content except and only to the extent that applicable law expressly permits, despite this
limitation.
5. RESERVATION OF RIGHTS AND OWNERSHIP. Microsoft reserves all rights not expressly granted to
you in this agreement. The Licensed Content is protected by copyright and other intellectual property laws
and treaties. Microsoft or its suppliers own the title, copyright, and other intellectual property rights in the
Licensed Content.
6. EXPORT RESTRICTIONS. The Licensed Content is subject to United States export laws and regulations.
You must comply with all domestic and international export laws and regulations that apply to the Licensed
Content. These laws include restrictions on destinations, end users and end use. For additional information,
see www.microsoft.com/exporting.
7. SUPPORT SERVICES. Because the Licensed Content is “as is”, we may not provide support services for it.
8. TERMINATION. Without prejudice to any other rights, Microsoft may terminate this agreement if you fail
to comply with the terms and conditions of this agreement. Upon termination of this agreement for any
reason, you will immediately stop all use of and delete and destroy all copies of the Licensed Content in
your possession or under your control.
9. LINKS TO THIRD PARTY SITES. You may link to third party sites through the use of the Licensed
Content. The third party sites are not under the control of Microsoft, and Microsoft is not responsible for
the contents of any third party sites, any links contained in third party sites, or any changes or updates to
third party sites. Microsoft is not responsible for webcasting or any other form of transmission received
from any third party sites. Microsoft is providing these links to third party sites to you only as a
convenience, and the inclusion of any link does not imply an endorsement by Microsoft of the third party
site.
10. ENTIRE AGREEMENT. This agreement, and any additional terms for the Trainer Content, updates and
supplements are the entire agreement for the Licensed Content, updates and supplements.
12. LEGAL EFFECT. This agreement describes certain legal rights. You may have other rights under the laws
of your country. You may also have rights with respect to the party from whom you acquired the Licensed
Content. This agreement does not change your rights under the laws of your country if the laws of your
country do not permit it to do so.
13. DISCLAIMER OF WARRANTY. THE LICENSED CONTENT IS LICENSED "AS-IS" AND "AS
AVAILABLE." YOU BEAR THE RISK OF USING IT. MICROSOFT AND ITS RESPECTIVE
AFFILIATES GIVES NO EXPRESS WARRANTIES, GUARANTEES, OR CONDITIONS. YOU MAY
HAVE ADDITIONAL CONSUMER RIGHTS UNDER YOUR LOCAL LAWS WHICH THIS AGREEMENT
CANNOT CHANGE. TO THE EXTENT PERMITTED UNDER YOUR LOCAL LAWS, MICROSOFT AND
ITS RESPECTIVE AFFILIATES EXCLUDES ANY IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
14. LIMITATION ON AND EXCLUSION OF REMEDIES AND DAMAGES. YOU CAN RECOVER FROM
MICROSOFT, ITS RESPECTIVE AFFILIATES AND ITS SUPPLIERS ONLY DIRECT DAMAGES UP
TO US$5.00. YOU CANNOT RECOVER ANY OTHER DAMAGES, INCLUDING CONSEQUENTIAL,
LOST PROFITS, SPECIAL, INDIRECT OR INCIDENTAL DAMAGES.
It also applies even if Microsoft knew or should have known about the possibility of the damages. The
above limitation or exclusion may not apply to you because your country may not allow the exclusion or
limitation of incidental, consequential or other damages.
Please note: As this Licensed Content is distributed in Quebec, Canada, some of the clauses in this
agreement are provided below in French.
Remarque : Ce le contenu sous licence étant distribué au Québec, Canada, certaines des clauses
dans ce contrat sont fournies ci-dessous en français.
EXONÉRATION DE GARANTIE. Le contenu sous licence visé par une licence est offert « tel quel ». Toute
utilisation de ce contenu sous licence est à votre seule risque et péril. Microsoft n’accorde aucune autre garantie
expresse. Vous pouvez bénéficier de droits additionnels en vertu du droit local sur la protection dues
consommateurs, que ce contrat ne peut modifier. La ou elles sont permises par le droit locale, les garanties
implicites de qualité marchande, d’adéquation à un usage particulier et d’absence de contrefaçon sont exclues.
EFFET JURIDIQUE. Le présent contrat décrit certains droits juridiques. Vous pourriez avoir d’autres droits
prévus par les lois de votre pays. Le présent contrat ne modifie pas les droits que vous confèrent les lois de votre
pays si celles-ci ne le permettent pas.
Module 1
Evaluating the Environment for Virtualization
Contents:
Lesson 3: Evaluating the Current Environment for Virtualization 2
Module Review and Takeaways 5
Lab Review Questions and Answers 6
1-2 Server Virtualization with Windows Server Hyper-V® and System Center
Lesson 3
Evaluating the Current Environment for Virtualization
Contents:
Demonstration: Assessing the Comp uting Environment by Using MAP 3
Evaluating the Environment for Virtualization 1-3
2. Move the mouse to the bottom left of the screen, right-click the Windows icon, and then click Run.
3. In the Run text box, type \\lon-dc1\e$\labfiles\mapsetup.exe, and then click OK.
4. In the Microsoft Assessment and Planning Toolkit Setup Wizard, on the Welcome page, click Next.
5. On the License Agreement page, review the license agreement, click I accept the terms of the
license agreement, and then click Next.
6. On the Installation Folder page, review the installation path, and then click Next.
7. On the Customer Experience Improvement Program page, click I don’t want to join the
program at this time, and then click Next.
8. On the Ready to Install page, click Install.
9. On the Installation Successful page, ensure the Open the Microsoft Assessment and Planning
and Toolkit check box is selected, and then click Finish.
10. On the Datasource page, in the Create or select a database section, in the Name text box, type
Demo, and then click OK.
Use MAP to collect inventory data
1. In MAP, on the Overview page, on the left side, click Server Virtualization, and under the Steps to
complete section, click Collect inventory data.
2. In the Inventory and Assessment Wizard, on the Inventory Scenarios page, select the Windows
computers check box, and then click Next.
3. On the Discovery Methods page, ensure that Use Active Directory Domain Services (AD DS) is
selected, and then click Next.
4. On the Active Directory Credentials page, in the Domain text box, type Adatum, in the Domain
account text box, type administrator, in the Password text box, type Pa$$w0rd, and then click
Next.
5. On the Active Directory Options page, ensure that Find all computers in all domains, containers,
and organizational units is selected, and then click Next.
6. On the All Computer Credentials page, click Create.
7. On the Account Entry page, in the Account name text box, type adatum\administrator, in the
Password text box, type Pa$$w0rd, in the Confirm password text box, type Pa$$w0rd, click Save,
and then click Next.
8. On the Credentials Order page, click Next.
9. On the Summary page, review the summary, and then click Finish.
10. In the Inventory and Assessment page, review the results of the data collection, wait for the
assessment to show as complete, and then click Close.
2. In the Performance Metrics Wizard, on the Collection Configuration page, ensure that the
Windows-based machine check box is selected, leave the default time, and then click Next.
3. On the Choose Computers page, ensure that Choose the computer from a list on the next step
of the wizard is selected, and then click Next.
4. On the Computer List page, select the check box next to Computer Name, which selects all the
computers, and then click Next.
5. On the All Computer Credential page, ensure that the adatum\administrator account is selected,
and then click Next.
1. At the bottom-left of the MAP console screen, in the running task drop-down list box, click Cancel
processing, and then click Yes.
2. Under the Steps to complete section, click Create hardware configuration.
3. On the Choose Scenarios page, click General Server Consolidation/Desktop Virtualization, and
then click Next.
4. On the Hardware Configuration page, click Create New, in the Create New text box, type Server-
Type1, and then click Next.
5. On the Infrastructure page, click Next.
6. On the CPU page, click each of the following attributes drop-down list boxes and assign the following
values:
o Manufacturer: Intel
o Model: Xeon X7560
o Number of physical processors: 2
o Processor speed (GHz): 2.262 (default value)
o Cores per processor 8 (default value)
7. Leave the L2, L3, Cache size, and Bus Speed (MHz) as default values, and then click Next.
8. On the Storage page, click Define IOPS and total available storage. In the Maximum disk I/O per
second (IOPS) text box, type 20000, in the Total available storage and (GB) text box, type 1800,
and then click Next.
9. On the Network and Memory page, in the Total Network throughput (Mbps) text box, type
4000, in the Amount of memory (GB) text box, type 128, and then click Next.
Evaluating the Environment for Virtualization 1-5
Review Question(s)
Question: What are some of the reasons that you would not virtualize a server or server application?
Answer: You should not virtualize the product if the server or application vendor does not support
virtualization, or if the server or application uses customized hardware.
Question: Which technology can assist you in managing large volumes of virtual machines and Hyper-V
clusters?
Answer: VMM is the most suitable technology for managing large volumes of virtual machines.
In MAP, when you click on most operations, you At the bottom, left of the MAP console, next
receive a warning that states, “The task processor is to the database name, will be the name of a
currently busy. You cannot perform this operation task that is running. Next to the task name,
while the task processor is running. Please wait for click the drop-down list box, and then either
the task processor to complete or cancel the task view the status of the running task, or cancel
process before retrying this operation.” it.
1-6 Server Virtualization with Windows Server Hyper-V® and System Center
Answer: Before you can run the Desktop Virtualization Planning Wizard, you will need to complete the
following steps:
• Collect inventory data.
Module 2
Installing and Configuring the Hyper-V Role
Contents:
Lesson 1: Installing the Hyper-V Role 2
Lesson 2: Managing Hyper-V 7
Lesson 3: Configuring Hyper-V Settings 10
Lesson 1
Installing the Hyper-V Role
Contents:
Questio n and Answers 3
Demonstration: Installing the Hyper-V Role 4
Installing and Configuring the Hyper-V Role 2-3
Answer: Windows Server 2012 R2 Datacenter includes virtualization rights for unlimited virtual machines
running on that platform, but virtual machines must be running a supported Windows Server
operating system. You are evaluating a Virtual Desktop Infrastructure (VDI) scenario in which you
will provide Windows 8.1 virtual desktops. Because Windows 8.1 is a client operating system and
not a Windows Server operating system, it is not covered by Windows Server 2012 R2 Datacenter
virtualization rights.
Answer: In Hyper-V in Windows Server 2012 R2, you can create virtual machines with up to 64 processors
and 1 TB RAM. Because the server that you plan to virtualize uses fewer resources than that, you
can virtualize it on Windows Server 2012 R2. In Hyper-V in Windows Server versions prior to
Windows Server 2012, you were able to create virtual machines with up to four processors and 64
GB RAM. Because the computer that is running SQL Server that you plan to virtualize uses more
resources than that, you would not be able to virtualize it on Hyper-V hosts running Windows
Server operating systems prior to Windows Server 2012. Alternatively, you could virtualize it, but
you would have to assign it fewer resources that it currently has.
Hyper-V Architecture
Question: You install Windows Server 2012 R2 on a virtual machine named VM1. Can you monitor disk
input/output (I/O) for the physical server from VM1?
Answer: VM1 is running in a virtual environment and you can monitor only the resources that are
available to VM1 from inside the virtual machine. You can monitor disk input/output (I/O) that is
from VM1, but not for the entire physical server. If you need to monitor Disk I/O for the entire
server, you will need to monitor Hyper-V in the parent partition.
Answer: Although technically you can use the same network adapter for performing remote Hyper-V
administration and for providing network access to virtual machines, this is not a best practice.
We recommend that the Hyper-V host has multiple network adapters, and that you use different
adapters for each purpose. You could put multiple network adapters in (NIC Teaming for
redundancy. You could then use virtual adapters that utilize this NIC team.
Answer: If you need to provide shared storage for virtual machine-based failover clustering, you can use
an Internet SCSI (iSCSI) target, a Fibre Channel SAN, or a shared virtual hard disk, which you store
on a Cluster Shared Volume (CSV) or scale-out file server SMB 3.0 share.
Answer: No. When you installed the Hyper-V role, appropriate Windows Firewall rules to allow remote
Hyper-V management were created and enabled automatically. Therefore, you do not have to
create these rules manually.
Get-WindowsFeature *Hyper*
3. Output shows that neither Hyper-V nor Hyper-V Management Tools are installed.
16. On the Start screen, search for and open Windows Firewall with Advanced Security.
17. In the Windows Firewall with Advanced Security window, in the navigation pane, click Inbound
Rules.
18. In the details pane, verify that there are no rules that start with the word Hyper-V.
19. Close the Windows Firewall with Advanced Security window.
20. On LON-HOST2, on the taskbar, click the Windows PowerShell icon.
Get-WindowsFeature *Hyper*
25. Verify that the output shows that both Hyper-V and Hyper-V Management Tools are installed.
26. In Windows PowerShell, run the following cmdlet:
27. Verify that the output lists many cmdlets, which confirms that the Hyper-V module is installed and
available.
28. Type and run bcdedit.exe. Verify that in the output, in the Windows Boot Loader section, a
hypervisorlaunchtype Auto line is present.
29. Minimize the Windows PowerShell window.
30. Open the Start screen, and search for programs containing the word hyper.
31. Confirm that two programs, Hyper-V Manager and Hyper-V Virtual Machine Connection, are
discovered.
32. On the Start screen, search for and open Performance Monitor.
38. On the Start screen, search for and open Windows Firewall with Advanced Security.
39. In Windows Firewall with Advanced Security, in the navigation pane, click Inbound Rules.
40. In the details pane, verify that multiple rules display that start with the word Hyper-V.
Lesson 2
Managing Hyper-V
Contents:
Questio n and Answers 8
Demonstration: Installing and Using Hyper-V Manager 9
2-8 Server Virtualization with Windows Server Hyper-V® and System Center
Answer: No. The Hyper-V feature is included in Windows 8 and newer Windows client operating systems.
If you want to administer Hyper-V hosts from such a client, you only need to turn on the Hyper-V
Management Tools Windows feature, and you do not need to install RSAT.
Answer: If you want to administer Hyper-V locally, you have installed the Hyper-V Module for Windows
PowerShell already, when you installed the Hyper-V role, and you can start using it. If you want to
administer Hyper-V from a remote computer that does not have the Hyper-V role installed, you
must first enable the Hyper-V Module for Windows PowerShell feature. You do not need to
import the Hyper-V module before you can use it, as was the case in operating systems prior to
Windows Server 2012.
Note: The output shows that five Hyper-V features have been disabled.
5. On the desktop, on the toolbar, right-click the Start icon and then click Control Panel.
6. In Control Panel, in the Search Control Panel text box, type Feature, and then click Turn Windows
features on or off.
7. In the Windows Features window, expand Hyper-V, click Hyper-V Management Tools, and then
click OK.
8. After Windows completes the requested changes, click Close.
9. Switch back to Windows PowerShell, and run the following cmdlet:
Note: Many cmdlets display, because the Hyper-V module is now installed.
14. In the Select Computer dialog box, click Browse, in the Enter the object name to select text box,
type LON-HOST1, and then click OK twice.
Lesson 3
Configuring Hyper-V Settings
Contents:
Questio n and Answers 11
Demonstration: Configuring Hyper-V Settings 11
Installing and Configuring the Hyper-V Role 2-11
What Is NUMA?
Question: Can you modify your server’s NUMA topology?
Answer: No. NUMA topology is based on the hardware architecture, and you cannot modify the
topology. However, you can configure virtual NUMA topology for virtual machines. This is usually
not recommended, because Hyper-V projects physical NUMA topology into virtual machines.
However, if you configure a virtual machine with suboptimal virtual NUMA topology, you can
always click the Use Hardware Topology button, and revert to default values.
2. In Hyper-V Manager, in the Actions pane, click New, and then click Hard Disk.
3. In the New Virtual Hard Disk Wizard, click Next three times.
4. In the New Virtual Hard Disk Wizard, on the Specify Name and Location page, in the Location text
box, verify that C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks\ is entered, and then
click Cancel.
5. In Hyper-V Manager, in the Actions pane, click Hyper-V Settings.
6. On the Hyper-V Settings for LON-HOST1 page, in the left pane, verify that Virtual Hard Disks is
selected. Verify that the same location as was used by the wizard is in the Location field.
2-12 Server Virtualization with Windows Server Hyper-V® and System Center
7. Click Browse, in navigation pane, click Local Disk (C:), in the details pane, click Users, and then click
Select Folder.
11. In the New Virtual Hard Disk Wizard, on the Specify Name and Location page, in the Location text
box, verify that C:\Users\ is entered.
Note: This is the same location as you configured for the virtual hard disk location.
15. In Hyper-V Manager, in the Actions pane, click Hyper-V Settings, and verify that \\LON-
HOST2\VHDs is specified as the Virtual Hard Disk location.
16. On the Hyper-V Settings for LON-HOST1 page, in the left pane, click NUMA Spanning, and verify
in the details pane that NUMA Spanning is enabled.
17. In the left pane, click Storage Migrations, and verify that 2 simultaneous storage migrations are
allowed.
18. Close the Hyper-V Settings for LON-HOST1 page, and minimize Hyper-V Manager.
19. On LON-HOST1, on the taskbar, click the Windows PowerShell icon.
21. Maximize Hyper-V Manager, and in the Actions pane, click Hyper-V Settings.
22. On the Hyper-V Settings for LON-HOST1 page, in the left pane, click NUMA Spanning, and verify
that NUMA Spanning is disabled. NUMA Spanning is disabled, because you disabled it with Windows
PowerShell. Enable NUMA Spanning.
23. In the left pane, click Storage Migrations, and verify that 4 simultaneous storage migrations are
allowed.
Note: These are allowed because you set it with Windows PowerShell.
24. Close Hyper-V Settings for LON-HOST1, and then close Hyper-V Manager.
Installing and Configuring the Hyper-V Role 2-13
Lesson 4
Hyper-V Host Storage and Networking
Contents:
Questio n and Answers 14
2-14 Server Virtualization with Windows Server Hyper-V® and System Center
Answer: You can include locally attached disks of different sizes that connect using different bus types.
However, because an iSCSI disk is on a remote storage (SAN), you cannot include the iSCSI disk in
Storage Spaces.
Answer: No. Windows Server 2008 R2 does not support SMB 3.0. It only supports SMB 2.1 and older SMB
versions. When you a copy file from a Windows Server 2008 R2 file server to a Windows Server
2012 R2 computer, SMB 2.1 will be used.
Question: You have a Windows 8.1 virtual machine that must be highly available. Can you use virtual
machine-based failover clustering to make it highly available?
Answer: For virtual machine-based failover clustering, the operating system that is installed on the virtual
machine must support failover clustering. Windows 8.1 does not support failover clustering, and
therefore you cannot use virtual machine-based failover clustering to make a Windows 8.1 virtual
machine highly available. If you need to make a Windows 8.1 virtual machine highly available,
you should use Hyper-V host-based failover clustering.
2-16 Server Virtualization with Windows Server Hyper-V® and System Center
Answer: Neither Server Core nor Hyper-V Server has a GUI. Therefore, you can manage Hyper-V locally
only by using Windows PowerShell. However, in reality, you would probably manage Hyper-V on
Server Core or on Hyper-V Server remotely, either by using Hyper-V Manager or by using VMM.
You also can still use Windows PowerShell to manage them remotely.
Question: Do you need to store a virtual hard disk locally if you want to start a virtual machine from it?
Answer: No. In Hyper-V prior to Windows Server 2012, you had to store a virtual hard disk locally if you
wanted to use it for a running virtual machine. However, with Hyper-V in Windows Server 2012
and newer, you can store a virtual hard disk on SMB 3.0 file shares, and then use it with running
virtual machines.
Question: How can you view Windows PowerShell cmdlets that you can use for managing Hyper-V host?
Answer: Windows PowerShell cmdlets for managing Hyper-V host are present in the Hyper-V module.
You can view cmdlets in the Hyper-V module by running the cmdlet Get-Command –Module
Hyper-V.
Creating and Managing Virtual Hard Disks, Virtual Machines, and Checkpoints 3-1
Module 3
Creating and Managing Virtual Hard Disks, Virtual Machines,
and Checkpoints
Contents:
Lesson 1: Creating and Configuring Virtual Hard Disks 2
Lesson 2: Creating and Configuring Virtual Machines 6
Lesson 1
Creating and Configuring Virtual Hard Disks
Contents:
Questio n and Answers 3
Demonstration: Creating a Virtual Hard Disk 4
Demonstration: Managing Virtual Hard Disks 5
Creating and Managing Virtual Hard Disks, Virtual Machines, and Checkpoints 3-3
Answer: Depending on how the virtual machine is accessing the directly attached disk, it might not be
visible in Disk Management on a Hyper-V host. If the virtual machine has the disk attached
through Hyper-V Manager as a physical hard disk, then the disk is visible in Disk Management,
but it is marked as offline. If the disk is attached by using the operating system that is installed on
the virtual machine, either by using iSCSI or a virtual Fibre Channel adapter, then the disk is not
visible in Disk Management on a Hyper-V host.
3-4 Server Virtualization with Windows Server Hyper-V® and System Center
Answer: SAN logical unit numbers (LUNs) can provide higher performance and throughput than locally
attached disks. Locally attached SSDs can offer better performance than SAN, but you can use
SAN as shared storage for failover clustering in high availability scenarios.
4. On the Choose Disk Format page, confirm that VHDX is selected, and then click Next.
5. On the Choose Disk Type page, confirm that the default disk type for VHDX hard disk is set to
Dynamically expanding, and then click Next.
6. On the Specify Name and Location page, in the Name field, type Dynamic.vhdx. Confirm that the
Location field is set to C:\Shares\VHDs\, and then click Next.
7. On the Configure Disk page, confirm that Create a new blank virtual hard disk is selected, in the
Size field, type 100, and then click Next.
8. On the Completing the New Virtual Hard Disk Wizard page, click Finish.
9. On LON-HOST1, in Hyper-V Manager, in the Actions pane, click New, and then click Hard disk.
10. In the New Virtual Hard Disk Wizard, on the Before You Begin page, click Next.
11. On the Choose Disk Format page, select VHD disk format, and then click Next.
12. On the Choose Disk Type page, click Differencing, and then click Next.
13. On the Specify Name and Location page, in the Name field, type Differencing.vhd. In the
Location field, confirm that C:\Shares\VHDs\ is entered, and then click Next.
14. On the Configure Disk page, click Browse, browse to E:\Program Files\Microsoft
Learning\base\Base14A-WS12R2.vhd, click Open, and then click Next.
Note: The actual drive letter on which base images are stored can be different, and it
depends on the physical server configuration. Drive E is used in the instructions, but you should
use the drive on which base images are stored in your environment.
15. On the Completing the New Virtual Hard Disk Wizard page, click Finish.
16. On LON-HOST1, on the taskbar, click the Windows PowerShell icon.
17. In Windows PowerShell, create a fixed-size virtual hard disk by typing the following cmdlet, and then
press Enter:
Creating and Managing Virtual Hard Disks, Virtual Machines, and Checkpoints 3-5
20. In the VHDs folder, confirm that the three virtual hard disks that you just created display in the folder.
21. In the VHDs folder, right-click Fixed.vhdx, confirm that its size on disk is 1.00 GB, and then click OK.
22. Verify that Dynamic.vhdx and Differencing.vhd are allocated less space on the disk, even though you
configured Dynamic.vhdx with 100 GB.
3. On the Locate Virtual Hard Disk page, click Browse, and then browse to C:\Shares\VHDs.
4. In the VHDs folder, click Fixed.vhdx, click Open, and then click Next.
5. On the Choose Action page, confirm that Expand is selected, and then click Next.
6. On the Expand Virtual Hard Disk page, in the New size field, type 2, and then click Next.
7. On the Completing the Edit Virtual Hard Disk Wizard page, click Finish.
8. In Hyper-V Manager, in the Actions pane, click Edit Disk.
9. In the Edit Virtual Hard Disk Wizard, on the Before you Begin page, click Next.
10. On the Locate Virtual Hard Disk page, click Browse, browse to C:\Shares\VHDs, click
Dynamic.vhdx, click Open, and then click Next.
11. On the Choose Action page, click Expand, and then click Next.
12. On the Expand Virtual Hard Disk page, in New size field, type 200, and then click Next.
13. On the Completing the Edit Virtual Hard Disk Wizard page, click Finish.
14. On LON-CL1, in Computer Manager, right-click Disk Management, and then click Refresh. Confirm
that Disk 1 and Disk 2 have expanded and now have 2 GB and 200 GB of unallocated space.
Note: Hyper-V expanded the virtual hard disks while the virtual machine was running.
3-6 Server Virtualization with Windows Server Hyper-V® and System Center
Lesson 2
Creating and Configuring Virtual Machines
Contents:
Questio n and Answers 7
Demonstration: Creating Vir tual Machines 8
Demonstration: Configuring Integration Services 8
Creating and Managing Virtual Hard Disks, Virtual Machines, and Checkpoints 3-7
Answer: Yes, you can add a virtual Fibre Channel adapter to a Windows 8.1 virtual machine on the Hyper-
V host. However, the virtual machine will not be able to use it, because Windows 8.1 does not
support Fibre Channel adapters.
3. On the Specify Name and Location page, in the Name field, type LON-VM2, and then click Next.
4. On the Specify Generation page, click Generation 2, and then click Next.
5. On the Assign Memory page, in Startup Memory, type 1024, select the Use Dynamic Memory for
this virtual machine check box, and then click Next four times.
6. On the Completing the Virtual Machine Wizard page, click Finish. A virtual machine named LON-
VM2 is created.
2. Make a note of the current time, and enter 11:00 as the current time.
3. Run the Time command again, and confirm that it was set back automatically to its previous value, as
Integration Services automatically synchronized the time on LON-CL1 with the time on LON-HOST1.
6. In Integration Services, in the details pane, clear the Time synchronization check box, and then click
OK.
7. On LON-CL1, at a command prompt, run the Time command. Make note of the current time, type
11:00 as the current time, and then press Enter.
8. At a command prompt, type Time, and then press Enter twice. Confirm that the returned time is few
seconds over 11:00. This is because the time on the virtual machine is no longer synchronizing with
the Hyper-V host.
9. At a command prompt, type devmgmt.msc, and then press Enter.
10. In Device Manager, expand Display adapters, and then confirm that the virtual machine is using the
Microsoft Hyper-V Video adapter, which is provided as part of Integration Services.
11. In Device Manager, expand System devices, and then confirm that several devices with Hyper-V in
their name are listed, including Microsoft Hyper-V Dynamic Memory. All of these virtual devices are
provided as part of Integration Services.
12. Close Device Manager.
3-10 Server Virtualization with Windows Server Hyper-V® and System Center
Lesson 3
Installing and Importing Virtual Machines
Contents:
Questio n and Answers 11
Demonstration: Importing a Virtual Machine 11
Demonstration: Using Enhanced Se ssion Mode 13
Creating and Managing Virtual Hard Disks, Virtual Machines, and Checkpoints 3-11
Answer: You cannot install an operating system on a virtual machine by starting the virtual machine from
a USB flash drive, because USB devices are not supported in virtual machines at startup. With
enhanced session mode, you can redirect USB devices in a virtual machine. For enhanced session
mode to be available, however, the operating system on the virtual machine must be running
already, and integration components must be installed. If you have an .iso file of the operating
system on a USB flash drive, you can mount it to a virtual machine and start the virtual machine
from the .iso file.
2. In the Import Virtual Machine Wizard, on the Before You Begin page, click Next.
3. On the Locate Folder page, type C:\VirtualMachines\LON-EXPORT\, and then click Next.
4. On the Select Virtual Machine Import Virtual Machine page, confirm that LON-EXPORT is
selected, and then click Next.
5. On the Choose Import Type page, confirm that Register the virtual machine in-place (use the
existing unique ID) is selected, and then click Next.
6. On the Configure Processor page, in Number of virtual processors field, type 1, and then click
Next.
Note: This page shows only if a virtual machine is configured with more processors than
are available on the Hyper-V host.
7. On the Connect Network page, click External Network as the virtual switch that you want the
virtual machine to be connected to.
Note: This page shows only if a virtual machine is configured to use a virtual switch, which
is not available on the Hyper-V host.
8. Click Next.
9. On the Completing Import Wizard page, click Finish.
10. When the error message “Hyper-V encountered an error during the import operation” displays, click
See details. Verify that the reason for the error is that the parent virtual hard disk was not found.
Click Close.
Note: The actual drive letter on which base images are stored can be different, and it
depends on the physical server configuration. Drive E is used in the instructions, but you should
use the drive on which base images are stored in your environment.
17. In Hyper-V Manager, in the Actions pane, click Import Virtual Machine.
18. In the Import Virtual Machine window, on the Before You Begin page, click Next.
19. On the Locate Folder page, type C:\VirtualMachines\LON-EXPORT\, and then click Next.
20. On the Select Virtual Machine Import Virtual Machine page, confirm that LON-EXPORT is
selected, and then click Next.
Creating and Managing Virtual Hard Disks, Virtual Machines, and Checkpoints 3-13
21. On the Choose Import Type page, confirm that Register the virtual machine in-place (use the
existing unique ID) is selected, and then click Next.
5. In the Hyper-V Settings window, in the left pane, in the Server section, click Enhanced Session Mode
Policy.
6. In the details pane, click Allow enhanced session mode, and then click OK.
10. In the Connect to LON-CL1 window, click Connect. Confirm that you are not automatically signed in
to LON-CL1.
11. On LON-CL1, click ADATUM\administrator, in the Password field, type Pa$$w0rd, and then press
Enter. Verify that your previous session displays.
12. On LON-HOST1, in File Explorer, browse to C:\Windows, right-click Write.exe, and then click Copy.
13. On LON-CL1, right-click the desktop, and then click Paste. Confirm that the file Write.exe is copied
to the desktop.
14. On LON-CL1, on the taskbar, click File Explorer. In the navigation pane, confirm that drives from
LON-HOST1 are mapped to the virtual machine.
15. In the navigation pane, right-click This PC, and then click Properties.
16. In the System window, click Remote Settings. In the Remote Desktop section, confirm that Don’t
allow remote connections to this computer is selected, and then click OK.
Lesson 4
Managing Virtual Machine Checkpoints
Contents:
Questio n and Answers 15
Demonstration: Working with Checkpoints 16
Creating and Managing Virtual Hard Disks, Virtual Machines, and Checkpoints 3-15
Answer: The virtual machine must be turned off for you to configure most of the virtual machine settings.
However, you can never modify a virtual machine configuration in a checkpoint, regardless of
whether the virtual machine was running or turned off when you created the checkpoint.
Checkpoints contain a virtual machine configuration from the past, which you cannot modify.
Answer: If you create two checkpoints, one after another, and if you never apply a previous checkpoint,
you will have a tree with one branch. If you apply the first checkpoint and then create a new
checkpoint, you will have another branch in the checkpoint tree.
operating system that is running on that virtual machine. However, be aware that Windows
Server 2008 R2 is not Generation ID–aware, so if you want to use it, the application that is
running on the virtual machine should be able to behave differently if Generation ID changes.
6. In Hyper-V Manager, double-click LON-VM1. On LON-VM1, complete the setup by clicking Next,
and then clicking I accept.
7. On the Settings page, provide the password Pa$$w0rd.
10. On LON-VM1, right-click the desktop, click New, click Folder, and then name it Folder1.
11. In Virtual Machine Connection, in the Action menu, click Checkpoint. In the Checkpoint Name field,
type Folder1, and then click Yes.
12. On LON-VM1, right-click the desktop, click New, click Folder, and name it Folder2.
13. On LON-HOST1, open Windows PowerShell, and then create a checkpoint for LON-VM1 by running
the following cmdlet:
14. In Windows PowerShell, view the existing checkpoints for LON-VM1 by running the following cmdlet:
15. In Hyper-V Manager, confirm that all three checkpoints for LON-VM1 display. Right-click the Folder1
checkpoint, and then click Apply. Click Apply in the Apply Checkpoint dialog box.
16. On LON-VM1, confirm that there is only a single folder named Folder1 on the desktop.
17. Right-click the desktop, click New, click Folder, and then name it Folder1.1.
18. In Hyper-V Manager, right-click LON-VM1, and then click Checkpoint.
19. In Hyper-V Manager, in the Checkpoints pane, right-click the created checkpoint, click Rename, and
then type Folder1.1.
20. On LON-HOST1, in File Explorer, browse to C:\Shares\Snapshots.
21. In the Snapshots folder, confirm that there are four .xml files and four subfolders, which is the same
number of checkpoints for LON-VM1 that you created.
Creating and Managing Virtual Hard Disks, Virtual Machines, and Checkpoints 3-17
22. In the Snapshots window, in the details pane, click the Date modified column to order content by
the time of creation.
23. Right-click the lowest folder in the details pane, and then click Properties.
24. In the Properties dialog box, confirm that the Size of the folder is 0, as the first checkpoint was
created when LON-VM1 was turned off, and then click OK.
25. In the Snapshots window, review the size of the other folders. You created other LON-VM1
checkpoints while the virtual machine was running, so each of those folders contains the memory
content of the virtual machine at the moment when the checkpoint was created.
3-18 Server Virtualization with Windows Server Hyper-V® and System Center
Lesson 5
Monitoring Hyper-V
Contents:
Questio n and Answers 19
Demonstration: Using Performance Monitor to Monitor Hyper-V 19
Creating and Managing Virtual Hard Disks, Virtual Machines, and Checkpoints 3-19
Answer: Performance Monitor in virtual machines does not have Hyper-V performance counters.
However, you can connect Performance Monitor to the Hyper-V host if there is connectivity
between the two, and you then can use it to monitor the Hyper-V host. You should be using the
Hyper-V Hypervisor Logical Processor performance object for monitoring the processor, and not
the Processor performance object, which you would use on a physical server.
7. In Performance Monitor, in the details pane, select both Disk Reads/sec and Read Operations/Sec,
right-click them, and then click Scale Selected Counters.
8. On LON-CL1, open Windows PowerShell.
C:\LabFiles\Mod03\sqlio.exe
12. On LON-CL1, in Windows PowerShell, run the following command, and then minimize the Windows
PowerShell window:
C:\LabFiles\Mod03\Cpustres.exe
13. In CPU Stress, set Process Priority Class to High. In the Thread 1 section, set Thread Priority to
Highest and Activity to Busy.
14. On LON-HOST1, in Performance Monitor, follow how processor utilization increases on the virtual
machine and on Hyper-V. Notice that the processor is much less utilized on LON-HOST1 than on
LON-CL1.
15. On LON-HOST1, in Hyper-V Manager, view CPU Usage for the LON-CL1 virtual machine.
18. In Hyper-V Manager, confirm that CPU Usage for the LON-CL1 virtual machine is considerably lower
than before.
19. On LON-CL1, close CPU Stress and Task Manager.
Creating and Managing Virtual Hard Disks, Virtual Machines, and Checkpoints 3-21
Lesson 6
Designing Virtual Machines for Server Roles and
Services
Contents:
Questio n and Answers 22
3-22 Server Virtualization with Windows Server Hyper-V® and System Center
Answer: Your solution depends on multiple options that you must consider. You should use the same
operating system and configuration for the Hyper-V hosts. You should use Windows PowerShell
to manage the Hyper-V hosts remotely and implement scripts to standardize their administration.
You should also consider implementing enterprise tools such as VMM for administering the
virtualization infrastructure.
Answer: In Hyper-V Manager, you should perform several configuration steps to create a virtual machine
with four processors, two virtual hard disks, and two network adapters. You first would need to
create a new virtual machine and then modify its configuration. You should consider using
Windows PowerShell, in which you can achieve the goal by running a simple script.
Answer: If you want Microsoft to support your configuration, you should not assign more than eight
virtual processors to Exchange Server virtual machines on the Hyper-V host, assuming that the
Hyper-V host is not running any non-Exchange Server virtual machines.
Creating and Managing Virtual Hard Disks, Virtual Machines, and Checkpoints 3-23
Question: Can you use shared virtual hard disks with two virtual machines that have Windows 8.1
installed?
Answer: No. You can configure virtual machines to use shared virtual hard disks, but Windows 8.1 will not
be able to use the shared storage, because this functionality is not part of the client operating
system.
Question: Can you use virtual machine settings to discover whether it is Generation 1 or Generation 2?
Answer: Yes, you can recognize from the virtual machine settings if it is Generation 1 or Generation 2.
Generation 2 supports fewer different hardware components, and conversely, a virtual machine
that has an IDE controller, legacy network adapter, or BIOS cannot be a Generation 2 virtual
machine.
Question: Can you use enhanced session mode to connect to a Windows Server 2012 R2 virtual machine
that is running on Windows Server 2012 Hyper-V host?
Answer: One of the prerequisites to be able to use enhanced session mode is that the virtual machine
must be running on Hyper-V in either Windows Server 2012 R2 or Windows 8.1. If this
requirement is not met, enhanced session mode is not available, regardless of the operating
system that is running on the virtual machine.
Question: Which monitoring tool can you use to monitor multiple servers simultaneously and to provide
you with alerts when the performance of servers is different than normal?
Answer: Performance Monitor is the only tool in Windows Server 2012 R2 that you can use to monitor
multiple servers simultaneously and to create alerts.
3-24 Server Virtualization with Windows Server Hyper-V® and System Center
Answer: If a disk is attached locally to a Hyper-V host, the host operating system does not use it. It is in
the offline state, and it can be attached directly to the virtual machine that is running on the
Hyper-V host. However, a locally attached disk is not a requirement. This storage can be on the
SAN, attached to the Hyper-V host, and exposed to the virtual machine as a directly attached
disk. Alternatively, the virtual machine can directly attach LUN on the iSCSI or Fibre Chanel SAN
and bypass the Hyper-V host completely.
Question: How can you use a virtual hard disk with the installed operating system as a template for new
virtual machines?
Answer: You first should generalize the operating system on the virtual hard disk by running the Sysprep
command. Then, you can copy the virtual hard disk and add the copy to the new virtual machine,
or you can create a differencing virtual hard disk and then use the existing virtual hard disk as a
parent. In the second scenario, you should be aware that you should not modify the parent disk,
and be aware of the performance implications.
Question: How can you prevent a virtual machine from monopolizing disk I/O when a disk-intensive
application is running on a virtual machine?
Answer: You can configure QoS for storage on the virtual hard disk that the disk-intensive application is
accessing. You can limit maximum IOPS and ensure that the application is not monopolizing disk
I/O.
Question: What are the requirements for virtual machines to use dynamic memory? Is this feature
available only to virtual machines that are running the Windows operating system?
Answer: Any virtual machine can use dynamic memory, providing it is running a supported operating
system and has integration services installed. For Linux operating systems, this can include most
supported Linux distributions. For a virtual machine to be able to use dynamic memory, you must
configure the dynamic memory for the virtual machine, and then the virtual machine can allocate
and release memory inside the configured boundaries.
Answer: No, you can use enhanced session mode to connect to virtual machines that are running on
Windows Server 2012 R2 or Windows 8 hosts and are running a supported operating system,
which currently includes only Windows 8.1 and Windows Server 2012 R2.
Answer: Windows Server 2012 includes the Generation ID, which virtual machines can use to detect
whether a checkpoint was applied or whether a virtual hard disk was added to a new virtual
machine. However, the operating system and applications should both be aware of and be able
to respond appropriately when a checkpoint is applied. Many applications are not able to
respond appropriately, and therefore, you should try to avoid checkpoints in a production
environment. Many applications also explicitly do not support the use of checkpoints. You should
also be aware that checkpoints create differencing virtual hard disks, which can have
performance implications. However, checkpoints are very useful in some scenarios, such as
testing, training environments, and Virtual Desktop Infrastructure (VDI) deployments where
pooled virtual desktops are used.
Question: Which Windows Server 2012 R2 tool should you use for monitoring Hyper-V hosts and virtual
machines?
Answer: Windows Server 2012 R2 includes several performance monitoring tools, but only Performance
Monitor is virtualization-aware. Therefore, you should use it for monitoring both Hyper-V host
performance and the performance of virtual machines.
Question: How can you enable resource metering for virtual machines in Hyper-V Manager?
Answer: You cannot use Hyper-V Manager to enable resource metering. You can only enable resource
metering by using the Windows PowerShell cmdlet Enable-VMResourceMetering.
Creating and Configuring Virtual Machine Networks 4-1
Module 4
Creating and Configuring Virtual Machine Networks
Contents:
Lesson 1: Creating and Using Hyper-V Virtual Switches 2
Lesson 2: Advanced Hyper-V Networking Features 6
Lesson 3: Configuring and Using Hyper-V Network Virtualization 10
Lesson 1
Creating and Using Hyper-V Virtual Switches
Contents:
Questio n and Answers 3
Demonstration: Using Virtual Switch Manager 3
Demonstration: Configuring and Using VLANs 5
Creating and Configuring Virtual Machine Networks 4-3
Answer: Yes. If there is no virtual switch on a Hyper-V host, you will not be able to connect virtual
machines to a network. In addition, virtual machines will be unable to communicate with other
computers on the network, or between themselves, even if they are running on the same Hyper-
V host. The Hyper-V host will still have network connectivity, but a virtual switch will not control
its network traffic. In practice, you will always create one or more virtual switches on a Hyper-V
host.
Answer: If a virtual machine is connected to an internal virtual switch, its connectivity is generally limited
to the Hyper-V host itself, and to other virtual machines that are running on the same Hyper-V
host and are connected to the same internal virtual switch. However, if the Hyper-V host has
Internet connectivity and is configured to perform NAT, then the virtual machine could also have
Internet connectivity. Another way to achieve Internet connectivity would be to configure
another virtual machine on the internal network as a gateway.
Question: What will happen in the parent partition when you create a new internal virtual switch? Will it
be the same as when you create a new private virtual switch?
Answer: When you create an internal virtual switch, a new virtual network adapter will be created in the
parent partition, and it will be connected automatically to the created internal switch. When you
create a private virtual switch, no additional network adapter is created in the parent partition.
3. In the Virtual Switch Manager for LON-HOST1 window, confirm that in the Virtual Switches section,
External Network is the only virtual switch listed.
4. In the right pane, in the Create virtual switch section, click Private, and then click New Virtual
Switch.
5. In the Virtual Switch Manager for LON-HOST1 window, in the Name text box, type Private Switch,
and then click OK.
6. In Hyper-V Manager, right-click 20409B-LON-PROD1, and then click Settings.
7. In the Settings for 20409B-LON-PROD1 window, in the left pane, click Network Adapter, in the
Virtual Switch drop-down list box, click Private Switch, and then click OK.
8. In Hyper-V Manager, right-click 20409B-LON-TEST1, and then click Settings.
9. In the Settings for 20409B-LON-TEST1 window, in the left pane, click Network Adapter. In the
Virtual Switch drop-down list box, click Private Switch, and then click OK.
10. On LON-PROD1, on the Start screen, search for Windows PowerShell. Right-click Windows
PowerShell, click Run as administrator, and then in User Account Control, click Yes.
ping 10.0.0.16
13. On LON-HOST1, in Hyper-V Manager, right-click 20409B-LON-PROD1, and then click Settings.
14. In Settings for 20409B-LON-PROD1, in the left pane, click Network Adapter, in the Virtual Switch
drop-down list box, click External Network, and then click OK.
15. On LON-PROD1, in Windows PowerShell, run the following command:
ping 10.0.0.16
16. Confirm that this time the destination host is unreachable. The destination host is unreachable
because LON-PROD1 is connected on a different virtual switch than LON-TEST1.
17. On LON-PROD1, in Windows PowerShell in Administrator mode, run the following cmdlet:
Note: By running this cmdlet, you will configure LON-PRODx to obtain an IP address
automatically from a Dynamic Host Configuration Protocol (DHCP) server.
ipconfig /all
19. Verify that the output confirms that LON-PROD1 obtained the IP address from the DHCP server that
is running on LON-DC.
Creating and Configuring Virtual Machine Networks 4-5
ping 10.0.0.16
4. Confirm that four replies are returned, which confirms that LON-PROD1 and LON-TEST1 have
network connectivity.
5. On LON-HOST1, in Hyper-V Manager, right-click 20409B-LON-PROD1, and then click Settings.
6. In Settings for 20409B-LON-PROD1, in the left pane, click Network Adapter, and then in the right
pane, click Enable virtual LAN identification.
7. Verify that the VLAN ID is 2, and then click OK.
8. On LON-PROD1, in the Windows PowerShell window, run the following command:
ping 10.0.0.16
9. Confirm that the destination host is now not reachable, because LON-PROD1 is connected to a
different VLAN than LON-TEST1.
10. On LON-HOST1, in Hyper-V Manager, right-click 20409B-LON-TEST1, and then click Settings.
11. In Settings for 20409B-LON-TEST1, in the left pane, click Network Adapter, and then in the right
pane, click Enable virtual LAN identification. Verify that 2 is specified as VLAN ID, and then click
OK.
12. On LON-PROD1, in the Windows PowerShell window, run the following command:
ping 10.0.0.16
13. Confirm that four replies are returned. This confirms that LON-PROD1 and LON-TEST1 have network
connectivity, as now they are connected to the same VLAN.
4-6 Server Virtualization with Windows Server Hyper-V® and System Center
Lesson 2
Advanced Hyper-V Networking Features
Contents:
Questio n and Answers 7
Demonstration: Configuring Network Adapter Advanced Features 8
Creating and Configuring Virtual Machine Networks 4-7
Answer: You can use virtual switch extensions to process or inspect any network packet in the virtual
switch, and therefore, you must compile and install them on the Hyper-V host. You can use
Windows PowerShell to enable and manage virtual switch extensions, but not to develop new
extensions.
What Is SR-IOV?
Question: Can you configure a Hyper-V virtual switch to use SR-IOV after you have created it?
Answer: No, you can only configure SR-IOV when you create the virtual switch. You cannot add SR-IOV
to a virtual switch after you create it, and you cannot convert an external virtual switch that has
SR-IOV enabled to an internal or private virtual switch. If you want to add SR-IOV to an existing
external virtual switch, you must remove the existing switch, create a new switch, and make sure
that SR-IOV is enabled when you create the virtual switch.
Answer: No, there are no special hardware requirements to use NIC Teaming in virtual machines. You can
enable and use NIC Teaming in virtual machines, regardless of model, network speed, and
configuration of the network adapters, or the manufacturer. However, if you want to have
redundancy, a virtual machine should have at least two network adapters in an NIC team.
2. In the This PC window, in the navigation pane, expand This PC, expand Local Disk (C:), and then
click Windows.
3. In the details pane, right-click the Inf folder, and then click Copy.
4. In the Windows window, in navigation, click the down arrow, type \\10.0.0.16\share, and then press
ENTER.
5. In the share window, in the details pane, right-click, and then click Paste.
6. When a window showing the progress of the copy process displays, note the copy speed and how
long the process takes.
7. When the copy process completes, right-click the Inf folder, click Delete, and then in the Delete
Folder confirmation message box, click Yes.
8. On LON-HOST1, in Hyper-V Manager, right-click 20409B-LON-PROD1, and then click Settings.
9. In Settings for 20409B-LON-PROD1, in the left pane, click Network Adapter, and then in the details
pane, click Enable bandwidth management. In the Minimum bandwidth text box, type 10, in the
Maximum bandwidth text box, type 10, and then click OK.
10. On LON-PROD1, in the share window, right-click in the details pane, and then click Paste.
11. When the window showing the progress of the copy process displays, notice that the copy process
takes noticeably longer to complete.
12. On LON-PROD1, in Windows PowerShell, run the following cmdlet to configure LON-PROD1 to
obtain an IP address automatically from a DHCP server. Note that PowerShell should be started in
Administrator mode:
13. On LON-PROD1, in the Windows PowerShell window, run the following commands, pressing Enter at
the end of each line:
ipconfig /release
ipconfig /renew
14. Review the output to verify that you renewed TCP/IP settings on LON-PROD1, and that TCP/IP
settings were obtained successfully.
15. On LON-HOST1, in Hyper-V Manager, right-click 20409B-LON-DC1, and then click Settings.
16. In Settings for 20409B-LON-DC1, in the left pane, expand Network Adapter, click Advanced
Features, in the right pane, enable DHCP guard, and then click OK.
17. On LON-PROD1, in a Windows PowerShell window, run the following commands, pressing Enter at
the end of each line:
ipconfig /release
Creating and Configuring Virtual Machine Networks 4-9
ipconfig /renew
Note: This time the process will take considerably longer, and LON-PROD1 will not be able
to obtain TCP/IP settings. This is because when you enable DHCP guard on the virtual machine
on which the rogue DHCP server is running, you cannot retrieve TCP/IP settings from that virtual
machine.
4-10 Server Virtualization with Windows Server Hyper-V® and System Center
Lesson 3
Configuring and Using Hyper-V Network
Virtualization
Contents:
Questio n and Answers 11
Demonstration: Configuring Network Virtualizatio n 12
Creating and Configuring Virtual Machine Networks 4-11
Answer: Yes. The purpose of network virtualization is to enable communication between virtual machines
from different segments, while isolating their traffic from all other network traffic.
Answer: Yes. When you move virtual machines between Hyper-V hosts, you must modify network
virtualization appropriately. For a virtual machine that you move, the network seems exactly the
same. The virtual machine preserves its network settings, but Hyper-V hosts must be made aware
that the virtual machine is now running on a different Hyper-V host. You can update the network
virtualization configuration by using either Windows PowerShell or VMM.
Question: Does a virtual machine customer address change when you move the virtual machine between
Hyper-V hosts?
Answer: No. When you move a virtual machine, its customer address stays the same. The only thing that
changes is its provider address, which is the address of the Hyper-V host on which it is running.
However, you must update the network virtualization configuration on the Hyper-V hosts so that
they are aware of the move.
Answer: Network virtualization policies define on which Hyper-V host the virtual machines are running.
When the Hyper-V host needs to form a Network Virtualization Generic Routing
Encapsulation-encapsulated package and send it on a physical network, it consults network
virtualization policies.
4-12 Server Virtualization with Windows Server Hyper-V® and System Center
ping 10.0.0.16
ping 10.0.0.25
ping 10.0.0.26
3. Confirm that four replies are returned for each command, which confirms that LON-PROD1 has
connectivity with LON-TEST1, LON-PROD2 and LON-TEST2.
4. On LON-HOST1, on the taskbar, click the Windows PowerShell icon.
5. In Windows PowerShell, run following cmdlet:
6. Confirm that the VirtualSubnetId property has a value of 0, which means that virtual subnets are not
used.
7. On both LON-HOST1 and LON-HOST2, in Windows PowerShell, run following cmdlet:
Get-NetAdapter
8. For the physical network adapter, under the ifIndex column, write down the Index number.
9. On LON-HOST1, on the desktop, on the taskbar, click File Explorer.
10. In the File Explorer window, in the This PC navigation pane, expand Local Disk (C:), expand LabFiles,
and then click Mod04.
11. In the details pane, right-click ConfigureNW1.ps1, and then click Edit.
12. When the file ConfigureNW1.ps1 opens in Windows PowerShell ISE, review the PowerShell script to
see how network virtualization is configured, and review the variables, which are defined at the start.
13. In Windows PowerShell ISE, on the toolbar, click Run Script (you can also press the F5 key). When
prompted, type the index number of the LON-HOST1 network adapter and the index number of the
LON-HOST2 network adapter that you recorded in step 8.
14. On LON-HOST1, in Windows PowerShell ISE, in the console (lower pane), run the following cmdlet:
15. Confirm that the VirtualSubnetId property has value of 5001, which was configured by the Windows
PowerShell script.
16. On LON-PROD1, in Windows PowerShell, run the following three commands, pressing Enter at the
end of each line:
ping 10.0.0.16
ping 10.0.0.25
ping 10.0.0.26
17. Confirm that four replies are returned from IP 10.0.0.25 only.
Creating and Configuring Virtual Machine Networks 4-13
Note: LON-PROD1 has connectivity with LON-PROD2, but it does not have connectivity
with LON-TEST1 and LON-TEST2, as they are on a different virtual network (which is sharing the
same physical network).
4-14 Server Virtualization with Windows Server Hyper-V® and System Center
Answer: No, you cannot. You can connect a virtual machine only to Hyper-V virtual switches that are
created on the Hyper-V host on which that virtual machine is running.
Answer: You can add virtual network adapters to a parent partition in a similar way as in other virtual
machines, but you cannot do so by using Hyper-V Manager. You can only do this by using the
Windows PowerShell cmdlet Add-VMNetworkAdapter with the parameter ManagementOS.
Question: Is DHCP guard enabled by default? Where can you change this setting, and why would you use
it?
Answer: The DHCP guard option is disabled by default. You can change this option on the network
adapter on the Advanced Features settings page. You should enable DHCP guard on the network
adapters of the virtual machines, where a potentially rogue DHCP server could be installed. When
you enable DHCP guard, the DHCP server in the virtual machine on which this option is enabled
will not be able to lease TCP/IP settings on the network.
Question: Is there a better way to configure network virtualization other than using Windows PowerShell?
Answer: When you are limited to Windows Server 2012 R2, Windows PowerShell is the only tool that you
can use for configuring network virtualization. However, if you can use additional tools such as
VMM, it is considerably easier to configure network virtualization, because you can use a
graphical tool for this purpose.
Virtual Machine Movement and Hyper-V Replica 05-1
Module 5
Virtual Machine Movement and Hyper-V Replica
Contents:
Lesson 1: Providing High Availability and Redundancy for Virtualization 2
Lesson 2: Implementing Virtual Machine Movement 4
Lesson 3: Implementing and Managing Hyper-V Replica 8
Lesson 1
Providing High Availability and Redundancy for
Virtualization
Contents:
Questio n and Answers 3
Virtual Machine Movement and Hyper-V Replica 05-3
Answer: Even if the virtual machines will be part of the same NLB farm, you must configure each virtual
machine with a different IP address. When you install and configure the NLB feature, you add
virtual machines to an NLB farm, which uses an additional IP address called the virtual IP address.
The virtual IP address is the same for all servers in the NLB farm. The NLB farm and client requests
will use that virtual IP address.
Answer: No. AlwaysOn Availability Groups expand the functionality that is available in the failover
clustering feature considerably, but you still require the failover clustering feature to be able to
use AlwaysOn Availability Groups in SQL Server 2012.
05-4 Server Virtualization with Windows Server Hyper-V® and System Center
Lesson 2
Implementing Virtual Machine Movement
Contents:
Questio n and Answers 5
Demonstration: Moving Vir tual Machine Storage 5
Demonstration: Moving a Running Vir tual Machine 6
Virtual Machine Movement and Hyper-V Replica 05-5
Answer: Live migration is a newer and better way of moving virtual machines as compared to quick
migration. When you use quick migration, the virtual machine is unavailable for a short period of
time during the move operation. In addition, quick migration is available only between nodes in
the same failover cluster. When you use live migration, the virtual machine is available during the
entire move operation. You can also perform live migration between any two Hyper-V hosts,
regardless of whether they are in the same failover cluster.
Answer: No, you can use storage migration to move any virtual machine data files. Virtual hard disks are
usually the largest virtual machine data files, but you can also use storage migration to move
checkpoints, current configuration, and smart paging files.
Answer: No, you do not need to be local administrator. You only need to be a member of the Hyper-V
Administrators group to be able to use Move Wizard.
Question: Does live migration use compression when migrating virtual machines?
Answer: One of the new features in Hyper-V in Windows Server 2012 R2 is that live migration can use
compression, SMB Multichannel, and SMB direct while transferring virtual machines. If you enable
Live Migration in Windows Server 2012 R2, it uses compression by default.
3. In Hard Drive, confirm that it is using the LON-MOVE1.vhdx VHD that is stored locally, and then click
OK.
4. In Hyper-V Manager, right-click LON-MOVE1, and then click Move.
5. In the Move “LON-MOVE1” Wizard, on the Before You Begin page, click Next.
6. On the Choose Move Type page, select the Move the virtual machine’s storage option, and then
click Next.
7. On the Choose Options for Moving Storage page, select the Move only the virtual machine’s
virtual hard disk option, and then click Next.
05-6 Server Virtualization with Windows Server Hyper-V® and System Center
8. On the Select Items to Move page, confirm that disk LON-MOVE1.vhdx is selected, and then click
Next.
9. On the Choose a new location for attached virtual hard disk page, in the Folder text box, type
\\LON-HOST2\VHDs\LON-MOVE1, and then click Next.
10. On the Completing Move Wizard page, click Finish.
13. On LON-HOST1, in Hyper-V Manager, right-click LON-MOVE2, and then click Settings.
14. In Settings for LON-MOVE2, under IDE Controller 0, click Hard Drive. Confirm that the hard drive is
using the LON-MOVE2.vhdx VHD, and that the VHD is stored locally.
15. Click Checkpoint File Location. Confirm that checkpoints are stored locally, that you cannot change
the location, and then click OK.
16. In Windows PowerShell, move LON-MOVE2 storage by running following cmdlet:
17. Confirm that storage was moved successfully by running the following cmdlet:
ping –t 10.0.0.25
8. On the Choose Move Options page, confirm that the Move the virtual machine’s data to a single
location option is selected, and then click Next.
9. On the Choose a new location for virtual machine page, in the Folder text box, type
C:\Moved\LON-PROD1, and then click Next.
10. In the Move “LON-PROD1” Wizard, on the Completing Move Wizard, click Finish. This will start
moving the running virtual machine, and performing live migration. Point out to students that you
can monitor the progress of the live migration in Hyper-V Manager. Demonstrate that LON-PROD1 is
able to ping LON-PROD2 throughout the live migration.
11. After live migration completes, in Hyper-V Manager, confirm that LON-PROD1 is no longer running
on LON-HOST1. In the Virtual Machine Connection dialog box, click Exit.
12. In Hyper-V Manager, in the navigation pane, click LON-HOST2.
Lesson 3
Implementing and Managing Hyper-V Replica
Contents:
Questio n and Answers 9
Demonstration: Enabling Vir tual Machine Replica tion 10
Demonstration: Performing a Planned Hyper-V Failover 11
Virtual Machine Movement and Hyper-V Replica 05-9
Answer: If you assume that the hosting provider is not part of the same Active Directory Domain Services
(AD DS) forest, then the replica Hyper-V host can authenticate the primary Hyper-V host by using
a digital certificate.
Question: How can you limit primary Hyper-V hosts to be able to access only virtual machines that
originate from the same company?
Answer: When you are configuring a Hyper-V host as a replica, you can specify the trust group. If you do
so, the Hyper-V host will be able to access only virtual machines that originate from the same
trust group.
Answer: No. Failover TCP/IP settings are useful if a virtual machine has a static IP address, and if the
addresses used in the recovery site differ from the addresses used in primary site. If the virtual
machine is using Dynamic Host Configuration Protocol (DHCP) for obtaining TCP/IP
configuration, or if the virtual machine does not have integration services installed, failover
TCP/IP settings are not useful.
Answer: No, resynchronization is a special event, which is not necessary if Replication Health is normal.
However, resynchronization becomes necessary if replication is interrupted for an extended
period, if the replica is modified (for example, restored from a backup), or if replication is
reversed. While resynchronization can be memory-intensive and processor-intensive, it is more
effective that performing the entire initial replication again.
3. In LON-TEST1 Settings, in the navigation pane, confirm that the Management section displays six
settings, that Replication is not present, and then click OK.
4. In Hyper-V Manager, right-click 20409B- LON-TEST1, and then click Enable Replication.
5. In Enable Replication for LON-TEST1, on the Before You Begin page, click Next.
6. On the Specify Replica Server page, in the Replica server text box, type LON-HOST2, and then
click Next.
7. On the Specify Connection Parameters page, confirm that Use Kerberos authentication (HTTP) is
selected, that Compress the data that is transmitted over the network is enabled, and then click
Next.
8. On the Choose Replication VHDs page, confirm that LON-TEST1 VHD is selected, and then click
Next.
9. On the Configure Replication Frequency page, in the drop-down list box, click 30 seconds, and
then click Next.
10. On the Configure Additional Recovery Points page, click Next.
11. On the Choose initial Replication Method page, confirm that both the Send initial copy over the
network and the Start replication immediately options are selected, and then click Next.
12. In Enable Replication for LON-TEST1, on the Completing the Enable Replication Wizard page, click
Finish.
15. In Hyper-V Manager, right-click 20409B-LON-TEST1, click Replication, and then click View
Replication Health.
16. In Replication Health for “20409B-LON-TEST1”, review Replication Health. Initial replication may not
yet have completed, and Replication Health is in the Warning state.
17. In Replication Health for “20409B-LON-TEST1”, click Close.
18. In Hyper-V Manager, right-click 20409B-LON-TEST1, and then click Settings.
19. In 20409B-LON-TEST1 Settings, in the navigation pane on the left, expand Network Adapter, and
confirm that two new nodes Failover TCP/IP and Test Failover, which were not present before, now
display.
Virtual Machine Movement and Hyper-V Replica 05-11
20. In 20409B-LON-TEST1 Settings, in the navigation pane, confirm that there are seven settings in the
Management section, including Replication, which was not present before. Click OK.
21. In Windows PowerShell, review replication settings and status by running the following cmdlets, and
pressing Enter at the end of each line:
22. In Hyper-V Manager, right-click 20409B-LON-TEST1, click Replication, and then click View
Replication Health.
23. In Replication Health for “20409B-LON-TEST1”, review Replication Health. Once initial replication
finishes, Replication Health will be set to Normal.
24. In Replication Health for “20409B-LON-TEST1”, click Close.
9. In Planned Failover, confirm that Start the replica virtual machine after failover is selected, and
then click Fail Over.
10. In Hyper-V Manager, in the navigation pane, click LON-HOST2. Confirm that 20409B-LON-TEST1 is
in the Running state.
11. Double-click 20409B-LON-TEST1.
12. Sign in as Administrator with the password Pa$$w0rd.
13. On LON-TEST1, confirm that a folder named Current State displays on the desktop. With planned
failover, all changes from the primary virtual machine are replicated.
14. Right-click the desktop, click New, click Folder, and then name the folder Planned Failover.
15. In Hyper-V Manager, right-click 20409B-LON-TEST1, click Replication, and then click Reverse
Replication.
16. In the Reverse Replication Wizard for 20409B-LON-TEST1, click Next five times, and then click Finish.
17. On LON-TEST1, press the Windows key+X, click Shut down or sign out, and then click Shut down
again.
05-12 Server Virtualization with Windows Server Hyper-V® and System Center
18. In Hyper-V Manager, verify that 20409B-LON-TEST1 is in the Off state. Right-click 20409B-LON-
TEST1, click Replication, and then click Planned Failover.
19. In Planned Failover, confirm that Start the replica virtual machine after failover is selected, and
then click Fail Over.
20. In Hyper-V Manager, in the navigation pane, click 20409B-LON-HOST1. Confirm that the 20409B-
LON-TEST1 state is Running.
21. In Hyper-V Manager, double-click 20409B-LON-TEST1. Notice that the Virtual Machine Connection
to 20409B-LON-TEST1 opens.
Question: Can you use self-signed certificates for authentication with Hyper-V Replica?
Answer: No, If you want to use certificates for authentication with Hyper-V Replica, a certification
authority (CA) must sign the certificate; it cannot be self-signed.
Question: Can you perform live migration of a virtual machine from a Windows Server 2012 Hyper-V host
to a Windows Server 2012 R2 Hyper-V host?
Answer: Yes, you can perform cross-version live migration of a virtual machine from Windows Server
2012 to Windows Server 2012 R2. However, such a cross-version live migration is possible only in
one direction. You cannot move a virtual machine from Windows Server 2012 R2 to Windows
Server 2012.
05-14 Server Virtualization with Windows Server Hyper-V® and System Center
Answer: Even when you move virtual machine storage by using Windows PowerShell, you can use a
graphical tool such as Hyper-V Manager to monitor the migration progress.
Question: Is Windows Server 2012 R2 Hyper-V host configured by default to allow incoming live
migration?
Answer: No, Windows Server 2012 R2 Hyper-V host by default does not allow incoming live migration.
You need to enable live migration if you want to migrate virtual machines to a Windows Server
2012 R2 Hyper-V host. You also have to configure from where virtual machines can be live
migrated, the authentication method, and how many live migrations can run concurrently.
Question: Do you need to configure constrained delegation if you want to use live migration?
Answer: If you are administering a Hyper-V host locally, then constrained delegation is not required.
However, if you want to use remote administration, (for example, to move a virtual machine by
using Windows PowerShell on your administrative workstation, or to use Hyper-V Manager to
move a virtual machine from the remote Hyper-V host), you need to configure delegation for the
Hyper-V host that will be acting on your behalf. Therefore, you need to configure delegation for
the Hyper-V host from which the virtual machine will be moved.
Question: When using Hyper-V Replica, what is the difference between test failover and planned failover?
Answer: Test failover does not affect virtual machine availability, and you can perform it regardless of the
state of the primary virtual machine. You can perform planned failover only if the primary virtual
machine is turned off, which causes some virtual machine downtime. In both cases, Failover
TCP/IP configuration is used for replica virtual machine.
Implementing Failover Clustering with Hyper-V 6-1
Module 6
Implementing Failover Clustering with Hyper-V
Contents:
Lesson 1: Overview of Failover Clustering 2
Lesson 2: Configuring and Using Shared Storage 5
Lesson 3: Implementing and Managing Failover Clustering with Hyper-V 9
Lesson 1
Overview of Failover Clustering
Contents:
Questio n and Answers 3
Implementing Failover Clustering with Hyper-V 6-3
Answer: No, not necessarily. After the failover process moves the cluster role to a different cluster node,
the cluster role may stay on that node and not fail back, even when the failed node is back
online. This depends on the configuration settings. Furthermore, the administrator may decide to
trigger failback manually or not at all.
What Is CSV?
Question: Can you format a CSV by using a CSV file system?
Answer: Although CSVs on Windows Server 2012 and Windows Server 2012 R2 display as though they
are formatted with the CSV file system, they are actually formatted with NTFS file server. The CSV
file system is used to make the application aware that it is running in a failover cluster and is
stored on a CSV, but the CSV file system is not the actual file system.
What Is a Quorum?
Question: Can a failover cluster that originally had six nodes still run cluster roles if three nodes fail and
only three nodes remain online?
Answer: It depends. Based on the quorum model used, and whether all three nodes failed simultaneously
or whether there was some time between each failure, the remaining three nodes might still run
cluster roles. The nodes must have enough resources and use the dynamic quorum model, which
is the default.
Answer: If the domain has at least one domain controller running Windows Server 2012 or a newer
operating system, you can create and use an encrypted cluster volume. If the domain functional
level is Windows Server 2008 R2, this means that domain controllers are running Windows Server
2008 R2 and newer operating systems.
Implementing Failover Clustering with Hyper-V 6-5
Lesson 2
Configuring and Using Shared Storage
Contents:
Questio n and Answers 6
Demonstration: Using an iSCSI Target Server 7
6-6 Server Virtualization with Windows Server Hyper-V® and System Center
Answer: If the virtual machine is not running, and if you will not run it from the shared network folder,
then you can store it on any shared network folder. However, if you plan to run it from the
shared network folder, you should store it on a shared folder on Windows Server 2012 or newer.
Hyper-V will not present you with a warning, but you should remember that running virtual
machine from non-SMB 3.0 file shares is not supported.
What Is iSCSI?
Question: What must you enable and configure in Windows Server 2012 R2 to be able to use storage on
an iSCSI SAN?
Answer: To be able to use storage on an iSCSI Storage Area Network (SAN), you need an iSCSI initiator.
An iSCSI initiator is part of every Windows Server and Windows client operating system and it is
installed by default, so you do not need to install anything in Windows Server 2012 R2. However,
you must first enable and configure the iSCSI initiator properly.
2. In the iSCSI VIRTUAL DISKS section, click TASKS, and then click New iSCSI Virtual Disk.
3. In the New iSCSI Virtual Disk Wizard, on the Select iSCSI virtual disk location page, click E:\, and
then click Next.
4. On the Specify iSCSI virtual disk name page, in the Name text box, type Disk11, and then click
Next.
5. On the Specify iSCSI virtual disk size page, in the Size text box, type 15, click Dynamically
expanding, and then click Next.
6. On the Assign iSCSI target page, click New iSCSI target, and then click Next.
7. On the Specify target name page, in the Name text box, type Lab6-Host1, and then click Next.
8. On the Specify access servers page, click Add. On Select a method to identify the initiator, click
Browse, in the Browse text box, type LON-HOST1, and then click OK twice.
9. On the Specify access servers page, click Add. On Select a method to identify the initiator, click
Browse, in the Browse text box, type LON-HOST2, click OK twice, and then click Next.
10. On the Enable Authentication page, click Next.
11. On the Confirm selections page, click Create.
15. In Server Manager, on the toolbar, click the Refresh icon. Confirm that virtual disk Disk12.vhdx
displays and it is mapped to the Lab6-Host1 target.
16. In Server Manager, click Tools, and then click iSCSI Initiator. In the Microsoft iSCSI dialog box, click
Yes.
17. In the iSCSI Initiator Properties dialog box, in the Target text box, type LON-SS1, and then click
Quick Connect. Disconnect any preconfigured targets.
Note: If Quick Connect fails, select iSCSI target with Lab6-Host1 in the name in the iSCSI
Initiator Properties dialog box, click Connect, disconnect other iSCSI target and then click OK.
18. In Quick Connect, click the Discovered target with Lab6-Host1 in the name, click Connect, click
Done, and then click OK.
19. In Server Manager, on the Tools menu, click Computer Management.
6-8 Server Virtualization with Windows Server Hyper-V® and System Center
20. In Computer Management, in the navigation pane, click Disk Management. In the details pane,
confirm that two disks are added, that they have the size of 15 GB, and that they are Offline.
21. Point out to students that these are the virtual disks that you just added on the iSCSI target.
Implementing Failover Clustering with Hyper-V 6-9
Lesson 3
Implementing and Managing Failover Clustering with
Hyper-V
Contents:
Questio n and Answers 10
Demonstration: Creating a Failover Cluster 11
Demonstration: Creating and Managing the Virtual Machine Clustered Role 12
6-10 Server Virtualization with Windows Server Hyper-V® and System Center
Answer: If any of the preferred owners is online and has available resources, the virtual machine will fail
over to one of those nodes. If no node from the preferred owners list is available, then the virtual
machine will fail over to one of the nodes on the possible owners list. If no node from either
owners list is available, then the virtual machine will fail over to any other node, but it will not
start on that node.
Question: How should you configure a service in a highly available virtual machine by using Service
Control Manager, if you plan to monitor it by failover cluster?
Answer: If you plan to monitor a service in a virtual machine, you should configure in Service Control
Manager one of the recovery options for this service as Take no action.
Answer: It depends on the cluster roles. If you can move a cluster role (such as a highly available virtual
machine or a scale-out file server) between nodes without downtime, then there is no downtime
when CAU is performing the update. If moving a role causes some interruption in client
connectivity, then there will be minimal downtime when CAU performs the update.
6. In the Validate a Configuration Wizard, on the Before You Begin page, click Next.
7. On the Testing Options page, click Next.
8. On the Confirmation page, click Next.
9. While you wait until all validation tests are performed, notice the many notifications that display
about the problems with the drives.
10. View the validation report, and then click Finish.
11. On the Access Point for Administering the Cluster page, in the Cluster Name text box, type LON-
CLUST, in the Address text box, type 172.16.10.105, and then click Next.
12. On the Confirmation page, click Next.
13. On the Summary page, view the report, and then click Finish.
14. In Server Manager, on the Tools menu, click Active Directory Users and Computers.
15. In Active Directory Users and Computers, expand Adatum.com, in the navigation pane, click the
Computers container, and confirm that it contains computer accounts for LON-HOST1, LON-
HOST2, and LON-CLUST (which was added when you created the failover cluster).
16. Close Active Directory Users and Computers.
17. On LON-HOST1, open File Explorer, click drive C, and in the details pane, confirm that a folder named
ClusterStorage displays.
18. Double-click the ClusterStorage folder, and confirm that the folder is empty.
19. In the Failover Cluster Manager, in the navigation pane, expand LON-CLUST.Adatum.com, expand
Storage, and then click Disks.
20. In the details pane, right-click Cluster Disk 2, and then click Add to Cluster Shared Volumes.
21. In File Explorer, confirm that the ClusterStorage folder contains a mounted volume for Volume1,
which was added when you added the disk to the cluster shared volume.
6-12 Server Virtualization with Windows Server Hyper-V® and System Center
3. In the New Virtual Machine Wizard, on the Before You Begin page, click Next.
4. On the Specify Name and Location page, specify the following values and then click Next:
o Name: LON-HA1
o Location: C:\ClusterStorage\Volume1\
5. On the Specify Generation page, confirm that Generation 1 is selected, and then click Next.
6. On the Assign Memory page, select the Use Dynamic Memory for this virtual machine check box,
and then click Next four times.
7. On the Competing the Virtual Machine Wizard page, click Finish.
8. Verify that the virtual machine named LON-HA1 is created.
17. Click the Advanced Policies tab, confirm that both LON-HOST1 and LON-HOST2 are selected as
Possible Owners, and then click OK.
18. On LON-HOST1, open Windows PowerShell.
19. In Windows PowerShell, add the virtual machine cluster role by running the following cmdlet:
20. On LON-HOST1, in the Failover Cluster Manager, select 20409B-LON-PROD1 as the cluster Role. In
the LON-PROD1 pane, click the Summary tab, and confirm that no Monitored Services are listed.
21. In the details pane, right-click 20409B-LON-PROD1, click More Actions, and then click Configure
Monitoring.
Implementing Failover Clustering with Hyper-V 6-13
22. In Select Services, click Print Spooler, and then click OK.
23. In the LON-PROD1 pane, confirm that Print Spooler is listed under Monitored Services.
6-14 Server Virtualization with Windows Server Hyper-V® and System Center
Question: How can you configure anti-affinity for virtual machines that are running in a failover cluster?
Answer: You cannot configure anti-affinity for clustered roles in failover clustering or any graphical tool
that is part of Windows Server 2012 R2. You can configure anti-affinity by using Windows
PowerShell, or by using VMM.
Implementing Failover Clustering with Hyper-V 6-15
Answer: When creating failover clustering, virtual machines can use iSCSI SAN, Fibre Channel SAN, or
shared virtual hard disks as shared storage.
Question: Where must you store a virtual hard disk if you want to use it as a shared storage for virtual
machines?
Answer: A virtual hard disk must be stored on a failover cluster, either on a CSV, or a on a highly available
file share on a scale-out file server.
Installing and Configuring Microsoft System Center 2012 R2 Virtual Machine Manager 7-1
Module 7
Installing and Configuring Microsoft System Center 2012 R2
Virtual Machine Manager
Contents:
Lesson 3: Installing VMM 2
Lesson 4: Adding Hosts and Managing Host Groups 7
Lesson 3
Installing VMM
Contents:
Demonstration: Installing the VMM Management Server and VMM Console 3
Installing and Configuring Microsoft System Center 2012 R2 Virtual Machine Manager 7-3
4. In the Properties for LON-VMM1 details pane, ensure that LON-VMM1 is in the Adatum.com
domain. Verify that the Operating system version, which is several lines below, is at least the
Standard or Data Center version of Windows Server 2012 R2. Scroll to the right, and confirm that the
operating system has at least a 2-gigahertz (GHz) Pentium processor, 4 gigabytes (GB) of random
access memory (RAM), and 80 GB of disk space available.
5. Close Server Manager.
8. In the Apps by name start screen, scroll to the right, and click the SQL Server Management Studio
tile.
9. In the Microsoft SQL Server Management Studio (Administrator) console, in the Connect to Server
dialog box, click the Connect button.
10. In the Object Explorer console, on the left side, note the top tree element that is labeled LON-VMM1
(SQL Server 11.0.3000 – ADATUM\administrator). This version number, 11.0.3000, corresponds to
SQL Server 2012 SP1. Confirm with the class that this version is supported by System Center 2012 R2
VMM.
11. Click the File drop-down list box, and then click Exit.
12. Ask the class if there are any other system requirements necessary for the VMM management server
installation. Answers should include: Windows PowerShell 3.0, Microsoft .Net Framework 4.5,
Windows Remote Management, and the Windows Assessment and Deployment Kit (ADK) for
Windows Server 2012 R2.
13. On the taskbar, click the Windows PowerShell icon.
14. In Windows PowerShell, type the following command, and then press Enter:
regedit.exe
15. In the Registry Editor window, click the HKEY_LOCAL_MACHINE subkey. Expand SOFTWARE,
expand Microsoft, expand Net Framework Setup, expand NDP, expand v4, and then click Client.
16. In the Version item, note the value in the Data column, which should be 4.5.51641 or higher.
services.msc
19. In the Services console, scroll down the Name column until you find Windows Remote
Management (WS–Management).You might have to expand the size of the name column to see
the object name. Verify that the service has a status of Running, and that the Startup Type is set to
Automatic.
7-4 Server Virtualization with Windows Server Hyper-V® and System Center
20. Close the Services console, and then close Windows PowerShell.
21. On the taskbar, click the File Explorer icon.
22. In File Explorer, in the This PC window, double-click the DVD Drive icon.
23. In the VMM folder, double-click the setup.exe file.
24. When the Microsoft System Center 2012 R2 Installation startup screen displays, note that all of the
hyperlinks on the page, except for Install and Local Agent, link to Microsoft websites.
25. Click the Install hyperlink.
26. In the Microsoft System Center 2012 Virtual Machine Setup Wizard, on the Getting started page,
double click Add Features, under the Select features to Add section, If this is the first installation of
a VMM product, there will be two selection boxes: one for the VMM management server, and the
other for the VMM console. In the course configuration, on LON-VMM1, the VMM console has
already been installed and therefore not available on this page. You will demonstrate how to install
both; the VMM management server on LON-VMM1, and the VMM console on LON-CL1. When you
install the VMM management server, it also installs the VMM console automatically. Select the VMM
management server check box, and then click Next.
27. On the Product registration information page, in the Name text box, type Administrator. In the
Organization text box, type A.Datum Corp Leave the Product key: text box blank, and then click
Next.
28. You can install VMM as an evaluation edition by leaving the Product Key text box blank. You can
also provide the product key after installation. After pointing this out to students, click Next.
29. On the Please read this license agreement page, review the license agreement, and then select the
I have read, understood, and agree with the terms of the license agreement check box.
Alternatively, you can use the Print button to print and save the license agreement for later viewing.
If the configuration does not meet these conditions, do not put a port number in the text box. For
this demonstration, you will leave the box empty.
In the Instance name: drop-down list box, click MSSQLSERVER. In the Select an existing database
or create a new database area, accept the default new database name of VirtualManagerDB. Point
out to students that you can also select other databases in the Existing database area. For the
purpose of this demonstration, use the default new database, and then click Next.
33. On the Configure service account and distributed key management page, add the Virtual
Machine Manager Service Account credentials. Emphasize to the class that administrators cannot
change the service account after they install VMM. If necessary, you can remove VMM from the
Installing and Configuring Microsoft System Center 2012 R2 Virtual Machine Manager 7-5
server, make the necessary change, and then reinstall it. However, you also could, as part of the
removal procedures, retain the VMM database and then use it again after you reinstall VMM. Explain
that this would be a potentially laborious and complex action. Explain also that if you are installing a
highly available VMM management server, you must use a domain account. This domain account
needs to have local administrator access on all host and management servers in the domain. For the
purpose of this demonstration, use the SCService account, which is a member of the Domain Admins
group. Point out to students that the Domain account option is preselected.
34. In the User name and domain text box, type ADATUM\SCService, and in the Password: text box,
type Pa$$w0rd.
35. Point out that under the Distributed Key Management section you can to store encryption keys for
VMM in AD DS instead of on the local machine. For highly available VMM installations, you must do
this. However, for the purpose of this demonstration, you will not do so. Therefore, on the Configure
service account and distributed key management page, click Next.
36. On the Port configuration page, point out the default port numbers that are assigned to various
entities and functions. Do not make any changes, but ask under what circumstances students might
make changes. Answers might include the port number already in use by another process, or the
desire to change default port assignments to a different number for enhanced security. After
reviewing this information, click Next.
37. On the Library configuration page, explain that here you can either create a new library share, or if
one already exists, select it. (In this demonstration, you will create a new library share.)
38. Click Create a new library share, and then click Next.
39. On the Installation summary page, review with the students the text that displays, and then click
Install. The installation features will now run for up to five minutes.
40. On the Set up completed successfully page, click the Close button.
41. On the Microsoft System Center 2012 R2 Installation splash screen, click the Close button.
42. If Windows Internet Explorer opens, close it.
47. In the Apps by name screen, scroll to the right, right-click the Virtual Machine Manager Console item,
and in the bar at the bottom of the Apps by name screen, click Pin to taskbar.
48. Click any empty area of the Apps by name screen, and when a white circle with a white up arrow
in it displays, click the arrow.
49. On the Start screen, click the Desktop tile.
50. On the desktop, on the taskbar, click the Virtual Machine Manager Console icon.
51. On the desktop, on the taskbar, right-click the VMM Console Icon and then click Pin this program
to the taskbar.
52. Verify that on the Connect to Server page, in the Server name text box, the setting displays
localhost: 8100. Also, point out the options for specifying credentials. The default selection, Use
7-6 Server Virtualization with Windows Server Hyper-V® and System Center
current Microsoft Windows session identity, is sufficient because you are signed on as the domain
administrator. Click the Connect button.
53. After a moment, the Virtual Machine Manager console will load. If time permits, review some of the
console areas, but remember that there will be a demonstration about using the console next.
54. Close the VMM Console and sign out of LON-VMM1.
Installing and Configuring Microsoft System Center 2012 R2 Virtual Machine Manager 7-7
Lesson 4
Adding Hosts and Managing Host Groups
Contents:
Demonstration: Using the VMM Console 8
Demonstration: Adding a Hyper-V Virtualiza tion Host to VMM 9
Demonstration: Managing Host Groups 13
7-8 Server Virtualization with Windows Server Hyper-V® and System Center
3. On the Connect to Server page, Explain the parameters. The Server name text box displays
Localhost:8100, which is the server you are currently signed on to. However, if you had installed the
VMM console on another computer, you would need to type that computer’s name here. As a best
practice, use the Fully Qualified Domain Name (FQDN) of a computer rather than its single host
name. Using the FQDN means the server can normally be found on any routable network, if the
firewalls allow the 8100 port through. 8100 is the default VMM port, and reflects the port number
assigned during the VMM management server installation. If you used a different port number during
installation, you would need to change it here.
4. On the bottom of the Connect to Server page is Credentials, which has two options: Use current
Microsoft Windows session identity, and Specify credentials. By default, the Use current
Microsoft Windows session identity option is selected. However, if you want to sign in using
alternate credentials, you can select the second option, and then supply the user domain and name in
the User name text box, and the corresponding password in the Password text box. This can be
useful when an administrator is testing user roles and permissions.
5. The very last item at the bottom of the page is the Automatically connect with these settings
check box. Without making any changes, click Connect.
If this check box is selected already, then you will not be asked for a server name and port, nor a user
name and password. If this information changes, you will be returned to the Connect to Server page
to correct the selections.
6. When the Virtual Machine Manager console opens, mention that the Virtual Machine Manager
console always opens to the last node that it was in when you last closed the console. Point out the
main areas of the consoles: workspace console tree, details pane, ribbon, library workspace.
7. Click the Workspace console tree, and point out the five main workspaces: VMs and Services,
Fabric, Library, Jobs, and Settings. Select each of the five workspaces and show how the console
tree changes. Do not expand any items in the tree yet.
8. Click in the details pane. Show students that different details panes display in the middle and right
depending on the workspace selected and the item selected in that workspace’s console tree.
Mention that sometimes two details panes display, one on top of the other.
9. Point to the ribbon at the top of the console. Point out that all System Center 2012 components have
a ribbon at the top of their respective consoles. Explain that the Virtual Machine Manager console
ribbon has different items, icons, buttons, and tabs on it depending on the workspace selected and
the item selected in that workspace’s console tree.
10. In the lower left, click the Library workspace. In the Library console tree (area on the left directly
above Workspaces), click Templates.
11. On the ribbon, on the Home tab, click Create Service Template.
12. In the New Service Template window, explain that you use this window to create a new service
template. You can start from several different patterns, depending on what you select in the Patterns
area.
13. In the New Service Template window, click the View Script button. Point out to the class that this
opens Notepad in which Windows PowerShell cmdlets display, and that you can use these cmdlets to
create the same item that the user interface can create. Explain that you can also save these cmdlets
Installing and Configuring Microsoft System Center 2012 R2 Virtual Machine Manager 7-9
as a Windows PowerShell script, so that you can alter and run them later, document your
configuration, or learn how to write Windows PowerShell scripts. Point out that most of the Create
items within the Virtual Machine Manager console will have a View Script button located within
them. Explain that some of the more advanced VMM wizards will have several pages, and that you
will often find the View Script button on the last page.
17. Close the Virtual Machine Manager console, and sign off LON-VMM1.
6. In the Windows Firewall: Allow inbound file and printer sharing exception dialog box, click
Enabled, in the Options text box, type an asterisk (*), and then click OK.
7. In the Domain Profile details pane, double-click Windows Firewall: Allow ICMP exceptions.
8. In the Windows Firewall: Allow ICMP exceptions dialog box, click the Enabled option, in the
Options area, select the Allow inbound echo request check box, and then click OK.
9. In the Domain Profile details pane, double-click Windows Firewall: Define inbound port
exceptions.
10. In the Windows Firewall: Define inbound port exceptions dialog box, click Enabled, in the
Options area, next to Define port exceptions, click Show.
11. In the Show Contents dialog box, under Value, type 5985, and then click OK twice. This allows the
Windows Remote Management service to communicate to the firewall.
12. In the Group Policy Management Editor console tree, under Administrative Templates, expand
Windows Components, expand Windows Remote Management (WinRM), and then click WinRM
Service.
13. In the WinRM Service details pane, double-click the Allow remote server management through
WinRM setting.
7-10 Server Virtualization with Windows Server Hyper-V® and System Center
14. In the Allow remote server management through WinRM dialog box, click the Enabled radio
button. In the Options area, in both the IPv4 and IPv6 text boxes, type an asterisk (*), and then click
OK.
15. Close the Group Policy Management Editor, and then close the Group Policy Management Console.
16. On LON-HOST1, on the taskbar, click the Windows PowerShell icon.
17. In the Administrator: Windows PowerShell window, type gpupdate /force, and then press Enter.
18. When both computer and user polices are updated successfully, close the Windows PowerShell
window.
25. Right-click All Hosts, and then click Add Hyper-V Hosts and Clusters.
26. In the Add Resource Wizard, on the Resource Location page, click the Windows Server computers
in a trusted Active Directory domain option (it should be the default selection). Describe for the
students the other options that are available. Note that as previously mentioned, some of the other
selections might require additional prerequisites. Also, review the Windows Server computers in a
perimeter network option, reviewing the steps from the Considerations for Adding Hyper-V
Virtualization Resources topic page. Because there is no perimeter network, you cannot demonstrate
these steps. Click Next.
27. On the Credentials page, review the two options. By default, the Use an existing Run As account
option is selected. You also have the option to select the Run As account and a Browse button to
find the account. Note that the Run As account must have local administrator permissions on the
host machine that is being assigned. In this demonstration, you will not use a Run As account. Select
the Manually enter the credentials check box, in the User name text box, type
ADATUM\Administrator, in the Password text box, type Pa$$w0rd, and then click Next.
28. On the Discovery Scope page, note the two options: Specify Windows Server computers by
names, and Specify and Active Directory query to search for Windows Server computers. Select
the Specify Windows Server computers by names option, in the Computer names text box, type
lon-host1.adatum.com, and then click Next.
29. On the Target resources page, in the Discovered computers section, select the lon-
host1.adatum.com check box, and then click Next.
30. When a Virtual Machine Manager pop-up window displays, warning you that if Hyper-V is not
enabled on the selected server VMM will do so, click OK.
31. On the Host Settings page, note that on the Host group drop-down menu, there is only one option,
All Hosts. Note the Reassociate this host with this VMM environment check box. This check box
selection reassigns hosts that have been assigned to a different VMM management server, to this one.
For this demonstration, you do not need to select this feature. Below this check box is a field to add
virtual machine placement paths as default locations to store virtual machines on the host. After
reviewing this page, click Next.
32. On the Summary page, on the upper left part of the page, click View Script.
Installing and Configuring Microsoft System Center 2012 R2 Virtual Machine Manager 7-11
33. When Notepad opens, point out the Windows PowerShell cmdlets necessary to run a script in
Windows PowerShell to add the Lon-host1 host to this VMM management server. Explain to the
students how useful this can be to document your work or to create another host, perhaps at a later
time.
34. In the Notepad window, on the File menu, click Save As. In the Save As window, under This PC, click
Documents. In the File name text box, type AddHost.ps1, in the Save as type drop-down list box,
click All Files (*.*), and then click Save. Explain to the students that you will use this script to add
LON-HOST2 as another host later.
40. To add LON-HOST2 as a physical host, you will use Windows PowerShell instead of using the Virtual
Machine Manager console. On the taskbar, click the Windows PowerShell icon.
41. In the Administrator: Windows PowerShell window, type the following commands, pressing Enter at
the end of each line:
cd documents
notepad AddHost.ps1
42. In the Notepad window, in the Format drop-down list box, click Word Wrap. Examine the Windows
PowerShell script with the class, going over all the different cmdlets and text. Note the two variables
that are created, and the cmdlets on which they are based. Note the Add-SCVMHost cmdlet and the
various parameters that it calls. Briefly explain what the cmdlet does. Ask the students if there is
anything on this line that needs to be changed. The answer should be just the -ComputerName
parameter, which should identify lon-host2 rather than lon-host1. Make this change, and then on
the File menu, click Save.
./addhost.ps1
45. In the Windows PowerShell credentials required pop-up window, in the User name text box, type
ADATUM\administrator and in the Password text box, type Pa$$w0rd, and then click OK.
46. It may take a few moments, but wait for Windows PowerShell to display a number of parameters and
values in columnar form.
47. In the Windows PowerShell window, type exit, and then press Enter.
7-12 Server Virtualization with Windows Server Hyper-V® and System Center
48. In the Virtual Machine Manager console, in the VMs and Services console tree, under All Hosts, click
Lon-host2. Note the virtual machines assigned to this host and that the Windows PowerShell script
has worked. Ask the students which was faster: using the Virtual Machine Manager console to enable
a host, or using the Windows PowerShell script. Most students will answer that the Windows
PowerShell script was faster. Remind them that the Virtual Machine Manager console is built on
Windows PowerShell, and therefore actions you take in the Virtual Machine Manager console are run
in Windows PowerShell at the lower level.
49. With LON-HOST2 still selected, on the ribbon, click the Folder tab, and then click Properties.
50. In the Properties dialog box, review the content of the following tabs :
a. General. This tab provides extensive information. It even gives the system management BIOS
(SMBIOS) ID and the VMM agent version.
b. Status. On this tab, you can view all jobs on this host that have run. If any jobs have failed, you
can select them and then click Repair All. When any failed jobs or jobs that have completed with
info are selected, information displays in the Error details pane. You use the Copy Errors button
to copy and paste the error details into another program.
c. Hardware. Most of the settings that display on the Hardware tab are for information only, and
cannot be changed. However, there are a few settings on this tab that you can change. Point out
to the class that in the CPU section, there is a NUMA modes check box that you can use to allow
virtual machines to span non-uniform memory access (NUMA) nodes. In the Network adapters
section, you can select the adapters, logical networks, and switches (if they exist), and make
changes to them. In the Advanced section, under the Baseboard Management Controller
(BMC) Settings area, you can also make other changes. Show this as well.
d. Host Access. On the Host Access tab, you can supply different host management credentials
such as Run As accounts. You can also specify whether the host is available for placement, and
set the remote connection port.
e. Virtual Machine Paths. On this tab, you can view detailed information about every virtual
machine on the host. You can also register additional virtual machine paths. Note that for this
demonstration, you may want to switch to the properties of LON-HOST1 to demonstrate this tab,
as there are no virtual machines currently assigned to LON-HOST2.
f. Reserves. If you do not want to use the host reserves settings from the parent host group, you
can use a check box to turn off inheritance, and change the resources reserved for this host.
When you select this check box, several configurable items display that you can use to set the
reserved resources. Show this to the class, but make no changes.
g. Storage. You use this tab to make extensive changes to various storage elements, including disks,
Internet SCSI (iSCSI), Fibre Channel, Serial Attached SCSI (SAS) arrays, and file shares. While you
also can add and remove storage elements, the various disks and arrays must already be
available.
h. Virtual Switches. Similar to the Storage tab, you can make many changes on the Virtual
Switches tab, including creating new logical and standard switches. Review the parameters with
the class but make no changes.
i. Migration settings. You can configure a number of migration settings on this tab, including live
storage migration, live migration settings, performance options, and authentication protocols for
use when migrating.
j. Placement paths. On this tab, you can specify both of the default virtual machine paths. The
default parent disk paths use running virtual machine placement.
k. Servicing Windows. You use this tab to add or remove Servicing Windows, if they exist.
Installing and Configuring Microsoft System Center 2012 R2 Virtual Machine Manager 7-13
l. Custom Properties. You use this tab to assign and manage custom properties. Click the Manage
Custom Properties button to show the students the various object types that they can select.
Explain also that by clicking the Create button, they can create custom properties.
51. Click Cancel.
52. Finally, point out the View Script button. Explain that by clicking this button, you can create a
Windows PowerShell script with cmdlets that will make the same changes that you can make with the
Properties dialog box. You can save the Windows PowerShell script, and later alter or rerun it, or
simply keep it for documentation.
53. Close the Properties dialog box, close all open windows, and then sign off of LON-VMM1.
8. In the VM’s and Services console tree, right-click lon-host2, and then click Move to Host Group.
9. In the Move Host Group pop-up dialog box, in the Parent host group drop-down list box, click
LocalGroup, and then click OK.
requirements. Click the Requirement drop-down list box, and show the different requirements
that are available. In the Create Custom Requirements pop-up dialog box, click Cancel.
e. On the Placement Rules page, select the Use the placement settings from the parent host
group check box.
f. In the console tree, click Host Reserves. Here you can set aside resources for a host operating
system. This means if a virtual machine needs the same resources that the host needs, the virtual
machine placement on this host will give an error. Select the Use the host reserves settings
from the parent host group check box, and demonstrate the changes that you can make in the
various items (CPU, Memory, Disk I/O, Disk space, and Network I/O). Keep the check box
selected, but do not retain any changes.
g. In the console tree, click Dynamic Optimization. Explain that you can use this page to balance
the virtual machine load automatically within a host cluster. You can set the responsiveness to the
changes before the virtual machine performs migration. Point out the Aggressiveness section,
which you can use to set high, medium, and low values, on a sliding scale. You can also set the
migration of virtual machines to balance the load at a frequency level measured in minutes. The
Thresholds area is similar to the Host Reserves section, which is also selectable.
h. Click the Power optimization Settings button. By default, power optimization runs at all times.
You can use the graphical hour/day of the week configuration pane to configure when power
optimization is used.
i. Click Cancel.
j. In the console tree, click Network. Here, you can select the following different resource types: IP
pools, Load balancers, Logical networks, and MAC pools. By default, you inherit network
logical resources from the parent host groups. If you clear the check box that provides this
inheritance, you can reset these resource types.
k. In the console tree, click Storage. By default, storage capacity of a host group includes storage
allocated to parent host groups. The top section shows both the local and remote storage
capacity for the hosts that make up this host group. Below this area is the Allocated storage for
this host group section, which has two buttons: Allocate Storage Pools, and Allocate Logical
Units.
l. Click Allocate Storage Pools. Note that there are no storage pools available. If there were, you
could add them.
m. Click Cancel.
n. Click the Allocate Logical Units button. Once again, note that there are no logical units
currently available. This is because some of the infrastructure described here will be created in a
later module.
o. Click Cancel.
p. The last item in the console tree is the Custom Properties item. Click the Manage Custom
Properties button. In the Manage Custom Properties pop-up dialog box, in the Object type
section, note the different object types that are available. Also, note the Create button. You click
this button to add the name and description of a new custom property. (There are none at this
time.)
q. Click Cancel.
r. On the Properties page, note the View Script button in the lower left corner. If you were to
make changes to this host group and then wanted to apply the same changes to another host
group, you could save the script, change the name of the host group within it, and then use it to
make those changes.
Installing and Configuring Microsoft System Center 2012 R2 Virtual Machine Manager 7-15
12. Close the Virtual Machine Manager console, and sign off LON-VMM1.
7-16 Server Virtualization with Windows Server Hyper-V® and System Center
Answer: If you are going to execute tasks that you will perform on large numbers of objects, or if you
want to apply custom filters to select objects, it is better to use Windows PowerShell.
You cannot add the physical computer as Make sure that the host has the required physical
a host. components.
Make sure that the host resides in a trusted domain.
Make sure that the host is running a required operating
system.
Make sure that the VMM service account is in the
physical server’s local administrators group.
You cannot perform a V2V conversion of a Make sure the virtual machine is not connected to an
VMware ESX–hosted virtual machine. IDE bus.
Installing and Configuring Microsoft System Center 2012 R2 Virtual Machine Manager 7-17
Module 8
Managing the Network and Storage Infrastructure in
Microsoft System Center 2012 R2 Virtual Machine Manager
Contents:
Lesson 1: Managing Networking Infrastructure 2
Lesson 2: Managing Storage Infrastructure 7
Lesson 1
Managing Networking Infrastructure
Contents:
Demonstration: Configuring Virtual Network Components in VMM 3
Demonstration: Configuring Network Virtualizatio n 5
Managing the Network and Storage Infrastructure in Microsoft System Center 2012 R2 Virtual Machine Manager 8-3
2. In the Virtual Machine Manager console, click the Fabric workspace, in the Navigation pane, click
Networking, and then on the on the ribbon, click Create Logical Network.
3. In the Create Logical Network Wizard, on the Name page, in the Name text box, type Adatum UK,
and then in the Description text box, type Adatum (London) logical network.
4. Click One connected network, click Allow new VM networks created on this logical network to
use network virtualization, and then click Next.
5. On the Network Site page, click Add, and then in the Host groups that can use this network site
section, click All Hosts.
6. In the Associated VLANs and IP subnets area, click Insert row, in the VLAN text box, type 0, and then
in the IP subnet text box, type 192.168.1.0/24.
7. Click the Network Site Name text box, select and delete the automatically generated site name, and
then type Docklands.
13. On the Network site page, click Use an existing network site, ensure that Docklands is selected,
and then click Next.
14. On the IP address range page, review the options, and then click Next.
15. On the Gateway page, review the options, and then click Next.
16. On the DNS page, review the options, and then click Next.
17. On the WINS page, review the options, and then click Next.
24. On the Network configuration page, under Network sites, click Docklands, click Gatwick, click
Enable Hyper-V Network-Virtualization, and then click Next.
28. In the Create Logical Switch Wizard, on the Getting Started page, click Next.
29. On the General page, in the Name text box, type Adatum UK, in the Description text box, type
Adatum production hosts logical switch, and then click Next.
30. On the Extensions page, leave the default extensions, and then click Next.
31. On the Uplink page, click Add, ensure that the Adatum UK uplink is selected, click OK, and then
click Next.
35. Click Include a virtual network adapter port profile in this virtual port, click the Native virtual
network adapter port profile, click Medium Bandwidth Adapter, click OK, and then click Next.
36. On the Summary page, click Finish.
45. Click Cancel, and then click Yes to close the warning.
2. On the Name page, in the Name text box, type Adatum North, ensure that Adatum UK is selected
as the logical network, and then click Next.
3. On the Isolation page, click Isolate using Hyper-V network-virtualization, and then click Next.
4. On the VM Subnets page, click Add, in the Name text box, type Adatum Finance, and then in the
Subnet text box, type 192.168.4.0/24.
5. On the VM Subnets page, click Add, in the Name text box, type Adatum Engineering, in the
Subnet text box, type 192.168.5.0/24, and then click Next.
6. On the Connectivity page, review the message, and then click Next.
7. On the Summary page review the summary, and then click Finish.
8. Close the Jobs window.
9. In the Virtual Machine Manager console, click the VMs and Services workspace, and then on the
ribbon, click Create VM Network.
10. On the Name page, in the Name text box, type Adatum South, ensure that Adatum UK is selected
as the logical network, and then click Next.
11. On the Isolation page, click Isolate using Hyper-V network-virtualization, and then click Next.
12. On the VM Subnets page, click Add, in the Name text box, type Adatum Warehouse, and then in
the Subnet text box, type 192.168.4.0/24.
13. On the VM Subnets page, click Add, in the Name text box, type Adatum Logistics, in the Subnet
text box, type 192.168.5.0/24, and then click Next.
14. On the Connectivity page, review the message, and then click Next.
15. On the Summary page, review the summary, and then click Finish.
16. Close the Jobs window.
17. In the VMs and Services workspace, click VM Networks click Adatum North, and then right-click
and click Create IP Pool.
18. On the Name page, in the Name text box, type Adatum Finance VM Network IP Pool. Ensure that
the VM Network is set to Adatum North, and that the VM subnet is set to Adatum Finance
(192.168.4.0/24), and then click Next.
19. On the IP address range page, note that the first IP address in the range is reserved. Leave the
default settings, and then click Next.
Lesson 2
Managing Storage Infrastructure
Contents:
Demonstration: Deploying Block Storage in VMM 8
Demonstration: Deploying and Managing Storage in VMM 9
8-8 Server Virtualization with Windows Server Hyper-V® and System Center
3. Click the Protocol drop-down list box, and then click SMI-S WMI.
4. In the Provider IP address or FQDN: text box, type lon-ss1.adatum.com, and then click Browse.
5. On the Select a Run As account page, click Create Run As Account.
6. On the Create Run As Account page, configure the following settings, and then click OK:
o Name: StorageAdmin
o User name: Adatum\Administrator
o Password: Pa$$w0rd
o Confirm password: Pa$$w0rd
7. On the Specify Discovery Scope page, click Next.
8. On the Gather Information page, review the discovery result, and then click Next.
9. On the Select Storage Devices page, click Create Classification, in the Name text box, type Gold,
in the Description text box, type 15K SAS Drives, and then click Add.
10. Click Create Classification, in the Name text box, type Silver, in the description text box, type 7K
SATA Drives, and then click Add.
11. Select the iSCSITarget: LON-SS1:C check box, click the Classification drop-down list box, and then
click Silver.
12. Select the next to iSCSITarget: LON-SS1:E check box, click the Classification drop-down list box,
click Gold, and then click Next.
2. In the Fabric navigation pane, click Storage, and then on the ribbon, click Create Logical Unit.
3. Click the storage pool drop-down list box, and then click iSCSITarget: LON-SS1:E.
4. In the Name text box, type LON-APP1_C, in the Size (GB) text box, clear the existing value, type 20,
and then click OK.
5. In the Fabric navigation pane, click Classifications and Pools. Verify that the new LUN displays.
6. Leave the virtual machines running for the next demonstration.
1. On LON-VMM1, in the Virtual Machine Manager console, click Fabric, right-click Storage, and then
click Add Storage Devices.
2. On the Select Provider Type page, click Windows-based file server, and then click Next.
3. In the Provider IP address or FQDN text box, type lon-svr1.adatum.com, and then click Browse.
4. On the Select a Run As account page, click Administrator, and then click OK.
1. On LON-VMM1, click Fabric, and then on the ribbon, click Create File Share.
2. On the Create File Share page, in the Name text box, type SVR1, click the Classification drop-down
list box, and then and then click Gold. In the Local path text box, type c:\SVR1_Gold, and then click
Create.
Assign Storage to the host server
1. On LON-VMM1, click Fabric, click All Hosts, click lon-host1.adatum.com, and then on the ribbon,
click Properties.
5. On the Storage page, click Add, and then click Add File Share. Click the File share path drop-down
list box, click \\lon-svr1.adatum.com, and then click OK.
Allocate Storage to a host group
Lesson 3
Managing Infrastructure Updates
Contents:
Demonstration: Implementing Infrastructure Updates 11
Managing the Network and Storage Infrastructure in Microsoft System Center 2012 R2 Virtual Machine Manager 8-11
2. In the Virtual Machine Manager console, click Connect, and when the console opens, click the Fabric
workspace.
3. In the navigation pane, expand the Servers node, expand Infrastructure, right-click Update Server,
and then click Add Update Server.
4. In the Add Windows Server Update Services Server dialog box, in the Computer name text box,
type LON-WSUS, and then in the TCP/IP port text box, type 8530.
5. Click the Enter a user name and password option. In the User name text box, type
Adatum\Administrator, in the Password text box, type Pa$$w0rd, and then click Add.
6. In the Jobs window, click the Add Update Server job. At the bottom of the Jobs window, click the
Summary tab, and then monitor the status of the configuration job.
7. When the job displays as Completed w/ info, close the Jobs window. The job status is Completed w/
info because there is no internet connection.
8. With the Update Server node selected, verify that LON-WSUS.adatum.com displays in the results
pane, and that the Agent Status column displays as Responding.
Create a Baseline
8. On the Summary page, review the details, and then click Finish.
9. In the Jobs window, click the Change properties of a baseline job. At the bottom of the Jobs
window, click Summary, and then monitor and review the configuration job.
10. When the job displays as Completed, close the Jobs window.
11. Confirm that the new baseline is available.
8-12 Server Virtualization with Windows Server Hyper-V® and System Center
Answer: When reviewing storage area networks to be used with VMM, you should confirm if they are
compliant with Storage Management Initiative Specification (SMI-S).
Question: Which storage types does VMM allows you to integrate with and configure automation for?
Answer: VMM allows you to integrate with and configure automation for block storage and file storage.
Question: Before you can configure a virtual machine network, what other network should you
configure?
Answer: Before you can configure a virtual machine network, you must first configure a logical network.
Question: You have been advised that a potential compatibility issue exists between a Windows
operating system security update and the antivirus software that you are using to protect your Hyper-V
hosts. What could you do in VMM to prevent this issue from affecting your Hyper-V hosts?
Answer: You must identify the KB number of the update, and then create an update exemption on one or
more of your servers.
Managing the Network and Storage Infrastructure in Microsoft System Center 2012 R2 Virtual Machine Manager 8-13
Question: The UK branch of A. Datum Corporation has decided to implement Hyper-V virtualization with
System Center 2012 R2, and will use Windows File storage for the virtual machines. You have created
update baselines for the virtualization VMM infrastructure, and for Hyper-V hosts. What can you do to
ensure the new file server is included in the scope of your new baseline?
Answer: To ensure the new file server is included in the scope of the baseline, you must configure the
Assignment Scope of the virtualization VMM Infrastructure baseline to include the new file server.
Creating and Managing Virtual Machines by Using Microsoft System Center 2012 R2 Virtual Machine Manager 9-1
Module 9
Creating and Managing Virtual Machines by Using Microsoft
System Center 2012 R2 Virtual Machine Manager
Contents:
Lesson 1: Virtual Machine Management Tasks in VMM 2
Lesson 2: Creating, Cloning, and Converting Virtual Machines 6
Lesson 1
Virtual Machine Management Tasks in VMM
Contents:
Demonstration: Operating Virtual Machine s 3
Demonstration: Creating and Managing Checkpoints 4
Creating and Managing Virtual Machines by Using Microsoft System Center 2012 R2 Virtual Machine Manager 9-3
10. Click the Power Off icon. Explain how this is the same as removing the power cord from a physical
machine. In the pop-up window, click No.
11. On the ribbon, click the Connect or View icon, and on the ribbon drop-down list box, click Connect
via Console.
12. In the Virtual Machine Viewer – 20409B-LON-SVR1, on server LON-HOST1.adatum.com, click the
Ctrl-Alt-Del icon. Sign in as Adatum\Administrator, with the password Pa$$word.
13. Find the taskbar for LON-SVR1. It may be partially hidden by the taskbar for LON-VMM1.
14. In the LON-SVR1 taskbar, click the Windows PowerShell icon.
15. In Windows PowerShell, type ipconfig /all, and then press ENTER.
16. Minimize the Virtual Machine Viewer (VMV) window, and in the LON-VMM1 VMM console, click the
Pause button.
17. In the pop-up window, click Yes.
18. Verify that the status indicates Paused, which might take a moment or two. On the ribbon, you can
also click the Refresh icon.
19. Switch back to the Virtual Machine Viewer for LON-SVR1, which is the single server icon on the
taskbar. Note that the virtual machine is grayed out, and cannot be accessed.
20. Minimize the Virtual Machine Viewer.
21. In the VMM console, verify that LON-SVR1 is still selected, and then on the ribbon, click the Resume
icon on the ribbon.
22. Return to the Virtual Machine Viewer, and note that the virtual machine is once again accessible (is no
longer grayed out).
23. At the top bar of the Virtual Machine Viewer, click File, and then click Exit.
24. On the ribbon, click the Manage Checkpoints icon. Explain to the students that you will discuss
checkpoints more in a later topic.
9-4 Server Virtualization with Windows Server Hyper-V® and System Center
25. In the 20409B-LON-SVR1 Properties dialog box, note the Checkpoints node settings. Point out to
the class how you can view all available checkpoints here, in addition to creating, deleting, and
restoring checkpoints. To delete or restore a checkpoint, you must first select a checkpoint from the
Available checkpoints window.
26. In the 20409B-LON-SVR1 Properties dialog box, click Cancel.
27. On the ribbon, click Properties. In the console tree, beginning with the General node, go through
each node and provide students with a broad overview of what each of them do.
28. Click Cancel.
29. Note that the Delete icon on the ribbon is grayed out, as it is still running and has not been shut
down. Explain to students that selecting Delete removes the virtual machine from both the console
and the host, and it deletes the virtual machine’s virtual hard disk (or disks) and files.
30. As time permits, click on any additional icons on the ribbon, and describe their functionality.
31. On the ribbon, click the Shutdown icon. Explain that this is the proper way to turn off a virtual
machine. Note that the pop-up window explains that any connected users will lose service.
2. When the LON-VMM1 desktop displays, on the taskbar, click the Virtual Machine Manager icon.
3. On the Connect to Server page, click Connect.
4. If the VMM console does not display, maximize the console.
5. In the Workspace area, in the lower left area, click VMs and Services.
6. In the VMs and Service console tree, expand All Hosts, expand LocalGroup, and then click LON-
HOST1.
7. In the VMs details pane, click 20409B-LON-SVR1, and on the ribbon, click the Power On icon.
8. Inform the students that you will be creating a checkpoint of both a running virtual machine and a
stopped virtual machine, and will demonstrate the differences when doing so.
9. After the 20409B-LON-SVR1 virtual machine is running, on the ribbon, click the Create Checkpoint
icon.
10. In the New Checkpoint pop-up dialog box, in the Description text box, type Demonstration of a
running system's checkpoint, and then click Create.
11. In the lower left of the VMM console, click the Jobs workspace.
Creating and Managing Virtual Machines by Using Microsoft System Center 2012 R2 Virtual Machine Manager 9-5
12. Explain to the students that in the Jobs workspace, they can see when a checkpoint is created. If a
failure occurs, they can see what caused it, and ways to troubleshoot or correct that failure.
13. In the Workspace area, in the lower left, click VMs and Services.
14. In VMs and Services, click the 20409B-LON-SVR2 virtual machine.
15. On the ribbon, click the Manage Checkpoints icon.
20. On the ribbon, click the Manage Checkpoints icon. Move the cursor over the last checkpoint
(timeline).
21. Observe that the context line pop-up window has the description Demonstration of a running
system’s checkpoint. Note how it shows a green triangle. This indicates that you took the
checkpoint when the system was online. Click OK.
22. Click the 20409B-LON-SVR2 virtual machine, and on the ribbon, click the Manage Checkpoints
icon. Move the cursor over the last timeline.
23. Observe that the context line pop-up window displays the description Demonstration of a stopped
system’s checkpoint. Also, note the red square icon, which indicates that you took the checkpoint
while the system was stopped. In the Properties dialog box, click OK.
24. On LON–HOST1, open the Hyper-V Manager console, and then click the 20409B-LON-SVR1 virtual
machine.
Lesson 2
Creating, Cloning, and Converting Virtual Machines
Contents:
Demonstration: Creating and Deploying New Virtual Machine s 7
Demonstration: Performing Vir tual Machine Cloning 9
Creating and Managing Virtual Machines by Using Microsoft System Center 2012 R2 Virtual Machine Manager 9-7
6. In the VMs and Service console tree, expand All Hosts, expand LocalGroup, and then click LON-
HOST1.
7. On the ribbon, click the Home tab, in the Create Virtual Machine drop-down list box, click Create
Virtual Machine.
8. In the Create Virtual Machine Wizard, on the Select Source page, click Create the new virtual
machine with a blank virtual hard disk, and then click Next.
Note: Explain to the class that if you chose the option to use an existing virtual machine,
virtual machine template, or virtual hard disk option, then they would have to exist already. In
this demonstration, you are going to make a new virtual machine. Tell the students that four
blank virtual hard disks pre-exist, created by VMM: a large and small blank.vhd, and a large and
small blank.vhdx.
9. On the Identity page, in the Virtual machine name text box, type Win2012test.
10. In the Description text box, type Test of create virtual machine functionality, and then click Next.
11. On the Configure Hardware page, explain the various options to the students:
o Point out the Hardware profile. This is set currently to Default, because no Hardware profiles
have been created at this point. If you had additional Hardware profiles, you could select one
from the drop-down list box.
o Point out the Save As, New, and Remove icons. Even when you are creating a new virtual
machine in the Create Virtual Machine Wizard, you can use these icons to save the profile, make
a new profile, or delete an existing profile.
o Point out the Compatibility node. Here you can select various capability profiles based on the
type of virtualization platform.
o Point out the General node. If you are creating a server, you may wish to choose additional
processors and additional memory. If you are creating a client, you may wish to choose
additional memory and use a higher-end video adapter with RemoteFX.
o Point out the Bus Configuration node. Here you can add disks, integrated drive electronics (IDE)
drives, small computer system interface (SCSI) drives, and DVD drives. You can also modify
existing virtual hard disks. Because you are installing an operating system on this virtual machine,
you can provide an ISO DVD as an image file.
o Point out the Network Adapters node. Here you can configure the network adapter. You can set
the connectivity, IP address, media access control (MAC) address, and even a port profile. Go over
the options on this page with the students. Note that by default the network adapter is not
connected.
9-8 Server Virtualization with Windows Server Hyper-V® and System Center
o Point out that under the Fibre Channel Adapters node, no options are available. This is because
no host computer currently has a Fibre Channel adapter assigned.
o Point out the Advanced node. Here you can set a number of options. These include the priority
of the virtual machine, the BIOS startup order, the CPU priority, whether to apply or not apply
virtual non-uniform memory access (NUMA), and assign a memory weight. Select all of these
options as you go through the demonstration showing them to the students, and then click
Next.
12. On the Select Destinations page, note the options available.
13. Explain to the students that the option to Deploy the virtual machine to a private cloud is grayed
out, because you have not yet set up private cloud functionality.
14. Point out the bottom option. If you did not want to start the virtual machine immediately, you could
store it in the library for later use. In this case, the virtual machine is not assigned to a host. If you wish
to start the virtual machine at a future date, you would need to assign it at that time to a host or
cloud. Because you are placing the virtual machine on a host, you will accept the default Place the
virtual machine on a host option, and from the drop-down list box, click Destination: All Hosts.
15. Click Next.
16. On the Select Host page, give VMM a moment to rate the hosts.
17. Point out the graphical star Rating column. The intelligent placement functionality of VMM looks at
various factors such as performance, space, and number of virtual machines on each host, to
determine the rating. The stars are colored in yellow to show how one host compares to another. In
this case, LON–HOST2 is rated slightly higher. This is because you have not yet deployed a virtual
machine on it. You will do so now.
18. Using the mouse, highlight LON–HOST2, and then click Next.
19. On the Configure Settings page, accept the defaults and click Next.
20. Point out to students that on the Configure Settings page, you can select the virtual machine path,
that is, the location on the host hard drive where you want the virtual machine files to reside. You can
have multiple paths, and you can pre-populate them so they appear in the drop-down list. You can
also use the Browse button to browse to any location in which you want to store the virtual machine
files.
21. On the Select Networks page, click Next.
22. Point out that on the Select Networks page, you can assign your network adapter to a virtual
machine network, Virtual Switch, Port Classification, and virtual local area network (VLAN). You did
not do so at this point, because you can address it later.
23. On the Add Properties page, click Next.
24. Discuss the fact that on the Add Properties page, you can specify the behavior you want the virtual
machine to take when the host machine starts or stops. You can also specify the operating system
that you can install on the virtual machine. The Operating system drop-down list box is
preconfigured by VMM. It includes all Windows operating systems going back to Windows XP, and
many Linux operating systems.
25. If the choice you are looking for is not available, you should select the Other category. Note,
however, that operating systems not on this list may not work correctly due to a lack of integration
services.
26. On the Summary page, in the Confirm the settings section, click the View Script button. This opens
Notepad, and displays the Windows PowerShell script used to create the virtual machine, and
cmdlets and parameters for all the options that you have chosen.
Creating and Managing Virtual Machines by Using Microsoft System Center 2012 R2 Virtual Machine Manager 9-9
27. Save the script for documentation purposes, or to recreate the virtual machine again later. You also
can save the script, and by altering a few parameters, use it for a different virtual machine.
30. In the Save as type: drop-down list box, click All Files (*.), and then click Save.
31. Close Notepad.
32. Note the Start the virtual machine after deploying it check box at the bottom of the page.
33. Point out that if you added the .iso image in the virtual DVD in the Configure Hardware page, you
can now have the virtual machine begin to install the operating system as soon as it is created. For
the purposes of this demonstration, you will not do so.
34. Click the Create button. A job then starts, with multiple steps to create the virtual machine, and a
Jobs pop-up window will display.
35. When the last job completes, close the Jobs pop-up window.
36. On the VMM console, in the console tree, under VMs and Services, under All Hosts, and under
LocalGroup, click LON–HOST2.
37. In the VMs details pane, verify that Wn2012test displays as the only virtual machine on this host.
38. Close the VMM console, and sign out of LON– VMM1.
6. In the VMs and Services console tree, expand All Hosts, expand LocalGroup, and then click LON-
HOST1.
7. In the VMs detail pane, click 20409B-LON-SVR2, and then ensure the Virtual Machine tab is also
selected.
8. On the ribbon, from the Create drop-down list box, click Clone.
9. In the Create Virtual Machine Wizard, point out to the students that the wizard does not have as
many nodes in its console tree as the wizard that you use to create a new virtual machine.
10. On the Identity page, point out how you can add a virtual machine name that identifies the virtual
machine to VMM. The name does not have to match the computer name of the virtual machine.
However, using the same name ensures consistent displays in System Center 2012 R2 Operations
Manager.
11. In the Description window, type Clone of the LON-SVR2 virtual machine, and then click Next
13. Point out that similar to previous versions, the Configure Hardware page has a considerable amount
of options. However, at this time these options are grayed out. Explain to the students that they still
can change the hardware profile in the drop-down list box, if any aside from the Default profile exist.
14. On the Select Destination page, click Next.
15. You can deploy the cloned virtual machine to a host, or you can store it in a library. In this case, you
will place it on a host, which is the default setting.
16. On the Select Host page, observe how VMM rates the hosts. In the Placement window where the two
hosts are listed, click LON-HOST2, and then click Next.
20. On the Select Networks page, point out that you can make choices similar to the choices that were
available when you created a new virtual machine.
21. On the Summary page, click Create.
22. Point out to the students the View Script button in the upper-right corner. Clicking this button will
open Notepad, and will present you with Windows PowerShell cmdlets that are the equivalents of the
configurable selections you made in this wizard. Saving these scripts can help you document your
new or cloned virtual machines.
23. Also point out the Start the virtual machine after deploying it check box. If you are setting the
cloned virtual machine for immediate functionality, you can select this check box.
24. Verify that the Jobs pop-up window displays, and in it are several steps detailing the virtual machine
cloning steps.
25. While you wait for the cloning job to finish, talk about some of the steps you might take to uniquely
identify the cloned virtual machine.
26. After several minutes, once the cloned virtual machine is created successfully, close the Jobs window.
27. In the VMM console, return to the VMs and Services console tree, expand All Hosts, expand
LocalGroup, and then click LON-HOST2.
28. Point out that the 20409B-LON-SVR2 virtual machine is now visible.
29. Right-click the cloned virtual machine, click Delete, and in the confirmation window, click Yes.
You cannot deploy a virtual machine to a Ensure that you have fulfilled the following
host. requirements:
The host has sufficient resources.
The host resides in a trusted domain.
VMM is managing the host.
The host is accessible to VMM.
You do not receive expected Change the host-rating metrics to accommodate the
results from the host rating. needs of your specific environment.
You cannot perform a virtual-to-virtual Check if one of the following factors is the cause:
machine conversion. You do not have the necessary files.
Your version of VMware virtual machine is not
supported.
The machine is not turned off.
9-12 Server Virtualization with Windows Server Hyper-V® and System Center
Answer: Virtual machines that you store in VMM library are turned off, and therefore cannot be updated
by using regular update management systems such as WSUS. Because these machines are often
used as hot spares for existing machines, and because at some point you will most likely deploy
them into production, it is crucial for you to keep them updated just like other computers.
Question: List some of the differences between WSUS and Configuration Manager.
Answer: WSUS is only an update management solution. Configuration Manager, in addition to being an
update management solution, is a system that you also can use to deploy operating systems and
applications in your environment, and perform hardware and software inventories.
Configuring and Managing the Microsoft System Center 2012 R2 Virtual Machine Manager Library and Library Objects 10-1
Module 10
Configuring and Managing the Microsoft System Center
2012 R2 Virtual Machine Manager Library and Library
Objects
Contents:
Lesson 1: Overview of the Virtual Machine Manager Library 2
Lesson 1
Overview of the Virtual Machine Manager Library
Contents:
Questio n and Answers 3
Demonstration: Working with the Virtual Machine Manager Library 3
Configuring and Managing the Microsoft System Center 2012 R2 Virtual Machine Manager Library and Library Objects 10-3
Answer: The primary purpose of the Virtual Machine Manager library is to catalog and index various
resources that you can use to build new virtual machines.
5. In the console tree, select and expand the Library Servers node. Point out the VMM management
server LON-VMM1.Adatum.com, underneath. Emphasize that the VMM management server is always
added as a library server when VMM is installed.
c. On the Home tab of the ribbon, click the New folder icon, in the text box, type Host1Library,
and then press Enter.
d. Right-click Host1Library, click Share with, click the arrow, and then click Specific people.
e. In the text box, click the Down Arrow, click Everyone, click Add, and then click Share.
f. In the File Sharing window, click Done.
g. Close File Explorer.
8. In the Add Library Server Wizard, on the Enter Credentials page, click the Enter a username and
password option. In the User name text box, type ADATUM\administrator, in the Password text
box, type Pa$$w0rd, and then click Next.
9. On the Select Library Servers page, in the Computer name text box, type Lon-host1, and then click
Add. You should now see the host in the Selected servers window. At the bottom of the page, click
Next.
10. On the Add Library Shares page, in the Select library shares to add details pane, select the
Host1Library check box.
11. Note the Add Default Resources check box on the same line as Host1Librabry and to the right.
Mention that this adds the ApplicationsFrameworks folder to the share, which includes 32-bit and 64-
bit versions of the Microsoft Server Application Virtualization (Server App-V) agent, Sequencer,
Windows PowerShell cmdlets for Server App-V, and the Microsoft Web Deployment Tool and scripts
to add application profiles in service templates. These files are grouped automatically as equivalent
resources because of matching values.
10-4 Server Virtualization with Windows Server Hyper-V® and System Center
12. Also, note the Show hidden shares check box at the bottom of the page. This setting displays those
shares that are created as hidden.
13. Select the Add Default Resources check box, and then click Next.
14. On the Summary page, note the View Script button. Clicking it will open Notepad with the Windows
PowerShell cmdlets linked together in a script that will re-create all the selections made by you in the
Add Library Server Wizard. This very useful file can help you document your administrative actions
and re-create your environment.
15. At the bottom of the Summary page, click Add Library Servers.
16. When the Jobs window opens, notice the Add library server job that displays. It will take about two
minutes to complete. When the job completes, close the Jobs window.
17. In the Virtual Machine Manager console, return to the Library workspace and review the new library
server you have added to the Library Servers node in the console tree. Expand each library server and
its library, and then review the various items.
18. In the ApplicationsFrameworks node of the Host1Library, in the Physical Library Objects details pane,
click SAV_x86_en-US_string-of-numbers.cr, and then in the Custom Resource tab of the ribbon,
click Properties (the string of numbers will vary over time).
19. Review the various items found in the SAV_x86_en-US_ string-of-numbers.cr Properties dialog
box. Click the View equivalent resources button, and point out to the class how the same object
appears on every library server, and then click Cancel.
20. In the console tree, click the Dependencies node. No dependencies display, but explain that if this
custom resource had dependencies, they would be enumerated here. This information is useful when
determining whether to delete an object to verify if it is still dependent or being depended upon by
another object. Click Cancel.
21. In the console tree of the VMM console, right-click Host1Library, and then click Explore.
22. In the Host1Library dialog box, click the Home tab, and then click New folder. In the New folder
text box, type ISOs, and then press Enter.
Lesson 2
Working with Profiles and Templates
Contents:
Questio n and Answers 6
Demonstration: Creating a Virtual Machine Template 6
10-6 Server Virtualization with Windows Server Hyper-V® and System Center
Answer: Hardware profiles enable you to perform rapid virtual machine deployment with consistent
hardware configurations.
2. On the desktop, on the taskbar, click the Virtual Machine Manager Console icon.
3. On the Connect to Server page, click Connect.
4. In the Virtual Machine Manager console, on the lower left, click the Library workspace.
5. Explain to students that before you create the virtual machine template, you will create a Guest OS
and Hardware Profile to include in the virtual machine template.
6. In the console tree, click and expand the Profiles node.
7. In the console tree, click the Guest OS Profiles node, and on the Home tab, click the Create icon. On
the shortcut menu, click Guest OS Profile.
8. In the New Guest OS Profile Wizard, on the General page, in the Name box, type DemoGuestOS. In
the Description box, type Demonstration creating a GuestOS profile.
9. In the New Guest OS Profile Wizard console tree, click the Guest OS Profile node.
10. In the New Guest OS Profile Wizard, on the General page, in the Operating System drop-down list
box, click 64-bit edition of Windows Server 2012 Standard.
11. Click the Identity Information section, and in the Computer name box, type WS2012-Core##.
12. Click the Admin Password item, and in the details pane, select the Specify password of the local
administrator account check box.
13. In the Password and Confirm boxes, type Pa$$w0rd.
14. Point out to students the View Script button, and explain that you use this to create a Windows
PowerShell cmdlets script that you can save for documentation purposes or to re-create this hardware
profile.
15. In the New Guest OS Profile Wizard, click OK. Verify that DemoGuestOS displays in the Profiles
details pane.
16. To create a hardware profile, in the console tree, click the Hardware Profiles node. On the Home
tab, click the Create icon, and on the shortcut menu, click Hardware Profile.
17. In the New Hardware Profile Wizard, on the General page, in the Name box, type DemoHWProfile.
In the Description box, type Demonstration creating a hardware profile.
Configuring and Managing the Microsoft System Center 2012 R2 Virtual Machine Manager Library and Library Objects 10-7
18. In the New Hardware Profile Wizard console tree, click the Hardware Profile node.
19. In the Compatibility section, select the Hyper-V check box.
20. In the central console tree, click the Memory item. In the Memory details pane, click the Dynamic
option, and in the Maximum memory area, overwrite the displayed value with 1024.
21. Scroll down in the center console tree, and then select both Network Adapters and Network
Adapt.
22. In the Network Adapter 1 details pane, click the Connected to a VM network option. In the VM
network area, click Browse. In the pop-up window, click the External Network item, and then click
OK.
23. Point out to students the View Script button, and explain that you use this to create a Windows
PowerShell cmdlets script that you can save for documentation purposes or to re-create this hardware
profile.
24. In the New Hardware Profile Wizard, click OK. Verify that the DemoHWProfile displays in the Profiles
details pane.
25. To create the virtual machine template, in the console tree, click and expand the Templates node,
and then click the VM Templates node.
26. On the Home tab of the ribbon, click the Create VM Template icon.
27. In the Create VM Template Wizard, on the Select Source page, note the Use an existing VM
template or a virtual hard disk stored in the library option. Click the Browse button to the right
of it.
28. In the Select VM Template Source dialog box, click Blank Disk – Small.vhdx, and then click OK.
29. On the Select Source page, click Next.
30. On the Identity page, in the VM Template name box, type DemoVMTemplate. In the Description
box, type Demonstration creating a VM template, and then click Next.
31. On the Configure Hardware page, in the Hardware profile drop-down list box, click
DemoHWProfile, and then click Next.
32. On the Configure Operating System page, in the Guest OS profile drop-down list box, click
DemoGuestOS, and then click Next.
33. On the Application Configuration page, in the Application profile drop-down list box, click None
– do not install any applications, and then click Next.
34. On the SQL Server Configuration page, in the SQL Server profile drop-down list box, click the
drop-down arrow, click None – no SQL Server configuration settings, and then click Next.
35. On the Summary page, note the View Script button, and once again mention its purpose. At the
bottom of the page, click Create.
36. When the Jobs window displays, wait for the jobs to finish, and then close the Jobs window.
37. In the Templates details pane of the VMM console, examine the DemoVMTemplate. Note the items
in the Template tab of the ribbon. From here, you can enable and disable a template, export its
settings, and even delete it. On the Template tab, click the Properties icon.
38. In the Properties dialog box, point out that the Hardware and OS Configuration pages no longer
point to the profiles that you created earlier, but now contain all the settings that you configured in
the profiles. Note also the additional pages that are now available. Go over these new settings with
the class.
10-8 Server Virtualization with Windows Server Hyper-V® and System Center
39. Point out to students that you can create custom Properties, and on the Settings page, assign self-
service Quota points.
40. Point out on the Dependencies page that the template is dependent on the Blank Disk –
Small.vhdx virtual hard disk that you selected earlier. Point out that there are no validation errors
and that on the Access page, you can assign other self-service users and roles.
Answer: The Virtual Machine Manager library is a catalog that gives access to file-based resources, such
as System Preparation Tool (Sysprep) scripts, .iso images, and virtual hard disks, that are stored on
your library servers. The Virtual Machine Manager library also provides access to virtual machine
templates, guest operating system profiles, and hardware profiles that reside in the Virtual
Machine Manager database.
Question: What should you create to deploy a VM Template in VMM?
Answer: You should create profiles that the template will use, such as Application, Guest OS, Hardware,
and SQL Server profiles. If these templates have the settings that you need, you can place the
profile into the VM Template, making template creation easier and faster.
Tools
• VMM console
• Server App-V
• Failover Cluster Management Console
You cannot add a library server. Make sure that Virtual Machine Manager agent can
install on the host that you want to add as a library
server. If the agent cannot deploy, or if the agent
cannot communicate with the VMM server, you will
not be able to use the library server.
Resources do not appear in the Virtual The Virtual Machine Manager library refreshes
Machine Manager library after you add (indexes) once per hour. Wait for a while, or initiate a
them to the library share. manual refresh.
You cannot add a file server cluster as a Verify that you are using the correct client access
library server. name.
Ensure that agent is on both nodes.
Ensure that the file server cluster service operates
correctly.
10-10 Server Virtualization with Windows Server Hyper-V® and System Center
Question: What was the purpose of using WS2012-Core### in the Computer name section of the Guest
OS Profile?
Answer: You can provide a pattern for the computer name. In this case, the first virtual machine would be
named WS2012-Core001, the second WS2012-Core002, and so on.
Managing Clouds in Microsoft System Center 2012 R2 Virtual Machine Manager 11-1
Module 11
Managing Clouds in Microsoft System Center 2012 R2
Virtual Machine Manager
Contents:
Lesson 1: Introduction to Clouds 2
Lesson 2: Creating and Managing a Cloud 4
Lesson 1
Introduction to Clouds
Contents:
Questio n and Answers 3
Managing Clouds in Microsoft System Center 2012 R2 Virtual Machine Manager 11-3
Lesson 2
Creating and Managing a Cloud
Contents:
Questio n and Answers 5
Demonstration: Creating a Cloud from Host Group 5
Managing Clouds in Microsoft System Center 2012 R2 Virtual Machine Manager 11-5
Managing a Cloud
Question: How does chargeback benefit application owners?
Answer: Chargeback helps application owners understand exactly which cloud resources they consume,
and then adjust that consumption to better reflect their business needs.
2. When the LON-VMM1 desktop displays, on the taskbar, click the Virtual Machine Manager Console
icon.
3. On the Connect to Server page, click Connect.
4. After a moment, when the Virtual Machine Manager console displays, maximize the console.
5. In the Workspace area, on the lower left, click VMs and Services.
6. On the Virtual Machine Manager console, on the ribbon, click Create Cloud.
7. In the Create Cloud Wizard, on the General page, in the Name text box, type DemoCloud. In the
Description text box, type Demonstration of creating a Cloud, and then click Next.
8. On the Resources page, in Select the resources for this cloud, select the LocalGroup check box.
Talk to the class about the other items on this page, including the following areas:
o Total Physical CPUs
o Total Memory
o Total Storage
Depending on how many Hosts or Host Groups you have, these numbers could vary quite a bit.
You should consider these numbers when making the decision of which resources to select.
Also, note the VMware resource pools area. If you had VMware resources, you can identify them
here.
9. After reviewing the Resources page, click Next.
10. On the Logical Networks page, note the logical networks available. In the Logical networks area,
select the External Network check box, and then click Next.
11. On the Load Balancers page, point out that the only item selectable on this page is the Microsoft
Network Load Balancing (NLB) item. To use it, you must first create NLB IP templates.
If you want to use this page for configuring any hardware load balancers, you must have already
installed the load balancer. However, For the purpose of this demonstration, you will not select
anything. Click Next.
12. On the VIP Templates page, do not select a virtual IP (VIP) template, and click Next.
13. The Port Classifications page has many classifications that are available to use for virtual machines
that you deploy from this private cloud. Select the following check boxes:
o Host management
o Guest Dynamic IP
o Medium bandwidth
11-6 Server Virtualization with Windows Server Hyper-V® and System Center
o Low bandwidth
o High bandwidth.
16. On the Library page, mention to the students that here is where they can assign read–only shares to
the private cloud. These read-only shares are where administrators can store read–only resources
(such as .iso files) that they want to make available to self–service users. However, point out that to
assign the shares, one or more library shares must already exist.
17. Next to the Stored VM path area, click the Browse button. When the Select Destination Folder
pop-up window opens, it displays an expandable tree format. Point out to students the library servers
that are part of the host group. Explain that from this page you can select different libraries.
18. Under lon-host1.adatum.com, click the Host1Library share, and then click OK.
19. On the Library page, click Next.
20. When the Capacity page displays, point out that on this page you can view the aggregate capacity,
use all of it or a signed particular capacity for various resource dimensions used by the cloud. Point
out the following areas of this page:
30. In the console tree, under VMs and Services, under the Clouds node, click DemoCloud. On the
ribbon, click the Overview icon. This will populate the details pane with information about the cloud.
Much of this information will have no values until you start using the cloud and adding items to it
such as virtual machines and services.
Managing Clouds in Microsoft System Center 2012 R2 Virtual Machine Manager 11-7
Lesson 3
Working With User Roles in Virtual Machine Manager
Contents:
Demonstration: Creating and Using a VMM User Role 9
Managing Clouds in Microsoft System Center 2012 R2 Virtual Machine Manager 11-9
d. Import Console Add–in. Add-ins from the VMM console enable customers and partners to
create extensions for the VMM console. These extensions perform specific actions or display
custom views when clicked.
e. Backup. Clicking the backup button backs up the VMM to a Universal Naming Convention (UNC)
share or to local path on Microsoft SQL Server.
f. PowerShell. Selecting this button opens a Windows PowerShell command window, which
connects to the same VMM server as the console.
g. Jobs. This button opens the floating jobs window, which displays information about actions
taken.
h. PRO. This button opens the Performance and Resource Optimization (PRO) tips window.
i. Delete. This button deletes the user role that you selected in the User Roles details pane. This
button will be grayed out unless a user role is selected. You cannot select the Administrator role.
j. Properties. Selecting this button opens the Properties dialog box for the user role selected in
the User Roles details pane.
8. On the Home tab, click the Create User Role button. This brings up.
9. In the Create User Role Wizard, on the Name and description page, in the Name text box, type
DemoRole, in the Description text box, type User role created for demonstration, and then click
Next.
10. On the Profile page, point out the four radio buttons: Fabric Administrator (Delegated
Administrator), Read–Only Administrator, Tenant Administrator and Application Administrator
(Self–Service User). For this demonstration, we will use the Fabric Administrator profile. Ensure that
the Fabric Administrator radio button is selected, and then click Next.
11. On the Members page, explain that while members can include Active Directory user accounts or
group accounts, it is always preferable to use group accounts, which is a standard practice in Active
Directory management. For the purpose of this demonstration, you will use the IT Active Directory
11-10 Server Virtualization with Windows Server Hyper-V® and System Center
group. Click the Add button, and in the Select Users, Computers, or Groups pop-up dialog box, in
the Enter the object names to select (examples) text box, type IT, and then click OK.
12. Verify that ADATUM\IT now displays on the Members page, and then click Next.
13. On the Scope page, in the Scope pane, select the DemoCloud check box. In the console tree with All
Hosts and LocalGroup underneath, select the LocalGroup check box, and then click Next.
14. On the Library Servers page, explain that this page is where you specify which library servers this
user role can use. Initially, no library servers display, so you want to add them. To add a library server,
click the Add button. In the Select a library server pop-up, click lon-host1.adatum.com, and then
click OK. Verify that LON-HOST1 displays in the Library servers: window, and then click Next.
15. On Run As accounts page, explain that because VMM administrators and Fabric administrators can
create Run As accounts, you typically would not add one here. In this case, click Next.
16. On the Summary page, point out that this is the last page of the wizard. Note the View Script
button on the upper right. Selecting this opens up Notepad, and displays the Windows PowerShell
script with all the cmdlets necessary to perform the action that you just created. Explain that it is
always helpful to view and save these Windows PowerShell scripts, because you can use them to re-
create the actions with just a few changes, or use them as documentation for existing objects. Click
the View Script button, and review the script with a class. Go over the various cmdlets and what they
do (there are only six lines in the script). However, do not save the script. In the Notepad window,
click the close (red X) button. On the Summary page, click Finish.
17. When the Jobs pop-up window displays, wait for all jobs to complete, and then close the window.
18. In the Settings console tree, in the Security node, in the User Roles details pane, verify that you see
the DemoRole object. Click DemoRole, and then on the ribbon, click the Properties button.
19. In the DemoRole Properties dialog box, show the students how you can select the different nodes in
the console tree and alter the various properties. When finished, click Cancel.
20. Close the Virtual Machine Manager console.
Managing Clouds in Microsoft System Center 2012 R2 Virtual Machine Manager 11-11
Answer: Before you delete a private cloud, you must ensure that there are no objects that reference the
private cloud. These objects could include services, service deployment configurations, user roles,
and deployed or stored virtual machines.
Question: You need to allow non-IT users to make their own virtual machines, but host server space is
limited. What would be the appropriate user role profile to use, and what specific settings should you set?
Answer: You should use the Application Administrator profile, and ensure that on the Quotas for the
name cloud page, you clear the Maximum selection for the Virtual machines rows are adjusted.
Tools
• Use the Create Cloud Wizard to create a private cloud in VMM 2012
• Use the Create User Roles Wizard to create collections of users that can be assigned permissions
to all or some private clouds, and select permission to what can be done by the user role on
resources in that private cloud.
• Use System Center 2012 - App Controller to provide a common self-service experience that can
help you configure, deploy, and manage virtual machines and services across private and public
clouds.
A user cannot create a virtual machine in a Make sure that the user belongs to a user role
specific cloud. assigned to that cloud.
Make sure that the Quotas for that cloud have not
been exceeded.
Make sure that the user role has permissions to
create a virtual machine.
You cannot delete a cloud because it has On the General page of the virtual machine
virtual machines that you want to keep. properties, use the Cloud drop-down list box to
select None – not associated with a cloud.
You have set the quotas for a particular cloud, Check the user role’s quotas properties for that
and the self-service users have consumed them cloud, and adjust them accordingly
all, but need to use more. You have added a
new host, but they still cannot create more
virtual machines.
11-12 Server Virtualization with Windows Server Hyper-V® and System Center
Module 12
Managing Services in Microsoft System Center 2012 R2
Virtual Machine Manager and App Controller
Contents:
Lesson 2: Creating and Managing Services in VMM 2
Lesson 3: Using App Controller 6
Lesson 2
Creating and Managing Services in VMM
Contents:
Demonstration: Working with Service Designer 3
Demonstration: Deploying a Service 5
Managing Services in Microsoft System Center 2012 R2 Virtual Machine Manager and App Controller 12-3
6. In the New Service Template dialog box, review the various configurable items with the class. Point
out the View Script button. Explain how you can use this to save a script of the various Windows
PowerShell cmdlets that would perform the same actions as this user interface. Point out the different
patterns in the Patterns section. Show students how, as you click each pattern, the Description line
gives a brief explanation of the pattern’s functionality.
7. In the New Service Template dialog box, in the Name field, type Demo Service Template. In the
Release section, type 1. In the Patterns section, click the Single Machine icon, and then click OK.
8. In the Virtual Machine Manager Service Template Designer console, note the name that you selected,
Demo Service Template. It should be part of the overall name, as this is what you are currently
designing.
9. Point out the Designer canvas area. Explain to students that this is the console’s central part and that
it has various blocks that connect to each other. Point out the text that appears dimmed with a large
down arrow. This provides advice on how you can drag-and-drop various virtual machine templates
into the designer, either in the blank canvas area itself to make a new tier, or onto the existing
template to replace its tier.
10. Note the box labeled Single Tier. Point out the red circle with an exclamation mark on it, and the
text below that explains why it has this warning. There is no virtual hard disk or virtual machine
network present in the template. You can make one by changing the properties of the Single Tier
virtual machine. To do this, right-click the Single Tier virtual machine name, and then click
Properties.
11. When the Single Tier properties dialog box opens, explain to students that this is where you make
changes to the Single Tier hardware configuration. Go through the various pages in the properties as
follows:
a. General page. Use this page to set the name and description, and prevent the virtual machine
from migrating automatically. Additionally, use this page to allow the scaling out of a single tier,
and to create and set the tier’s availability. In the Name: box, type DemoServiceVM.
b. Hardware Configuration. Use this page to set the various hardware configurations that you
typically set for a new virtual machine in the VMM console, including:
i. In the Compatibility section, select the Hyper-V check box.
ii. In the console tree, directly under Bus Configuration, click IDE Devices.
iii. Click the green plus sign entitled New, and then click Disk.
iv. In the Virtual Hard Disk details area, click Browse.
v. In the Select a virtual hard disk pop-up window, click SmallCore.vhd, and then click OK.
vi. In the Hardware Configuration console tree, scroll down, and in the Network Adapters
section, click Network Adapt… Not connected.
12-4 Server Virtualization with Windows Server Hyper-V® and System Center
vii. In the Network Adapter 1 (Legacy) details pane, click the Connected to a VM network
option, and then click Browse.
viii. In the Select a VM Network dialog box, click External Network, and then click OK.
ix. Point out the Create VM Network button, and explain to students that they can use this
button to add a new network here.
c. When you finish reviewing the Select a VM Network pop-up window, click OK.
d. OS Configuration. In the Operating system drop-down list, click 64-bit edition of Windows
Server 2012 Standard. Point out the other items that you can select, including the name of the
computer, the local administrator password, the product key, and a time zone. Note the Roles
and Features area, in which you can you can add roles and feature that can run on a Windows
Server. Also, explain that you can join a domain and appear in a workgroup. Point out the Scripts
area, where you can provide Answer File and even Run Once commands.
e. Application Configuration. Explain to students that you can use this page to add applications
and scripts that will run on the virtual machine. Under the Application profile list, there are
three sections: OS Compatibility, Applications, and Scripts. In the OS Compatibility area, in
the list in the details pane of the Compatible operating systems available, you can select none,
one, some, or all. In the console tree of the Application Configuration page, select
Applications. Note that currently there are none listed, but also note the green Add plus sign
pull-down list. Demonstrate to the class the choices that are available, but do not select any. In
the console tree, note that currently there are none listed, but also point out the Add list (which
is the same as the previous Add list). Note again the Application profile list at the top of the
page. Use it to select the None – do not install any applications. It will make all previously
viewed items on this page appear dimmed.
f. SQL Server Configuration. By default, the SQL Server profile drop-down list is set to None –
no SQL Server configuration settings. For the purpose of this demonstration, click Default –
create new SQL Server configuration settings. Click the Add: SQL Server Deployment icon,
and note the various settings that you can configure. Point out the Instance name area that lets
you specify a SQL Server Instance. Change the drop-down list box back to None.
g. Custom Properties. You can use this page to add various custom properties. Click the Manage
Custom Properties button, and show the various configurable items in the pop-up window.
Click Cancel when done.
h. Settings. You can use this page to specify the number of points to apply towards an owner’s
virtual machine quota, when a virtual machine is assigned to a self-service user.
i. Dependencies. Because this is a default template, note that it displays No dependencies found.
j. Validation Errors. This section lists any validation errors.
k. Finally, note the View Script button in the lower left. Point out the usefulness of keeping
Windows PowerShell scripts to document the settings. At the bottom of the Single Tier
Properties dialog box, click OK.
12. Do not close any windows, but end the demonstration at this point. Inform the students that you will
continue deploying the service in a subsequent demonstration.
2. On the Home tab, click the Save and Validate icon, and then click the Configure Deployment icon.
3. In the Select name and destination pop-up dialog box, in the Name text box, type Demo Service,
and in the Destination drop-down box, chose LocalGroup, and then click OK.
4. In the Deploy Service – Demo Service console, if a pink shaded area displays in the middle of the
screen with a message that it could not find a host, click Refresh Preview on the ribbon. This should
clear the error.
5. Note that placement ratings dictate to which host it selects to deploy. In this case, the selected host is
lon-host2.adatum.com.
Lesson 3
Using App Controller
Contents:
Demonstration: Overvie w of an App Controller 7
Demonstration: Using App Controller to Deploy Virtual Machines and Services 8
Managing Services in Microsoft System Center 2012 R2 Virtual Machine Manager and App Controller 12-7
3. Point out that App Controller is a web-based console, and will launch in Windows Internet Explorer.
Maximize this window.
4. In the Enter your credentials to sign in section, in the User name box, type
ADATUM\administrator, and in the Password box, type Pa$$w0rd, and then click Sign In.
5. In the Overview pane, in the Status area, under Private Clouds, click the Connect a Virtual Machine
Manager server and clouds hyperlink. In the Add a new VMM connection, provide the following
settings, and then click OK:
a. Connection name: Adatum
b. Server name: LON-VMM1.adatum.com.
6. Click OK.
7. The first page that loads is the Overview page. Go over the page with the students. Point out that the
various links that display in the details pane are hyperlinks. Additionally, point out that some links,
such as the Connect a Windows Azure link and all the Online Help links, would require Internet
access. Under the Private Clouds section, click the X Virtual Machine Manger clouds, where X is a
number. This can vary, depending on how many clouds you made in the previous modules. Note that
clicking this option takes you to the Clouds area of the console tree to the left. This part of the
console tree should display the DemoCloud cloud that you made in the previous module.
8. At the top of the window, click the large back arrow. In the Status area, under Private Clouds, click
the 1 Virtual Machine Manager server hyperlink. Note that this takes you to the Settings area of
the console tree, and then expanding Settings takes you to the Connections item. Click the back
arrow.
9. Go through the various items in the console tree. Because you have already reviewed the Clouds
item, click Services. Note that there are no services yet in this view, because you have not deployed
any services.
10. Click the Virtual Machines node. This displays the virtual machines that you created in the previous
modules.
11. In the console tree, click the Library node. Point out the additional console tree placed in the middle
of the screen. As you click the various items in this console, mention how the details pane items
correspondingly changes. Note that when you click Shares, an Add button displays immediately
above it on the control bar. Note the Refresh, Customize view, and Copy URL for this view icons,
which are on the right side of the control bar. While not all nodes in this console tree will have an
Add button, the three other controls will be present.
12. Click each of the remaining nodes in the middle console tree, and explain what they do. Note that
Windows Azure will not present data, because you have not yet connected to it. Show how when you
select the various items under the Adatum node, you then can select those items in the details pane,
and right-click them to perform additional actions.. Alternatively, you can select them, and then from
the control bar above, perform various actions on them depending on what kind of items they are.
13. In the main console tree, click the Jobs item to display the different jobs that have run in App
Controller. If no jobs have been run, the details pane will be empty.
12-8 Server Virtualization with Windows Server Hyper-V® and System Center
14. In the console tree, click Settings, and note that it is an expandable node with three child nodes.
Click the Connections, Subscriptions, and User Roles nodes, and then point out the various control-
bar options available in each node.
15. In the top-right corner of the webpage, click the Sign out hyperlink.
16. Close Internet Explorer, and then close all open windows..
4. In the Enter your credentials to sign in section, in the User name text box, type
ADATUM\administrator, and in the Password text box, type Pa$$w0rd, and then click Sign In.
5. In the console tree, select the Services node. Right-click the empty space in the All Deployed
Services area, and then click Deploy.
6. In the New Deployment design view, click the Cloud Configure link.
7. In the Select a cloud for this deployment box, click DemoCloud, and then click OK.
8. Point out how the New Deployment design view is similar to the Service Template Designer. It has
added a connector from the Private Cloud/DemoCloud box to a new box entitled Template, which
now has a Select a template hyperlink. Click this hyperlink.
9. In the Choose a template window, click the Demo Service Template that you created earlier, and
then click OK.
10. In the New Deployment window, verify that you now see more items as connected boxes. Point out
that the Deploy button in the lower-right portion of the screen appears dimmed. This is normal until
all configurable requirements have been set.
11. In the Instance box, click the Configure hyperlink.
12. In the Properties of a new virtual machine dialog box, note the two navigational areas. On the left
is a console tree and on the right is a scrollbar. Point out that clicking the Name and description and
Virtual network adapters moves the view further down the scrolled page.
13. In the Computer name box, type AppCDemoVM, and then in the Description box, type
Demonstration creating a virtual machine in a service template for App Controller.
14. Point out that many items in the Properties of a new virtual machine dialog box are not
configurable, such as Operating system or Memory. Note the Tag and Cost center areas that you
would use to assign further details about usage to the virtual machine. After reviewing the dialog box,
click OK.
15. In the New Deployment window, point out that the Service box now has a Configure hyperlink, and
then click this link.
16. In the Properties of Demo Service Template dialog box, in the Service name box, type DemoApC,
and then click OK.
Managing Services in Microsoft System Center 2012 R2 Virtual Machine Manager and App Controller 12-9
17. In the New Deployment window, note that the Deploy button in the lower-right corner no longer
appears dimmed. This is because you have met all the requirements for a service deployment. Point
out, however, that this does not mean the service deployment will work. It only means that you have
defined the required elements. Click the Deploy button.
18. On the yellow bar at the bottom of the App Controller webpage, you should see a hyperlink that
says VMM service deployment started. Wait a few minutes while the service deploys. This can take
up to 30 minutes. When you see the DemoApC service display in the All Deployed Services details
pane, point out to the students that the status is still Deploying.
19. In the console tree, click Virtual Machines. Wait a moment while the virtual machines and the
various clouds are discovered, and are then displayed. Note the virtual machine with a name of
multiple letters and numbers, and note that in the Status column, it is listed as Under creation.
20. Wait a few more minutes while the virtual machine is created. After a time, point out to students that
the status has changed to Running. Additionally, point out that the yellow bar at the bottom of the
webpage now states VMM service deployment completed.
21. In the Virtual Machines details pane, right-click the newly created virtual machine, and then in the
context menu, click the Console.
If the yellow and white bar at the bottom of the webpage appears, click Install. In the Internet
Explorer – Security Warning pop-up dialog box, click Install. Wait a few moments for the console
to load the virtual machine. If a connection failure pop-up window displays, at the top of the console,
click Reconnect. If you receive another connection failure warning, complete the following steps:
a. Switch back to the VMM console, and then in the VMs and Services workspace console tree, in
the Clouds node, click DemoCloud.
b. In the VMs details pane, right-click the newly created virtual machine, and on the context menu,
click View, and then Connect via Console.
c. When the console window displays the sign-on screen for the virtual machine, in the File drop-
down menu, click Exit.
d. Return to the App Controller window, and then click the Reconnect button.
22. When the virtual machine displays the Sign on screen, at the top of the webpage, click Send Ctrl-
Alt-Del. If nothing happens, you may have to refresh the page, and then try again.
23. Sign in as Administrator with the password Pa$$w0rd. The virtual machine should be an installation
of Windows Server 2012 Standard Core.
24. There is nothing more to demonstrate in this virtual machine, so at the top of the screen, click Send
Ctrl-Alt-Del again, and then click Sign out.
25. Close the Console page. If it is in tabbed view, only close the current tab.
26. On the upper-right of the App Controller webpage, click the Sign out hyperlink.
27. Close Internet Explorer, close all open windows, and then sign out of LON-VMM1.
12-10 Server Virtualization with Windows Server Hyper-V® and System Center
• Make a detailed plan for private cloud capacity, capability, and resources for each private cloud
that you create.
• Use App Controller rather than single virtual machines for deploying services.
• Test service templates before publishing them to users.
Review Question(s)
Question: What should you create to deploy a service in VMM?
Answer: You should create a service template and a deployment configuration.
Question: Can a user deploy new virtual machines by using App Controller?
Answer: Yes, users can deploy virtual machines or services by using App Controller.
You cannot deploy a service to a specific Ensure the proper User Role has been added to the
private cloud. cloud and that no specific quotas have been triggered.
You cannot add a virtual machine Ensure no specific quotas have been triggered, and that
template to a service template tier. the virtual machine does not exist. Examine remaining
resources to ensure no over-allocation exists.
App Controller cannot connect to the Ensure that the SSL certificate has been installed and
VMM server. that the user has typed in the correct URL by using
https, rather than http. If the user is using the local
VMM certificate, a certificate warning will be triggered.
User cannot deploy a service by using App Ensure the proper User Role has been added to the
Controller. cloud and that no specific quotas have been triggered.
Managing Services in Microsoft System Center 2012 R2 Virtual Machine Manager and App Controller 12-11
Module 13
Protecting and Monitoring Virtualization Infrastructure
Contents:
Lesson 1: Overview of Backup and Restore Options for Virtual Machines 2
Lesson 3: Using Operations Manager for Monitoring and Reporting 4
Lesson 4: Integrating VMM with Operations Manager 7
Lesson 1
Overview of Backup and Restore Options for Virtual
Machines
Contents:
Demonstration: Backing Up and Restoring Virtual Machines 3
Protecting and Monitoring Virtualization Infrastructure 13-3
5. On the Server Selection page, click LON-HOST1.Adatum.com, and then click Next. On the Select
server roles page, click Next.
6. On the Select features page, scroll down and click Windows Server Backup, and then click Next.
8. On the Select Items to Exclude page, click Local disk (E:), and then click OK. In the File Type text
box, type *.ISO, and then click the VSS Settings tab.
9. On the VSS Settings tab, click VSS copy Backup, click OK, and then click Next.
10. On the Specify Destination type page, click Local Drives, and then click Next.
11. On the Select Backup Destination page, click the Backup destination drop-down list box, click
Local Disk C, and then click Next.
12. On the Confirmation page, click Backup. The backup may take as long as 15 minutes. On the
Backup Progress page, verify that the Status is Creating shadow copy of volume.
13. When the backup completes, click Close.
Lesson 3
Using Operations Manager for Monitoring and
Reporting
Contents:
Demonstration: Using the Operations Console 5
Demonstration: Configuring Notifications 5
Protecting and Monitoring Virtualization Infrastructure 13-5
4. Right-click an alert, review the options that display, and then click Properties.
5. In the Alert Properties dialog box, click some of the Alert Property tabs, and discuss the page
content.
9. Click the Administration workspace. Explain that this is where you can run discoveries, deploy
agents, create notifications (alerts), import management packs, and configure security and accounts.
10. Click My Workspace. Explain that this is where you can customize and save your console settings,
including commonly used views and searches.
11. Close the Operations console.
4. In the E-mail Notification Channel window, on the Description page, click Next to accept the default
channel name and description.
5. On the Settings page, click Add.
6. In the Add SMTP Server window, enter the following information, and then click OK:
a. SMTP server (FQDN): smtp.adatum.com
b. Port number: 25
8. On the Format page, click Finish to accept the default message format.
9. After the channel saves, click Close.
Create a notification subscriber
13-6 Server Virtualization with Windows Server Hyper-V® and System Center
3. In the Notification Subscriber Wizard, on the Description page, in the Subscriber Name text box,
type Administrator, and then click Next.
4. On the Schedule page, click Always send notifications, and then click Next.
7. On the Channel page, in the Channel Type text box, click E-mail (SMTP).
8. In the Delivery address for the selected channel text box, type administrator@adatum.com, and
then click Next.
9. On the Schedule page, click Always send notifications, and then click Finish.
10. In the Notification Subscriber Wizard, click Finish, and then click Close.
Create a notification subscription
1. In the Operations console, in the Administration workspace, under Notifications, click Subscriptions.
2. In the tasks pane, click New.
3. In the Notification Subscription Wizard, on the Description page, in the Subscription name text box,
type Windows Server 2012 notifications, and then click Next.
4. On the Criteria page, in the Conditions box, select the raised by any instance in a specific group
check box.
14. On the Channels page, click Delay sending notifications if conditions remain unchanged for
longer than (in minutes), type 10, and then click Next.
15. On the Summary page, click Finish, and then click Close.
Lesson 4
Integrating VMM with Operations Manager
Contents:
Demonstration: Integrating VMM and Operations Manager 8
13-8 Server Virtualization with Windows Server Hyper-V® and System Center
2. In File Explorer, expand drive D, expand SCOM, and then click setup.exe.
3. In the Operations Manager window, click Install.
4. On the Select features to install page, select the Operations console check box, and then click
Next.
5. On the Select installation location page, click Next.
6. On the Proceed with Setup page, review the warning, and then click Next.
7. On the license terms page, review the license, click I have read, understood and agree with the license
terms, and then click Next.
8. On the Help improve System Center 2012 - Operations Manager 2012 page, click No, I am not willing
to participate for both Customer Experience Improvement Program and Error Reporting, and then
click Next.
9. On the Microsoft Update page, click Off, and then click Next.
2. In the VMM console click the Settings workspace, in the navigation pane, click System Center
Settings, right-click Operations Manager Server, and then click Properties.
3. In the Add Operations Manager Wizard, on the Introduction page, read the requirements for
integration, and then click Next.
4. On the Connection to Operations Manager page, in the Server name text box, type lon-
om1.adatum.com. Review the options, leave the defaults, and then click Next.
5. On the Connection to VMM page, in the User name text box, type adatum\scservice, in the
Password text box, type Pa$$w0rd, and then click Next.
6. On the Summary page, click Finish.
7. In the Jobs window, click New Operations Manager connection, and wait for the job to complete.
This may take as long as five or more minutes.
8. When the job completes, close the Jobs window.
Protecting and Monitoring Virtualization Infrastructure 13-9
• Recover an item from within a virtual machine, such as a file, folder, volume or disk.
Question: Your data protection strategy calls for an offsite copy of your backups. What features does
DPM provide to facilitate this?
Answer: To enable a protection strategy that requires an offsite copy of your DPM backups, you can do
any of the following:
• Place the primary DPM server offsite, and back up directly to an offsite location.
• Implement a secondary DPM server offsite, install the DPM agent on the primary DPM
server, and then back up the primary DPM server by using the secondary DPM server.
• Enable Windows Azure Online Backup, install the Windows Azure Online Backup agent on
the primary DPM server, and then back up to the Windows Azure vaults.
13-10 Server Virtualization with Windows Server Hyper-V® and System Center
• Capacity Utilization
• Host Group Forecasting
• Host Utilization