10751A ENU Beta TrainerHandbook Part1

MCT USE ONLY.
STUDENT USE PROHIBITED

ETA COURSEWARE EXPIRES 1/2013
O F F I C I A L M I C R O S O F T L E A R N I N G P R O D U C T
RE
W G
10751A
FT IN
A
Configuring and Deploying a Private Cloud
SO US
with System Center 2012
SE ED
EA P
EL ELO
ER EV
PR D
MCT USE ONLY. STUDENT USE PROHIBITED
ii 10751A: Configuring and Deploying a Private Cloud with System Center 2012
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.
2012 Microsoft Corporation. All rights reserved.
Microsoft and the trademarks listed at

http://www.microsoft.com/about/legal/en/us/IntellectualProperty/Trademarks/EN-US.aspx are trademarks of
the Microsoft group of companies. All other trademarks are property of their respective owners
Product Number: 10751A
Released: 04/2012
MICROSOFT LICENSE TERMS
OFFICIAL MICROSOFT LEARNING PRODUCTS
MICROSOFT OFFICIAL COURSE Pre-Release and Final Release Versions
These license terms are an agreement between Microsoft Corporation and you. Please read them. They apply to
the Licensed Content named above, which includes the media on which you received it, if any. These license
terms also apply to any updates, supplements, internet based services and support services for the Licensed
Content, unless other terms accompany those items. If so, those terms apply.
BY DOWNLOADING OR USING THE LICENSED CONTENT, YOU ACCEPT THESE TERMS. IF YOU DO NOT ACCEPT
THEM, DO NOT DOWNLOAD OR USE THE LICENSED CONTENT.
If you comply with these license terms, you have the rights below.
1. DEFINITIONS.
a. Authorized Learning Center means a Microsoft Learning Competency Member, Microsoft IT Academy
Program Member, or such other entity as Microsoft may designate from time to time.
b. Authorized Training Session means the Microsoft-authorized instructor-led training class using only
MOC Courses that are conducted by a MCT at or through an Authorized Learning Center.
c. Classroom Device means one (1) dedicated, secure computer that you own or control that meets or
exceeds the hardware level specified for the particular MOC Course located at your training facilities or
primary business location.
d. End User means an individual who is (i) duly enrolled for 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 MOC Course and any other content accompanying this agreement.
Licensed Content may include (i) Trainer Content, (ii) software, and (iii) associated media.
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, (ii) currently certified as a
Microsoft Certified Trainer under the Microsoft Certification Program, and (iii) holds a Microsoft
Certification in the technology that is the subject of the training session.
g. Microsoft IT Academy Member means a current, active member of the Microsoft IT Academy
Program.
h. Microsoft Learning Competency Member means a Microsoft Partner Network Program Member in
good standing that currently holds the Learning Competency status.
i. Microsoft Official Course or MOC Course means the Official Microsoft Learning Product instructor-
led courseware that educates IT professionals or developers on Microsoft technologies.
j. Microsoft Partner Network Member or MPN Member means a silver or gold-level Microsoft Partner
Network program member in good standing.
k. Personal Device means one (1) device, workstation or other digital electronic device that you
personally own or control that meets or exceeds the hardware level specified for the particular MOC
Course.
l. Private Training Session means the instructor-led training classes provided by MPN Members for
corporate customers to teach a predefined learning objective. 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.
m. Trainer Content means the trainer version of the MOC Course and additional content designated
solely for trainers to use to teach a training session using a MOC Course. Trainer Content may include
Microsoft PowerPoint presentations, instructor notes, lab setup guide, demonstration guides, beta
feedback form and trainer preparation guide for the MOC Course. To clarify, Trainer Content does not
include virtual hard disks or virtual machines.
2. INSTALLATION AND 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 four separate sets of installation and use rights. Only one set of rights apply to you.
a. If you are a Authorized Learning Center:

i. If the Licensed Content is in digital format for each license you acquire you may either:
1. install one (1) copy of the Licensed Content in the form provided to you on a dedicated, secure
server located on your premises where the Authorized Training Session is held for access and
use by one (1) End User attending the Authorized Training Session, or by one (1) MCT teaching
the Authorized Training Session, or
2. install one (1) copy of the Licensed Content in the form provided to you on one (1) Classroom
Device for access and use by one (1) End User attending the Authorized Training Session, or by
one (1) MCT teaching the Authorized Training Session.
ii. You agree that:
1. you will acquire a license for each End User and MCT that accesses the Licensed Content,
2. each End User and MCT will be presented with a copy of this agreement and each individual
will agree that their use of the Licensed Content will be subject to these license terms prior to
their accessing the Licensed Content. Each individual will be required to denote their
acceptance of the EULA in a manner that is enforceable under local law prior to their accessing
the Licensed Content,
3. for all Authorized Training Sessions, you will only use qualified MCTs who hold the applicable
competency to teach the particular MOC Course that is the subject of the training session,
4. you will not alter or remove any copyright or other protective notices contained in the
Licensed Content,
5. you will remove and irretrievably delete all Licensed Content from all Classroom Devices and
servers at the end of the Authorized Training Session,
6. you will only provide access to the Licensed Content to End Users and MCTs,
7. you will only provide access to the Trainer Content to MCTs, and
8. any Licensed Content installed for use during a training session will be done in accordance
with the applicable classroom set-up guide.
b. If you are a MPN Member.

i. If the Licensed Content is in digital format for each license you acquire you may either:
1. install one (1) copy of the Licensed Content in the form provided to you on (A) one (1)
Classroom Device, or (B) one (1) dedicated, secure server located at your premises where
the training session is held for use by one (1) of your employees attending a training session
provided by you, or by one (1) MCT that is teaching the training session, or
2. install one (1) copy of the Licensed Content in the form provided to you on one (1)
Classroom Device for use by one (1) End User attending a Private Training Session, or one (1)
MCT that is teaching the Private Training Session.
ii. You agree that:
1. you will acquire a license for each End User and MCT that accesses the Licensed Content,
2. each End User and MCT will be presented with a copy of this agreement and each individual
will agree that their use of the Licensed Content will be subject to these license terms prior
to their accessing the Licensed Content. Each individual will be required to denote their
acceptance of the EULA in a manner that is enforceable under local law prior to their
accessing the Licensed Content,
3. for all training sessions, you will only use qualified MCTs who hold the applicable
competency to teach the particular MOC Course that is the subject of the training session,
4. you will not alter or remove any copyright or other protective notices contained in the
Licensed Content,
5. you will remove and irretrievably delete all Licensed Content from all Classroom Devices and
servers at the end of each training session,
6. you will only provide access to the Licensed Content to End Users and MCTs,
7. you will only provide access to the Trainer Content to MCTs, and
8. any Licensed Content installed for use during a training session will be done in accordance
with the applicable classroom set-up guide.
c. If you are an End User:

You may use the Licensed Content solely for your personal training use. If the Licensed Content is in
digital format, for each license you acquire you may (i) install one (1) copy of the Licensed Content in
the form provided to you on one (1) Personal Device and install another copy on another Personal
Device as a backup copy, which may be used only to reinstall the Licensed Content; or (ii) print one (1)
copy of the Licensed Content. You may not install or use a copy of the Licensed Content on a device
you do not own or control.
d. If you are a MCT.
i. For each license you acquire, you may use the Licensed Content solely to prepare and deliver an
Authorized Training Session or Private Training Session. For each license you acquire, you may
install and use one (1) copy of the Licensed Content in the form provided to you on one (1) Personal
Device and install one (1) additional copy on another Personal Device as a backup copy, which may
be used only to reinstall the Licensed Content. You may not install or use a copy of the Licensed
Content on a device you do not own or control.
ii. Use of Instructional Components in Trainer Content. You may customize, in accordance with the
most recent version of the MCT Agreement, those portions of the Trainer Content that are logically
associated with instruction of a training session. If you elect to exercise the foregoing rights, you
agree: (a) that any of these customizations will only be used for providing a training session, (b) any
customizations will comply with the terms and conditions for Modified Training Sessions and
Supplemental Materials in the most recent version of the MCT agreement and with this agreement.
For clarity, any use of customize refers only to changing the order of slides and content, and/or
not using all the slides or content, it does not mean changing or modifying any slide or content.
2.2 Separation of Components. The Licensed Content components are licensed as a single unit and you
may not separate the components and install them on different devices.
2.3 Reproduction/Redistribution Licensed Content. Except as expressly provided in the applicable

installation and use rights above, you may not reproduce or distribute the 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 Programs. The Licensed Content may contain third party programs or services. These
license terms will apply to your use of those third party programs or services, unless other terms accompany
those programs and services.
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 that respective component and supplements the terms described in this Agreement.
3. PRE-RELEASE VERSIONS. If the Licensed Content is a pre-release (beta) version, in addition to the other
provisions in this agreement, then these terms also apply:
a. Pre-Release Licensed Content. This Licensed Content is a pre-release version. It may not contain the
same information and/or work the way a final version of the Licensed Content will. We may change it
for the final version. We also may not release a final version. Microsoft is under no obligation to
provide you with any further content, including the final release version of the Licensed Content.
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 software, 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 software,
technologies, or products to third parties because we include your feedback in them. These rights
survive this agreement.
c. Term. If you are an Authorized Training Center, MCT or MPN, you agree to cease using all copies of the
beta version of the Licensed Content upon (i) the date which Microsoft informs you is the end date for
using the beta version, or (ii) sixty (60) days after the commercial release of the Licensed Content,
whichever is earliest (beta term). Upon expiration or termination of the beta term, you will
irretrievably delete and destroy all copies of same in the possession or under your control.
4. INTERNET-BASED SERVICES. Microsoft may provide Internet-based services with the Licensed Content,
which may change or be canceled at any time.
a. Consent for Internet-Based Services. The Licensed Content may connect to computer systems over an
Internet-based wireless network. In some cases, you will not receive a separate notice when they
connect. Using the Licensed Content operates as your consent to the transmission of standard device
information (including but not limited to technical information about your device, system and
application software, and peripherals) for internet-based services.
b. Misuse of Internet-based Services. You may not use any Internet-based service in any way that could
harm it or impair anyone elses use of it. You may not use the service to try to gain unauthorized access
to any service, data, account or network by any means.
5. 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:
install more copies of the Licensed Content on devices than the number of licenses you acquired;
allow more individuals to access the Licensed Content than the number of licenses you acquired;
publicly display, or make the Licensed Content available for others to access or use;
install, sell, publish, transmit, encumber, pledge, lend, copy, adapt, link to, post, rent, lease or lend,
make available or distribute the Licensed Content to any third party, except as expressly permitted
by this Agreement.
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;
access or use any Licensed Content for which you are not providing a training session to End Users
using the Licensed Content;
access or use any Licensed Content that you have not been authorized by Microsoft to access and
use; or
transfer the Licensed Content, in whole or in part, or assign this agreement to any third party.
6. 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. You may not remove or obscure any copyright, trademark or patent notices that
appear on the Licensed Content or any components thereof, as delivered to you.
7. 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.
8. LIMITATIONS ON SALE, RENTAL, ETC. AND CERTAIN ASSIGNMENTS. You may not sell, rent, lease, lend or
sublicense the Licensed Content or any portion thereof, or transfer or assign this agreement.
9. SUPPORT SERVICES. Because the Licensed Content is as is, we may not provide support services for it.
10. 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 any termination of this agreement, you
agree to immediately stop all use of and to irretrievable delete and destroy all copies of the Licensed
Content in your possession or under your control.
11. 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.
12. ENTIRE AGREEMENT. This agreement, and the terms for supplements, updates and support services are
the entire agreement for the Licensed Content.
13. APPLICABLE LAW.

a. United States. If you acquired the Licensed Content in the United States, Washington state law governs
the interpretation of this agreement and applies to claims for breach of it, regardless of conflict of laws
principles. The laws of the state where you live govern all other claims, including claims under state
consumer protection laws, unfair competition laws, and in tort.
b. Outside the United States. If you acquired the Licensed Content in any other country, the laws of that
country apply.
14. 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.
15. DISCLAIMER OF WARRANTY. THE LICENSED CONTENT IS LICENSED "AS-IS," "WITH ALL FAULTS," AND "AS
AVAILABLE." YOU BEAR THE RISK OF USING IT. MICROSOFT CORPORATION AND ITS RESPECTIVE
AFFILIATES GIVE NO EXPRESS WARRANTIES, GUARANTEES, OR CONDITIONS UNDER OR IN RELATION TO
THE LICENSED CONTENT. YOU MAY HAVE ADDITIONAL CONSUMER RIGHTS UNDER YOUR LOCAL LAWS
WHICH THIS AGREEMENT CANNOT CHANGE. TO THE EXTENT PERMITTED UNDER YOUR LOCAL LAWS,
MICROSOFT CORPORATION AND ITS RESPECTIVE AFFILIATES EXCLUDE ANY IMPLIED WARRANTIES OR
CONDITIONS, INCLUDING THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NON-INFRINGEMENT.
16. LIMITATION ON AND EXCLUSION OF REMEDIES AND DAMAGES. TO THE EXTENT NOT PROHIBITED BY
LAW, YOU CAN RECOVER FROM MICROSOFT CORPORATION AND ITS SUPPLIERS ONLY DIRECT
DAMAGES UP TO USD$5.00. YOU AGREE NOT TO SEEK TO RECOVER ANY OTHER DAMAGES, INCLUDING
CONSEQUENTIAL, LOST PROFITS, SPECIAL, INDIRECT OR INCIDENTAL DAMAGES FROM MICROSOFT
CORPORATION AND ITS RESPECTIVE SUPPLIERS.
This limitation applies to

o anything related to the Licensed Content, services made available through the Licensed Content, or
content (including code) on third party Internet sites or third-party programs; and
o claims for breach of contract, breach of warranty, guarantee or condition, strict liability, negligence,
or other tort to the extent permitted by applicable law.
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 Qubec, Canada, certaines des clauses dans ce
contrat sont fournies ci-dessous en franais.
EXONRATION 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 pril. Microsoft naccorde aucune autre garantie
expresse. Vous pouvez bnficier 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, dadquation un usage particulier et dabsence de contrefaon sont exclues.
LIMITATION DES DOMMAGES-INTRTS ET EXCLUSION DE RESPONSABILIT POUR LES DOMMAGES. Vous

pouvez obtenir de Microsoft et de ses fournisseurs une indemnisation en cas de dommages directs uniquement
hauteur de 5,00 $ US. Vous ne pouvez prtendre aucune indemnisation pour les autres dommages, y
compris les dommages spciaux, indirects ou accessoires et pertes de bnfices.
Cette limitation concerne:
tout ce qui est reli au le contenu sous licence , aux services ou au contenu (y compris le code)
figurant sur des sites Internet tiers ou dans des programmes tiers ; et
les rclamations au titre de violation de contrat ou de garantie, ou au titre de responsabilit
stricte, de ngligence ou dune autre faute dans la limite autorise par la loi en vigueur.
Elle sapplique galement, mme si Microsoft connaissait ou devrait connatre lventualit dun tel dommage.
Si votre pays nautorise pas lexclusion ou la limitation de responsabilit pour les dommages indirects,
accessoires ou de quelque nature que ce soit, il se peut que la limitation ou lexclusion ci-dessus ne sappliquera
pas votre gard.
EFFET JURIDIQUE. Le prsent contrat dcrit certains droits juridiques. Vous pourriez avoir dautres droits prvus
par les lois de votre pays. Le prsent contrat ne modifie pas les droits que vous confrent les lois de votre pays
si celles-ci ne le permettent pas.
Revised December 2011

x 10751A: Configuring and Deploying a Private Cloud with System Center 2012
10751A: Configuring and Deploying a Private Cloud with System Center 2012 xi
Acknowledgments
Microsoft Learning would like to acknowledge and thank the following for their contribution towards
developing this title. Their effort at various stages in the development has ensured that you have a good
classroom experience.
Joel Stidley Content Developer

Joel Stidley is a Microsoft Certified IP Professional (MCITP), MCSE, and Microsoft Certified IT Specialist
(MCTS), and a Microsoft Exchange Most Valuable Professional (MVP) with more than 13 years of IT
experience. Currently, he is a principal systems architect at Terremark Worldwide, Inc., where he works
with a variety of directory, storage, virtualization, and messaging technologies. Joel has authored several
books and courses on Microsoft Technologies, including Windows PowerShell, Microsoft Exchange
Server, and Windows Server 2008. He also manages an Exchange Server blog and forum site.
Damir Dizdarevic Content Developer

Damir Dizdarevic is a manager of the Learning Center at Logosoft d.o.o. (Sarajevo, Bosnia and
Herzegovina) and an MCT. He has worked as a subject-matter expert and technical reviewer on several
Microsoft Official Course (MOC) courses, and has published more than 350 articles in various IT
magazines, such as Windows ITPro. He is an MVP for Windows Server Infrastructure Management, and an
MCSE, MCTS, and MCITP (Windows Server 2008 and Exchange Server 2007). He specializes in Windows
Server and Exchange Server.Name5
Byron Wright Content Developer

Byron Wright is a partner in a consulting firm, where he performs network consulting, computer systems
implementation, and technical training. Byron is also a sessional instructor for the Asper School of
Business at the University of Manitoba, teaching management information systems and networking. Byron
has authored and co-authored a number of books on Windows servers, Windows Vista, and Exchange
Server, including the Windows Server 2008 Active Directory Resource Kit.
Justin Kimber Technical Reviewer

Justin (MCTS, MCITP, MCSE MCSA, MCP) has worked in the IT industry for over 17 years in various systems
management roles. For six years he worked as technical director at Inframon. In this role, he was
responsible for architecting and implementing some of the biggest systems management roll-outs in
EMEA, and he was personally involved with the roll-out of a global, application monitoring platform for
Microsoft IT. He now runs his own business specialising in Microsoft System Center training development.
xii 10751A: Configuring and Deploying a Private Cloud with System Center 2012
Contents
Module 1: Planning for the Private Cloud
Lesson 1: Understanding the Private Cloud 1-3
Lesson 2: Requirements for Deploying a Private Cloud 1-13
Lesson 3: Designing the Private Cloud Components 1-22
Lesson 4: Overview of System Center 2012 Components 1-32
Lesson 5: Deploying Hyper-V Clustering with VMM 1-41
Lab: Planning for the Private Cloud 1-47
Module 2: Private Cloud Configuration and Deployment with

System Center Virtual Machine Manager
Lesson 1: VMM Architecture and Components Overview 2-3
Lesson 2: Installing and Upgrading Virtual Machine Manager 2-18
Lesson 3: Configuring VMM Security and Roles 2-26
Lesson 4: Understanding Host Groups 2-33
Lab: Configuring and Deploying the Private Cloud Infrastructure 2-44
Module 3: Extending and Maintaining the Private Cloud Infrastructure

Lesson 1: Overview of the PXE and Update Server Roles 3-3
Lesson 2: Deploying Bare Metal Hyper-V Host Servers 3-8
Lesson 3: Configuring the Update Server Role 3-18
Lesson 4: Creating and Remediating an Update Baseline 3-27
Lab: Maintaining the Private Cloud Infrastructure 3-34
Module 4: Configuring Virtual Application Delivery

Lesson 1: Dynamic Application Deployment Overview 4-3
Lesson 2: Web Deployment Packages 4-8
Lesson 3: Server Application Virtualization Overview 4-13
Lesson 4: Configuring Server App-V Components 4-23
Lesson 5: Sequencing and Deploying Virtual Applications 4-28
Lab: Configuring Virtual Application Delivery 4-34
Module 5: Creating the Private Cloud Building Blocks

Lesson 1: Configuring Guest Operating System Profiles 5-3
Lesson 2: Configuring Hardware Profiles 5-12
Lesson 3: Configuring SQL Server Using SQL Server Profiles 5-25
Lesson 4: Configuring Application Profiles 5-34
Lesson 5: Configuring Virtual Machine Templates 5-39
Lesson 6: Configuring the Self-Service User Role 5-45
Lab: Creating the Private Cloud Building Blocks 5-52
10751A: Configuring and Deploying a Private Cloud with System Center 2012 xiii
Module 6: Deploying and Accessing the First Business Unit Cloud

Lesson 1: Understanding Private Cloud Computing 6-3
Lesson 2: Installing and Configuring App Controller 6-12
Lesson 3: Creating and Managing Services and Service Templates 6-21
Lab: Deploying and Accessing the First Business Unit Cloud 6-31
Module 7: Monitoring the Private Cloud Infrastructure

Lesson 1: Operations Manager Architecture and Security 7-3
Lesson 2: Upgrading Operations Manager 2007 R2 7-15
Lesson 3: Configuring Notifications 7-26
Lesson 4: Configuring Management Packs 7-32
Lesson 5: Configuring Integration with System Center 2012 7-41
Lab: Monitoring the Private Cloud Infrastructure 7-48
Module 8: Extending and Customizing Monitoring of the

Private Cloud Infrastructure
Lesson 1: Configuring the SharePoint Portal 8-3
Lesson 2: Monitoring Templates 8-9
Lesson 3: Distributed Application Monitoring 8-20
Lab: Extending and Customizing Monitoring 8-25
Module 9: Implementing Service Management for the Private Cloud

Lesson 1: Service Manager Architecture Overview 9-3
Lesson 2: Upgrading to Service Manager 2012 Service Manager 9-12
Lesson 3: Understanding Service Manager Work Items 9-17
Lesson 4: Configuring Service Manager Connectors 9-30
Lesson 5: Configuring Service Manager Notifications 9-39
Lab: Implementing Service Management for the Private Cloud 9-43
Module 10: Configuring a Private Cloud Service Catalog

Lesson 1: Implementing a Private Cloud Service Catalog 10-3
Lesson 2: Service Level Management 10-12
Lab: Configuring a Private Cloud Service Catalog 10-15
xiv 10751A: Configuring and Deploying a Private Cloud with System Center 2012
Module 11: Protecting the Private Cloud Infrastructure

Lesson 1: Planning DPM Deployment 11-3
Lesson 2: DPM Architecture and Components 11-15
Lesson 3: Upgrading DPM 11-23
Lesson 4: Configuring DPM for the Private Cloud 11-28
Lesson 5: Configuring Application Protection for the Private Cloud 11-38
Lesson 6: Restoring Applications to the Private Cloud 11-46
Lab: Protecting the Private Cloud Infrastructure 11-51
Module 12: Automating and Standardizing the Private Cloud

Lesson 1: Orchestrator Architecture and Components Overview 12-3
Lesson 2: Deploying and Configuring Core Components 12-13
Lesson 3: Managing Runbooks 12-22
Lesson 4: Configuring Integration Packs 12-35
Lab: Automating the Private Cloud 12-45
Appendix: Lab Answer Keys

Module 1 Lab: Planning for the Private Cloud L1-1
Module 2 Lab: Configuring and Deploying the Private Cloud
Infrastructure L2-5
Module 3 Lab: Maintaining the Private Cloud Infrastructure L3-13
Module 4 Lab: Configuring Virtual Application Delivery L4-19
Module 5 Lab: Creating the Private Cloud Building Blocks L5-25
Module 6 Lab: Deploying and Accessing the First Business Unit Cloud L6-35
Module 7 Lab: Monitoring the Private Cloud Infrastructure L7-45
Module 8 Lab: Extending and Customizing Monitoring L8-59
Module 9 Lab: Implementing Service Management for the
Private Cloud L9-75
Module 10 Lab: Configuring a Private Cloud Service Catalog L10-87
Module 11 Lab: Protecting the Private Cloud Infrastructure L11-103
Module 12 Lab: Automating the Private Cloud L12-111
About This Course i
About This Course

This course describes private cloud configuration and deployment with Microsoft System Center 2012 -
Virtual Machine Manager (VMM) for data center administrators. It is suggested administrators have
prerequisite knowledge in Windows Server 2008 R2 operating system, Active Directory Domain
Services (AD DS, networking and storage experience, working knowledge of VMM, Service Manager,
Opalis, Data Protection Manager, and Operations Manager, Microsoft SharePoint configuration,
Windows Server 2008 Hyper-V, familiarity with data center management processes, and previous work
with of ITIL and MOF.
Course Description
This course describes private cloud configuration and deployment with VMM.
Audience
Data center administrators responsible for designing, installing and configuring a private cloud
infrastructure.
Student Prerequisites
In addition to their professional experience, students who attend this training should already have the
following technical knowledge:
Windows Server 2008 R2 operating system
AD DS.
Networking and storage experience.

Working knowledge of Virtual Machine Manager, Service Manager, Opalis, Data Protection
Manager, and Operations Manager.
Microsoft SharePoint configuration.
Windows Server 2008 Hyper-V.
Familiarity with data center management processes.
Working knowledge of ITIL and MOF.
Course Objectives
After completing this course, students will be able to:
Produce a high-level design that accounts for requirements for the private cloud environment.
Configure and deploy the application fabric.
Configure a PXE server, an update server, and a software update baseline.
Configure Server App-V so that it can be used to sequence and deploy an application virtually.
Build the core components necessary for delivering services on the fabric.
Allocate resources to the private cloud and granting access to the private cloud.
Understand of how to monitor the private cloud using system center operations manager.
ii About This Course
Understand the tools necessary to extend Operations Manager to be customized for a private cloud
environment.
Setup, configure and integrate the core components of Service Manager into the private cloud fabric.
Configure a service catalog and publish this to the self-service portal.
Gain the knowledge to be able to deploy and configure Data Protection Manager in a Private.
Deploy and configure Orchestrator in a Private Cloud Scenario and integrate it with other System
Center components.
Course Outline
This section provides an outline of the course:
Module 1, Planning for the Private Cloud In this module, you will learn the basics about the private
cloud and the Microsoft private cloud services.
Module 2, Private Cloud Configuration and Deployment with System Center Virtual Machine Manager
In this module, you will learn about private clouds, Microsoft System Center 2012 - App Controller, and
private cloud services
Module 3, Extending and Maintaining the Private Cloud Infrastructure" In this module you will learn how
to monitor the private cloud using system center operations manager.
Module 4, Configuring Virtual Application Delivery" In this module, you will learn how to use the
Microsoft Web Deployment Tool and Server App-V to dynamically deploy applications in your private
cloud.
Module 5, Creating the Private Cloud Building Blocks In this module you will learn about the profile
configurations that you can use with virtual machine deployment templates and services. You will also
learn how to configure user self-service in System Center 2012 - Virtual Machine Manager (VMM), which
allows you to delegate virtual machine management tasks.
Module 6, Deploying and Accessing the First Business Unit Cloud In this module, you will learn about
private clouds, Microsoft System Center 2012 - App Controller, and private cloud services.
Module 7, Monitoring the Private Cloud Infrastructure In this module you will learn how to monitor the
private cloud using system center operations manager.
Module 8, Extending and Customizing Monitoring of the Private Cloud Infrastructure In this module
you will learn how to monitor the private cloud using system center operations manager.
Module 9, Implementing Service Management for the Private Cloud In this module you will learn about
Service Manager architecture, upgrade options, work items, connectors, and notifications.
Module 10, Configuring a Private Cloud Service Catalog In this module you will learn more about how
to configure a service catalog and publish this to the self-service portal.
Module 11, Protecting the Private Cloud Infrastructure In this module you will learn how to deploy and
configure Data Protection Manager (DPM) in a private cloud infrastructure.
Module 12, Automating and Standardizing the Private Cloud In this module, you will learn how to use
Microsoft System Center 2012 - Orchestrator to automate the VMM components as well as understand
how to use it to automate other IT systems.
About This Course iii
Course Materials
The following materials are included with your kit:
Course Handbook A succinct classroom learning guide that provides all the critical technical
information in a crisp, tightly-focused format, which is just right for an effective in-class learning
experience.
Lessons: Guide you through the learning objectives and provide the key points that are critical to
the success of the in-class learning experience.
Labs: Provide a real-world, hands-on platform for you to apply the knowledge and skills learned
in the module.
Module Reviews and Takeaways: Provide improved on-the-job reference material to boost
knowledge and skills retention.
Lab Answer Keys: Provide step-by-step lab solution guidance at your finger tips when its
needed.
Course Companion Content on the http://www.microsoft.com/learning/companionmoc/ Site:

Searchable, easy-to-navigate digital content with integrated premium on-line resources designed to
supplement the Course Handbook.
Modules: Include companion content, such as questions and answers, detailed demo steps and
additional reading links, for each lesson. Additionally, they include Lab Review questions and answers
and Module Reviews and Takeaways sections, which contain the review questions and answers, best
practices, common issues and troubleshooting tips with answers, and real-world issues and scenarios
with answers.
Resources: Include well-categorized additional resources that give you immediate access to the most
up-to-date premium content on TechNet, MSDN, Microsoft Press.
Student Course files on the http://www.microsoft.com/learning/companionmoc/ Site: Includes the

Allfiles.exe, a self-extracting executable file that contains all the files required for the labs and
demonstrations.
Course evaluation At the end of the course, you will have the opportunity to complete an online
evaluation to provide feedback on the course, training facility, and instructor.
To provide additional comments or feedback on the course, send e-mail to
support@mscourseware.com. To inquire about the Microsoft Certification Program, send e-mail
to mcphelp@microsoft.com.
iv About This Course
Virtual Machine Environment

This section provides the information for setting up the classroom environment to support the business
scenario of the course.
Virtual Machine Configuration

In this course, you will use Microsoft Hyper-V deployed on Windows Server 2008 R2 to perform the labs.
The following table shows the role of each virtual machine used in this course:
Virtual machine Role

10751A-LON-DC1 Domain controller for the Contoso.com domain
Server running Virtual Machine Manager in the

10751A-LON-VM1
Contoso.com domain
Server running Operations Manager in the

10751A-LON-OM1
Contoso.com domain
Server running Service Manager in the

10751A-LON-SM1
Contoso.com domain
Server running Data Protection Manager in the

10751A-LON-DM1
Contoso.com domain
Server running Orchestrator in the Contoso.com

10751A-LON-OR1
domain
Server running SharePoint in the Contoso.com

10751A-LON-AP1
domain
Server running SQL Server in the Contoso.com

10751A-LON-SQ1
domain
10751A-LON-AP2 File Server running in the Contoso.com domain
Classroom Setup
Each classroom computer will have the same virtual machine configured in the same way.
Course Hardware Level
To ensure a satisfactory student experience, Microsoft Learning requires a minimum equipment

configuration for trainer and student computers in all Microsoft Certified Partner for Learning Solutions
(CPLS) classrooms in which Official Microsoft Learning Product courseware are taught.
1-1
Module 1
Planning for the Private Cloud
Contents:
Lesson 1: Understanding the Private Cloud 1-3
Lesson 2: Requirements for Deploying a Private Cloud 1-13
Lesson 3: Designing the Private Cloud Components 1-22

Lesson 4: Overview of System Center 2012 Components 1-32
Lesson 5: Deploying Hyper-V Clustering with VMM 1-41
Lab: Planning for the Private Cloud 1-47

1-2 Planning for the Private Cloud
Module Overview
Many information technology (IT) professionals today consider cloud computing one of the most
important technical inventions in recent years. Cloud computing can reduce IT costs by automatically
increasing the availability of servers and applications. Though cloud computing has existed for a few
years, fully utilizing its benefits required new virtualization and management tools to enable organizations
to use cloud computing within their private networks, thus creating private cloud infrastructures.
Planning a private cloud involves understanding these tools and technologies so that you can use them to
create an internal infrastructure that will support cloud computing within the organization.
In this module, you will learn the basics about the private cloud and the Microsoft private cloud services.
After completing this module, you will be able to:
Describe the private cloud.
Understand the requirements for deploying a private cloud.
Design the private cloud infrastructure components
Describe the Microsoft System Center 2012 components.
Deploy Hyper-V host clustering with Microsoft System Center 2012 - Virtual Machine Manager.
10751A: Configuring and Deploying a Private Cloud with System Center 2012 1-3
Lesson 1
Understanding the Private Cloud
Private and public cloud computing models provide different services based on your needs. Before
moving to a cloud-computing model, you need to understand its requirements and challenges. For
greater control and manageability, you can adopt a private cloud model. The public cloud offers less
control and functionality. However, a public cloud might suit your technical needs or budgetary
constraints.
This lesson describes the private cloud and the infrastructure components that you can use to create a
private cloud.
After completing this lesson, you will be able to:
Describe the business problem.

Describe the difference between the private cloud and public cloud.
Describe the benefits of using the Microsoft private cloud.
Describe the System Center 2012 components for the private cloud.
Understanding the Business Problem

For many years, traditional computing involved a rapid growth of data centers with a great deal of server
inefficiency. IT professionals would purchase a significant amount of physical, individual servers, and
assign one workload typically to each server. With the ability to run multiple workloads on a single server,
there was some application or hardware-based resource consolidation, , but typically, IT professionals
used single workloads or functions that were deployed on servers using less than 10 percent of their
available resources. This meant that in a data center, hundreds or thousands of servers were consuming
large amounts of space and power, with low overall use.
About 10 years ago, technology improved enough to enable the data center to isolate the workload and
the operating system inside a virtual machine. IT professionals could now consolidate these virtual
machines on fewer instances of hardware. There was a significant increase in resource use with reduced
costs and power consumption.
The Rise of Cloud Computing

The next evolution for virtual computing technology is cloud computing. Cloud computing extends the
the virtualization concepts to make them more elastic. Public and private clouds are more easily accessible
to business unit IT teams, and more accountable through features such as the cost center-based
chargeback model for billing.
Cloud computing introduces the concept of a single resource infrastructure pool that delivers infinite
computer, network, and storage resources for key services. For example, an application owner can deploy
a developed application to the private cloud infrastructure and be assured that the infrastructure will
adjust resources dynamically for the application, scale the application, and enable the application to
migrate across the servers based on best resource match.
This current cloud computing model ultimately delivers elasticity, design scalability, and accountability for
the actual resource use that the application is employing. Additionally, this computing model makes
maximum use of the resources that are available in the data center.
The Benefits of Cloud Computing

The advantages in cloud computing are:
Virtualized data center. Cloud computing provides methods to access computing services that are
independent both of your physical location, and the hardware that you use to access it. With cloud
computing, you no longer need to store data or applications on your local computer. The data center
remains a key element when adopting cloud computing; however, cloud computing emphasizes
virtualization technologies that focus on delivering applications rather than supporting the data
center infrastructure.
Reduced operational costs. Cloud computing helps mitigate issues such as low system use,
inconsistent availability, and high operational costs, by providing pooled resources, elasticity, and
virtualization technology.
Server consolidation. Cloud computing allows you to host multiple virtual machines on a
virtualization host, which enables you to consolidate servers across the data center.
Improved resilience and agility. With products such as System Center 2012, cloud computing can
reduce costs and improve efficiency.
Public Clouds and Private Clouds

There are two different types of clouds: the public cloud and the private cloud. These terms are defined are
follows:
Public cloud. The public cloud infrastructure is made available to the public or a large industry group,
and is owned by an organization that sells cloud services. Thus, the resources are shared with other
organizations, and the public cloud exists only off-premises.
Private cloud. The private cloud infrastructure is operated only for one organization, and exists either
on-premises or off-premises. A private cloud may be managed by the organization itself, or by an
outside company.
Public Cloud and Private Cloud Workloads

The key difference between a public cloud and a private cloud is the workloads that are running on the
infrastructure.
With public cloud services, the organization that signs up for the service has less management overhead
than organizations that use private clouds. This also means, however, that control of the infrastructure and
services is greatly reduced, because the service provider manages this for the organization. In addition,
the public cloud hosts the infrastructure and services for multiple organizations (multi-tenant), which
introduces security implications that you need to review.
Private clouds are owned by their respective organizations. The cloud infrastructure is managed and
maintained in the organizations data center. One of the key benefits of this is that the organization has
complete control over the cloud infrastructure and services that it provides. However, the organization
also has the management overhead and costs that are associated with this model.
There are different types of private clouds. For example, hosted private clouds are private clouds that
hosting companies create specifically for your needs. This means that there are no other companies or
applications running on the infrastructure other than yours.
Considerations for Choosing a Cloud Computing Model

When moving to a cloud-computing modelregardless of the cloud model that you choose to adopt
you need to consider the following factors:
Cloud service models. You can choose either Infrastructure as a Service (IaaS), Software as a Service
(SaaS), or Platform as a Service (PaaS) for your cloud service model. You should understand the
difference between these models so that you can choose the model that is the best for your
organization.
IaaS. IaaS is a cloud-computing model in which you manage your virtual server within your
organization. For example, creating a private cloud with System Center 2012 provides you with
the IaaS model.
SaaS. Saas is a cloud-computing model in which you receive a service such as email messaging.
For example, Microsoft Office 365 is a SaaS offering.
PaaS. PaaS is a cloud-computing model that lies somewhere between IaaS and SaaS. This model
provides a computing platform that you use, and upon which you manage your applications. For
example, Windows Azure is a PaaS.
Internet connection. Your Internet connection can become a single point of failure when using your
line-of-business (LOB) applications. Whether moving to a public cloud or a private cloud, you need to
ensure that the connectivity between your on-premises computers and the cloud-based applications
are always available. Network latency is also a major factor. If you spread your infrastructure across
multiple sites and site links, and over wide areas, this can have a detrimental effect on the
performance and availability of your applications.
Data protection and recovery. Although you will have methods in place already to protect and
recover your mission-critical data, you need to consider the following questions when moving to a
cloud computing model:
Are the current protection and recovery methods compatible with the virtualization technologies
that the public cloud or private cloud uses?
Is data being stored securely?
Do you need a local backup of your data in the event of an Internet connection failure? In this
case, how is the data transferred back to your organization, and how is the data restored in the
event of a catastrophic failure?
Disaster recovery. Ask yourself the following questions:
What is your current disaster recovery model?
Do you have mirrored sites? If so, how will data synchronize between the sites?
How will mirrored sites and data synchronization affect the cloud-computing model that you
choose?
Performance and availability. Application performance and availability are key factors to consider
when adopting any cloud-computing model. With a public cloud, you need to ensure that the service
provider can meet the performance and availability requirements of your applications. You need to
consider the service level agreements (SLAs) that the service provider includes with their services.
If you choose to adopt a public cloud, there are a number of additional factors to consider. When
deciding whether to adopt a private cloud or a public cloud solution, consider the following questions:
Private cloud Public cloud
Are the virtualization technologies that you plan What virtualization technologies does the
to adopt compatible with your applications? public cloud vendor offer?
What guarantees can you make to your Are the technologies compatible with your
organization that the mission-critical applications applications?
will always be available?
What tools will you have in place to monitor Is the vendor a reputable company that can
application performance and how will they alert cope with your expanding business
you to the occurrence of when potential issues requirements and geographical locations?
are about to occur?
Question: What are the benefits of moving to a private cloud instead of a public cloud?
Benefits of Using the Microsoft Private Cloud

The Microsoft private cloud business service is based on the following four key benefits.
Improves Application Availability

Applications are vital for most businesses. The private cloud provides you with the following functionality
to improve application availability:
Optimize the application life cycle with service templates and self-service.
Improve availability and performance with application monitoring and diagnosis.
Remediate application issues faster, and improve SLAs.
Provides Cross-Platform Integration

IT environments are heterogeneous, with a wide range of operating systems, virtual machine managers,
and development tools that run together. The Microsoft private cloud allows you to:
Manage multiple virtual machine managers (Microsoft, VMware, & Citrix).
Run and monitor multiple operating systems.
Drive process automation and configuration across platforms and toolsets.
Develop applications using multiple application toolsets.
Allows for Growth

Microsoft private cloud services allows you to:
Deliver high performance for your key Microsoft workloads.
Use the economics of the private cloud without the limitations of per-virtual machine licensing.
Fully integrate management systems, from hardware resources to application services.

Enables Customization Based on Business Needs

You can distribute IT across public cloud and private cloud computing models, depending on your
business or security requirements. You can:
Construct and manage public cloud and private cloud infrastructures across multiple data centers,
and service providers.
Use common management, identity, virtualization, and development tools that span private and
public clouds.
Provide delegated authority and tools to enable self-service across environments.
Retain control across your private clouds and public clouds for compliance and security.
Question: Which benefit would be most important for your company to consider when
implementing a private cloud?
System Center 2012 Private Cloud Components

Microsoft private cloud solutions are built around Windows Server 2008 R2 Hyper-V, and System Center
2012. System Center 2012 helps you manage your physical and virtual IT environments from the desktop
computers to the infrastructure components. These components provide the following key capabilities:
application management, service delivery and automation, and infrastructure management.
Application Management
This capability can help your application owners deliver application services to their business counterparts.
Application management helps you manage the full application life cyclefrom provisioning services
(such as configuration), to operating them (such as monitoring or patching). The following System Center
2012 components facilitate application management:
System Center 2012 - App Controller. This component provides a common self-service experience
across private and public clouds that can help application owners build, configure, deploy, and
manage new services.
System Center 2012 - Virtual Machine Manager (VMM). This component provides virtual machine
management and services deployment that can help you deliver a flexible and cost-effective private
cloud environment.
System Center 2012 - Operations Manager. This component provides deep application diagnostics
and infrastructure monitoring that can help you ensure the predictable performance and availability
of vital applications, and it offers a comprehensive view of your data center, private cloud, and public
cloud.
Service Delivery and Automation

Service delivery and process automation helps you simplify and standardize your data center. The
following System Center 2012 components facilitate service delivery and automation:
System Center 2012 - Orchestrator. This component provides orchestration, integration, and
automation of IT processes through the creation of runbooks that can help you define and
standardize best practices and improve operational efficiency.
System Center 2012 - Service Manager. This component provides self-service experiences and
standardized data center processes that can help you integrate people, workflows, and knowledge
across enterprise infrastructure and applications.
Infrastructure Management
This capability provides integrated management functionality to help you configure, provision, monitor,
and operate your physical and virtual infrastructures. The following System Center 2012 components
facilitate infrastructure management:
System Center 2012 Configuration Manager. This component provides software management
capabilities for Windows-based clients. Using Configuration Manager, you can deploy operating
systems, software applications, and updates, and monitor hardware and software inventory to ensure
that compliance settings are applied.
System Center 2012 - Data Protection Manager (DPM). This component provides unified data
protection for Windows-based servers and clients that can help you deliver scalable, manageable, and
cost-effective protection and restore scenarios from disk, tape, and off-premise.
System Center 2012 - Virtual Machine Manager
System Center 2012 - Operations Manager
Note This course covers all of the System Center 2012 the components except for
Configuration Manager.
Lesson 2
Requirements for Deploying a Private Cloud
Before moving to the private cloud, you need to ensure that your systems meet the prerequisites. This
includes ensuring that you have a public key infrastructure (PKI) in place to help secure the private cloud
service. You also need to identify the services that you want to migrate to the private cloud infrastructure,
and then plan how you will manage, monitor, and protect them.
Describe the key business requirements for moving to a private cloud.

Explain how to identify and migrate services.
Describe service management process automation.
Explain how to monitor and protect services.

Key Business Requirements

There are a number of business challenges that should be considered when deciding to implement a
private cloud solution. These business challenges differ from technical challenges that typically receive
more consideration. Therefore, it is important to differentiate between the two. For example, when
discussing the redundant array of independent disks (RAID)-level decision for a disk-subsystem, it would
be relevant to an engineer, but not to a chief financial officer.
The three common business requirements can induce organizations to move to a private cloud
infrastructure are:
Competitive Advantage
This could mean the ability to perform better or faster, or at a much lower cost, than your competitors.
For example, you may not want to wait weeks for physical hardware to be delivered so that you can
deploy a new service. Using cloud-computing, you can immediately react to a service request and provide
the service in a short time.
Scalability
This is the ability to scale the business quickly, and with minimal cost and downtime. Scalability also
means being able to deploy and retire business applications on demand. Consider the traditional IT
environment where, in many cases, new infrastructure needs to be provisioned to expand the business.
Along with the initial cost of purchasing the hardware, there would be additional costs of managing and
maintaining the infrastructure. Furthermore, there would most likely be time-factors involved in
provisioning the infrastructure and bringing it online so it is ready for the business to use.
Reduced Costs
This includes being able to reduce IT overhead without compromising business revenue. The traditional IT
environment consists of multiple application servers, each dedicated to a single role. In many cases, the
servers that host these applications do not use all the computing power or resources that are assigned to
them. Consolidating server roles enables the consolidation of physical servers, which reduces the cost
without affecting the business revenue.
Question: What other business requirements can you think of that would affect your
decision in moving to a private cloud infrastructure?
Service Identification and Migration

When planning your private cloud infrastructure, you must know which services are suitable for cloud
computing, and how you will migrate those services to the private cloud. For example, some of your
business-critical applications may not be suitable for the private cloud because of security or budget
constraints.
Identifying the Services

A service can be an application, process, function, or it can be data. During the identification process,
consider the following:
Does the application need to reside in the same location as the data?
What security implications might you encounter when moving data to the private cloud, and how
might you mitigate them?
What computer resources does the service require?
What are the services software and operating system requirements?
What are the fault-tolerance and load-balancing considerations?

What virtualization constraints might you encounter?
Are modifications required before the application is compatible?
What network bandwidth will the application require given the users and the private cloud
infrastructure?
Which dependent resources do you also need to include in the private cloud?
Other areas of consideration may include:

How important is the service to the business?
What are the availability, confidentiality, and integrity requirements for the service, and how will
those be affected if all or part of it is managed in the private cloud?
What data flow does the service require, and are customers accessing the data?
You should create detailed documentation for each application, process, function, and data, to assist in
making an informed decision regarding whether the service is suitable for the private cloud.
Migrating to the Private Cloud

After identifying the services that you want to migrate to the private cloud, you should consider a number
of factors to ensure a successful migration process. You should create a document with detailed steps and
checkpoints that you can track to ensure that the migration process is as fault-free as possible.
The documentation should include the answer to the following questions:
What is the application or service name?
Who is the application or service owner?

Have relevant backups taken place?
Have all the prerequisites been verified?
What are the software support details?

Has the service passed identity check, and is it ready for the private cloud?
What is the expected start and finish times of the migration process?
Will there be any downtime?
Has the migration been tested successfully in pre-production or user-acceptance testing?
Is a side-by-side migration option available?
Is there a documented method for fallback?

The migration process you use depends on the services you are moving to the private cloud
infrastructure. The process can include a number of functions, such as:
Creating one or more virtual machines.
Building the application server.
Updating the private cloud.
Updating the service catalog with service and offering requests.
Configuring access to the application.
Configuring networking and firewalls.
Testing access to the service or application.
Configuring the monitoring for the service or application.
Monitoring is a critical function that you configure after the service is functional. Typically, you monitor all
elements of the service, including the virtual machines and physical infrastructure upon which they rely.
Service Management Process Automation

The System Center Cloud Services Process Pack integrates with Service Manager, VMM, and Orchestrator
to provide a standardized and well-defined process for requesting and managing private cloud services.
Many elements make up a successful private cloud service, including:
Self-service portal
Ticketing system
Notifications
Workflows
Automation
Implementing and integrating the various private cloud service elements is a complicated process. The
System Center Cloud Services Process Pack together with the System Center components address this
concern by enabling the IaaS model.
Using the System Center Cloud Services Process Pack

Service Manager contains its own configuration management database that holds nearly all of the
configuration and management information that relates to the environment. With the System Center
Cloud Services Process Pack, additional information from VMM such as virtual machine templates and
service names, are also included. The configuration management database receives a copy of this
information on a regular basis. Service Manager also uses a service catalog containing services that are
made available through a self-service portal to users within the organization.
In this scenario, a user requests a new virtual machine through the self-service portal, and Service
Manager automatically starts a workflow to manage the request. The users request is forwarded to his or
her manager for approval, and if approved, the workflow would then start an Orchestrator runbook. The
Orchestrator runbook would then interact with VMM by using a built-in activity that requests the virtual
machine be created. VMM then checks the users quota and private cloud resources. If both are sufficient,
VMM creates the request. This is one example of how you can use System Center to manage service
management and process automation.
Service Monitoring and Continuous Service Protection

For optimum performance and availability, you should enable monitoring and protection for the private
cloud. System Center provides these functions through Operations Manager and DPM.
Consider the following scenario: As the private cloud administrator at Contoso, Ltd, you have successfully
deployed a LOB application to the private cloud. The application uses a website, a database, and an
application server. You now need to ensure that the application performs at the expected user levels, and
that it is available at all times. You also need to ensure that adequate backups occur without any
disruption to the application.
Operations Manager
To monitor the LOB application, Operations Manager must have discovered and be monitoring
technologies such as Windows Server 2008 R2, Microsoft SQL Server 2008 R2, Internet Information
Services (IIS), and Microsoft ASP.NET. You need to configure the Operations Manager to start monitoring
these technologies. After that Operations Manager starts to automatically monitor the LOB application.
Operations Manager also includes the Application Diagnostics and Application Advisor consoles, which
provide analysis reporting and event diagnosis to help you monitor the .NET application.
Note Operations Manager will be discussed in detail in module 7.
Data Protection Manager

DPM allows you to protect your LOB applications and services. To use DPM, you decide which
technologiessuch as Windows Server 2008 R2 or SQL Serveryou want to back up together, and then
group all the required resources for these technologies into a protection group. This ensures that the
required services are backed up at the same time so that a restore would provide immediate service
access.
Operations Manager also provides monitoring for DPM. For example, state and diagram views in
Operations Manager show the overall health of the DPM environment. Alert views give you instant
notification if a problem occurs in the environment. You can also run a number of DPM tasks in the
Operations Console, such as performing a consistency check.
Note DPM will be discussed in detail in module 11.

Lesson 3
Designing the Private Cloud Infrastructure Components
The first step in planning a private cloud is to evaluate your organizations current environment, and then
determine what components you can and should virtualize. You can use virtualization to address many
issues in most organizations. However, getting the maximum benefit out of virtualization requires careful
planning.
In this lesson, you will learn what you need to consider, and how to design your private cloud.

Assess your current data center environment.
Design for high availability.
Design for scalability.
Design for business continuity.
Design for disaster recovery.

Assessing the Current Data Center Environment

Before designing your private cloud infrastructure, you must assess your current data center environment.
Virtualization addresses many requirements, but you cannot virtualize all servers and applications. This
means that before implementing virtualization, you need to identify those servers and applications that
are the best candidates to run in the private cloud.
There are several factors to consider when choosing whether to virtualize a workload:
Hardware requirements. Typically, virtual machines require approximately the same resources as a
physical server. For example, if a physical server uses 1 gigabyte (GB) of memory, you should expect
the virtual machine to use the same amount of memory, assuming that it runs the same operating
system and applications as the physical server. In some cases, a server workload may require hardware
resources that make it impractical to deploy the workload on to a virtual machine. For example, if an
application requires direct access to a certain hardware part such as a special computer-aided design
(CAD) metal-cutting plotter, you cannot virtualize the server. Additionally, if the server workload
requires more than half of the hardware resources that are available on a virtualization host, there
may not be any server consolidation benefit.
Note Ensure that you are using the actual hardware utilization rather than the actual
physical hardware when evaluating the hardware requirement for the virtual machine. You
can deploy a physical server that is only using 5 percent of its current hardware resources in
a virtual machine with much lower hardware resources.
Compatibility. Determine whether the application can run in a virtualization environment. Business
applications range from simple executables to complex, distributed multitier applications. You need
to consider requirements for specific components of distributed applications, such as specific needs
for communication with other infrastructure components, and requirements for direct access to the
system hardware. You can virtualize some lightly-used web servers easily, while the back-end
components may need to continue running on dedicated hardware. Applications and services that
have specific hardware or driver requirements generally are not well suited for virtualization. An
application may not be a good candidate for application virtualization if it contains low-level drivers
that require direct access to the system hardware. This may not be possible through a virtualization
interface, or it may affect performance negatively.
Note For details on which Microsoft applications are supported in a virtual environment,
see the suggested additional reading link for this topic on the companion CD.
Supportability. Evaluate whether the operating system and the application are supported in a
virtualized environment. Verify other vendor support policies for deployment of the operating system
and the application using the virtualization technologies.
Workload pattern. Investigate the current workload pattern of the applications that you want to
migrate to the private cloud. This is important for predicting peak times and allocating sufficient
virtual resources. Workload patterns are classified in the following four categories:
On or Off. This defines a workload where the applications are used only at specific times, such as
a lottery website where people only check the status after the drawing.
Growing Fast. This workload is defined when the applications require more and more computing
power every day or every week, thereby requiring a continuous extension in resources. An
example could be an online news service with registered users, in which the more a user
advertises or becomes known, the more computing power the user requires.
Predictable Bursting. This workload has certain known peak periods (such as Tax Services), and as
such, has a few predictable resource usage "spikes" throughout the year.
Unpredictable Bursting. This is a workload that has unpredictable peaks.
Licensing. You also need to evaluate whether you can license your application for use in a virtual
environment. Reducing your licensing costs for multiple applications or operating systems could
provide significant savings and provide a strong financial case for using virtualization.
Availability requirements. Most organizations have some applications that must be available for users
almost always. Some applications provide built-in options for enabling high availability, while other
applications you cannot easily make highly available outside of a virtual machine environment. When
considering whether to virtualize a server, evaluate whether the application has high availability
options, whether those options are supported in a virtual machine environment, and whether you can
use failover clustering to make the virtual machine highly available.
Microsoft Assessment and Planning Toolkit

The Microsoft Assessment and Planning Toolkit (MAP) is the primary tool to help you identify which
applications, desktops, and servers would make ideal candidates for virtualization. MAP provides the
following functionality:
Hardware inventory. MAP uses a secure process, which does not utilize an agent, from a single
networked computer to collect and organize system resources and device information across your
network. Some of the examples of the information that MAP returns includes operating system
information, system memory details, installed drivers, and installed applications. MAP saves this
information in a local database, and then uses it to provide you with specific reports and
recommendations.
Data analysis. MAP performs a detailed analysis of hardware and device compatibility for migration to
Windows 7, Windows Server 2008 R2, Windows Server 2008, Microsoft Office 2010, Microsoft
Application Virtualization, and Windows Vista. The tool helps you gather performance metrics, and
generates server consolidation recommendations that identify the candidates for server virtualization
and suggests how you might place the physical servers in a virtualized environment. MAP also
includes a Microsoft Private Cloud Fast Track Consolidation Wizard, which matches your requirements
as identified in the hardware inventory to a cloud reference architecture.
Readiness reporting. MAP generates reports containing both summary and detailed assessment
results for each migration scenario. The results are provided in both Office Excel and Office Word
documents.
Question: What server workloads do you plan to virtualize in your organization? How will
you make the decisions about what to virtualize?
Designing for High Availability

For designing a private cloud that is highly available, you should consider the following four design
principles: compute, network, storage, and management.
Compute
Ensure that you have sufficient computing power to satisfy your requirements such as enough processors,
cores, random access memory (RAM), and bandwidth. Consider the following:
Provide sufficient cores, processors, and memory to satisfy your applications needs.
Provide fast throughput to your storage system. You can use serial attached Small Computer System
Interface (SCSI)known as SASor serial ATA (SATA) for direct attached disks. However, we
recommend using Fibre Channel, internet SCSI (iSCSI) or Fibre Channel over Ethernet (FCoE) for a
storage system. The key consideration here is that you need to have high I/O throughput and low
latency.
Network
The network between the physical clients and the servers is crucial for the service. Thus, the network
should provide sufficient bandwidth, and should provide redundancy so a single outage of a component
(such as a network switch) does not cause a server outage. Consider the following:
Provide a network with sufficient bandwidth to satisfy all computing requirements. For example, if
you use graphic-intensive CAD applications, you might need to consider more bandwidth than you
would for a simple account application.
Each server must be highly available with multiple network interface cards (NICs) and virtual NICs. If
one NIC fails, the other can take over so failure does not affect the service.
Network redundancy throughout the existing network infrastructure is crucial. You should consider
switches, routers, load-balancers, and other components that should be configured for failover.
Storage
Provide a storage system with sufficient throughput and data redundancy. Do not use storage in which a
single disk outage can cause outage of a full service. Consider the following:
Provide a high level of disk I/O and throughput.
Make sure the storage I/O is isolated from the network I/O.
Provide redundancy for your disks such as with RAID1 and RAID5.
Provide shared disk access, such as a clustered shared volume for Hyper-V clustering.
Management
Management tools for the private cloud are crucial for a highly available virtual environment. The System
Center 2012 suite provides you with several components:
Hyper-V clustering and live migration. Hyper-V together with VMM can move virtual machines
between hosts without affecting users.
Bare-metal deployment to the private cloud infrastructure. VMM can not only boot a bare-metal
machine, but also set up and join the machine to the infrastructure so that it can be used to run
virtual machines. You can use Operations Manager to monitor resources and trigger the setup.
Provisioning and de-provisioning. VMM together with Service Manager can provide self-service for
virtual machines or services that are supplied on demand. You can use Orchestrator with VMM and
Service Manager to automate the process. Additionally, you can use Operations Manager to monitor
the process and issue alerts when a failure occurs.
Infrastructure monitoring. Operations Manager can monitor the private cloud infrastructure and,
when a failure occurs, can issue an alert that causes VMM to move the components to alternate
servers and data centers.
Resource optimization. VMM together with Operations Manager can use a feature called
Performance and Resource Optimization (PRO) to enable you to migrate virtual machines between
physical hosts when certain performance thresholds are reached.
Question: Which design principle would be the most important for your own organizations
private cloud design? Why?
Designing for Scalability

Designing for scalability requires not only having sufficient computing resources, but also having an
automated way to provide additional resources when a virtual machine or application requires them. For
this reason, the System Center 2012 components provide tightly integrated functionality.
Integrating Service Manager with VMM and Orchestrator

The System Center Cloud Services Process Pack facilitates private cloud capacity requests from your
business unit IT application owners and end users. It also includes a set of standardized processes for
requesting and managing private cloud services, including the ability to define projects, capacity pools,
and virtual machines.
Integrating VMM with Operations Manager

By integrating VMM with Operations Manager, you can monitor the various components of VMM by
using the Operations console. You can use a number of monitoring views to check the health of the VMM
environment. For example, the Cloud Health state view shows the health state of each business unit cloud.
Other health state views include Host Health and Service Health.
Integration also allows you to use the PRO tips feature, which automates tasks with VMM based on the
state of the virtualized environment. For example, when an alert in Operations Manager generates
because of poor service performance from an end-user perspective, a PRO-enabled management pack
automatically starts a task in VMM that scales the service by adding new service tiers.
Integrating Orchestrator with Other System Center Components

Orchestrator has a number of built-in runbook activities that perform a wide range of functions that you
can extend with Orchestrator integration packs. Orchestrator integrations packs contain additional
runbook activities that provide Orchestrator with the ability to extend its capabilities to other Microsoft
and non-Microsoft components. The Orchestrator integration pack for Service Manager includes activities
that enable Orchestrator to obtain details about incidents and problems that have been generated in the
Service Manager environment.
This integration provides a useful mechanism in automating tasks with Service Manager. For example, you
can create a runbook in Orchestrator that creates a problem record in Service Manager when the number
of related incidents reaches a specified number. The Orchestrator integration pack for DPM includes
activities that enable you to automate tasks within the DPM environment. For example, you can create an
Orchestrator runbook that automates data source protection (such as SQL Server protection) for a new
service being deployed in VMM.
Integrating Service Manager with Other System Center Components

Service Manager provides two types of connectors for Operations Manager:
Operations Manager Alert Connector. When you configure this connector, it automatically generates
Service Manager Incidents when subscription-based alerts generate in Operations Manager. For
example, you can have incidents generate automatically, based on critical alerts that are raised in
Operations Manager, that relate to a SQL Server that is used by a particular service tier.
Operations Manager Configuration Item Connector. This connector collects discovered objects from
Operations Manager, and then imports them as configuration items in the Service Manager database.
For example, you can create a business service model in Service Manager for distributed applications
that have been created in Operations Manager to represent application components that are being
monitored within a service. This can be useful when you try to define relationships between service
components and other configuration items.
For VMM, a Service Manager connector enables you to import VMM objects such as clouds, templates,
and virtual machines. You can then use these objects to create service offerings in Service Manager. For
example, a business group is planning a big marketing campaign that will drive up usage for an
application in the private cloud. The business group can use Service Manager to create a request for more
resources, which VMM then deploys automatically.
For Orchestrator, a Service Manager connector enables you to invoke Orchestrator runbooks from within
Service Manager through the use of workflows. You can import Orchestrator runbooks into Service
Manager through the Service Manager connector, and then use the runbooks for automation activities.
For example, a user can submit a service fulfillment request for a new service in a business unit cloud to a
business unit IT administrator through the self-service portal with an Orchestrator runbook, which after
approval, will automatically provision the service.
Designing for Business Continuity

Business continuity ensures that your business operations can continue in the case of internal and external
threats, such as a data center loss. If you move your data center to the private cloud, you should also be
concerned about how your operations will continue if such a threat arises.
The following private cloud options provide business continuity:

On-premises private cloud. Build a private cloud infrastructure on-premises for your organization.
You can use resources such as the Hyper-V cloud deployment guides to help you plan for the private
cloud. Optionally, Microsoft can help you with assessments, proofs-of-concept, and deployments
through partners or Microsoft Services. For business continuity, you should plan and implement more
than one data center. Additionally, consider replication or backup between two or more data centers,
or consider offsite backup storage.
Preconfigured private cloud. Use a pre-validated private cloud that includes a hardware and software
configuration from Microsoft Private Cloud Fast Track original equipment manufacturers (OEM)
partner such as Dell, IBM, and HP. For business continuity, you should provide the necessary
requirements to your OEM partner. Some OEM partners also provide a mixed preconfigured and
hosted private cloud that allows you to back up your virtual machines to a hosted cloud.
Hosted private cloud. Use a hosted private cloud service provider to provide you with an off-premises
private cloud. You order what you need and you are assigned your own, dedicated private cloud. For
business continuity, this option automatically provides the highest standard of business continuity
because a hosted private cloud is already designed to overcome most threats, such as data center
outages.
Designing for Disaster Recovery

Disaster recovery is a crucial design consideration when you are planning for the private cloud. You must
ensure that you do not lose applications and data when a failure occurs. Some important considerations
for disaster recovery include:
Decide which applications and data you need to back up. Consider how to group backups according
to the services they provide, which services and data you require, and which services do not need to
be backed up, because, for example, they are shared.
Verify that your backup was successful. You must ensure that backups are completing successfully. As
a best practice, we recommend implementing a monitoring tool that can verify the backups.
Understand how to restore applications and data quickly when a failure occurs. Ensure that your
administrators understand how to restore applications and data. For example, you could provide a
periodic disaster recovery workshop in which your administrators perform a full restore.
You can use DPM to backup and restore applications and data in your private cloud.
Note Performing backup and restore using DPM is described in detail in Module 11.
Lesson 4
Overview of System Center 2012 Components
To design and deploy a private cloud you require different tools to manage, monitor, and deploy virtual
machines and services. The System Center 2012 suite provides you with many tools to create a private
cloud.
This lesson provides an overview of the System Center 2012 private cloud creation and management
products.

Describe VMM.
Describe App Controller.
Describe Service Manager.
Describe Orchestrator.
Describe Operations Manager.
Describe DPM.
VMM Overview
VMM is a management solution for the virtualized data center. VMM enables you to configure and
manage your virtualization host, networking, and storage resources to create and deploy virtual machines
and services to private clouds.
VMM provides the following features:

Multi-host and multivendor virtual machine management support. You can host your virtual
machines on several virtual machine managers, such as Microsoft Hyper-V and VMware ESX servers.
All hardware that these virtual machine managers support are also supported for VMM virtual
machine placement.
Intelligent placement. VMM provides resources that can help you decide on the best available host
for a new virtual machine.
PRO. PRO allows you to react to alerts sent by Operations Manager so that you can move avirtual
machines to other hosts, which allows you to maintain performance continuity.
Physical-to-virtual machine (P2V) conversion. VMM allows you to convert a physical machine to a
virtual machine.
Microsoft Application Virtualization Management Server (Server App-V) support. VMM allows you to
virtualize server applications.
Live migration. In VMM, you can move virtual machines to different host machines without impacting
the users.
Delegated administration. You can delegate administrative tasks to users, and allow them to create
and manage virtual machines on their own.
Cloud, infrastructure, and services management. VMM allows you to manage your cloud and services
from a single console.
Power optimization. VMM can optimize hosts by moving virtual machines from underused hosts and
then powering off the host machine.
Note VMM is discussed in detail in Module 4 and Module 5.

App Controller Overview

Using App Controller, you can manage private clouds that are created with VMM, and public clouds that
are running on the Windows Azure platform.
App Controller provides role-based views that administrators can customize for the application owner.
This allows the application owner to manage the services that are deployed into the private and public
clouds. For example, the application owner can deploy a service to the private cloud. The owner can also
scale the service in or out, depending on their requirements. Additionally, the owner can connect to
virtual machines in the private cloud directly from the App Controller portal.
Managing Private Clouds

After the App Controller portal is connected to the VMM environment, the business unit clouds, virtual
machines, and libraries become available through the App Controller portal.
Private cloud administrators can create services and service templates from within VMM and then deploy
them to the private cloud. Business unit IT administrators can then manage and deploy these services and
service templates through the App Controller portal.
App Controller also helps users manage the individual virtual machines that are running within a service.
All of the typical VMM management capabilitiessuch as stopping, starting, mounting an ISO image, and
opening a remote desktop connectionare available to the user. Because the App Controller functionality
is delivered under the context of the service, the user only has access to the resources within it.
Managing Public Clouds

When connecting App Controller to a Windows Azure subscription, you can delegate subscription access
out to users through their AD DS credentials. This provides a common access model across the
management of private and public clouds, including the services that are running in them.
For example, you can manage the development of a service that is running in the Windows Azure
environment while managing a production implementation of a service that is running in your private
cloud environment.
You can also use App Controller to move applications between private and public clouds, and copy
resources such as service templates between VMM servers.
Note App Controller is discussed in detail in Module 6.

Service Manager Overview

Service Manager is a comprehensive, IT service management solution that you can use to add process-
driven automation and self-service infrastructure provisioning to your private cloud infrastructure.
Service Manager provides several key benefits to your organization including increased productivity,
reduced costs, swifter problem resolution, and built-in compliance management. Built-in processes in
Service Manager are based on industry best practices such as those found in the IT Infrastructure Library
(ITIL) and the Microsoft Operations Framework (MOF).
Service Manager comes enabled with process management packs for incident and problem resolution,
service request provisioning, change and release control, and configuration and knowledge management.
Through its integration with other System Center components and key infrastructure services such as
AD DS, Service Manager provides accurate configuration management database population and private
cloud process integration.
By using Service Manager, you can:
Reduce the mean time to resolve issues through a self-service user experience.
Improve private cloud efficiency through centralized management of incident, problem, and change
processes.
Provide self-service deployment of private cloud resources through integration with other System
Center 2012 components.
Implement effective compliance controls for the management of private cloud infrastructure
components.
Note Service Manager is discussed in detail in Module 9.

Orchestrator Overview
Orchestrator, formally known as Opalis, is an IT process automation solution for the private cloud that you
can use to automate the creation, monitoring, and deployment of key resources in your environment.
Private cloud administrators perform many critical daily tasks to ensure that their infrastructure is highly
available and reliable. They also require the ability to reduce the time it takes to provision new
infrastructure, while providing self-service capabilities to end users. Additionally, the administrators must
maintain quality standards and system efficiency. Orchestrator can combine disparate tasks and
procedures together by using the GUI Runbook Designer to create reliable, flexible, and efficient end-to-
end solutions in the private cloud environment.
By using Orchestrator, you can:
Automate processes in your private cloud, regardless of hardware or platform.

Automate your private cloud operations and standardize best practices to improve operational
efficiency.
Connect different systems from different vendors without having to know how to use scripting and
programming languages.
Note Orchestrator is discussed in detail in Module 12.

Operations Manager Overview

Operations Manager allows you to monitor services, devices, and operations for many computers from a
single console. Operators can gain immediate insight into the state of the IT environment and the IT
services that are running across different systems and workloads by using numerous views that show state,
health, performance information, and alerts generated for availability, performance, configuration, and
security situations.
IT departments today are responsible for ensuring the performance and availability of critical services and
applications. That means that IT departments need to know when there is a problem, identify where the
problem is, and figure out what is causing the problem, ideally before the users of the applications
encounter the problems. The more computers and devices in the business, the more challenging this task
becomes.
Operations Manager will display monitored objects that are not healthy, send alerts (such as a short text
message or e-mail) when problems are identified, and provide information to help you identify the cause
of a problem and possible solutions.
Note Operations Manager is discussed in detail in Module 7 and Module 8.

DPM Overview
DPM provides disk-based and tape-based data protection and recovery for servers such as SQL Server,
Exchange Server, SharePoint, virtual servers, file servers, and support for Windows operating system
desktops and laptops. DPM can also centrally manage system state and bare-metal recovery.
By using DPM, you can:

Recover bare-metal servers and desktops running Windows operating systems. This allows you to
quickly recover servers and desktops without first installing the operating system.
Back up and recover from disk or tape. Depending on the backup storage type that is available, you
can decide whether you want to store it on disk or in a tape library.
Centrally manage the DPM servers with the administration console. In larger environments, it is
especially beneficial to manage all the DPM servers from a central console.
Use role-based access permissions to distribute backup and restore management. You can assign
permissions to users so that they can restore the systems for which they are responsible. The benefit is
that you do not grant them full permissions, so they will not be able to access data that they do not
own.
Perform quick item-level recovery for virtual machines. To recover a specific item such as a file, you
do not need to recover the entire virtual machine. Instead, you can just recover the particular file..
Note DPM is discussed in detail in Module 11.

Lesson 5
Deploying Hyper-V Clustering with VMM
Using VMM, you can now use a Hyper-V host cluster to manage virtual machines, and configure and
manage host machines. This is crucial for private cloud platforms, because it allows you to move virtual
machines and their applications quickly between physical hosts and data centers. Therefore, you should
consider Hyper-V clustering a basic requirement when you are planning and implementing a private
cloud.
In this lesson, you will learn about the requirements for a Hyper-V host cluster, an how to create a host
cluster using VMM.
Describe the prerequisites for cluster deployment.

Describe the cluster creation process in VMM.
Create a Hyper-V host cluster in VMM.
Verify a successful Hyper-V host cluster deployment.

Cluster Deployment Prerequisites

A cluster demands much more attention than a typical Hyper-V host. Not only does the cluster require
hardware specifications, the cluster also requires certain configuration settings on every host computer
before you can use it as a cluster node. For this reason you should consider the following prerequisites
before deploying a cluster in VMM:
Hosts must be managed by VMM and belong to the same VMM host group. You cannot create a
cluster out of hosts that are in different host groups.
The hosts must run either Windows Server 2008 R2 Enterprise or Windows Server 2008 R2 Datacenter
editions, because these are the only two Windows Server editions that support the failover clustering
feature, which is required to configure a Hyper-V host cluster.
Hosts must belong to the same domain.

Hosts must meet all failover clustering requirements, including those for hardware, processor type,
memory. You cannot cluster two systems that do not have the same processor type. For example, if
one server runs on Intel processors, you must ensure that the other node does not run on AMD
processors. They must be the same for clustering to work.
Shared storage must be presented to all hosts in the cluster. You can preconfigure logical unit
numbers (LUNs) or use VMM to manage shared storage for the cluster.
Each host must have access to the storage array. This is a physical requirement, and you have to
ensure that all hosts can access the storage array using features such as Multipath I/O (MPIO).
Hosts must belong to the same Active Directory site and the same IP subnet, and be configured with
a static IP address.
Once all these requirements are satisfied, you should be able to install and configure the cluster
accordingly.
Creating Clusters in VMM

To create a Hyper-V host cluster, you use the Create Hyper-V Cluster Wizard. Through the wizard, you can
select which Hyper-V hosts to cluster, and configure the networking and storage resources that are used
during cluster creation. VMM then performs the following tasks:
Validate each host that meets the prerequisites, such as the required operating system and domain
membership.
Enable the failover clustering feature on each host.
Unmask the selected storage logical units to each host

Create the configured external virtual networks.
Run the cluster validation process.
Create the cluster with a quorum, and enables clustered shared volumes..
For each LUN that is designated as a clustered shared volume, assigns the logical unit as a clustered
shared volume on the cluster.
The benefit of using VMM for creating a Hyper-V host cluster is that you can use Windows PowerShell to
script the process. This allows you to automatically create or extend a Hyper-V host cluster as needed.
Question: Do you use the failover clustering feature in your organization? If so, do you
experience challenges when using it?
Creating a Hyper-V Host Cluster in VMM

You can create a Hyper-V host cluster directly from the VMM console, as follows:
1. Connect to the VMM console.
2. Add the System Center Virtual Machine Manager agents to all Hyper-V hosts that you want to cluster.
3. In the VMM console, in the ribbon, click Create, and then click Hyper-V Cluster to open the Create
Hyper-V Cluster Wizard.
4. In the wizard, configure the following:
Cluster name. The name of the Hyper-V host cluster.

Hyper-V host nodes. The nodes that you want to add to the cluster. You must define at least two
nodes, and there is a maximum of 16 nodes per cluster.
Storage disk(s). Select the disks that you want to use for the cluster.
Virtual network(s). Define the virtual network that you want to use for the cluster
After you complete the Create Hyper-V Cluster Wizard, VMM creates a job and installs the cluster.
Verifying a Successful Hyper-V Host Cluster Deployment

During and after cluster installation, you can verify the installation status. To do this, in the VMM console,
in the Jobs workspace, locate the Install cluster job. This area displays information about each installation
step, and whether the step completed successfully.
In addition, when the cluster installation completes, you can confirm successful Hyper-V host cluster
deployment by:
Checking the cluster properties. The Status item displays the status of all cluster nodes, and provides a
link to the last cluster validation report.
Running Validate Cluster manually. You will find the cluster validation report in the
%windir%\Reports\Cluster folder or as noted in the Validate cluster job in the Jobs workspace.
The most common method for verifying the status of the cluster is to access the status page through the
clusters properties.
Lab: Planning for the Private Cloud

Lab Setup
For this lab, you will use the available virtual machine environment. Before you begin the lab, you must
complete the following steps:
1. On LON-HOST1, click Start, point to Administrative Tools, and then click Hyper-V Manager.
2. In Hyper-V Manager, click 10751A-LON-DC1, and in the Actions pane, click Start.
3. In the Actions pane, click Connect. Wait until the virtual machine starts.
4. Log on using the following credentials:
User name: Administrator
Password: Pa$$w0rd
Domain: Contoso
5. Repeat steps 2 to 4 for 10751A-LON-SQ1.
6. On LON-HOST2, click Start, point to Administrative Tools, and then click Hyper-V Manager.
7. In Hyper-V Manager, click 10751A-LON-VM1, and in the Actions pane, click Start.
Password: Pa$$w0rd
Domain: Contoso
Lab Scenario
You have been asked by Contoso, Ltd to begin planning for the private cloud. The business requires that
the private cloud infrastructure be highly available.
Virtualization is the fundamental building block for any private cloud infrastructure and as such, you have
provisioned two Hyper-V hosts. You must now cluster those hosts for high availability.
Exercise 1: Deploying the Virtual Machine Manager Agent

Scenario
You recognize that the provisioned Hyper-V hosts are not managed using VMM. You need to add them
to VMM so that you can manage the hosts.
The main tasks for this exercise are as follows:
1. Open the VMM console.
2. Deploy the Virtual Machine Manager agent to the hosts.
X Task 1: Open the VMM console

On LON-VM1, on the desktop, double-click Virtual Machine Manager Console. Configure the
console to automatically connect using the current Microsoft Windows session identity.
X Task 2: Deploy the Virtual Machine Manager agent to the hosts

1. In the VMM console, in the VMs and Services workspace, right-click All Hosts, and then click Add
Hyper-V Hosts and Clusters.
2. In the Add Resource Wizard, use the following options:
Windows Server computers in a trusted Active Directory domain with the following
credentials:
User name: Contoso\administrator
Password: Pa$$w0rd
Specify an Active Directory query to search for Windows Server computers:
Generate an AD query with Computer name: *host*
Discovered computers: Lon-host1.contoso.com and Lon-host2.contoso.com
3. In the Jobs window, wait until all jobs display Status as Completed.
Results: After this exercise, you should have deployed the Virtual Machine Manager agent to the host
machines.
Exercise 2: Creating a Hyper-V Host Cluster Using VMM

Scenario
The two Hyper-V host machines are not yet prepared for a cluster, because they do not have iSCSI
configured properly. You need to configure iSCSI, and then create a Hyper-V host cluster with these hosts.
1. Configure the iSCSI target software on LON-HOST1.
2. Configure the iSCSI target software on LON-HOST2.

3. Create a Hyper-V host cluster in VMM.
X Task 1: Configure the iSCSI target software on LON-HOST1

1. On LON-HOST1, click Start, point to Administrative Tools, and then click iSCSI Initiator.
2. If prompted by a dialog box to start the Microsoft iSCSI service, click Yes.
3. In the iSCSI Initiator Properties dialog box, click the Discovery tab, and then click Discover Portal.
4. In the IP address or DNS name text box, type 10.10.0.10 with port 3260.
5. On the Targets tab, select iqn.1991-05.com.microsoft:lon-dc1-lon-host1-target, and then click

Connect.
6. Enable the following:
Add this connection to the list of Favorite Targets
Enable multi-path
X Task 2: Configure the iSCSI target software on LON-HOST2

1. On LON-HOST2, click Start, point to Administrative Tools, and then click iSCSI Initiator.
2. If prompted by a dialog box to start the Microsoft iSCSI service, click Yes.
3. In the iSCSI Initiator Properties dialog box, click the Discovery tab, and then click Discover Portal.
4. In the IP address or DNS name text box, type 10.10.0.10 with port 3260.
5. On the Targets tab, select iqn.1991-05.com.microsoft:lon-dc1-lon-host2-target, and then click

Connect.
6. Enable the following:
Add this connection to the list of Favorite Targets
Enable multi-path
7. From the VMs and Services workspace, refresh both Lon-host1 and Lon-host2.
X Task 3: Create a Hyper-V host cluster in VMM

1. On LON-VM1, in the VMM console, click the Fabric workspace.
2. In the ribbon, click Create, and then click Hyper-V Cluster.
3. In the Create Hyper-V Cluster Wizard, configure the following:
Cluster name: LON-CLUSTER01
User name: Contoso\administrator
Password: Pa$$w0rd
Hosts to cluster: lon-host1.contoso.com and lon-host2.contoso.com
Network: 10.10.0.0/16
IP Address: 10.10.0.15
Storage: Quick Format and CSV selected on all listed disks
4. In the Jobs window, wait until Install cluster job shows Status Completed w/ Info, then close the
window. This might take approximately 15 minutes to complete.
Results: After this exercise, you should have created a Hyper-V host cluster using VMM.
Module Review and Takeaways

Review Questions
1. What is a private cloud?
2. What components does System Center 2012 offer for your private cloud?
3. How can you monitor your private cloud?

2-1
Module 2
Private Cloud Configuration and Deployment with System
Center Virtual Machine Manager
Contents:
Lesson 1: VMM Architecture and Components Overview 2-3
Lesson 2: Installing and Upgrading Virtual Machine Manager 2-18

Lesson 3: Configuring VMM Security and Roles 2-26
Lesson 4: Understanding Host Groups 2-33
Lab: Configuring and Deploying the Private Cloud Infrastructure 2-44

2-2 Private Cloud Configuration andd Deployment with System
S Center Virtual Machine Manager
Module Overrview
Creaating a private
e cloud infrastrructure is an im
mportant part of the cloud ccomputing con ncept. Private cloud
infra
astructure is a collection of various
v compo onents such ass hardware, sofftware, configuurations, profilles,
instances, and con nnectivity thatt together run within the datta center. In orrder to build a private cloud
d
infra
astructure, youu will need to learn about thhe software an d technologiees that are avaiilable to help yyou
achieve this goal.
In th
his module, yo
ou will learn ho
ow to build a private
p cloud i nfrastructure b
by using Micro
osoft System
m
Cennter 2012 - Virttual Machine Manager
M (VMM M).
Afte y will be able to:

er completing this module, you
Describe VMM e and components.

M architecture
Install and up
pgrade VMM.
Configure VM
MM security an
nd roles.
Understand host
h groups.
10751A: Coonfiguring and Deplooying a Private Cloudd with System Centerr 2012 2-3
Lesson
n1
VMM
M Architecture and
a Components Ove
erview
VMM has chang ged significanttly from the Syystem Center VVirtual Machin ne Manager 20008 version. VM
MM has
many
m new components and architectural
a cooncepts. Beforre starting to p ement the VMM
plan and imple
in
nfrastructure, you
y should learn about its ke ey componentts and architeccture.
In
n this lesson, yo
ou will learn about VMM arcchitecture, whaat componentts you can include in it, and how to
deeploy virtual machines
m in yo
our VMM.
After completin
ng this lesson, you
y will be able to:
Describe VM
MM architectu
ure.
Describe th
he VMs and Services tab.
Describe prrivate cloud infrastructure co

omponents in VMM.
Describe VM
MM libraries.
Describe jobs in VMM.
Describe VM
MM settings.
Deploy virtual machines in

i VMM.
VM
MM Architecture
VMM is a manage ement solutionn for a virtualizzed data centeer. VMM enables you to creaate and deployy
virtu
ual machines and
a services too private cloud ds by configuriing and managging your virtu
ualization hostt,
netwworking, and storage
s resourrces.
VMM is a compon nent of Microssoft System Ce

enter 2012, andd manages poolicies, processe
es, and best
pracctices with auttomations by discovering,
d ca nowledge of viirtualization
apturing and aaggregating kn
infra
astructure.
VMM succeeds VM MM 2008 R2 and a is a key coomponent in e nabling privatte cloud infrasttructure which
h
help
ps transition ennterprise IT fro
om an infrastru
ucture-focused
d deployment model into a service-oriente ed,
userr-centric environment.
VMM architecture everal differentt, interrelated components. These compon

e consists of se nents are:
Managementt server. The management

m se
erver is the com
mputer on which the VMM sservice runs. T
The
managementt server processses commands and controlss communicatiions with the V VMM database e, the
library server,, and the virtual machine ho
osts. The VMM server is the h
hub of a VMM
M deployment
through whicch all other VM MM componen nts interact and
d communicatte. The VMM sserver also con
nnects
to a Microsofft SQL Server database (VMMM database) that stores all VMM configuuration information.
Database. VM MM uses a SQLL Server databa ase to store th

he informationn that you vieww in the VMM
managementt console, such h as managed virtual
v machin nes, virtual macchine hosts, virtual machine
libraries, jobs, and other virrtual machine--related data.
Managementt console. The management

m console is a prrogram that yo ou use to connnect to a VMMM
managementt server, to view w and manage e physical and virtual resourrces, including virtual machin
ne
hosts, virtual machines, servvices, and libra
ary resources.
Library. A librrary is a catalog of resourcess (for example,, virtual hard d

disks, template
es, and profiless), that
are used to deploy virtual machines
m and services. A librrary server also
o hosts shared folders that sttore
file-based resources in the VMM library. The VMM Management server is always the default library
server, but you can add additional library servers later.
Command Shell. Windows PowerShell is the command-line interface into which you use cmdlets
that perform all available VMM functions. You can use these VMMspecific cmdlets to manage all the
actions in a VMM environment.
Self-Service Portal. The self-service portal is a web site that users who are assigned to a self-service
user role can use to deploy and manage their own virtual machines.
All the components described in the preceding section form the VMM architecture; by mutually
interacting, they enable you to deploy your private cloud solution.
The VMs and

d Services Tab in VM
MM
The VMM management console e is divided intto several partts. Each part grroups similar rresources that
enable you to build a virtual priivate cloud envvironment. Th e VMs and Services tab provvides you with h the
ability to view, add, and manage virtual mach hine hosts, virtuual machines, and services. W When deploying a
VMM infrastructure, this is usua
ally the starting
g point for buiilding a privatee cloud.
Within the VMs and Services tab

b, you can do following:
Add hosts and d create host groups.
g You can add VMM m managed physiical hosts when you deploy V VMM.
Hosts and host groups are important parrts of the VMM M infrastructuree. A virtual maachine host is a
physical computer that hossts one or more virtual mach hines. A host co omputer can rrun different
virtualization platforms, succh as Hyper-V , Microsoft VVirtual Server, XXEN Server or VMWare. With
VMM, you can create custo om groups of virtual
v machinee hosts, known n as host group
ps, for organizzing
hosts and theeir virtual machhines. For exammple, you mig ht create a ho ost group for e
each of your
organizations branch office es. Or, you cann create a hostt group to organize hosts that are part of the
same private cloud. When you y create a private
p cloud, yyou select whicch host groups will be part o of the
private cloud. You can then n allocate all or some of the resources from m the selectedd host groups tto the
private cloud. You should beb aware that several
s setting
gs and resourcees are assigned d at the host ggroup
level, such as:: custom place
ement rules, ho ost reserve setttings for placeement, dynamic optimization and
power optimiization settings, network resource inheritaance, host grou up storage allo
ocation, and cuustom
properties.
Create and manage

m virtual machines. Whhen you add a host to the VM
MM Console yyou will be able
e to
manage existting as well as newly created machines.
Create and manage
m privatee clouds. A privvate cloud is a cloud that is p nd managed on-
provisioned an
premise by an n organization n or is hosted by
b a service prrovider. An org ganization dep
ploys their privvate
cloud using their own hardware. Through h VMM, an org ganization can n manage the private cloud
definition, acccess to the privvate cloud, and the underlyiing physical reesources.
Create and manage services. In VMM, a service is a set of virtual machines, settings and applications
that you configure and deploy together, and that you manage as a single entity for example, when
you carry out a deployment of a multi-tier line-of-business (LOB) application. In the VMM console,
you use the Service Template Designer to create a service template, which defines the configuration
of the service. The service template includes information about the virtual machines that are deployed
as part of the service, which applications to install on the virtual machines, and the networking
configuration necessary for the service (including using load balancing). The service template can
make use of existing virtual machine templates, or you can define the service without using any
existing virtual machine templates.
Priivate Cloud
d Infrastru
ucture Com
mponents in VMM
The key architectu

ural concept in
n VMM is privaate cloud infraastructure. Sim
milar to public ccloud solutions such
as in
n Windows Azzure, private cloud infrastru
ucture in VMM M is an abstracttion layer thatt shields the
undderlying technical complexities, and provid
des the ability tto manage deefined resource e pools of servvers,
netwworking, and storage
s in the associated entterprise infrasttructure.
Thiss concept is presented expliccitly in the VMM 2012 mana gement conso ole user interfaace. With VMM
M
2012, you can cre eate a private cloud
c from Hyper-V, VMwarre ESX, and Cittrix XenServer hosts, and ben nefit
from
m cloud computing attribute es including seelf-servicing, reesource poolin
ng, and elasticiity.
You
u can configure
e the following
g resources fro
om the VMM m
management cconsole Fabricc pane:
Servers. In the
e Servers nodee, you can configure and maanage several ttypes of serverrs. Host groups
contain virtuaalization hosts as the destina
ations for wherre to deploy vvirtual machine es. Library servvers
are the repositories of build
ding blocks succh as images, .iso files, and ttemplates, for creating virtuaal
machines. To deploy Hyperr-V hosts on ba are-metal macchines automaatically and bo oot a virtual
machine from m bare-metal remotely
r via neetworks, use P
Preboot Executtion Environme ent (PXE) serve ers
such as Windows Deployment Services to initiate thee operating sysstem installatio on on a physiccal
computer. Up pdate servers such
s as Windo ows Server Upddate Services (W WSUS) servicee virtual machines
automaticallyy based on com mpliance policies. For intero perability, the VMM 2012 ad dmin console ccan
add VMware vCenter servers to enable th he manageme nt of VMware ESX hosts.
Networking. In VMM 2012, the Networkin ng pool is wheere you can: deefine logical networks, assign
pools of staticc IPs and media access control (MAC) add dresses, and inttegrate load bbalancers. Logiccal
networks are user-defined groupings
g of IP subnets and d virtual local aarea networks (VLANs) to
organize and simplify netw work assignmen nts. Logical nettworks providee an abstractio on of the
underlying ph hysical infrastrructure and en
nable an admin nistrator to proovision and iso
olate network ttraffic
based on seleected criteria liike connectivitty properties, aand service-levvel agreementts (SLAs).
Storage. Using the VMM 2012 admin console, an administrator can discover, classify, and provision
remote storage on supported storage arrays. VMM 2012 uses the Microsoft Storage Management
Service (which is enabled by default during the installation of VMM 2012), to communicate with
external arrays. An administrator must install a supported Storage Management Initiative
Specification (SMI-S) provider on an available server, and then add the provider to VMM 2012. SMI-S
is a storage standard for operating among heterogeneous storage systems. VMM 2012 automates the
assignment of storage to a Hyper-V host or Hyper-V host cluster, and then tracks the storage that is
managed by VMM. Note that storage automation through VMM 2012 is only supported for Hyper-V
hosts.
2-10 Private Cloud Configuration and Deployment with System Center Virtuual Machine Manage r
VM
MM Librariies
The VMM library is one of the main

m compone ents of VMM 22012, and is a rresource catalo
og that you caan use
to build
b virtual ma
achines, servicces, and private
e clouds. The llibrary contain
ns componentss such as tempplates,
opeerating system profiles, and hardware
h profiles that the V MM database stores.
The VMM library catalogs all resources that you use when ccreating new vvirtual machine
es. Therefore, some
orga
anizations mayy find it very im
mportant for the
t library to b
be highly availaable.
Lib
brary Resourrces
The VMM library provides accesss to file-based d resources thaat you need to o build virtual machines. Theese
file--based resourcces can includee Sysprep scrip
pts, Internation nal Organizatio on for Standarrdization (ISO)
images, and virtua al hard disks th
hat your librarry servers storee. In addition, ffrom the VMMM library, you ccan
man nage virtual machine templa ates, guest ope erating systemm profiles, and hardware proffiles that reside e in
the VMM databasse. You also ca an store virtual machines in tthe library wheen you are nott using them, aas
welll as service tem
mplates.
Onee of the benefiits of VMM is that

t you can use
u libraries to simplify virtuaal machine creeation by
centtralizing all ne
ecessary resourrces in one loccation. You can
n store a varietty of compone entssuch as vvirtual
disk
ks, virtual DVDs, operating syystem templates, and hardw ware profilesiin a VMM libraary. Then when you
crea
ate a virtual machine, the pre econfigured co omponents arre immediatelyy available to yyou. This make es
crea
ating virtual machines much faster and sim mpler than if yoou had to creaate them manu ually every tim
me.
The VMM 2012 lib brary contains templates forr services deplooyment, profil es for applicattions and operrating
systems, and resources being ussed to build prrivate cloud so olution. You caan also use thee VMM library to
view
w Updates Catalog if it is connnected to the e Microsoft Sysstem Center 20 012 Configuraation Managerr or
WSUUS server.
Library Server and Shares

The VMM library is hosted on a VMM library server. When you install VMM, the VMM server is configured
as the default library server. The VMM server indexes files that are stored on library shares. You cannot
remove or modify the default library server that is created during the installation process. However, you
can add additional library servers, if necessary.
Each library server can have one or more library shares. A library share is a file share that physically
contains the resources that you use to build virtual machines. When you add a new library share, the
wizard does not create the share for you; instead, you must create and configure a file share before
adding it as a new library share.
You can organize content in a library share by creating subfolders, just as you create folders in a file share.
However, the folders will not appear in the VMM management console if they do not have any content.
Job
bs in VMM
M
VMM creates a job whenever yo ou perform anny action that cchanges a man
naged objectss status in VMM.
You
u can track these units of work in the Jobs view.
Deffinition of a Job
Jobss are compose ed of steps perrformed seque
entially to com
mplete an actio
on. Some jobs, such as when you
start or stop a virttual machine or
o refresh the view
v in the VM
MM Administraator Console, cconsist of onlyy a
sing
gle step. Otherr jobs, such as when you movve a virtual maachine from o ne host to anoother, create se
everal
addditional steps too make up thee one high-level job. Most w
wizards that you run in the VMM Administrrator
Connsole create jobs with multip ple steps.
How VMM Perrforms Jobss

VMM performs an nd logs each joob as an indep
pendent task. TThe steps with
hin a job may h
have dependenncies
on other
o steps witthin the job, but jobs are designed to be inndependent. A job cannot ddepend on anoother
jobs status. This means
m that youu can start mu
ultiple jobs with
hin the VMM AAdministrator Console, and the
jobss can run asynchronously.
Wheen you start a job in the VMM Administrattor Console, V VMM verifies th hat you have tthe required
perm
missions to run n the job. Addditionally, the jo
ob may requirre credentials tto perform a sspecific task. Fo
or
exam
mple, when yo ou are converting a physical server to a virrtual machine, you must havve the required d
dentials to starrt the job, and then the job may
cred m require crredentials to pperform the tassk on the physsical
macchine.
Using Jobs
You can use jobs to view detailed information about a virtual machine that experienced some kind of
failure, and then you can use this information to determine how to repair the virtual machine. You can use
the Repair action for a virtual machine to either restart the job that caused the virtual machine to fail, or
return the virtual machine to the state that it was in before the job ran.
VMM jobs provide a complete list of all changes to the VMM environment. To get detailed information
about exact changes that were made to VMM objects by a job, you can access the jobs Change Tracking
tab. Depending on the job type, the Change Tracking tab may display either very little or very detailed
information. For example, when you refresh the view in the VMM Administrator Console, if no objects in
VMM have been modified since the previous refresh, the Change Tracking tab does not display any
information. However, if you move a virtual machine from one host to another, the Change Tracking tab
displays detailed information about all of the changes that occurred during the move.
VM
MM Manag
ger Setting
gs
Youu configure thee VMM Manag gement Server from the Setttings tab in th
he VMM Conso ole. From here, you
can configure gen neral settings for
f VMM, as wellw as Security roles and acco n also configure
ounts. You can
servvicing hours fo
or your servers,, and configuration providerrs.
Setttings groups within

w the Settings tab that you
y can config ure are:
General. In th
he General panne you can con nfigure networrk settings, VMMM guest agennt settings, and
d
Customer Exp perience Improovement Program settings. Y You can also mmanage VMM database
connections, configure Librrary refresh inttervals, define a port for VMConnect, and define an
administrativee contact person for SelfServvice Users.
Security. Secu
urity allows youu to define User roles and R un As Accountts. Security is p
part of the Setttings
pane. These features
f de the ability to delegate rig
provid ghts to perform
m some tasks w with hosts and
virtual machinnes, and also to
t use predefin ned accounts ((and password ds) for some taasks. User roless and
Run As accou unts will be discussed later in
n more detail.
Servicing Win
ndows. You cann use Servicing
g Windows to d define intervals for regular m
maintenance wwhen
your servers or
o virtual mach
hines are unavvailable. After ccreating a servvicing window,, you can subsscribe
resources for it.
Configuration n Providers. In the Configuration Providerss pane, you cann view configu
uration provide ers
that are installed in VMM for example, a configuratioon provider forr Microsoft Neetwork Load
Balancing (NLLB) or for out-of-band powe er managemen nt. A configuraation provider is a plug-in to
o
VMM that tra anslates VMM Windows Pow werShell commmands to appliccation program mming interfacce
(API) calls tha
at are specific to
t a type of load balancer orr baseboard m
management controller.
System Center Settings. You can configure connections to other System Center products, such as
Microsoft System Center 2012 - Operations Manager with System Center Settings. If you connect
VMM and Operations Manager, you will be able to use Performance and Resource Optimization
(PRO) technology. This technology enables VMM to move virtual machines automatically from one
host to another based on information about resource usage provided by Operations Manager.
De
eploying Virtual
V Macchines in VMM
V
Onee of the advantages of using

g a virtualized environment
e tthat is manageed by VMM is the flexibility tthat it
provvides to create
e and deploy new
n virtual ma
achines quicklyy.
Usin c create a new virtual macchine manuallyy with new co nfiguration settings and a new
ng VMM, you can
hard
d disk. You can
n then deploy the new virtua
al machine fro
om one of follo
owing sources::
An existing viirtual hard disk

k (VHD) file (blank or precon
nfigured)
A virtual machine template
e
A VMM librarry
Youu can create neew virtual machines either byy converting aan existing phyysical machine, or by cloning
g an
existing virtual ma
achine.
Cre
eating a New
w Virtual Machine
M from
m an Existin
ng VHD
You
u can create a new
n virtual maachine based on
o either a blaank VHD, or on
n a preconfigu
ured VHD that
contains a guest operating
o syste
em. VMM provvides two blan nk VHD templaates that you ccan use to creaate
new
w disks:
Blank Disk Small

S
Blank Disk Large

L
Youu can also use a blank VHD when

w you wantt to use an op erating system
m with a PXE. AAlternatively, yyou
can place an ISO image
i on a virrtual DVD-ROM M, and then innstall an opera ting system from scratch. Th his is
an effective
e way to build a virtu
ual machines source
s image, which you can n then use as a future template.
To install the operating system on such a virtuual machine, yyou can use ann ISO image file from the library
or from local disk, then map a physical
p drive from
f the host machine, or in
nitiate the gueest operating system
setu
up through a network
n service
e boot.
If you have a library of VHDs that you want to leverage in your VMM environment, you can create a
virtual machine from an existing VHD. You also can choose existing VHDs when deploying any operating
system from which VMM cannot create a template, such as a non-Windows operating system.
When you create a new virtual machine using an existing VHD, you are essentially creating a new virtual
machine configuration that is associated with the VHD file. VMM will create a copy of the source VHD so
that you do not have to move or modify the original.
In this scenario, the source VHD must meet the following requirements:
You must leave the Administrator password blank on the VHD as part of the System Preparation Tool
(Sysprep) process.
You must install the Virtual Machine Additions on the virtual machine.
You must use Sysprep to prepare the operating system for duplication.
Deploying from a Template

This method creates a new virtual machine based on a template from the VMM library. The template is a
library resource, which links to a virtual hard drive that has a generalized operating system, hardware
settings, and guest operating-system settings. You use the guest operating system settings to configure
operating system settings such as computer name, local administrator password, and domain
membership.
The deployment process does not modify the template, which you can reuse multiple times. If you are
creating virtual machines in the Self-Service Portal, you must use a template.
The following requirements apply if you want to deploy a new virtual machine from a template:
You must install a supported operating system on the VHD.
You must leave the Administrator password blank on the VHD as part of the SysPrep process.
However, you do not have to leave blank the Administrator password for the guest operating-system
profile.
For customized templates, you must prepare the operating system on the VHD by removing
computer identity information. For Windows operating systems, you can prepare the VHD by using
Sysprep.
Deploying from the VMM Library

If you deploy a virtual machine from the library, the virtual machine is removed from the library, and
placed on the selected host. When using this method, you must provide the following details in the
Deploy Virtual Machine Wizard:
The host for deployment. The template that you use provides a list of potential hosts and their
ratings.
The path of the virtual machine files on the host.
The virtual networks used for the virtual machine. You are presented with a list of existing virtual
networks on the host.
Lesson 2
Installiing and
d Upgrading Virtual M
Machine Manag
ger
Installing VMM is a very important part of operating and m managing yourr private cloud. There are sevveral
prerrequisites for installing VMMM, and there arre various scen h you can impllement VMM. If you
narios in which
already have an older
o version of VMM installe
ed, you can ch hoose to upgraade your curre
ent VMM versio on to
the newest VMM version, to ach hieve new feattures and funcctionalities.
In th
his lesson, you
u will learn abo
out how to insttall and upgra de VMM.
Afte ou will be able to:

er completing this lesson, yo
Describe VMM
M installation prerequisites and
a considerattions.
Upgrade VMM
M from previo
ous versions.
Describe conssiderations forr deploying a highly

h availabl e VMM serverr.
10751A: Connfiguring and Deployying a Private Cloud w
with System Center 22012 2-19
Prerequisit
P es for Installing VMM
Be
efore deployinng VMM and itts componentss, you should bbe certain thatt your system meets the harrdware
an
nd software re
equirements. While
W software requirements do not chang ge based on nu umber of hostss that
VMM can mana age, hardware prerequisites may vary depeending on thee number of ho osts. In additio
on, not
all VMM compo onents have th
he same hardwware and softw
ware requiremeents. However,, Windows Serrver
20
008 R2 is the only
o supported
d operating system for VMMM.
VMM
V Manag
gement Serv
ver
In
n addition to having
h Window ws Server 2008 8 R2 installed, yyou need to e nsure that the
e following softtware is
in
nstalled on the server that wiill run the VMMM Manageme nt Server:
Microsoft .N
NET Frameworrk 3.5 Service Pack
P 1 (SP1) o r later
Windows Automated
A Insttallation Kit (A
AIK)
Windows PowerShell
P 2.0 (if the VMM management
m cconsole will run
n on the same
e server)
Windows Remote
R Manag gement (WinRM M) 2.0 (this is iinstalled by deefault in Windo
ows Server 200
08 R2,
so you shou
uld just verify if the service iss running)
SQL Server 2008 SP2 (Sta andard or Enteerprise) or SQL Server 2008 R
R2 SP1 Standarrd, Enterprise o
or
Datacenter this is necesssary only whe
en you install V
VMM Managem ment Server and SQL Serverr on
same machhine.
Hardware requirements vary depending

d on
n number of ho
osts, and have the following limits:
Central pro
ocessing unit (C
CPU): Single co
ore CPU 2 gigaahertz (GHz) Dual core CPU 2.8 GHz
Random acccess memory (RAM): 4 8 gigabyte

g (GB)
Disk space: 40 GB 150 GB

G (depending
g on whether o
or not SQL dattabase is installed on the sam
me
server)
2-20 Private Cloud Configuration and Deployment with System Center Virtual Machine Manager
VMM Database
The VMM database stores all VMM configuration information, which you can access and modify by using
the VMM management console. The VMM Database requires a SQL Server 2008 SP2 or newer. Because of
this, the base hardware requirements for VMM Database are equal to the minimum system requirements
for installing SQL Server. Additionally, if you are going to manage more than 150 hosts, it is
recommended that you have at least 4 GB of RAM on the database server. Software requirements for the
VMM Database are the same as for SQL Server.
VMM Library
The VMM library is the server that hosts resources for building virtual machines, services and business unit
clouds. In smaller environments, you usually install the VMM library on the VMM Management Server, in
which case the hardware and software requirements are the same as for the VMM Management Server. In
larger and more complex environments, it is recommended to have VMM library on separate server in
highly available configuration. If you want to deploy another VMM library server, the server should fulfill
following requirements:
Supported operating system: Windows Server 2008 or Windows Server 2008 R2
WinRM 2.0
CPU: at least 2.8 GHz

RAM: at least 2 GB
Hard disk space: Varies based on the number and size of files stored
VMM
V Installation Consideratio
ons
Be
efore installing
g VMM, ensure e that the commputer meets tthe minimum hardware requ uirements, and
d that all
th
he prerequisitee software is in
nstalled. The in
nstallation wizaard will not insstall any prereq
quisite compoonents,
so
o ensure that all
a prerequisite es are installed prior to runn ing the Installaation Wizard.
Yo
ou should con
nsider the follo
owing when pla
anning your V
VMM installatio
on:
Before you begin installin

ng your VMM management server, ensuree that you have
e a computer w with the
supported SQL Server verrsion installed and running. Unlike VMM 2
2008 R2, VMM
M does not insttall an
Express edition of SQL Seerver automatically.
The VMM console

c installss automaticallyy when you in stall a VMM m
management se erver. Howeve
er, you
cannot use the VMM con nsole to connect to a VMM sserver from a p previous versio
on of VMM (fo
or
example, VMM 2008 R2)..
If you are in
nstalling the VMM
V managem
ment server on
n a computer tthat is a memb
ber of a clusterr, you
will be aske
ed whether you want to mak
ke the VMM m management seerver highly avvailable.
If there is a problem with

h setup comple
eting successfu he log files in the
ully, consult th
%SYSTEMD DRIVE%\PrograamData\VMMLogs folder. Bee aware that P ProgramData iss a hidden fold
der by
default.
During the VMM manage ement server installation, onn the Configuree service account and distribbuted
key management page, you
y must configure the VMM M service to usse either the Local System acccount
or a domain account. We
e will discuss co
onsiderations for choosing tthis account later in this mod
dule.
efore beginnin
Be MM, close any open program
ng to install VM ms, and ensuree that there arre no pending restarts
on
n the computeer. For example, if you have recently instal led a server roole by using Seerver Managerr or
ha
ave applied a security updatte, you may ne eed to restart tthe computer and then log o on to the com
mputer
with
w the same user
u account too finish the serrver role or seccurity update installation.
Up
pgrading VMM
V from
m Previous Versions
If yo
ou already havve a previous VMM
V version installed in you
ur environmennt, it may be possible to upg
grade
direectly to VMM 2012.
2 Howeverr, there are sevveral requirem
ments and limittations that yo
ou must be awaare of
befoore planning an
a upgrade.
Sup
pported Verrsions of VM
MM to Upgrrade
VMM 2008 R2 SP1 is the only suupported earliier version tha t you can direectly upgrade tto VMM 2012
verssion. VMM 200
08 R2 SP1 musst be running on
o Windows SServer 2008 R2 2 SP1. If your V
VMM server for
VMM 2008 R2 SP1 is installed on
o Windows Se erver 2008 SP22, you need to upgrade the o operating systtem to
Win
ndows Server 2008
2 R2 SP1 beefore you can begin an in-p place upgrade to VMM.
SQL Server Ediition

VMM does not su upport the SQLL Server Expresss edition for VVMM databasees. This meanss that you shou uld
mig
grate your VMM M Database to o a supported SQL Server ve rsion before sttarting your VMM upgrade. The
R command-line utilities arre not mandato
SQLL Server 2008 R2 ory for an upg grade, but theyy are highly
ommended. If the SQL Serve
reco er 2008 R2 com mmand-line uttilities are not present on thee VMM server,, a
warning displays in
i the prerequ uisites check du
uring the upgrrade process. TThis does not pprevent installation,
and you can install these utilitie
es later.
Req
quirement for
f AIK
VMM requires thaat you install an Automated Installation Kitt (AIK). AIK too
ols help you deploy virtual
macchines automa
atically. Windows AIK for Win ndows 7 is thee only supporteed version. You must uninstaall
prevvious Windows AIK versions before installing Windows A AIK for Window ws 7.
VMM 2005 R2
Virtual machine hosts running Microsoft Virtual Server 2005 R2 are no longer supported in VMM. If you
upgrade a VMM environment that has Virtual Server hosts, the hosts are removed from the VMM
database. If you do not want these hosts to be removed automatically, remove the hosts manually before
upgrading. Virtual machine hosts running certain versions of VMware ESX and VMware vCenter Server are
also no longer supported. VMM 2012 supports only VMware vCenter Server 4.1, and VMware ESX 3.5,
ESXi 3.5, ESX 4.1, and ESXi 4.1.
PRO Configurations
When upgrading to VMM, Performance and Resource Optimization (PRO) configurations are not
maintained. If you have an existing connection to Operations Manager, the upgrade process removes the
connection. If you do not want the connection to be removed automatically, remove the connection
manually before upgrading. After the upgrade process completes, you can reconfigure your connection to
Operations Manager.
Library Server on Windows Server 2003

VMM does not support a library server on a computer that is running Windows Server 2003. If your library
server is running Windows Server 2003 and you continue with the upgrade, you will not be able to use the
library server in VMM. You will only be able to remove the library server from VMM 2012.
Note During an upgrade process, VMM provides automatic rollback functionality in the
event of a failure. If an upgrade failure is detected, the upgrade automatically reverts to the
original VMM 2008 R2 SP1 configuration.
Co
onsideratio
ons for Dep
ploying a Highly Avaailable VM
MM Server
VMM now supports a highly available VMM Server.

S You can
n use failover cclustering to aachieve high
avaiilability for VM
MM, because VMM
V is now a cluster-aware application. H
However, there e are several th
hings
you should consid der before dep
ploying a VMM M cluster.
Befo
ore you begin the installation of a highly available
a VMM
M management server, ensurre the following:
You have insttalled and configured a failo

over cluster thaat is running W
Windows Serve
er 2008 R2 or
Windows Servver 2008 R2 SP P1.
All computerss on which you g the highly avvailable VMM management server meet th
u are installing he
minimum harrdware require ements, and all prerequisite software is insstalled on all co
omputers.
You have crea
ated a domain n account that will be used b
by the VMM seervice. You mu
ust use a domaain
user account for a highly avvailable VMM management server.
You are prepa

ared to use disstributed key management
m tto store encryp
ption keys in A
Active Directorry
Domain Serviices (AD DS). You
Y must use distributed
d keyy management for a highly aavailable VMM M
managementt server.
You have a co
omputer with a supported SQL Server verssion installed aand running. U
Unlike VMM 20
008
R2, VMM will not install auttomatically a SQL
S Server Exp
press edition.
Hig
ghly Availab
ble Databases and Libra
ary Servers
To achieve
a full red
dundancy, we recommend that you use a highly availab ble SQL Server.. You should innstall
a highly available SQL Server on n a separate fa
ailover cluster ffrom the failovver cluster on which you aree
installing the high hly available VMM managem ment server. Simmilarly, we alsoo recommend d that you use a
highhly available file server for ho
osting your lib
brary shares.
Self Service Portal and Clustered VMM Server

For best practices, do not install the VMM Self-Service Portal on the same computer as the highly
available VMM management server. If your VMM Self-Service Portal currently resides on the same
computer as the VMM server, we recommend that you uninstall the VMM Self-Service Portal for VMM
2008 R2 SP1 before upgrading to VMM. We also recommend that you install the VMM Self-Service Portal
on a highly available web server to achieve redundancy and load balancing.
Failover Cluster Manager

You cannot perform a planned failover (for example, to install a security update or do maintenance on a
cluster node) by using the VMM console. Instead, to perform a planned failover, use the Failover Cluster
Manager console.
During a planned failover, ensure that there are no tasks actively running on the VMM management
server. Any tasks that are executing during a failover will be stopped, and will not restart automatically.
Any connections to a highly available VMM management server from the VMM console or the VMM Self-
Service Portal will also be lost during a failover. However, the VMM console will be able to reconnect
automatically to the highly available VMM management server after a failover if it was opened before you
performed failover to another VMM server.
Lesson 3
Config
guring VMM
V Se
ecurity and Roles
Because VMM is software

s that operates
o a privvate cloud infrrastructure, it is very importaant to design
secu
urity properly. In addition, it is very importtant to define precisely the aaccess permisssions to various
reso
ources that privvate cloud useers will use. VM
MM provides seeveral optionss for configurin ng and manag ging
secu
urity. Howeverr, you must firsst define a VMM service acco ount, key man nagement, and d then define rrun as
acco
ounts and secu urity roles.
In th
his lesson, you
u will learn abo
out VMM security and roles.

Specify VMM service accou
unts.
Configure disstributed key management.

m
Configure run
n as accounts.
Configure use
er roles.
Specifying VMM Serv

vice Accou
unts
During the VMM M Managemen nt Server installation in VMM M, on the Conffigure service account and
diistributed key management page, you mu ust configure thhe VMM servicce to use eithe
er the Local Syystem
acccount or a doomain accountt. If you specifyy a domain acccount, the acccount must be a member of the
lo
ocal Administraators group on
n that computer.
It is very importtant that you create

c a service
e account befo ore starting yo our VMM deployment. You ccan also
coonsider using the
t managed service
s accoun n Windows Se
nts feature tha t is available in erver 2008 R2, to
crreate an accou
unt for VMM.
When
W planning a service acco
ount for VMM,, take into acco
ount the follow
wing considerations:
If you speciify a domain account, we strrongly recomm mend that you create an acccount that is
designated specifically fo e. When a hostt is removed frrom the VMM management server,
or this purpose
the account under which the VMM servvice is running g is removed frrom the local A Administratorss group
of the host.. If the same account is used
d for other purrposes on the hhost, this can ccause unexpeccted
results.
In the follow
wing instancess, you must use a domain acccount:
If you plan
p to use sha
ared ISO images with Hyperr-V virtual macchines
If you are
a using a disj
sjointed namesspace
If you are
a installing a highly availab
ble VMM man
nagement server
If you are
a installing a highly availab
ble VMM mannagement server on a release e candidate ve
ersion of
VMM, you must add the domain account directlyy to the local AAdministratorss group. The ddomain
accounnt cannot be a member of a group that is itself a membeer of the local Administratorrs
group.
Configurring Distrib
buted Key Managem
ment
Durring a VMM management se erver installatio

on, on the Con
nfigure service account and ddistributed keyy
man nagement pag ge, you can select to use disttributed key m
management to o store encrypttion keys in AD
D DS,
instead of storing the encryptio on keys on the computer on which the VM MM manageme ent server is
installed. If you ch
hoose to enable distributed key managem ment, coordinatte with your A
Active Directoryy
admministrator abo out creating the appropriate container in A ographic keys. If you
AD DS for storing the crypto
ghly available VMM manage
are installing a hig ement server, yyou must use d
distributed keyy managemen nt to
storre encryption keys
k in AD DS.
Disttributed key management

m is required in th
his scenario, beecause when the VMM service fails over to o
other node in the cluster, the
ano e VMM service still needs acccess to the enccryption keys tto access data in
the VMM databasse. This is only possible if thee encryption keeys are stored in a central lo
ocation such ass AD
DS.
Youu must create a container in AD

A DS to store
e the encryptio
on keys. You ccan create the container befo
ore
installing VMM byy using ADSI Edit.
E
The following are some conside

erations when using distributted key manag
gement in VM
MM:
If the accountt with which you are installin
ng VMM has t he appropriat e permissions to create a
container in ADA DS, you do o not need to create
c the con tainer in AD DDS before startting the VMM
installation. In
nstead, on the Configure serrvice account aand distributedd key manage ement page, yo ou
can enter the e name for the container, andd the containeer will be creatted automaticaally as part of tthe
VMM installation process.
You can creatte the containe

er anywhere in
n your AD DS hierarchy. Examples of locattions in AD DSS are:
CN=VMM
MDKM,DC=co
ontoso,DC=com
m
orp,DC=contoso,DC=com
CN=VMMDKM,CN=co
The account with which you are installing VMM must have at least Read, Write, and Create all child
objects permissions to the container in AD DS, and the permissions must apply to this object and all
descendant objects of the container.
On the Configure service account and distributed key management page, you must specify the
location of the container in AD DS by typing the location. For example, you can type:
CN=VMMDKM,DC=contoso,DC=com.
Wh
hat Is a Ru
un As Acco
ount?
In VMM,
V the credentials that a user
u enters forr any process ccan instead bee provided by a Run As account. A
Runn As account iss a container fo
or a set of storred credentialss.
Only administratoors and delegated administra
ators can creatte and manage Run As acco ounts. Read-onnly
adm
ministrators can
n see the acco
ount names asssociated with R
Run As accounnts that are in the scope of their
userr role.
The same restrictions on creatin
ng, managing, and viewing R Run As accoun nts are in effect for both the VMM
console and the VMM
V comman nd shell. Delega ated administrrators and selff-service users can only acceess
obje
ects that are in e, and can onlyy perform the actions that th
n the scope of their user role heir user role aallows.
VMM uses the Wiindows Data Protection
P API (DPAPI) to proovide operatin
ng system-leveel data protection
servvices during sto
orage and retrrieval of the Ru
un As account credentials. DDPAPI is a passsword-based ddata
prottection service
e that uses cryp
ptographic rou ong Triple Datta Encryption SStandard (DES))
utines (the stro
algoorithm, with strong keys) to offset the risk posed by passsword-based d data protection.
User
U Roles in VMM
Yo
ou can create user roles in VMM
V to define
e the objects th
hat users can m
manage, and tthe manageme
ent
op
perations that users can perfform.
Administrato
A or
Members
M e administrators user role ca
of the an perform all administrativee actions on alll objects that VMM
manages.
m
Administrative users
u have sole
e responsibilityy for the follow
wing VMM feaatures:
Only admin nistrative userss can add stand

d-alone Citrix Xen-Server ho
osts and Xen-SServer clusters (known
as pools) to
o VMM manag gement.
Only adminnistrative userss can add a WS
SUS server to V
VMM to enablle VMM privatte cloud infrasttructure
updates thrrough VMM.
Delegated
D Administrato
or
Members
M of De elegated Administrator user roles can perfo orm all adminiistrative tasks within their asssigned
ho
ost groups, clo
ouds, and libra
ary servers, exccept for adding
g a Citrix Xen--Server host orr cluster, and aadding
WSUS
W servers.
Self-Service User
Members
M of the
e self-service user
u roles creatte, deploy, and
d manage theiir own virtual m
machines and services
byy using the VMMM management console orr a Self Servicee Portal. The seelf-service user:
Specifies th
he business unit cloud to which their virtuaal machines an e deployed, and the
nd services are
actions thatt the Self-Servvice users can take.
t
Grants acce
ess to logical and
a physical re
esources both iin the library aand on their ow
wn user data p
paths.
Sets quotas on virtual machines and computing resources.

Specifies whether self-service users can view and implement PRO tips.
Read-Only Administrator
Read-Only Administrator users can view status, job status, and properties of objects within their assigned
host groups, clouds, and library servers. The Read-Only Administrators user role also specifies the Run As
accounts that the Read-Only Administrator can view.
Lesson
n4
Unde
erstanding Host Group
ps
A virtual machin
ne host is one of the main objects in the V VMM private ccloud infrastruccture. A host iss a
physical compuuter that runs the
t virtual macchines. You can n organize hossts into groups, so they can share
co
ommon prope erties and settings. It is very important to kknow how to mmanage hosts properly when n
eploying your virtual environ
de nment.
In
n this lesson, yo
ou will learn about configuriing host group
ps.
After completin
ng this lesson, you
y will be able to:
Describe ho
ost groups.
Configure placement
p rule
es.
Configure host
h reservatio
ons.
Configure dynamic
d optim
mization.
Configure networks.
n
Configure Storage.
S
Wh
hat Are Ho
ost Groupss?
You
u can organize hosts into hosst groups, whicch help you si mplify management tasks by enabling you u to
app
ply settings to multiple
m hosts with a single action. By defaault, there is a single host grroup named A
All
Hossts. However, iff necessary you can create additional grouups for your en nvironment.
The host groups are

a hierarchica al. When a neww child host grooup is created
d, it inherits the
e settings from
m the
pareent host groupp. When a child d host group moves
m to a neww parent host group, the ch hild host groupp
maintains its origiinal settings exxcept for PRO settings, whic h are managed separately. W When the settiings
in a parent host group
g change, you have the option to app ply those changges to child ho ost groups.
The following are scenarios in which

w you wou
uld use host grroups:
To provide ba
asic organization when you are managing large numberrs of hosts and d virtual machiines.
You can creatte custom view
ws within the Hosts
H view and
d Virtual Machhines view to p
provide easy
monitoring and access to a host. For exam
mple, you migght create a ho
ost group for e
each branch offfice
in your organ
nization.
Reserving resources for use e by hosts. Hosst reserves are useful when pplacing virtual machines on a
host. The hosst reserves dete ermine the ammount of CPU, memory, disk space, disk I/O O capacity, and d
network capa acity that are available
a continnuously to thee host operatin
ng system. Usee the Host grou up
properties acttion for the ro
oot host group All Hosts, to sset default hosst reserves for all hosts that V
VMM
y want to use more of the resources on some hosts rather than on o
manages. If you other hosts, yoou can
set host reserrves differentlyy for each hostt group.
Designating hosts
h on whichh users can creeate and operaate their own vvirtual machines. When a VM MM
administratorr adds self-servvice user roles,, one part of roole creating is to identify the
e hosts on which
self-service ussers or groupss in that role arre allowed to ccreate, operatee, and manage e their own virrtual
machines. It is recommende ed to designatte a specific hoost group for tthis purpose.
You can create a business unit cloud from resources in host groups. When you create a private cloud,
you select which host groups will be part of the private cloud. You can then allocate all or some of
the resources from the selected host groups to the private cloud.
Each host group has a set of properties and settings that are common to all hosts within that host group.
These properties include changing the name or description of a host group, moving a host group within
the host group hierarchy, or modifying the resources reserved for the host operating system on the host.
You can access a host groups properties by right-clicking the host group, and then selecting Properties.
This gives you access to three tabs with various options.
You can assign host groups to the Delegated Administrator and the Read-Only Administrator user roles to
scope the user roles to specific host groups. Members of these user roles can view and manage the private
cloud infrastructure resources that are assigned to them at the host group level.
Co
onfiguring Placemen
nt Rules
In VMM
V 2008, virttual machine placement
p ena
ables VMM to o evaluate hostts capacity, and then suggesst the
mosst appropriate virtualization host for deplo
oyment. VMM extends this ccapability with over 100 virtuual
macchine placemeent checks, and placement rules.
d adds supportt for custom p
VM
MMManage
ed Virtual Machine
M Placcement
Placcement rules th hat are defined
d on a host grroup level help
p you to manage virtual macchine placeme
ent on
speccific hosts insid
de a host grou
up. In general, VMM always ttries to recom mend the mosst appropriate
e host
for virtual
v machin ne placement byb calculating host rating. Hoowever, by speecifying Custo
om placement rules,
you can define yo our own rules for
f placement or placement blocking.
Cusstom Placem
ment Rules
Custom placemen nt rules are bassed on host annd virtual mac hine Custom P Properties. On each host, you can
defiine values for 10
1 predefined custom prope erties, and you ne your own n
u can also defin new custom
properties and the eir values. Sim
milarly, you can define customm properties foor each virtual machine.
By defining
d custom placement rules
r on a hostt group level, yyou can actuaally define a rule that is using
ga
custtom property as
a a condition for allowing or
o blocking virrtual machine d deployment on a host in a h host
group.
For example, you can define a rule

r specifying that a specificc custom propperty value mu
ust match on b
both
the host and the virtual
v machine, or the virtua
al machine willl not be allow
wed to deploy.
Configuring
C g Host Resservationss
Host reserve setttings specify the

t amount off resources thaat VMM sets asside for the ho ost operating ssystem
to
o use. For a virtual machine to
t be placed ono a host, the hhost must be aable to meet the virtual macchines
re
esource require ements withou ut using host reserves.
r You ccan set host reserves for both
h individual ho ost
groups, and for individual hossts. The host reeserve settingss for the root h
host group, All Hosts, sets th
he
de
efault host reserves for all ho
osts.
Yo
ou can configu
ure reserve vallues for the following resourrces:
CPU: By configuring the CPU

C u specify how much of the C
value, you CPU resources are available tto the
host machine.
Memory: Yo
ou can define the amount of
o RAM memorry that hosts n
need to operatte normally.
Disk I/O: Byy configuring Disk

D I/O, you reserve
r some b
bandwidth to d
disk for the ho
ost operating ssystem.
Disk space: You can reserrve amount of free disk spacce to always bee available for hosts
Network I/O
O: This setting specifies how
w much of the ttotal network I/O is available on the host
machine.
Yo
ou should connsider configurring host reservvations on thee host group leevel. By config
guring host resserves,
yo
ou will optimizze resource usa
age, and ensure that all vita l services on p
physical hosts h
have enough
re
esources to runn even when virtual
v machinees are operatin ng with heavy load.
Co
onfiguring Dynamic Optimizattion
VMM provides tw wo new feature es that help opptimize power and resource usage on hostts managed byy
VMM which are dynamic
d optimmization and po ower optimiza tion. Dynamicc optimization balances the vvirtual
macchine load with hin a host clusster, while pow
wer optimizatio
on enables VM
MM to evacuate balanced clu uster
hostts, and then tu
urn them off to o save power.
While power optimization is an optional setting within the Dynamic Optimization grou
up of settings, it is
imp
portant to conssider it separattely.
Dyn
namic Optim
mization
Durring dynamic optimization,
o VMM
V migratess virtual machi nes within a host cluster to improve load--
ancing among hosts, and to correct any placement consstraint violation
bala ns for virtual m
machines.
You
u can configure e dynamic opttimization on a host group to o migrate virtu
ual machines w within host clu
usters
with
h a specified frrequency and aggressiveness settings. Agg gressiveness deetermines the amount of loaad
balance that is required to initiate a migrattion during dyynamic optimizzation. By defaault, virtual
imb
macchines with me edium aggresssiveness are migrated every 10 minutes. W When configuring frequency and
agg
gressiveness for dynamic opttimization, an administrator
a should factor in the resource cost of addittional
mig
grations againsst the advantag ges of balancin
ng loads amon ng hosts in a h
host cluster. Byy default, a hosst
group inherits dyn namic optimizzation settings from its paren
nt host group.
Youu can set up dyynamic optimizzation for clusters with two oor more nodess. If a host gro
oup contains sttand-
alon
ne hosts or host clusters thatt do not suppoort live migratiion, dynamic o
optimization iss not performeed on
thosse hosts. Any hosts
h that are in maintenancce mode also aare excluded frrom dynamic o optimization. In
adddition, VMM on e virtual machi nes that use shared storage. If a host clustter
nly migrates highly available
contains virtual machines
m a not highly available, thosse virtual mach
that are hines are not m
migrated durin ng
dynamic optimiza ation.
On-demand dynamic optimization is also available for individual host clusters, by using the Optimize
Hosts action in the virtual machines and Services workspace. You can perform on-demand dynamic
optimization without configuring dynamic optimization on host groups. After dynamic optimization is
requested for a host cluster, VMM lists the virtual machines that will be migrated for the administrator's
approval.
Power Optimization in VMM

Power optimization is an optional feature within Dynamic Optimization, and it is only available when a
host group is configured to migrate virtual machines through dynamic optimization. Through power
optimization, VMM helps to save energy by turning off hosts that are not needed to meet resource
requirements within a host cluster, and then turns the hosts back on when they are needed again.
By default, when the feature is turned on, VMM performs power optimization at all times. However, you
can schedule specific hours and days of the week that VMM will perform power optimization. For
example, you might initially schedule power optimization only on weekends, when you anticipate low
resource usage on your hosts. After observing the effects of power optimization in your environment, you
might increase the hours.
Co
onfiguring Networkss
Networking in VM MM includes se everal enhance

ements that en
nable administtrators to provvision networkk
reso
ources efficienttly for a virtualized environm
ment. Networkking enhancem
ments include tthe following:
The ability to create and de
efine logical ne
etworks.
Static IP addrress and static MAC address assignment.
Load balance
er integration.
Log
gical Netwo
orks
A lo
ogical network that is combin ned with one or
o more assoc iated networkk sites is a user-defined name ed
grouping of IP subnets, VLANs, or IP subnet/V VLAN pairs thaat are used to organize and simplify netwo ork
assignments. Som me possible log
gical network examples
e inclu
ude BACKEND,, FRONTEND, LLAB,
MANAGEMENT and BACKUP. Logical networks represent a n abstraction o of the underlyying physical
netw
work infrastruccture that enables you to mo odel the netwo ork based on b business needs and connecttivity
properties. After you
y create a loogical network he network on which to deploy a
k, you can use it to specify th
hostt or a virtual machine
m d-alone or partt of a service). Users can assiign logical nettworks as part of
(stand
crea
ating a virtual machine and service,
s withou
ut having to un nderstand the network details.
Youu can use logical networks too describe netwworks with diffferent purposees, such as for traffic isolation, and
to provision
p networks for differe
ent types of se
ervice level agrreements (SLA As). For example, for a tiered
appplication, you may
m group IP subnets
s and VLANs that you u use for the fr ont-end web ttier into a logical
netwwork named FRONTEND. Yo ou may choose e to group bacckend servers iinto a logical n network named
BACCKEND for the IP subnets and VLANs that you use. When n a self-servicee user models the applicatioon as a
servvice, they can easily
e choose the
t logical network for virtuaal machines in n each tier of the service to w
which
to connect.
c
At least one logical network must exist for you to deploy virtual machines and services. By default, when
you add a Hyper-V host to VMM management, VMM creates automatically logical networks that match
the first Domain Name System (DNS) suffix label of the connection-specific DNS suffix on each host
network adapter.
To make a logical network available to a host, you must associate the logical network with a physical
network adapter on the host, and make it available through an external virtual network (otherwise known
as an external virtual switch). You perform this association on a per network adapter basis.
By default, when you add a Hyper-V host to VMM management, if a physical network adapter on the host
does not have an associated logical network, VMM creates and associates automatically a logical network
that matches the first DNS suffix label of the connection-specific DNS suffix. For example, if the DNS suffix
for the host network adapter is corp.contoso.com, VMM creates a logical network that is named corp. If
a virtual network is not associated with the network adapter, when a job connects a virtual machine to a
logical network that is associated with the physical network adapter, VMM creates automatically an
external virtual network, and then associates it with the logical network. Be aware that no network sites
are created automatically. These default settings provide an out-of-the-box solution to help you create
and deploy virtual machines on your existing network.
MAC Address Pools

VMM can assign static MAC addresses automatically to new virtual network devices on Windows-based
virtual machines that are running on any managed Hyper-V, VMware ESX or Citrix Xen-Server host. VMM
has two default static MAC address pools: the default MAC address pool (for Hyper-V and Citrix Xen-
Server), and the default VMware MAC address pool (for VMware ESX hosts). The default static MAC
address pools are used only if you set the MAC address type for a virtual machine to Static. If the virtual
machine setting is set to Dynamic, the hypervisor assigns the MAC address. You can use either the default
MAC address pools, or you can configure custom MAC address pools that are scoped to specific host
groups.
Load Balancer Integration

By adding a load balancer to VMM, you can load-balance requests to the virtual machines that make up a
service tier. You can use NLB, or you can add supported hardware load balancers through the VMM
console. NLB is included as an available load balancer when you install VMM. NLB uses round-robin as the
load-balancing method.
To add supported hardware load balancers, you must install a configuration provider that is available
from the load-balancer manufacturer. The configuration provider is a plug-in to VMM that translates
Windows PowerShell commands to API calls, which are specific to a load-balancer manufacturer and
model.
Co
onfiguring Storage
In VMM,
V through the VMM con nsole, you can discover, classsify and provission remote sto
orage on supp ported
storrage arrays. VM
MM fully autom mates storage assignment to o a Hyper-V ho V host cluster, and
ost or Hyper-V
thenn tracks any storage that it manages.
m
To enable
e the new
w storage features, VMM use es the new Miccrosoft Storag ge Managemen nt Service to
com
mmunicate with external arra ays through an n SMI-S provid ge Management Service installs
der. The Storag
by default
d during the VMM insttallation. You must
m install a ssupported SMI-S provider on an available
servver, and then add
a the provid der to VMM ma anagement.
Note For backward

b com
mpatibility purpposes, if you doo not add an SSMI-S provider to VMM
managemen nt, VMM still uses a Virtual Disk
D Service (VD DS) hardware provider for Sttorage
Area Network (SAN) transffer functionality. However, ssupport for VD
DS hardware prroviders
has deprecated, and future
e VMM release es will not sup
pport VDS provviders.
The following is a list of steps th

hat you must complete
c to diiscover, classifyy, and assign sstorage throug
gh
VMM:
1. For a supportted storage arrray, obtain an SMI-S storagee provider fromm your storage e array vendorr, and
then install th
he provider on
n an available server
s accordin
ng to the instrructions that are provided byy your
storage vendor.
2. From the VMM console Sto orage node, co onnect to the SSMI-S storage provider to diiscover and claassify
the storage. Connect
C to the
e provider by using
u either th otocol version 4 (IPv4) address or
he Internet Pro
the fully qualified domain name
n (FQDN). Classifying stoorage entails aassigning a me
eaningful
classification to storage poools. For exampple, you may asssign a classifi cation of GOLD to a storage
e pool
that resides on
o the fastest, most redundant storage arraay. This enablees you to assig gn and use storage-
based classificcation withoutt actually know
wing its hardw ware characteristics.
3. Optionally, from the Storage node of the VMM console, create logical units from a managed storage
pool.
4. From either the VMM console Storage node or the target host group Properties dialog box you need
to allocate pre-created logical units or storage pools to specific host groups. If you allocate a storage
pool, you can create and assign logical units directly from managed hosts in the host group that can
access the storage array. In addition, if you use rapid provisioning to provision virtual machines by
using SAN snapshots or cloning, VMM can create logical units automatically from the storage pool.
5. In the VMM console, from either the host or host cluster Properties dialog box, assign logical units
from the host group to either specific Hyper-V hosts or to Hyper-V host clusters, as shared (Cluster
Shared Volume) or available storage. If you allocated a storage pool to a host group, you can create
and optionally assign logical units directly from a host or host clusters Properties dialog box. If the
storage array supports Internet Small Computer System Interface (iSCSI) host connectivity, you can
also create iSCSI sessions to the storage array from a hosts Properties dialog box.
Note The hosts must be able to access the storage array. For example, if you are using a
Fibre Channel SAN, each host must have a host bus adapter (HBA), and the hosts must be
zoned correctly.
Lab: Co onfigurring and

d Deplo
oying th
he Private Clou
ud
Infrasttructure
e
Lab
b Setup
Notte: Before startting this lab, you must have completed th e lab in Modu
ule 1.
For this lab, you will

w use the avaailable virtual machine
m enviro
onment. Beforre you begin the lab, you mu
ust
ensu
ure that the virtual machines are running by completing g the following
g steps:
6. On LON-HOS
ST1, click Startt, point to Adm Tools, and the n click Hyper--V Manager.
ministrative T
7. In Hyper-V Manager,
M click 10751A-LON-
1 -DC1, and in tthe Actions paane, click Startt.
8. In the Action
ns pane, click Connect.
C Wait until the virtu
ual machine staarts.
User nam
me: Administra
ator
Password
d: Pa$$w0rd
Domain: Contoso
10. Repeat steps 2 to 4 for 107

751A-LON-SQ
Q1.
11. On LON-HOS
ST2, click Startt, point to Adm Tools, and the n click Hyper--V Manager.
ministrative T

M click 10751A-LON-
1 -VM1, and in tthe Actions p
pane, click Starrt.
13. In the Action


Password: Pa$$w0rd
Domain: Contoso
15. Repeat steps 6 to 9 for 10751A-LON-AP1.
Lab Scenario
You are administrator at Contoso, Ltd You have just deployed VMM and two physical hosts, and you now
want to make basic configuration changes, and then perform a test deployment of the virtual machines.
Exercise 1: Reviewing and Configuring Hosts

Scenario
You have just added a host cluster in VMM, and before implementing any resources or virtual machines,
you want to review the current physical hosts configurations.
1. Review cluster configuration.
2. Review and configure host network adaptors.
X Task 1: Review cluster configuration

1. On LON-VM1, in the VMM console, click the VMs and Services workspace, and then open the
Properties dialog box for LON-CLUSTER01.
2. Review the cluster configuration by browsing through all of the tabs. Do not make any changes.
X Task 2: Review and configure host network adaptors

1. Expand LON-CLUSTER01, and then open the lon-host1.contoso.com Properties dialog box.
3. For the network adapter, type Adapter for host management and virtual machine usage in
the Description field.
4. Under logical network connectivity, ensure that the network adapter is connected to External
Network. Also, make sure that options Available for placement and Used by management are
both selected.
5. In Virtual Networks, ensure that name of the network is External, and network binding is
External.
6. Repeat steps 1 and 5 on lon-host2.
Results: After this exercise, you should have reviewed and configured hosts.
Exercise 2: Configuring Host Groups

Scenario
After configuring hosts and clusters, you have decided to implement a host group named Production, and
then place your current hosts into that group. You also want to configure some of the options that are
available for the host group.
The main task for this exercise is as follows:
1. Create and configure a host group named Production.
X Task: Create and configure a host group named Production

1. In the VMM Manager Console, create host group, and name it Production.
2. Open the properties for the Production host group, and then configure host reserves with the
following settings:
CPU : 10%
Memory : 512 MB
Disk Space : 10%

Network I/O : 5%
3. Configure Dynamic Optimization to migrate virtual machines automatically on 15 minute intervals.
4. Configure Power Optimization thresholds with the following settings:

CPU: 40%
Memory: 2048
Disk I/O : 5
Network I/O : 10%
5. Configure Power Optimization to work during night hours (from 7:00 P.M. to 6:00 A.M.) 7 days a
week.
6. Clear the Enable power optimization and Automatically migrate virtual machines to balance
load at this frequency check boxes. Note: you are disabling these options, as we do not want to
implement this in the lab.
7. Move LON-CLUSTER01 to the Production host group.
Results: After this exercise, you should have created and configured host group.
Exercise 3: Configuring User Roles and Run As Accounts

Scenario
To provide users with ability to access their private cloud resources, you decide to create dedicated user
roles for StockTrader business unit. For administrative purposes, you decide also to create a Run As
account.
1. Configure a Run As account.
2. Create a user role for the StockTrader Business Unit.
X Task 1: Configure a Run As account

1. In the VMM Manager console, in the Security node of the Settings workspace, run Create Run
As Account.
2. Create a Run As Account called Administrator account for Contoso\Administrator with the
password of Pa$$w0rd.
X Task 2: Create a user role for the StockTrader Business Unit

1. Create a new Self-Service User profile, called StockTrader Business Unit.
2. Add the StockTrader security group as a member of StockTrader Business Unit.
3. Configure MSSCVMMLibrary as a resource for the StockTrader Business Unit.
4. Allow the following actions: Author, Checkpoint, Deploy, Local Administrator, Remote
Connection, Shut down, and Start.
5. When the task is complete, close the Jobs window.
6. Open a new connection to the VMM Manager console in context of Contoso\Bart with the
password of Pa$$w0rd. Clear the Automatically connect with these settings check box and
verify that you can only see the Clouds node in the VMs and Services workspace.
7. Close the VMM instance that was started with the Contoso\Bart credentials.
Results: After this exercise, you should have configured a User role and a Run As account.
Exercise 4: Configuring the Library

Scenario
To provide balance and redundancy you decide to implement an additional VMM Library share.
1. Add a Library share.
X Task: Add a Library share

Use the VMM Manager console to add the VHD shared folder on LON-VM1.Contoso.com as a
Library share.
Results: After this exercise, you should have configured a library share.
Exercise 5: Preparing the Private Cloud Infrastructure

Scenario
In order to prepare private cloud infrastructure resources, you must create a new logical network, a MAC
pool, and a virtual IP (VIP) template.
1. Create a new Logical Network.
2. Create an IP Pool for the External Network.

3. Create a MAC Pool and a Virtual IP template.
X Task 1: Create a new Logical Network

1. In VMM console, click the Fabric workspace, expand the Networking node and then create a new
logical network.
2. Name the new logical network StockTrader Production Network.
3. Create a new IP pool named StockTrader IP Pool. Select the StockTrader Production Network as
the logical network.
4. Create a network site named Contoso HQ, with a subnet 172.16.0.0/16. Allow the Production host
group to use the network site.
5. Configure 172.16.0.100 as a reserved IP address.

6. Configure 172.16.0.200 as a default gateway.
7. Configure 172.16.0.10 as a DNS server address and Contoso.com as a Connection specific DNS
suffix.
X Task 2: Create an IP Pool for the External Network

1. Create a new IP pool named External. Select the External Network as the logical network.
2. Create a network site named External, with a subnet 10.10.0.0/16. Allow the Production host group
to use the network site.
3. Configure 10.10.0.80 as the Starting IP address.
4. Configure 10.10.0.95 as the Ending IP address.
5. Configure the Gateway address as 10.10.0.1.
6. Configure the DNS Server Address as 10.10.0.10 and Contoso.com as a Connection specific DNS
suffix.
X Task 3: Create a MAC Pool and a virtual IP template

1. Create a new MAC pool named StockTrader MAC for the Production host group with
00:27:B4:BF:A7:4F as the starting MAC address, and 00:27:B4:BF:A7:7F as the ending MAC address.
2. Create a new VIP template named web load balancer which uses Virtual IP TCP port 80. Configure a
Specific template type which uses Microsoft Network Load Balancing (NLB).
Results: After this exercise, you should have prepared private cloud infrastructure resources.
Exercise 6: Deploying a New Virtual Machine

Scenario
For testing purposes, you decide to deploy one new virtual machine that is based on a virtual hard drive
that is stored in the VMM Library.
1. Create and deploy a new virtual machine.
X Task: Create and deploy a new virtual machine

1. On LON-VM1, in the VMM console, click the VMs and Services workspace.
2. Select the option to create a new virtual machine.
3. Use VHD drive Win2008R2SP1.vhd from the library as a template. Name the new virtual machine
TestVM.
4. Configure the new virtual machine to have 1024MB of static memory.
5. Connect the new virtual machine to the External Network.
6. Deploy the new virtual machine on lon-host1.contoso.com.
7. On the Add Properties page, select 64-bit edition of Windows Server 2008 R2 Enterprise.
Results: After this exercise, you should have deployed new virtual machine.
Modulle Revie
ew and Takeaw
ways
Rev
view Questiions
1. What is a servvice in VMM te
erminology?
2. What is privatte cloud infrasstructure in VM
MM terminolog
gy?
3. Which earlierr version of VM pgrade to 201 2 VMM?

MM can you up
4. What is dynamic optimizatiion?

5. Why should you
y configure roles?
Com
mmon Issue
es
Isssues Trou bleshooting tips
VMM Managem
ment Server cannot install. Veriffy that all prerrequisite comp
ponents are
instaalled.
Veriffy if you have privileges to in
nstall VMM.
Upgrading to VMM
V 2012 failss. Veriffy that you aree upgrading a supported verrsion
of V MM.
Yo
ou cannot placce a virtual ma
achine on a specific Checck host resour ces.
ho
ost. Checck host rating explanation.
Checck custom prooperties on thee virtual machine,
and the host and pplacement rule es on the hostt
grou
up.
Yo
ou cannot add
d a host to a VMM
V console. Veriffy that Remotee Managemen
nt is enabled on a
hostt
Best Practices Related to a Particular Technology Area in This Module

Provide enough hardware resources for VMM components.
Before deploying virtual machines, create a private cloud infrastructure and library resources.
Deploy VMM as a highly available component.
Use dynamic optimization to save energy and resources.
Leverage user roles.
Tools
Tools Used for Where to find it
VMM management console VMM Administration Start Menu
Windows PowerShell VMM Administration Start Menu

3-1
Module 3
Extending and Maintaining the Private Cloud Infrastructure
Contents:
Lesson 1: Overview of the PXE and Update Server Roles 3-3
Lesson 2: Deploying Bare Metal Hyper-V Host Servers 3-8
Lesson 3: Configuring the Update Server Role 3-18

Lesson 4: Creating and Remediating an Update Baseline 3-27
Lab: Maintaining the Private Cloud Infrastructure 3-34

3-2 Extending and
a Maintaining the Private Cloud Infrasttructure
Module Overrview
Maintaining the innfrastructure in Microsoft System Cente r 2012 - Virtuaal Machine Maanager (VMM))
includes tasks such as adding ne ew Windows Server
S Hyper-VV host serverrs, and ensurinng that the
infra
astructure com
mponents conttain the latest approved softtware updates.. VMM provide es support for
converting a physsical server without an operaating system in
nto a fully man naged Hyper-VV host. VMM aalso
inte
egrates functio
onality provided by the Wind dows Server 2008 R2 featu ure Windows Server Update
Servvices (WSUS), to e compliant witth the latest update baseline
t ensure that all servers are e requirements
In th
his module, yo
ou will learn ab
bout integratin
ng features pro
ovided by Win
ndows Deplo
oyment Service
es and
WSU US to help extend and mana age the VMM private cloud infrastructure.
Afte y will be able to:

er completing this module, you
Describe how ates with WDS and WSUS to provide PXE SServer role and
w VMM integra d Update Server
roles.
Describe how
w to deploy bare-metal Hype
er-V host serveers.
Configure the
e Update Serve
er role.
emediate a sofftware update compliance baaseline.

Create and re
10751A: Connfiguring and Deployying a Private Cloud with System Center 2012 3-3
Lesson
n1
Overv
view of the PXE and Update
U SServer R
Roles
Th
he PXE Server and Update Server roles aree used within tthe VMM infraastructure to help deploy new
w host
se
ervers, and to manage
m updattes for servers that make up the private clo
oud.
In
n this lesson yo w VMM 2012 integrates with
ou will see how h PXE and softw
ware update sservices to provvide a
co
onsistent and efficient
e deplo
oyment and up
pdate manage ment solution for the virtual server enviro
onment.
After completin
ng this lesson, you
y will be able to:
he VMM PXE Server architectture.

Describe th
Describe th
he update man
nagement proccess in the VM
MM environment.
3-4 Extending and
VM
MM PXE Se
erver Architecture
Whe en managing a virtual data center

c using VMM
V 2012, a ccommon task iis configuring and adding ne ew
Hypper-V host servvers to the envvironment as a standalone o r clustered ressource. You can add existing
g
Hypper-V hosts andd host clusterss, or you can use
u VMM to di scover a new sserver withoutt an operating
system. You can then deploy a virtual
v machinne and configu
uration to the nnew system too become a
mannaged Hyper-V V host.
VMM 2012 suppo orts discovery of
o servers with
hout an operatting system, an
nd then fully p
provisions the
servvers with Hype
er-V enabled. After
A discovering the host co
omputer, the pprovisioning prrocess compleetes as
follo
ows:
1. After the out of band disco
overy, the bare-metal server reboots using the built-in PX
XE boot
capabilities.
2. The bare mettal server seekss out a WDS seerver that has been added to
o VMM 2012 aas a managed
server role. Th
he WDS serverr contains a VM
MM provider tthat manages PXE requests ffrom bare mettal
servers that have
h been startted using the VMM
V provisio
oning tools.
3. The VMM pro ovider on the WDS

W server co ontacts the VM MM server to v erify that the b bare-metal serrver
has the autho
orization to peerform a managed host depl oyment. If thee server has no ot been authorrized
from within VMM,
V then WD DS attempts to
o use another p provider to insstall an operatting system on
n the
bare metal machine.
m If no other
o provider is available, th
hen the PXE innstallation failss.
4. If the server iss authorized within

w VMM, a Windows Preiinstallation Envvironment (Windows PE) im
mage
downloads to o the server, which contains a VMM agent controls the o operating syste
em deploymennt to
the host serve er.
5. The VMM age ent runs generic command scripts

s that yo
ou can specify tto update firm
mware, configu
ure
redundant array of indepen
ndent disks (RA
AID), and conffigure and form
mat partitions..
6. A virtual hard disk (VHD) downloads from the library server to the host computer. Hyper-V host
deployment uses native boot from VHD.
7. Any drivers that are host-specific can be installed from the library server.
8. Post-deployment customizations take place, such as using the System Preparation Tool (Sysprep)
setup process to provide settings such as a unique name for the server, and joining the server to the
domain.
9. The final step in the provisioning process is to install and enable the Hyper-V server role.
Question: What do you think the next step might be when adding the new host server to
the VMM environment?
3-6 Extending and
The Update Managem

ment Process in the V
VMM Envirronment
Microsoft providees a number off solutions for scanning com

mputers for com mpliance and ddeploying softtware
upddates. Howeverr, some network clientssucch as cluster-b
based server no odes or other highly available
servver rolestypically present complexities
c hat can make iit difficult and time-consuming to maintaiin a
th
stan
ndard update management
m process.
p
VMM 2012 integrrates with WSU US to provide on-demand

o coompliance scanning and rem mediation of se
ervers
thatt make up the infrastructure, including Hyper V hosts, lib
brary servers, P
PXE servers, an
nd the VMM
mannagement servver.
Inte
egrating WSUS S with VMM 20 012 also providdes you with t he ability to p
perform orchesstrated update es of
Hypper-V host clussters. When yo
ou remediate a host cluster, V VMM places o one cluster nod de at a time in
n
maintenance mod de, and then in
nstalls the approved updatess. For clusters that support liive migration,
inte ment moves virrtual machiness off the cluste r node being u
elligent placem updated. If a ccluster does no
ot
support live migraation, then VM
MM saves the state
s of the virrtual machiness before updating the clusterr
nodde.
Note You must have Windows Server 2008 R2 for livve migration ssupport.
The process for im

mplementing update
u management within your VMM en
nvironment is aas follows:
1. To use VMM 2012 to mana age updates, yoou must first eenable update managementt. You enable
update mana
agement by ad ng WSUS serveer to VMM, orr you can instaall a dedicated
dding an existin
WSUS server, and then add
d the new upda ate server to V
VMM.
2. After you add d the WSUS server to VMM, you can then configure and d manage updaate baselines. An
update baseliine specifies a set of updatess to be deployyed to a host g
group, a standaalone host, a h
host
cluster, or a VMM
V server.
3. Once you have assigned an update baseline, you can start a scan to determine compliance status.
During a compliance scan, WSUS checks each update in the assigned update baseline to determine
whether the update is applicable and installed on the target server. The target server will then report
a compliance status for each update.
4. You perform an update remediation to bring a managed server or Hyper-V host cluster into
compliance. You can choose to remediate either all update baselines assigned to a computer, all
noncompliant updates in a specific update baseline, or a single update as needed.
5. You can specify update exemptions to prevent a specific update from being installed on a server. The
computer will still remain accountable for the assigned baseline, even if a specific update has been
exempted from being installed.
3-8 Extending and
Lesson 2
Deploy
ying Bare Meta
al Hype
er-V Hosst Serve
ers
To discover
d and deploy
d the Hyp
per-V host servver role to a baare metal com
mputer, you mu
ust first undersstand
seve
eral configurattion requireme
ents related to
o both the servver and VMM eenvironment.
In thhis lesson you will learn about the requirements and pro ocess for integ
grating a PXE SServer role into
o the
privvate cloud infra
astructure. Youu will also learn about how yyou use the Ad
dd Resource WWizard to disco over
and deploy a Hyp per-V host.

Describe the requirements for PXE serverr integration.
Describe the process for ba

are metal deplo
oyment.
Describe how
w to configure and add the PXE
P Server rolee to VMM.
Prepare and create

c the host profile.
Use the Add Resource Wiza
ard to discoverr and deploy a Hyper-V hostt.
10751A: Connfiguring and Deployying a Private Cloud with System Center 2012 3-9
Requireme
R nts for PX
XE Server In
ntegration
n
To
o add the PXE Server role to
o your VMM en nvironment, yo ou need to ensure that prere
equisites and
re
equirements arre met for both the physical server and thee VMM infrasttructure.
Physical
P Serv
ver Requirem
ments
o support the VMM host deployment proccess through, yyou need to e nsure that the
To e physical serve
er meets
th
he following re
equirements:
Support forr Hyper-V. The server must use X64-based processors. Yo ou may also ne
eed to configu ure the
appropriate output system (BIOS) setting
e basic input/o hat Hardware-aassisted virtuallization
gs to ensure th
and hardwa are-enforced Data
D Execution
n Prevention (DDEP) are both enabled.
Note Th he names assocciated with hardware-assisteed virtualizatio

on and hardware-enforced
DEP may vary
v based upo
on manufacturer. Check withh your serverss manufacturer to verify
equivalentt settings.
Support forr PXE Boot. The e server must support

s PXE bo
oot. You may also need to sset the boot orrder to
ensure thatt the first boott device is the PXE-enabled n
network adaptter.
Support forr out-of-band management.

m For VMM 20122 to discover tthe physical se
erver and manage
power statees, the server must
m have a ba
aseboard man agement conttroller (BMC). T The BMC itselff should
support anyy one of the foollowing proto
ocols:
Microsoft Intelligent Platform Man

nagement Inte rface (IPMI) veersions 1.5 or 2
2.0
Data Center Manage
ement Interface (DCMI) versiion 1.0
System
ms Managemen
nt Architecture
e for Server Haardware (SMASSH) version 1.0
0 over WS-
Managgement
3-10 Extending and Maintaining the Private Cloud Infrastructure
You will need to configure the BMC to enable the appropriate protocol, and configure the local area
network (LAN) parameters, such as the domain and host name, IP address source (static or dynamic),
the IP address (if configured to use DHCP), and logon credentials for the BMC.
VMM Requirements
To support the PXE Server role in VMM 2012, the following infrastructure requirements need to be
considered:
Windows Deployment Services. The PXE Server role in VMM 2012 uses the Windows Deployment
Services server role, which is available in Windows Server 2008. You can use an existing Windows
Deployment Services server, or you can deploy a dedicated Windows Deployment Services server for
VMM. Consider the following when integrating Windows Deployment Services into the VMM
environment:
When you install the Windows Deployment Services server role, select both the Deployment
Server and Transport Server options. After the server role installs, you can run the Windows
Deployment Services Configuration Wizard and accept all default settings. When prompted, do
not add images to the server.
You do not have to configure any settings on the PXE Response tab. VMM installs its own
provider and agent, which it uses to respond to VMMinitiated PXE requests. The provider will
coexist with other providers, such as the provider which installs when integrating Microsoft
System Center 2012 Configuration Manager.
You do not have to add images to WDS. During managed host deployment, VMM will use a
preconfigured .vhd file that is stored in the VMM library.
Account Credentials. To add a PXE Server to the VMM environment, you need to provide credentials
for an account that has local permissions on the WDS server. You can provide these credentials by
creating and specifying a VMM-configured Run As account that you configure with the appropriate
administrative credentials.
Additional Reading
Hyper-V Installation Prerequisites
Prepare the Physical Computers
How to Add a PXE Server to VMM

10751A: Conffiguring and Deploying a Private Cloud w
Process
P forr Bare Mettal Deploym
ment
Th
he process for performing a bare-metal de
eployment forr a managed H
Hyper-V host iss as follows:
1.. Prepare thee physical server. This step in

ncludes all BIO
OS and BMC co
onfiguration se
ettings, as desccribed
in the previious topic.
2.. Add the PXXE server to the

e VMM environment. From w within the VM
MM manageme ent console, usse the
Add PXE Server dialog boxb to providee the compute r name and crredentials that are required tto add
an existing WDS server too the VMM inffrastructure.
3.. Add libraryy resources. Lib

brary resourcess that you nee d to make avaailable include a generalized
d
Windows Server 2008 R2 .vhd file, and any device driiver files necesssary for the bare-metal servvers.
4.. Create hostt profiles. You can create and
d store one orr more host prrofiles within th
he VMM librarry. You
create a ho
ost profile using
g the New Ho ost Profile Wizzard. The hostt profile contaains various setttings
such as whiich operating system .vhd fille to use, hard ware configurration, operatin
ng system
configuratio
on, and virtual machine placcement paths ffor default loccations to storee virtual machines.
5.. Run the Ad dd Resource Wizard.

W When you use the A Add Resource e Wizard, the P Physical comp puters
to be prov visioned as virrtual machine e hosts optionn should be sellected. This op
ption allows yo
ou to
specify the Run As account and out of band manageement protoco ol to use for disscovery. You also
specify setttings such as th
he IP address, subnet, or ran
nge discovery sscope for baseeboard management
controllers, host provisionning options such as which h host group to assign the serrver to and the
e host
profile to use.
After the Add Resource

R Wizarrd completes, a host job is c reated and thee VMM manag gement serverr restarts
th
he physical com
mputer. After the
t restart, the e PXE server reesponds to thee boot requestts by providingga
cu
ustomized Win ndows PE boott image. The Windows
W PE ag gent performs configurationn tasks such as
co
onfiguring thee hardware, downloading the e operating sy stem VHD, injeecting device driver files as n
needed,
an
nd then enable es the Hyper-V
V server role.
3-12 Extendingg and Maintaining the Private Cloud Infraastructure
Co
onfiguring and Addin
ng the PXE
E Server Ro
ole to VMM
The process for co

onfiguring and
d adding the PXE
P Server rolee to VMM is ass follows:
1. Open the VM
MM manageme
ent console, an
nd then click th
he Fabric worrkspace.
2. In the navigattion pane, exp
pand the Serve
ers node, and then click the PXE Servers node.
3. In the ribbon, click Add Resources, and then

t click PXEE Server. The A
Add PXE Serv
ver dialog box
opens.
4. In the Add PX
XE Server diallog box, config
gure the follow
wing settings, and then clickk Add:
Computeer name. Provid

de the name of
o the PXE servver you will add to the VMM
M environment.
Credentiaals. Provide cre

edentials from
m an existing Ru
un As accountt, or enter a usser name and
password d. The accountt credentials th
hat you use muust have local administrativee rights on the
e PXE
server that you are add ding.
The Jobs dialog box

b opens to provide
p a setupp status for thee new PXE servver. You can vverify that the sserver
has been added by
b clicking the PXE Servers node in the Faabric workspacce. The new PX XE Server shou uld
have the Agent Status
S column display a statu
us of Respond ding.
Preparing
P For
F and Crreating the
e Host Pro
ofile
Be
efore creating a host profile,, you need to ensure that alll prerequisite ccomponents aare available in
n the
VMM library. Yoou also need to address configuration setttings within th e VMM enviro onment. The fo ollowing
se es the prerequisites for creatting a host pro
ection discusse ofile.
Host
H Profile Prerequisites
Be
efore you crea
ate a host proffile, consider th
he following p
prerequisites:
Windows Server 2008 R2 .vhd file. The host profile reeferences a .vh hd file that it w
will use for the
managed Hyper-V
H host deployment.
d Th
he .vhd file is sstored in the V
VMM library, aand must contaain a
generalizedd x64-based Windows
W Server 2008 R2 or H Hyper-V Serverr 2008 R2 operating system. It is
recommend ded that you use
u a fixed .vhdd file to help i ncrease perforrmance. By de efault, the hostt profile
specifies to convert a dyn
namic disk to a fixed disk. Yo
ou can modify this default behavior when you
configure the host profile
e.
Device drivvers. If the servver requires any custom devi ce drivers, youu must place these in the VM
MM
u have the choice of configuring the host p
library. You profile to filterr drivers based
d upon a match
hing
plug and play ID, or you can tag specific drivers man nually, and then filter them b based upon maatching
custom tag gs.
Dynamic Host Configurattion Protocol (DHCP)

( or stattic IP address. During the ho
ost profile
configuratio eed to specify how the netw
on, you will ne work adapter on the server w will obtain its IP
P
address. Yo
ou can obtain an
a IP address from
f DHCP, orr you can speccify to allocatee a static IP from a
preconfigured logical nettwork. In order to assign a sttatic IP addresss from VMM, the logical nettwork
must have a configured associated
a netw ubnet, and static IP address pool.
work site, IP su
Run As acco
ount. You need to configure
e a Run As accoount that VMM oin the target host to
M will use to jo
the domain
n. You can crea m the Settings workspace in the VMM con
ate the Run Ass account from nsole.
Creating a Host Profile

The process for creating a host profile is as follows:
1. Open the VMM console, and then click the Library workspace.
2. In the navigation pane, expand the Profiles node, and then click the Host Profiles node.
3. In the ribbon, click Create, and then click Host Profile. The New Host Profile Wizard starts.
4. In the New Host Profile Wizard, on the Profile Description page, configure the following, and then
click Next:
Name. Provide a name for the host profile.
Description. Provide a descriptor that will help identify the host profile use.
5. In the New Host Profile Wizard, on the OS Image page, next to VHD file, provide the library path
and name of the VHD file for deployment. By default a dynamic hard disk will be converted
automatically to a fixed disk. If you do not want this behavior to occur, select the Do not convert the
VHD to fixed type during deployment check box. Click Next.
6. On the Hardware Configuration page, configure the following settings, and then click Next:
Management NIC. You can choose between obtaining an IP address through DHCP, or you can
allocate a static IP address from a specified logical network.
Disk. This setting configures the partitioning scheme for the first disk. You can select either
Master Boot Record (MBR) or GUID Partition Table (GPT). By default, MBR is selected. If
computers use Extensible Firmware Interface (EFI), then you should select Guid Partition Table.
OS. Under the Disk section, you can select OS. In the Partition information pane, you can specify
a Volume label for the partition, select whether to use all remaining free disk space or only use a
specified amount of space, and specify whether to make this the boot partition. You can select
the Add Disk or Add Partition buttons to add additional disks or partitions as needed.
Driver filter. The Driver filter option allows you to choose between Filter drivers with matching
PnP IDs, or Filter drivers with all matching tags specified below. If you choose to filter using
matching tags, VMM will only consider drivers that you have tagged specifically to for use by the
configuration. This ensures that only drivers that you have tested are installed into the
deployment. You need to ensure that all driver files are added to the VMM library, and if you
decide to use matching tags, you need to assign corresponding tags to the drivers in the library
share.
7. On the OS Configuration page, configure the following settings, and then click Next:
Domain. In the Domain text box, specify the domain that the Hyper-V host is to join. You also
need to specify a pre-configured Run As account that has permissions to join the host to the
domain.
Admin Password. This setting specifies the password that you want to assign to the local
administrator account.
Identity Information. This setting specifies the Full name and Organization name for the
operating system deployment.
Product Key. This setting specifies the product key to be used for activation. If you do not provide
a product key, the standard activation grace period is applied.
Time Zone. Use this setting to specify the time zone for the host computer.
Answer File. You can use this setting to specify an Unattend.xml file to be used during
deployment. You must store the answer file the VMM library.
[GUIRunOnce] Commands. You can use this setting to specify one or more commands to be run
the first time a user logs on to the server. Any commands specified in this section will be added
to the [GuiRunOnce] section of the Sysprep file.
8. On the Host Settings page, you can specify the path to be used to store the files associated with the
virtual machines that are placed on the host. If you do not specify a path, VMM placement processes
will determine the most suitable location. You can change the path after you deploy the host, if
needed.
Additional Reading
How to Create a Host Profile
Understanding Virtual Hard Disks with Native Boot

Using the Ad
dd Resourcce Wizard to Discovver and Deploy a Hyp
per-V Hosst
You
u can use the Add
A Resource Wizard
W to disccover a physicaal computer, and then to deploy a fully-
man
naged Hyper-V V host. The phhysical server can be a bare-m metal computeer, or it may co
ontain an existting
ope
erating system that you will overwrite
o durin ng the deploy ment process.
Pre
erequisites
Befo
ore you run the Add Resourcce Wizard, con
nsider the follo
owing prerequ
uisites:
Physical serveer and VMM reequirements. You
Y must havee already config
gured the phyysical server, an
nd
already added d the PXE Servver role to VMM.
Media access control (MAC)) Address. If yo

ou decide to asssign a static I P address on tthe host server, you
need to obtain the MAC ad ddress of the network
n adapteer that you will use to comm municate with the
VMM management server. You can obtaiin the MAC ad ddress from the server BIOS, or from the
hardware con
nfiguration listings from the hardware man nufacturer.
Run As accou
unt. You can co
onfigure a Run
n As account th
hat has permisssions to accesss the BMC use
ed for
out of band management.
m
Disscovering an
nd Deployin
ng a Hyper--V Host
The process for diiscovering and
d deploying a Hyper-V
H host is as follows:
1. Open the VM
MM console, an
nd then click th
he Fabric panee.
2. In the ribbon, click Add Resources, and then

t click Hyp
per-V Hosts and Clusters. T
The Add Resou
urce
Wizard starts.
3. In the Add Re
esource Wizaard, on the Ressource locatio
on page, selecct the Physicall computers tto be
provisioned as virtual ma
achine hosts option,
o and theen click Next. You use this o
option for both
h
bare-metal co
omputers and computers that are to be reefreshed with a new operatinng system.
4. In the Add Resource Wizard, on the Credentials and protocol page, specify the Run As account,
configure the appropriate out of band management protocol to be used for discovery, and then click
Next.
5. In the Add Resource Wizard, on the Discovery scope page, specify IP address, IP subnet, or IP
range to be used for discovering the BMC IP address, and then click Next.
6. If you selected the IP subnet or IP range, the Target resources page will list all discovered
computers within the scope. Select the check box next to each server that you want to deploy as a
Hyper-V host, and then click Next.
7. In the Add Resource Wizard, on the Provisioning Options page, select the host group of which the
new Hyper-V host will become a member. You also use this page to specify whether the Hyper-V host
will obtain IP addresses and other network settings from DHCP, or whether static IP addresses will be
assigned from an IP address pool. For both options, you also specify a specific host profile to be
applied during the deployment.
8. On the Deployment customization page, perform the following:

For a host profile that uses DHCP, select each BMC IP address on the list, and then specify the
computer name that should be associated with them. You can also choose to select the Skip
Active Directory check for this computer name option. You would select this option if you
want to overwrite any existing computer account listed in Active Directory Domain Services.
For a host profile that uses static IP addresses, select each BMC IP address in the list, and then
specify the computer name that should be associated with them. You can also choose to select
the Skip Active Directory check for this computer name option. In the MAC address text box
specify the MAC address of the network adapter that communicates with the VMM management
server. Note that this is not the MAC address of the BMC. Finally, select the logical network and
IP subnet that will provide the IP address.
Additional Reading
How to Discover Physical Computers and Deploy as Hyper-V Hosts
Lesson 3
Config
guring the
t Upd
date Serrver Role
VMM 2012 provid des support for on-demand software updaate compliancee scanning, an nd for remediaation
of servers that ma
ake up your prrivate cloud inffrastructure. Itt is important tto understand how VMM 20 012
inte
egrates with WSUS
W to help maintain
m softwa
are update basselines, and ho ow you can easily plan specific
scen
narios such as updating hostt cluster resources.
Afte
ou will be able to:
Explain how the

t Update Server role mana
ages server up
pdates.
Describe conssiderations forr integrating WSUS

W with VM M 2012.
Add an Upda
ate Server to VMM.
ate settings in VMM.

Manage upda
Managing
M Server Updates
Maintaining
M seccurity and softw
ware updates has become a prevalent task in most orgaanizations.
Administration tools such as Configuration
C Manager and WSUS are botth popular to help automate e and
manage
m compliiance scanning g and update deployment.
d EEven though th hese tools worrk fine for most
in
nfrastructure reequirements, some
s scenariosssuch as updaating cluster n
nodes or updatting other highhly
avvailable data center
c rolesbe
ecome more complicated.
Yo
ou can use thee Update Serve er role in VMMM 2012 to man
nage update taasks for servers that make up
p your
private cloud in
nfrastructure. These
T include:
Hyper-V ho
osts
Hyper-V clu
usters
Library servvers
PXE serverss
VMM serve
ers
For More Information You only use e the Update SServer role forr updating servvers that
make up the
t VMM infrastructure. For maintaining u updates for VM MMmanaged virtual
machines, you must use a compatible solution similaar to the Virtu
ual Machine Se ervicing Tool
0. For more infformation abo
(VSMT) 3.0 out updates to this solution aaccelerator, refer to Virtual
Machine Servicing
S Too ol (VMST) 3.0 at http://tech
hnet.microsofft.com
/en-us/lib
brary/cc50123 31.aspx.
Fo oles within the VMM infrastru

or all server ro ucture, you scaan against a baaseline of app proved updatess to
etermine compliance status.. For any serve
de ers that are non n-compliant, yyou can perforrm update
re
emediation tassks to have the e missing upda
ates installed aand the serverss restarted, if n
necessary.
For a Hyper-V cluster, VMM performs a rolling update for each cluster node. The process for performing
the rolling update includes the following:
1. VMM places a non-compliant node into maintenance mode. If a node is compliant, VMM will bypass
the node and continue with the next node in the cluster.
1. If specified, VMM uses live migration to move the virtual machines from the host being updated. You
also have the option to save state, which will shut down the virtual machines, and then proceed with
the update remediation tasks.
2. If specified, the server will reboot to complete the update. Once the server reboots, the node
compliance status changes to Compliant, and the node is removed from maintenance mode.
Considerat
C ions for In
ntegrating WSUS
Th
he VMM 2012 Update Serve
er role uses WS
SUS functionallity for the foll owing:
The Window
ws Update and
d Microsoft Up
pdate catalog
The Window
ws Update Agent for compliance scanning
g
Update disttribution of the binary files to

t managed seervers
To
o integrate the
e Update Seve
er role, you nee
ed to install W
WSUS 3.0 64-bitt with Service Pack 2 (SP2) e
either on
th
he VMM server, or on a remoote server.
Note Be e sure that the server that ho

osts WSUS meeets all prerequisites for WSUS 3.0 SP2 x64
as listed on the Microsoft website.
Yo
ou can also inttegrate an exissting WSUS server; however,, you must maake special con
nsiderations if tthe
WSUS
W server is also shared wiith Configuratiion Manager.
Consider the following when integrating WSUS

W into the V
VMM infrastructure:
If WSUS is installed
i on a remote
r server,, you must insttall the WSUS Administration console on tthe
VMM mana agement serve er. If the VMM managementt server is part of a cluster, yo ou must install the
WSUS administration con nsole on each node of the cl uster.
If you are using

u a dedicatted WSUS servver, consider li miting the lan
nguages, produ
ucts, and
classificatio
ons to only tho hat make up t he VMM infrastructure.
ose required byy the servers th
If you are using a WSUS server that is shared with a Configuration Manager environment:
You should only make WSUS configuration changes from within Configuration Manager.
Note that for the VMM environment, the synchronization schedule is always on demand.
In Configuration Manager, create a collection that includes all of the servers for which VMM will
manage updates. Exclude this collection from any software update deployments that
Configuration Manager deploys.
After you add the WSUS server to VMM, ensure that the Allow Update Server configuration
changes check box is cleared. You configure this in the Virtual Machine Manager console Update
Server Properties window.
Additional Reading
How to Install a WSUS Server for VMM
How to Integrate Fabric Updates with Configuration Manager

Adding
A an Update Se
erver to VM
MM
Th
he process for adding the Update server to
o VMM is as fo
ollows:
1.. Open the VMM

V console, and then click
k the Fabric paane.
2.. In the navig
gation pane, expand the Serrvers node, an
nd then click th
he Update Serrver node.
3.. In the ribbo

on, click Add Resources,
R and then click U pdate Server.. The Add Win
ndows Serverr
Update Services Server dialog box op pens.
4.. In the Add Windows Serrver Update Services
S Serve
er dialog box, configure the following setttings,
and then click Add:
Compu uter name. Pro

ovide the name
e of the WSUS server that yo
ou want to add
d to the VMM
infrastrructure.
TCP/IP t TCP/IP port that the WSSUS website listtens on for connections. A d
P port. Specify the default
WSUS installation will typically use the Internet I nformation Seervices (IIS) deffault website o
on port
80 (porrt 443 for SSL), or a custom website
w using port 8530 (85531 for SSL).
Creden
ntials. You can provide crede
entials from ann existing Run As account, orr enter a user nname
and pa
assword. The account creden ntials that you enter must haave local adminnistrative rightts on
SUS server thatt you are adding.
the WS
Th
he Jobs dialogg box opens too provide a settup status for tthe new Update server. You can verify that the
se
erver has been
n added by cliccking the Upda ate Server no ode in the Fabrric pane. The n new Update Se
erver
sh
hould display with
w the WSUS S version, and have the Agen umn show a staatus of Responding.
nt Status colu
Th a Synchronization Result columns also
he Last Sync and o display the reesults of the W
WSUS synchron
nization
with
w Windows Update.
U
To view the updates that have been downloaded during WSUS synchronization, perform the following
steps:
1. Open the VMM console, and click the Library workspace.
2. In the navigation pane, expand the Update Catalog and Baselines node, and then click the Update
Catalog node. You can select an update to view a description and additional details for the update.
By default, only the first 100 updates display. If you want to view all of the downloaded updates, click
the Load All Updates button, which is located in the ribbon.
VMM 2012 does not perform scheduled automatic synchronization after the initial synchronization. To
perform on-demand synchronizations, perform the following steps:
1. Open the VMM console, and then click the Fabric pane.
2. In the navigation pane, expand the Servers node, and then click the Update Server node.
3. In the results pane, select the update server, and then in the ribbon, click Synchronize. The Jobs
window opens to display synchronization results.
Additional Reading
How to Add an Update Server to VMM
Managing
M Update Se
ettings in VMM
V
When
W you add a dedicated WSUS
W server to VMM, all mannagement taskks should take place from within the
VMM console. Once
O you add an Update Server, you can p ollowing tasks from within V
perform the fo VMM:
On-demand
d WSUS synch
hronization witth Windows Up
pdate
Proxy Serve
er name and port
p settings, iff required for cconnecting to the Internet fo
or WSUS
synchroniza
ations
Specifying update classifiications to synchronize
Specifying products to syynchronize
Specifying supported languages to synchronize

To
o manage upd
date settings, perform
p the fo
ollowing tasks:
1.. Open the VMM

k the Fabric wo
orkspace.
2.. In the navig

gation pane, expand the Serrvers node, an
nd then click th
he Update Serrver node.
3.. In the results pane, selectt the update se

erver, and then
n in the ribbon
n, click Properrties. The Prop
perties
dialog box opens.
4.. In the Prop

perties dialog box, on the General page, vverify that the Allow Updatte Server
configurattion changes check
c box is se
elected. This o
option is requirred to apply co
onfiguration cchanges
to the WSUUS server.
5.. In the Prop

perties dialog box, on the Prroxy Server p
page, configuree a proxy serve
er name and p
port
number if needed.
n
6.. In the Prop

perties dialog box, on the Update Classiffications pagee, select the up
pdate classificaations
that you wa
ant to synchro
onize.
7. In the Properties dialog box, on the Products page, select the products that you want to
synchronize. For a dedicated WSUS installation, this should only be products that are installed within
your VMM infrastructure.
8. In the Properties dialog box, on the Languages page, select the languages that you support and for
which you want software updates.
9. Click OK to apply the changes, and close the Properties dialog box.
Additional Reading
How to Update WSUS Settings in VMM
Lesson
n4
Creatting and
d Remed
diating an Upd
date Basseline
After you have added a WSUS S server to VMMM to perform m the Update SServer role, youur next step is to
de
etermine whicch updates you private cloud infrastructure. VMM
u should install on each serveer within the p
ad
dds the update gainst which eeach server scaans. VMM can then
es that you sellect to an update baseline ag
re
emediate any server
s that doe
es not meet thhe baseline to have the missiing updates innstalled as needed.
After completin
ng this lesson, you
y will be able to:
Describe co
onsiderations for
f planning an
n update baseeline.
Configure an
a update baseline.
Scan for up
pdate complian
nce.
Perform up
pdate remediattion on a non--compliant serrver.
Co
onsideratio
ons for Planning an Update
U Baaseline
Whe en you determ mine which upd dates are requ

uired for your V
VMM infrastru
ucture servers, you need to ccreate
a lisst for use as a baseline
b to be scanned againnst and remeddiated. VMM uuses the update baseline as tthe
list, from which yo ou can add or remove updattes as needed..
Wh
hat Is an Update Baselin
ne?
All updates
u from a specific prod
duct and categ gory is displayeed within the V
VMM console when you
syncchronize with WSUS.
W To speccify only the updates necesssary for your reequirements, yyou create an
upd A update basseline is made up of a set of required updaates that are assigned to a sccope
date baseline. An
of in
nfrastructure servers
s within the
t private clo oud. You can a ssign a baselinne to the follow
wing:
All hosts with
hin all host gro
oups
Specific host groups
A specific standalone server within a hostt group

A specific hosst cluster within a host group
p
Library serverrs
PXE servers
The VMM serrver
Update Serve
er
Planning Considerations
Consider the following when planning update baselines:
If you have assigned a baseline to a host group, any host or host cluster within that group will be
assigned to that baseline. If you move a host to a new host group, the original baseline will be
removed, and the host will inherit the baseline associated with the new host group.
If you assign a baseline specifically to a standalone host or host cluster, the baseline will stay with the
object when it moves from one host group to another.
When you first add the Update Server, two built-in update baselines are provided. The Sample
Baseline for Critical Updates contains all of the critical updates that are initially synchronized. The
Sample Baseline for Security Updates contains all of the security updates that are initially
synchronized. If you plan to use these built-in update baselines, you will need to maintain the
updates as you perform subsequent synchronization tasks. You also need to assign computers to the
baseline before you are able to use the baseline for compliance scanning and remediation.
You can create a new update baseline that contains updates that you require, and that you assign to
the servers that you want to maintain update compliance.
Co
onfiguring an Update
e Baseline
Wheether you mod dify one of the

e sample update baselines o r create a new
w baseline, use the following
proccess to modifyy the baseline settings:
1. Open the VM
MM console, an
nd then click th
he Library wo
orkspace.
2. In the navigattion pane, exp

pand the Upda
ate Catalog an
nd Baselines node, and the
en select the
Update Base elines node.
3. If you want to
o create a new
w update baseline, in the ribbbon, click Crea
ate, and then cclick Baseline.. If
you want to modify
m one of the sample ba
aselines, selectt the desired b
baseline, and th
hen in the ribb
bon,
click Properties.
4. In the Properrties dialog bo
ox, on the Gen
neral page, pro
ovide a Name
e and Descripttion for the up
pdate
baseline.
5. In the Properrties dialog bo

ox, on the Upddates page, cliick Add. In thee Add Update es to Baseline
e
dialog box, se
elect the approopriate update
es to include in
n the baseline.. From the Updates page, yo ou
can also remoove an update e from the base
eline by select ing specific up
pdates, and then clicking
Remove.
6. ox, on the Assignment Scop
In the Properrties dialog bo pe page, selecct the host groups or individual
servers to which you want tot apply the update baselinee, and then co mplete the tassk. If any of the
selected updaates require an t a Microsoft license agreem
n acceptance to ment, the Microsoft License e
Terms dialogg box opens fo or you to accep
pt the license tterms.
7. To verify thatt the update ba ured correctly,, select the Up

aseline configu pdate Baselinees node, and tthen
in the results pane, select th
he update baseline that you created. In th he preview pan
ne, you can vie
ew
how many up pdates are conntained within the baseline, aand how manyy objects are aassigned to the
e
baseline.
Additional Reading
How to Configure Update Baselines in VMM
Sca
anning forr Update Complianc
C e
Afte
er you have assigned a baselline to a serverr, you can scann the server to
o determine coompliance status.
Wheen a scan occu
urs, the Windoows Update Ag gent on the serrver scans each h update in th
he baseline to ssee if
the update is applicable, and whether or not it is installed.
Each
h scan is perfo
ormed on-dem mand. Howeverr, you can autoomate the proocess using Win ndows
Pow
werShell. Afte er the complia
ance scan completes, each u pdate providees a status of C
Compliant, No
on-
Com
mpliant, Errorr, or Unknown n.
To scan
s for updatte compliance, perform the following
f taskss:
1. Open the VM
MM console, an he Fabric panee.
nd then click th
2. In the navigattion pane, click the Servers node, and theen in the ribbo on, click the Co
ompliance button.
In the results pane, each server that has an
a update baseeline assigned displays. You will also see e
each
servers comppliance status, and the last time a scan hass taken place.
3. elect the servers to be scann ed, and then in the ribbon, cclick the Scan
In the Complliance view, se
button. The Operational
O Status column displays that a scan is takingg place. After tthe compliancce
scan complettes, the Complliance Status column updattes. If the Com mpliance Statu us column disp plays
Non-Compliant, then you will have to perform requireed remediation tasks.
Additional Rea
ading
How to Scan for Update Co
ompliance in VMM
V
Scripting in Virtual
V Machine
e Manager
Remediatin
R ng Softwarre Update Non-Com
mpliance
When
W you chooose to remedia ate updates on
n a server or ho
ost cluster, anyy non-compliaant server is made
co
ompliant by in
nstalling missin
ng updates tha
at are defined w
within the upd date baseline. Remediation
pe
erforms on-deemand, or you can automate e it using Winddows PowerSh hell.
Yo
ou can use the ace to track the progress of an update rem
e Jobs workspa mediation taskk.
o remediate updates, perform the followin

To ng tasks:
1.. Open the VMM
k the Fabric wo
orkspace.
2.. In the navig

gation pane, click the Serverrs node, and tthen in the ribb
bon, click the Compliance b
button.
3.. In the Commpliance view, select the servvers to be rem

mediated, and tthen in the rib bbon, click the
Remediate e button. The Remediate
R bu er has a Compliance
utton is only avvailable if the sselected serve
Status of Non Compliant.
4.. In the Upda

ate Remediattion dialog bo
ox, you can seleect or clear up
pdate baseliness or individual
updates as needed.
5.. Click Reme

ediate to start update remed
diation.
Additional
A Reading
R
Performing
g Update Reme
ediation in VM
MM
Lab: Maintain
M ning the
e Private
e Cloud
d Infrasttructure
e
Lab
b Setup
Note Befo
ore starting thiss lab, you musst have compleeted the lab in
n Module 2.
For this lab, you will

w use the avaailable virtual machine
m enviro
onment. Beforre you begin the lab, you mu
ust
ensu
ure that the virtual machines are running by completing g the following
g steps:
1. On LON-HOS
ST1-B, click Sta
art, point to Administrative
A e Tools, and th
hen click Hype
er-V Manager.
M click 10751A-LON-
1 -DC1, and in tthe Actions paane, click Startt.
3. In the Action

User nam
me: Administra
ator
Password
d: Pa$$w0rd
Domain: Contoso
5. Repeat steps 2 to 4 for 107
751A-LON-SQ
Q1.
6. On LON-HOS
ST2-B, click Sta
art, point to Administrative
A e Tools, and th
hen click Hype
er-V Manager.
M click 10751A-LON-
1 -VM1, and in tthe Actions p
pane, click Starrt.
8. In the Action

Password: Pa$$w0rd
Domain: Contoso
Lab Scenario
Contoso, Ltd wants to expand its private cloud infrastructure resources. However, manually installing,
configuring, and deploying new Hyper-V hosts as they arrive requires substantial overhead. You have
been asked to implement a WDS infrastructure to provide bare-metal Hyper-V host provisioning.
Your compliance manager has also asked you to implement a new system for monitoring private cloud
infrastructure servers for update compliance against a baseline.
You must now implement these two features into the new private cloud infrastructure.
Exercise 1: Configuring a PXE Server in VMM

Scenario
You need to add the PXE Server role to VMM. To complete this task, you need to install Windows
Deployment Services, and then configure the PXE Server role in VMM.
1. Install the Windows Deployment Services Server Role.
2. Configure Windows Deployment Services.
3. Configure the PXE Server Role in VMM.
X Task 1: Install the Windows Deployment Services Server Role

1. On LON-VM1, click Start, point to Administrative Tools, and then click Server Manager.
2. Add the Windows Deployment Services server role with the Deployment Server and Transport
Server role services selected.
X Task 2: Configure Windows Deployment Services

1. On LON-VM1, click Start, point to Administrative Tools, and then click Windows Deployment
Services. The Windows Deployment Services console opens.
2. Run the Windows Deployment Services Configuration Wizard, and configure the following:
On the Remote Installation Folder Location page, verify that the path displays
C:\RemoteInstall.
On the PXE Server Initial Settings page, click Respond to all client computers (known and
unknown).
On the Operation Complete page, clear the Add images to the server now check box.
X Task 3: Configure the PXE Server Role in VMM

1. On LON-VM1, on the desktop, double-click Virtual Machine Manager Console.
2. If the Connect to Server dialog box opens, ensure that Use current Microsoft Windows session
identity is selected, and then click Connect. The Virtual Machine Manager console opens.
3. Add a PXE Server with the following options:
Computer name: LON-VM1

User name: Contoso\Administrator
Password: Pa$$w0rd
4. Monitor the status of the configuration job.
Results: After this exercise, you should have added a PXE Server to VMM.
Exercise 2: Configuring an Update Server Role in VMM

Scenario
You have been asked to add the Update Server role to VMM. You have an existing WSUS server located
on LON-VM1, which uses port 8530.
1. Add an Update Server to VMM.
X Task: Add an Update Server to VMM

1. On LON-VM1, in the VMM console, click the Fabric workspace.
2. In the navigation pane, expand the Servers node, and then click Update Server.
3. Add an Update Server with the following configuration:
Computer name: LON-VM1
TCP/IP port: 8530
User name: Contoso\Administrator
Password: Pa$$w0rd.
Results: After this exercise, you should have added the Update Server role to VMM.
Exercise 3: Configuring a Software Update Baseline in VMM

Scenario
Now that you have added the Update Server role to VMM, you need to create a software update baseline
containing several updates that the compliance team has approved.
1. Create a software update baseline.
2. Verify baseline compliance.
X Task 1: Create a software update baseline

1. On LON-VM1, in the VMM console, click the Library workspace.
2. In the navigation pane, expand Update Catalog and Baselines, and then click Update Catalog.
3. Verify that various updates display.

4. Create a new update baseline with the following settings:
Name: Server Baseline
Updates:
Update for Windows Server 2008 R2 x64 Edition (KB976662)
Update for Windows Server 2008 R2 x64 Edition (KB2506014)
Assignment Scope:
Library Servers: LON-VM1.Contoso.com
PXE Servers: LON-VM1.Contoso.com
Update Server: LON-VM1.Contoso.com
VMM Server: LON-VM1.Contoso.com
5. Verify that Create new baseline has completed successfully.
X Task 2: Verify baseline compliance

1. On LON-VM1, click the Fabric workspace.
2. In the navigation pane, expand Servers, and then click Library Servers.
3. In the ribbon, click the Compliance button.
4. In the results pane, note the compliance and operational status of lon-vm1.contoso.com.
5. Scan lon-vm1.contoso.com, and verify its compliance status.
6. Shut down LON-VM1.
Results: After this exercise, you should have configured an update baseline, and verified baseline
compliance.
Modu
ule Reviiew and
d Takeaw
ways
Review
R Quesstions
1.. What are thhe physical serrver and VMM requirementss for integratin
ng a PXE Serve
er into the VMM
M
private clou
ud infrastructu
ure?
2.. You need to create a hosst profile for se

erver deploymeent. What do yyou need to have in the VM
MM
library to crreate a host prrofile?
3.. What is the

e difference be
etween managing updates w
with Configurattion Manager and managing
g
updates witth VMM?
4-1
Module 4
Configuring Virtual Application Delivery
Contents:
Lesson 1: Dynamic Application Deployment Overview 4-3
Lesson 2: Web Deployment Packages 4-8
Lesson 3: Server Application Virtualization Overview 4-13

Lesson 4: Configuring Server App-V Components 4-23
Lesson 5: Sequencing and Deploying Virtual Applications 4-28
Lab: Configuring Virtual Application Delivery 4-34

4-2 Configuring Virtual Application Delivery
Module Overview
Private clouds benefit from using virtual resources to make deploying new workloads easier. Microsoft
System Center 2012 - Virtual Machine Manager (VMM) allows you to use web deployment packages,
Microsoft Server Application Virtualization (Server App-V), and other methods to simplify the process for
deploying services and applications to your private cloud. These methods enable you to deploy, resize,
and update many of the applications in your private cloud.
In this module, you will learn how to use the Microsoft Web Deployment Tool and Server App-V to
dynamically deploy applications in your private cloud.
After completing this module, you will be able to:
Describe dynamic application deployment.
Create web deployment packages by using the Web Deployment Tool.
Configure the Server App-V Sequencer and Agent.
Sequence and then deploy a Server App-V virtualized application.

Lesson 1
Dynamic Application Deployment Overview
VMM allows you to dynamically deploy packaged server-based applications and services. You can easily
manage private cloud resources, because you can distribute and resize the deployment of a defined
application without manually creating virtual machines, installing software, and managing load balancers.
VMM uses three technologies to facilitate dynamic deployments: the Web Deployment Tool, Server App-
V, and Microsoft SQL Server data-tier applications (DACs). (We will discuss SQL Server in the next
module.)
In this lesson, you will review the Web Deployment Tool and Server App-V, which you can use to enable
VMM to dynamically deploy services.

Describe the benefits of dynamic application deployment.
Describe the Web Deployment Tool.
Describe Server App-V.
.
What Is Dynamic Application Deployment?

Dynamic application deployment provides a simpler method for you to deploy prepackaged solutions,
which are called services. Services may be simple web-based applications or multitier line-of-business
(LOB) applications that include SQL Server. You can customize services to meet the deployment and
scaling needs of many server-based applications.
You must install and configure traditional applications either manually, or by using a solution such as
Microsoft System Center 2012 Configuration Manager. You can use application virtualization
technologies, including App-V, to simplify application deployment and management for user-based
applications. However, server-based applications do not typically work using these tools. For this reason,
VMM introduces a server application virtualization tool called Server App-V.
Note Server App-V is not suitable for all server-based applications, so VMM also allows
you to use the Web Deployment Tool, SQL Server DAC packages, and profiles to address a
broader set of deployment scenarios.
Question: What services or applications do you think you can deploy in a private cloud?
Question: What are some challenges that you might face when trying to adjust the resources
needed for a virtualized website deployment?
Overview of the Web Deployment Tool

You may want to deploy web-based applications in your private cloud. To deploy a website to multiple
servers, you can manually copy the content, and then configure Internet Information Services (IIS) on each
load-balanced server. Alternatively, you can use the Web Deployment Toolknown as Web Deployto
create a file, known as a package, that contains the website content and settings that are located on one
server. Web Deploy collects website data and then packages it into a zip file, which you can then use to
deploy the contents to other servers in the private cloud.
Web Deploy is available as a separate download, and by default in the ApplicationsFrameworks folder of
the VMM library server. Web Deploy works with IIS versions 6.0, 7.0, and 7.5, and with Microsoft Visual
Studio 2010. When you install Web Deploy, the tool extends Internet Information Services (IIS) Manager
to allow an administrator to export or import a web deployment package. When used in conjunction with
Visual Studio, Web Deploy enables an application developer to package an application for deployment.
Additionally, Web Deploy provides a command-line tool.
Server Application Virtualization Overview

Application virtualization allows you to isolate an applications configuration, binaries, and runtime state
from the applications operating system, so that you can simplify your deployment scenarios and reduce
dependencies on a specific operating system environment.
Note Application virtualization is not intended to enable applications to run on

an.operating system that it does not support. For example, you cannot use Server App-V to
enable a 16-bit application to run on a 64-bit operating system.
In a traditional deployment scenario, each application installs its own binaries, and adds its own
configuration and data to the operating system to which it is deployed. A virtualized application is
packaged in a way that encapsulates the configuration and runtime state of the application separate from
the operating system environment.
Traditional Server-Based Applications

A traditional server-based application creates Windows services, and creates and modifies registry
settings during installation. While the application is running, the application may further modify settings
and generate data for purposes such as logging and application functionality. This behavior makes it
difficult to move an application from a deployed server to another server while at the same time
maintaining the configuration and the runtime state of the application.
Server Application Virtualization

Server application virtualization as performed by Server App-V allows you to deploy server-based
applications while maintaining the resources, configuration, and runtime state separate from the
underlying operating system. This separation streamlines application deployment, and allows you to
redeploy to new or additional servers while still maintaining the settings, log files, and the runtime state.
You do not have to rewrite the applications to enable the Server App-V functionality; instead, Server App-
V converts the applications in a process called sequencing. Sequencing is described later in this module.
Question: How does Server App-V differ from automated deployment?

Lesson 2
Web Deployment Packages
The private cloud can host a variety of web-based applications. However, deploying the virtual servers,
installing and configuring IIS, and then installing the web-based content is a time-consuming process. You
can use Web Deploy to streamline this process by bundling all of the web content and settings into a
package. You can place multiple web deployment packages in the Virtual Machine Manager library, and
then deploy them onto virtual machines as required.
In this lesson, you will learn how to use web deployment packages within Virtual Machine Manager to
deploy scalable websites.
Describe the web deployment process.

Create a web deployment package.
Use web deployment packages with Virtual Machine Manager.

Overview of the Web Deployment Process

The web deployment process allows you to deploy an entire website to a web server without managing
the server directly. In this process, you use Visual Studio 2010 or other development tools to complete the
following steps:
1. Create the website content, settings, and data.

2. Package the site content and configuration settings.
3. Deploy the content to a server or multiple servers.
You can deploy the package on the server by using Web Deploy. Alternatively, if the server has the Web
Deployment Agent service configured on it, you can then also use Visual Studio 2010 to publish the
content to a web server. Microsoft WebMatrix, another tool that you can use to simplify website creation,
also uses the Web Deployment Agent Service to both publish content and perform backups of a deployed
sites content and settings.
In a more traditional deployment scenario, the process can be significantly more complicated. As before,
you still need to create the website content, settings, and data for the website. After that, you need to
create a new website on the server to which you are deploying the site. Then you copy the web content to
the web server along with any associated data. Lastly, you must set the website settings manually. The
manual deployment process can take additional time to complete, and can lead to errors if one of the
configuration tasks are not done correctly.
Note Virtual Machine Manager does not use the Web Deployment Agent Service to
deploy the content in the web deployment packages. To simplify the virtual machine setup
process, the target virtual machine transfers the web deployment package from the VMM
library, and then uses Web Deploy to import the deployed packages.
Creating Web Deployment Packages

There are a number of ways to create web deployment packages using Web Deploy, depending on how
the source content for the website was created. You may use the following methods to create a web
deployment package:
IIS Manager. IIS Manager provides a graphical interface to Web Deploy, which allows you to export a
configured website or application to a web deployment package. You can customize the package to
include specific settings, while leaving other settings undefined.
Visual Studio 2010. Visual Studio developers can create a web deployment package using the Visual
Studio Web Packaging feature. This allows the developer to customize the settings, content, and
configuration that is included in the web deployment package.
Web Deployment Tool command line. The Web Deployment Tool command-line has all of the
functionality of the other methods, and can be used to automate the website packaging process. For
example, you could develop a script to create a package, and then copy that package to the VMM
library.
These methods perform more than simple backups of the site content. They also allow you to package the
following:
A single web-based application or an entire site
Access control lists (ACLs)
Microsoft COM settings
Global assembly cache settings
Registry settings
A sites associated databases

Secure Sockets Layer (SSL) certificates

Microsoft .NET Framework configuration
Application pool configuration
When you create a web deployment package, you specify which parameters must be defined when the
package is deployed. This is important for settings that you typically include in the Web.config file that
point to server names or items such as database connection strings. You must also specify these
parameters when you create the web deployment package.
Once you have created a web deployment package, you must copy the file to your VMM library so that it
can be deployed.
Discussion: Using Web Deployment Packages with Virtual Machine

Manager
Web deployment packages simplify the deployment process for web-based application content and
settings. You can deploy additional virtual servers, and then use the web deployment package to install
and customize specified settings.
VMM uses web deployment packages for deploying new content; it does not synchronize the content on
a deployed server across multiple servers. If a specific web application has files that frequently change and
need to be shared with each web server, you may choose to use a file share to make the content available
to all of the servers, instead of using web deployment packages. Using web deployment packages is
especially beneficial when you deploy the content more than once, either across multiple servers in the
same environment, or across multiple environments.
Using web deployment packages make sense when content will be static across the servers. If the required
content needs to be unique for every deployment, you may not want to use a web deployment package.
Question: What types of deployments might benefit from web deployment packages?
Lesson 3
Server Application Virtualization Overview
Application virtualization has been available to help client operating system administrators deploy
applications for many years. VMM now provides server-based application virtualizationServer App-V
to enable dynamic application deployment on your private cloud servers.
In this lesson, you will learn about Server App-V and its components.
Describe how Sever App-V works.
Describe Server App-V usage scenarios.
Describe invalid Server App-V usage scenarios.
Define key application virtualization terms.
Describe the application sequencing process.
Describe the Server App-V package.
Describe the differences between Server App-V and App-V.

Server App-V Fundamentals

Virtualizing an application with Server App-V allows you to capture not only the information required to
install the applicationsuch as the applications binary files and registry settingsbut it also retains the
runtime state of the deployed application, which includes registry settings, log files and other data stored
by the application. This runtime state persists on disk until you remove the application from the server.
The application runtime state includes the data that is captured while the deployed application is running.
This data can include log files, collected data, and settings that are modified for a specific application
deployment.
Server App-V performs a sequencing operation that captures an applications settings and configuration
prior to deployment. After sequencing, this information along with the runtime state information enables
you to back up a deployed Server App-V application. It also enables you to capture not only the initial
settings, but also the entire runtime state of the application. You can then deploy this backup to another
server with the applications last runtime state intact.
If an application can function in a load-balanced environment, VMM can deploy the application across
additional servers, and reconfigure the load balancer to use the newly deployed servers.
Question: What are the benefits of using Server App-V?
Question: Why is the ability to back up the runtime state beneficial in a production
environment?
Server App-V Usage Scenarios

Server App-V allows you to virtualize and deploy many server-based applications. There are a number of
components that Server App-V can sequence. Additionally, applications such as multi-tier web
applications and third-party network service applications lend themselves to virtualization with Server
App-V.
A single application may require you to specify registry settings, modify configuration files, or create
Windows operating system services. Additionally, an application may have many other points where it
interacts with the operating system. If so, the Sequencer needs to capture these points, otherwise the
application may not work properly when you deploy it.
Applications that require you to perform the following tasks may be suitable for virtualization with Server
App-V:
Save runtime state to local disk.
Install Windows services.
Create IIS applications.
Add and change registry settings.
Install and use COM+ and Distributed COM (DCOM).
Use text-based configuration files.

Install Windows Management Instrumentation (WMI) providers.
Install and use Reporting Services, a feature of SQL Server.
Add, modify, or use Local Users and Groups.
Install and use Java-based applications.

If an application requires another type of virtualized information that is not included on this list, it may
not properly work with Server App-V. No exhaustive list of applications that work with Server App-V
exists. You must thoroughly test all applications that you are virtualizing before you run them in a
production environment.
Invalid Server App-V Usage Scenarios

Server App-V is flexible, and you can use it to virtualize a wide variety of server-based applications.
However, there are a few functions that you cannot virtualize using Server App-V. For example,
applications that require the following functionality are not supported:
Windows drivers or other components that must load when the operating system boots.
Microsoft SharePoint Server, or applications that install SharePoint Server.
SQL Server
Just as there is no complete list existing for supported Server App-V virtualization application types, there
is also no exhaustive list of unsupported applications types for Server App-V.
Note Even though you may not use Server App-V to virtualize SQL Server, you may still
automate deployment by using VMM and DAC packages. Deploying SQL Server using VMM
is discussed in Module 5.
Key Server App-V Terms

Before working with Server App-V, you should understand the main components used for Server App-V.
The following terms apply to Server App-V:
Application. An application is the binaries, configuration, and settings that you plan to virtualize.
Sequencer. The Sequencer packages an application. It monitors and records all of the changes that an
application makes during installation and setup of the application, and then creates a Server App-V
package.
App-V Agent. The agent is installed on the server that will run the virtualized application. It executes
and maintains the virtualized application and its runtime state.
Package. A package includes the binaries, configuration, and runtime state information for the
virtualized application Packages are imported on a server that has the Virtualization Agent installed.
Server App-V virtual drive (Q:\). The virtual drive stores the binaries and settings for the virtualized
application. Application settings and installation files are stored on this virtual drive during
sequencing. The App-V agent creates and maintains the virtual drive in a folder on your system drive
based on the contents of packages that have been imported.
Overview of the Application Sequencing Process

Application sequencing is the process of registering the changes an application makes during the setup
and configuration procedure. The application registration consists of the settings and configuration
captured during the sequencing. This represents how the application will initially deploy.
Sequencing provides Server App-V with information about how an application works and what resources
it requires. Specifically, Server App-V can determine which binaries and settings are required to make the
application run, and how the application creates and consumes data. The Server App-V package then
encapsulates all of this information.
The sequencing process is as follows:
1. Install the Server App-V Sequencer.
2. Start the Server App-V Sequencer to monitor the system.

3. Launch the installer and install your application.
4. Stop the Server App-V Sequencer from monitoring the system.
5. Save the Server App-V package.
You will learn more about the process of sequencing applications later in this module.
The Server App-V Package

After sequencing an application, you save the sequenced information as a Server App-V package. You can
then use the package file to deploy the virtualized application. Server App-V packages includes the
following files:
Sequencer project (.sprj). The .sprj file is an XML-based file that the Sequencer uses to save
information about the package so that you can edit or upgrade the package later.
Package payload (.sft). The sft file is a binary file that the Sequencer creates. This file contains the
deployed files, folders, registry settings, and other package-related information.
Open Software Descriptor (.osd). The .osd files are XML-based files that describe how the application
should be imported on the Agent computer.
Package manifest (_manifest.xml). The package name_manifest.xml file is an XML-based file that
contains metadata information that describes the package. The Server App-V Agent uses the
information included in this file to import and then run a Server App-V package.
Deployment configuration (DeploymentConfig.xml). The DeploymentConfig.xml file is an XML-based

file containing the data that will be passed to the Server App-V Agent. The date is then used to
customize the package settings that were specified when the application was sequenced. For
example, settings in this file may include database connection strings, server names, and passwords
customized for a specific deployment.
Differences Between Server App-V and App-V

Both Server App-V and Microsoft Application Virtualization (App-V) virtualize applications, but you should
be aware of their differences. You can stream App-V packaged applications using a number of protocols
from either an App-V streaming server, or from a simple file location. Server App-V expects you to deliver
the applications directly to the running server by using VMM or a Windows PowerShell command-line
interface. For Server App-V, you cannot stream applications from network locations.
App-V has more limited virtualization capabilities than Server App-V. Server App-V allows you to
sequence and deliver services, WMI components, COM objects, and IIS applications.
Server App-V is designed to use VMM to deploy applications that both run on servers and provide
network services, such as a third-party File Transfer Protocol (FTP) services. App-V, however, is designed to
deploy user-based applications, such as Microsoft Office.
The following table shows the key differences between Server App-V and App-V.
Server App-V App-V
The application-created data or user-specific The application-created data or user-specific
registry settings that are made when the registry settings that are made when the
application is sequenced, remains associated with application is sequenced, is mapped so that it is
the same user at deployment time and run time. accessible to any user running the application.
Application files that are part of a virtual Application files that are part of a virtual
application package are available to all processes application package are only available to that
that are running on the computer. virtual application and any other processes
started in the virtual application's environment.
COM objects, DCOM objects, COM+ objects, WMI COM, DCOM, COM+, WMI, and service
providers, and Windows services that are part of a information that are associated with a virtual
virtual application package are exposed on the application package are kept within that package,
local system so that the operating system, tools, and are unavailable to processes running outside
and other applications can interact with them. of that package.
The Server App-V Agent uses heuristics to detect For a process to be virtualized, that process must
automatically which processes on a computer be opened by an App-V program (such as
must be run within virtual environments. sfttray.exe), or it has to be the child of another
virtual process.
Lesson 4
Configuring Server App-V Components
Server App-V requires that you install and configure the Server App-V Agent and the Server App-V
Sequencer properly. For the best results when deploying the virtualized applications, you must also
consider the operating system configurations to which you will deploy the virtualized applications.
In this lesson, you will learn how to configure the Server App-V components.
Describe the Server App-V software requirements.
Explain how to configure the Server App-V Agent and Agent cmdlets.
Describe the best practices for configuring the Server App-V Sequencer.
Server App-V Software Requirements

The Server App-V Sequencer and the Server App-V Agent run on the same operating system versions.
Because Server App-V is a server-based product, it only runs on server operating systems. The following
table lists the supported operating systems:
Operating system System architecture

Windows Server 2003 with Service Pack 2 (SP2) x86 and x64
Windows Server 2003 R2 with SP2 x86 and x64
Windows Server 2008 with SP2 x86 and x64
Windows Server 2008 R2 x64
In addition to a supported operating system, the Server App-V Sequencer and the Server App-V Agent
require you to install the Microsoft Visual C++ 2005 SP1 Redistributable Package. If Visual C++ 2005 is
not already installed, the Server App-V Sequencer or Server App-V Agent installation process will install it
for you.
The Server App-V installation files are located on the Virtual Machine Manager server in the Install
Drive:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\SAV directory. Depending
on the system architecture of the operating system onto which you intend to install the Server App-V
components, you will use the files in either the 64-bit or the 86-bit folders. These folders contain the
following files:
AgentSetup.exe. This file installs the Server App-V Agent.
AgentCmdletsSetup.exe. This file installs the Windows PowerShell cmdlets that the Server App-V
Agent uses. You must install the Server App-V Agent on the same machine for the cmdlets to
function.
SeqSetup.exe. This file installs the Server App-V Sequencer.

SequencerCmdletSetup.exe. This file installs the Windows PowerShell cmdlets that the Server App-V
Sequencer uses. You must install the Server App-V Sequencer on the same machine for the cmdlets to
function.
Configuring the Server App-V Agent and Agent Cmdlets

You install the Server App-V Agent on the server that will run the virtualized application. If the virtualized
application requires Windows roles or features, you should install them before you deploy the application.
To test package deployment, you may also wish to install the Server App-V PowerShell Agent cmdlets.
These cmdlets allow you to verify the functionality of a package quickly, without using VMM. To install the
Server App-V PowerShell Agent cmdlets, use the AgentCmdletsSetup.exe file that is found in the Server
App-V installation folder on the VMM server.
Once you have installed the Server App-V PowerShell Agents cmdlets, you must also set the Windows
PowerShell execution policy to RemoteSigned, which allows scripts and configuration files to execute if
they are signed by a trusted publisher. The default execution policy does not allow scripts or configuration
files to execute. To adjust the policy, run the following command from an elevated Windows PowerShell
prompt to set the execution policy to RemoteSigned:
Set-ExecutionPolicy RemoteSigned
The execution policy is a user preference, and must be set by each user. After setting the Windows
PowerShell execution policy, run the following cmdlet from an elevated Windows PowerShell prompt to
import the ServerAppVAgent module:
Import-Module ServerAppVAgent
Note Changing the Windows PowerShell execution policy alters the security configuration
of the server. These changes could allow malicious scripts to be run on the server, which
could cause damage. You should only make changes to the execution policy after
understanding the consequences of making the changes.
Best Practices for Configuring the Server App-V Sequencer

You cannot install the Server App-V Sequencer on a machine that already has the Server App-V Agent
installed. You must uninstall the Server App-V Agent before attempting to install the Server App-V
Sequencer. We recommend the following best practices for configuring your sequencing server:
Set up the sequencing machine with the same base configuration as the target servers. Server App-V
can run the same virtualized application on different operating system configurations. However, you
should limit the number of variables to reduce the possibility of incompatibilities.
Verify that the default sequencing drive is valid for your deployments. By default, Server App-V uses
Q: for the default drive letter. If you are already using this drive in your environment, you may need
to adjust the default drive to a different letter. Use the same virtual drive letter for all of your
applications to reduce confusion.
Disable unused applications. Shut down antivirus software, Windows Update, and other applications
when you are running the Server App-V Sequencer. These processes can slow down the sequencing
process, and cause the Server App-V Sequencer to package data that is not related to the application
you are sequencing.
Document your sequencing environment. Be sure to document any software and configuration
changes that you made before you sequenced the application. This is helpful if you ever have to
troubleshoot, update, or recreate your virtualized application.
If you are deploying the virtualized application to multiple operating system types, use the lowest
version to sequence the application. For example, if you plan to deploy your virtualized application to
both Windows Server 2008 and Windows Server 2008 R2, sequence the application on a Windows
Server 2008 machine.
Use a virtual machine for sequencing, and create a checkpoint before you sequence a new
application. Use the checkpoint to revert the virtual machine to a clean runtime state after
sequencing, so that you can sequence another application using the same virtual machine.
Lesson 5
Sequencing and Deploying Virtual Applications
Before deploying a virtual application, you must first sequence it. The sequencing process is critical for
creating a package that works properly after deployment. In addition, you should always test a sequenced
application to verify that it will function correctly once you deploy it.
In this lesson, you will learn how to sequence and test the deployment of applications.
Describe how to create a Server App-V package.
Describe the Server App-V Agent and Sequencer PowerShell cmdlets.
Describe how to test a Server App-V package before deployment.
Describe how to back up and restore a Server App-V package.

Creating a Server App-V Package

To sequence an application, complete the following steps:

1. Deploy a sequencing server that matches your deployment standard.
2. Install the Server App-V Sequencer on the sequencing server. If you are using a virtual machine,
create a checkpoint of the machine so that you can revert to it after you finish sequencing the
machine.
3. Install Windows roles and features required to support your application.
4. Run the New Virtual Application Package Wizard.
5. Select your applications installer, or if you plan to install your application manually, select a custom
installation.
6. Install the application to the Server App-V virtual drive (Q:\).

7. Run any other installers needed to complete the application configuration.
8. Perform configuration changes as needed.
9. Customize the package information. Customization may include configuring which files and settings
are included, and which need to be specified when the application deploys.
10. Save the package to another server. When you have completed your sequencing session, you can
revert the virtual machine back to the checkpoint created in step 2.
VMMs Service Templates feature makes use of Server App-V. After creating and testing the Server App-V
package, you must copy the package to the VMM library so that you can use it. Once the package is in
the library, you can use when you create or modify a Service Template. You will learn more about service
templates in Module 5.
Server App-V Agent and Sequencer Cmdlets

You can use the Server App-V Agent cmdlets to manage Server App-V packages without the need to use
VMM. This is helpful because it allows you to test single package deployments quickly, without having to
add the packages to the VMM library and then deploy new virtual machines. You receive near immediate
feedback on how the application functions. The Server App-V Agent cmdlets allow you to deploy a
package, start and stop a deployed application, and back up and restore the runtime state of an
application.
The following Server App-V Agent cmdlets are available:
Cmdlet Description
Add-ServerAppVPackage This cmdlet adds a new virtual application package to a
computer that is running the Server App-V Agent, or upgrades
an existing virtual application package on a computer that is
running the Server App-V Agent.
Use this cmdlet to import a sequenced application on the
computer without using VMM.
Backup-ServerAppVPackageState This cmdlet backs up to a specified location the runtime state

that is associated with an existing virtual application package.
Use this cmdlet to save the runtime state of a deployed
package so that you can restore it to a new server or to the
same server at a later time.
Restore-ServerAppVPackageState Using a previously created backup, this cmdlet restores the

runtime state that is associated with a virtual application
package.
Use this cmdlet to restore the package state after a previous
backup has been created.
You can use the Server App-V Sequencer cmdlets to create scripts to sequence applications. This is
helpful, because it allows you to sequence an application the same way each time, which is important
when updating Server App-V packages. The following Server App-V Sequencer cmdlets are available:
Cmdlet Description
New-ServerAppVSequencerPackage This cmdlet creates a new virtual application package.
Use this cmdlet to create a Server App-V Sequencer package
from a Windows PowerShell command prompt.
Protect-UpdateConfiguration This cmdlet encrypts the private values in the deployment

configuration document. Private values include passwords and
user names that the application requires to function.
Unprotect-UpdateConfiguration This cmdlet decrypts the private values in the deployment

configuration document. Private values include passwords and
user names that the application requires to function.
Update- This cmdlet updates an already created existing virtual

ServerAppVSequencerPackage application package. Server App-V updates an already created
package if a newer version of the software must be integrated
into the package, or if other adjustments are required.
Testing a Server App-V Package

You can use the Server App-V Agent cmdlets to test the Server App-V packages .To test a package
deployment, complete the following steps:
1. Customize the DeploymentConfig.xml file.
2. Run the Add-ServerAppVPackage cmdlet to add the Server App-V package.
3. Run the Start-ServerAppVPackage cmdlet to start the Server App-V package.
VMM configures the DeploymentConfig.xml file automatically when you use VMM to deploy a Server
App-V package. However, when you use the cmdlets, you must modify this file manually. Specifically, to
test a deployment properly, you may need to edit the attributes of the <ENTRY> XML elements in the
<CONFIGURATION><VIRTUALENVIRONMENT>and the <CONFIGURATION><LOCAL> sections of the
file. Elements that you may need to edit include database connection strings, server names, and other
settings that would change for the application each time it is deployed.
Backing Up and Restoring a Server App-V Package

After you deploy an application, the application may create log files, change settings, or otherwise change
the runtime state. With Server App-V, you can back up the runtime state of the deployed application and
restore it on another server. You may need to complete this process if you need to replace the server on
which the application is deployed, or if you want to test the application on another server. The backup
and restore process is as follows:
1. Run the Stop-ServerAppVPackage cmdlet to stop the Server App-V application.
2. Run the Backup-ServerAppVPackageState cmdlet to back up the Server App-V application runtime
state.
3. Copy the backup files and the Server App-V package to the new server.
4. Run the Add-ServerAppVPackage cmdlet to add the Server App-V package to the new server.
5. Run the Restore-ServerAppVPackageState cmdlet to restore the Server App-V package runtime
state.
6. Run the Start-ServerAppVPackage cmdlet to start the Server App-V package.

Question: Why might you want to back up and restore a deployed application?
Lab: Configuring Virtual Application Delivery

Lab Setup
Note Before starting this lab, you must have completed the lab in Module 2.
For this lab, you will use the available virtual machine environment. Before you begin the lab, you must
ensure that the virtual machines are running by completing the following steps:
1. On LON-HOST1-B, click Start, point to Administrative Tools, and then click Hyper-V Manager.
2. In Hyper-V Manager, click 10751A-LON-DC1, and in the Actions pane, click Start.
Password: Pa$$w0rd
Domain: Contoso
5. Repeat steps 2 to 4 for 10751A-LON-SQ1.
6. On LON-HOST2-B, click Start, point to Administrative Tools, and then click Hyper-V Manager.
7. In Hyper-V Manager, click 10751A-LON-AP1, and in the Actions pane, click Start.

Password: Pa$$w0rd
Domain: Contoso
10. Repeat steps 7 to 9 for 10751A-LON-SE1.
Lab Scenario
As a part of the move to a private cloud infrastructure, Contoso, Ltd has decided to change its server
application delivery strategy so that it can provide a more scalable platform. Contoso, Ltd has decided to
use Server App-V to deliver existing applications. One of the applications that you will virtualize using
Server App-V is the .NET Pet Shop application. You will need to test the virtualized Pet Shop application
before you deploy it.
You must configure Server App-V so that you can use it to sequence and deploy an application virtually.
Exercise 1: Configuring the Server App-V Sequencer

1. Install the Server App-V Sequencer on LON-SE1.
X Task: Install the Server App-V Sequencer on LON-SE1

1. Log on to LON-SE1 as Contoso\Administrator using the password Pa$$w0rd.
2. Install Microsoft Server Application Virtualization Sequencer from C:\SAV\x64\SeqSetup.exe.
Results: After this exercise, you should have installed the Server App-V Sequencer on LON-SE1.
Exercise 2: Configuring the Server App-V Agent

1. Install the Server App-V Agent on LON-AP1.
X Task: Install the Server App-V Agent on LON-AP1

1. Log on to LON-AP1 as Contoso\Administrator using the password Pa$$w0rd.
2. Install Microsoft Server Application Virtualization Agent from E:\Labfiles\SAV\x64\AgentSetup.exe.
Results: After this exercise, you should have installed the Server App-V Agent on LON-AP1.
Exercise 3: Sequencing an Application

1. Sequence the Pet Shop application.
X Task: Sequence the Pet Shop application

1. On LON-SE1, open Microsoft Server Application Virtualization Sequencer and create a new Virtual
Application package.
Application installer: C:\SAV\Microsoft .NET Pet Shop 4.0.msi
Package Name: PetShop4.0
2. Complete the .NET Pet Shop 4.0 Source Code Only installation on Q:\PetShop4.0\.
3. Complete the site installation by executing the following commands from an elevated command
prompt:
Q:
Cd \PetShop4.0
Build.bat
DecryptWebConfig.bat
4. Create a new website using IIS Manager.
Name: PetShop4
Physical Path: Q:\PetShop4.0\web
Port: 8081
5. In the Microsoft Server Application Virtualization Sequencer, finish the sequencing process.
6. Save the completed package to \\LON-AP1\E$\Labfiles\SAV\PetShop\PetShop4.0.sprj.
Results: After this exercise, you should have successfully sequenced the Pet Shop application, and saved
the package to LON-AP1.
Exercise 4: Testing the Server App-V Package Deployment

1. Install the Server App-V Agent cmdlets on LON-AP1.
2. Import the Server App-V package.
X Task 1: Install the Server App-V Agent cmdlets on LON-AP1

On LON-AP1, install Microsoft Server Application Virtualization Agent cmdlets from
E:\Labfiles\SAV\x64\AgentCmdletsSetup.exe.
X Task 2: Import the Server App-V package

1. On LON-AP1, open Windows Explorer and browse to E:\Labfiles\SAV\PetShop.
2. In the PetShop folder, right-click deploymentconfig.xml and then click Edit.
3. Replace all instances of localhost and (local) with LON-SQ1.
4. Replace all instances of password= with password=pass@word1.

5. Save and close Notepad and then close the PetShop window.
6. In an elevated Windows PowerShell window, set the Windows PowerShell execution policy to
RemoteSigned.
7. Import the ServerAppVAgent PowerShell module.
8. Add the Server App-V package using the following settings:
Name: PetShop4
Manifest: E:\Labfiles\SAV\Petshop\PetShop4.0_manifest.xml
SFT: E:\Labfiles\SAV\Petshop\PetShop4.0.sft
Configuration: E:\Labfiles\SAV\PetShop\Deploymentconfig.xml
9. Start the PetShop4 Server App-V package.
10. Open Windows Internet Explorer to test the site using http://localhost:8081/.
11. Close Internet Explorer.
12. Close the Windows PowerShell window.
13. Shut down LON-SE1.
Results: After this exercise, you should have installed the Server App-V Agent cmdlets on LON-AP1, and
successfully tested the Pet Shop application that you sequenced in Exercise 3.
Module Review and Takeaways

Review Questions
1. For what are web deployment packages used?
2. What is Server App-V, and what types of applications can you use it for?
3. What types of applications might not be suitable for Server App-V or dynamic deployment?
Common Issues Related to Server App-V

Identify the causes for the following common issues related to a particular technology area in the module,
and fill in the troubleshooting tips. For answers, refer to relevant lessons in the module.
Issue Troubleshooting tip

Server App-V package will not deploy. Verify that the proper roles and features are installed on
the server.
Verify that all package files are available.
If deploying an IIS website, be sure Web Deploy and the
proper IIS Management Role Services are installed.
Review the customization file to ensure it has been
configured for deployment.
Server App-V Sequencer will not deploy. Determine whether the Server App-V Agent is already
installed on the server.
Best Practices Related to Server App-V

Supplement or modify the following best practices for your own work situations:
Configure the sequencing server with the same roles and features that will be deployed in
production.
Create a checkpoint for the sequencing virtual machine before creating a package, so that you can
revert to it after creating a package.
Use unique package names for each package that you will deploy.

10751A ENU Beta TrainerHandbook Part1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

10751A ENU Beta TrainerHandbook Part1

Uploaded by

Copyright:

Available Formats

MCT USE ONLY.

STUDENT USE PROHIBITED

Microsoft and the trademarks listed at

Product Number: 10751A

a. If you are a Authorized Learning Center:

b. If you are a MPN Member.

c. If you are an End User:

2.3 Reproduction/Redistribution Licensed Content. Except as expressly provided in the applicable

13. APPLICABLE LAW.

This limitation applies to

LIMITATION DES DOMMAGES-INTRTS ET EXCLUSION DE RESPONSABILIT POUR LES DOMMAGES. Vous

Revised December 2011

Joel Stidley Content Developer

Damir Dizdarevic Content Developer

Byron Wright Content Developer

Justin Kimber Technical Reviewer

Module 2: Private Cloud Configuration and Deployment with

Module 3: Extending and Maintaining the Private Cloud Infrastructure

Module 4: Configuring Virtual Application Delivery

Module 5: Creating the Private Cloud Building Blocks

Module 6: Deploying and Accessing the First Business Unit Cloud

Module 7: Monitoring the Private Cloud Infrastructure

Module 8: Extending and Customizing Monitoring of the

Module 9: Implementing Service Management for the Private Cloud

Module 10: Configuring a Private Cloud Service Catalog

Module 11: Protecting the Private Cloud Infrastructure

Module 12: Automating and Standardizing the Private Cloud

Appendix: Lab Answer Keys

About This Course

Networking and storage experience.

Microsoft SharePoint configuration.

Windows Server 2008 Hyper-V.

Familiarity with data center management processes.

Working knowledge of ITIL and MOF.

Configure and deploy the application fabric.

Configure a PXE server, an update server, and a software update baseline.

Configure a service catalog and publish this to the self-service portal.

Course Companion Content on the http://www.microsoft.com/learning/companionmoc/ Site:

Student Course files on the http://www.microsoft.com/learning/companionmoc/ Site: Includes the

Virtual Machine Environment

Virtual Machine Configuration

Virtual machine Role

Server running Virtual Machine Manager in the

Server running Operations Manager in the

Server running Service Manager in the

Server running Data Protection Manager in the

Server running Orchestrator in the Contoso.com

Server running SharePoint in the Contoso.com

Server running SQL Server in the Contoso.com

10751A-LON-AP2 File Server running in the Contoso.com domain

Course Hardware Level

To ensure a satisfactory student experience, Microsoft Learning requires a minimum equipment

Lesson 2: Requirements for Deploying a Private Cloud 1-13

Lesson 3: Designing the Private Cloud Components 1-22

Lesson 5: Deploying Hyper-V Clustering with VMM 1-41

Lab: Planning for the Private Cloud 1-47

After completing this module, you will be able to:

Describe the private cloud.

Understand the requirements for deploying a private cloud.

Design the private cloud infrastructure components

Describe the Microsoft System Center 2012 components.

After completing this lesson, you will be able to:

Describe the business problem.

Describe the benefits of using the Microsoft private cloud.