Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
MICROSOFT
LEARNING
PRODUCT
6331A
Deploying and Managing Microsoft System Center Virtual Machine Manager
ii
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. 2008 Microsoft Corporation. All rights reserved. Microsoft, Access, Active Directory, Excel, Hyper-V, Internet Explorer, Microsoft Press, MS, MSDN, SQL Server, Windows, Windows NT, Windows PowerShell, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other trademarks are property of their respective owners.
MICROSOFT LICENSE TERMS OFFICIAL MICROSOFT LEARNING PRODUCTS - TRAINER EDITION 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. The terms also apply to any Microsoft updates, supplements, Internet-based services, and support services
for this Licensed Content, unless other terms accompany those items. If so, those terms apply. By using the Licensed Content, you accept these terms. If you do not accept them, do not use the Licensed Content. If you comply with these license terms, you have the rights below.
1. DEFINITIONS. a. Academic Materials means the printed or electronic documentation such as manuals,
workbooks, white papers, press releases, datasheets, and FAQs which may be included in the Licensed Content. location, an IT Academy location, or such other entity as Microsoft may designate from time to time. conducted at or through Authorized Learning Centers by a Trainer providing training to Students solely on Official Microsoft Learning Products (formerly known as Microsoft Official Curriculum or MOC) and Microsoft Dynamics Learning Products (formerly know as Microsoft Business Solutions Courseware). Each Authorized Training Session will provide training on the subject matter of one (1) Course. Center during an Authorized Training Session, each of which provides training on a particular Microsoft technology subject matter.
b. Authorized Learning Center(s) means a Microsoft Certified Partner for Learning Solutions
c. Authorized Training Session(s) means those training sessions authorized by Microsoft and
d. Course means one of the courses using Licensed Content offered by an Authorized Learning
e. Device(s) means a single computer, device, workstation, terminal, or other digital electronic or
analog device.
f.
Licensed Content means the materials accompanying these license terms. The Licensed Content may include, but is not limited to, the following elements: (i) Trainer Content, (ii) Student Content, (iii) classroom setup guide, and (iv) Software. There are different and separate components of the Licensed Content for each Course. Software means the Virtual Machines and Virtual Hard Disks, or other software applications that may be included with the Licensed Content.
g.
h. Student(s) means a student duly enrolled for an Authorized Training Session at your location.
i.
Student Content means the learning materials accompanying these license terms that are for use by Students and Trainers during an Authorized Training Session. Student Content may include labs, simulations, and courseware files for a Course. Trainer(s) means a) a person who is duly certified by Microsoft as a Microsoft Certified Trainer and b) such other individual as authorized in writing by Microsoft and has been engaged by an Authorized Learning Center to teach or instruct an Authorized Training Session to Students on its behalf. Trainers and Students, as applicable, solely during an Authorized Training Session. Trainer Content may include Virtual Machines, Virtual Hard Disks, Microsoft PowerPoint files, instructor notes, and demonstration guides and script files for a Course. Virtual Hard Disks means Microsoft Software that is comprised of virtualized hard disks (such as a base virtual hard disk or differencing disks) for a Virtual Machine that can be loaded onto a single computer or other device in order to allow end-users to run multiple operating systems concurrently. For the purposes of these license terms, Virtual Hard Disks will be considered Trainer Content. Microsoft Virtual PC or Microsoft Virtual Server software that consists of a virtualized hardware environment, one or more Virtual Hard Disks, and a configuration file setting the parameters of the virtualized hardware environment (e.g., RAM). For the purposes of these license terms, Virtual Hard Disks will be considered Trainer Content. you means the Authorized Learning Center or Trainer, as applicable, that has agreed to these license terms.
j.
k. Trainer Content means the materials accompanying these license terms that are for use by
l.
m. Virtual Machine means a virtualized computing experience, created and accessed using
n.
2. OVERVIEW.
Licensed Content. The Licensed Content includes Software, Academic Materials (online and electronic), Trainer Content, Student Content, classroom setup guide, and associated media. License Model. The Licensed Content is licensed on a per copy per Authorized Learning Center location or per Trainer basis.
3. INSTALLATION AND USE RIGHTS. a. Authorized Learning Centers and Trainers: For each Authorized Training Session, you
may: i. either install individual copies of the relevant Licensed Content on classroom Devices only for use by Students enrolled in and the Trainer delivering the Authorized Training Session, provided that the number of copies in use does not exceed the number of Students enrolled in and the Trainer delivering the Authorized Training Session, OR
ii. install one copy of the relevant Licensed Content on a network server only for access by classroom Devices and only for use by Students enrolled in and the Trainer delivering the Authorized Training Session, provided that the number of Devices accessing the Licensed Content on such server does not exceed the number of Students enrolled in and the Trainer delivering the Authorized Training Session. iii. and allow the Students enrolled in and the Trainer delivering the Authorized Training Session to use the Licensed Content that you install in accordance with (ii) or (ii) above during such Authorized Training Session in accordance with these license terms.
i.
Separation of Components. The components of the Licensed Content are licensed as a single unit. You may not separate the components and install them on different Devices.
ii. Third Party Programs. The Licensed Content may contain third party programs. These license terms will apply to the use of those third party programs, unless other terms accompany those programs.
b. Trainers:
i. Trainers may Use the Licensed Content that you install or that is installed by an Authorized Learning Center on a classroom Device to deliver an Authorized Training Session.
ii. Trainers may also Use a copy of the Licensed Content as follows:
A. Licensed Device. The licensed Device is the Device on which you Use the Licensed Content.
You may install and Use one copy of the Licensed Content on the licensed Device solely for your own personal training Use and for preparation of an Authorized Training Session. personal training Use and for preparation of an Authorized Training Session.
B. Portable Device. You may install another copy on a portable device solely for your own 4. PRE-RELEASE VERSIONS. If this is a pre-release (beta) version, in addition to the other provisions
in this agreement, 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, commercial version. We also may not release a commercial version. You will clearly and conspicuously inform any Students who participate in each Authorized Training Session of the foregoing; and, that you or Microsoft are under no obligation to provide them with any further content, including but not limited to the final released version of the Licensed Content for the Course. 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, Licensed Content, or service that includes the feedback. You will not give feedback that is subject to a license that requires Microsoft to license its software or documentation to third parties because we include your feedback in them. These rights survive this agreement.
b. Feedback. If you agree to give feedback about the Licensed Content to Microsoft, you give to
c. Confidential Information. The Licensed Content, including any viewer, user interface, features
and documentation that may be included with the Licensed Content, is confidential and proprietary to Microsoft and its suppliers. i. Use. For five years after installation of the Licensed Content or its commercial release, whichever is first, you may not disclose confidential information to third parties. You may disclose confidential information only to your employees and consultants who need to know the information. You must have written agreements with them that protect the confidential information at least as much as this agreement. Survival. Your duty to protect confidential information survives this agreement.
ii.
iii. Exclusions. You may disclose confidential information in response to a judicial or governmental order. You must first give written notice to Microsoft to allow it to seek a
protective order or otherwise protect the information. Confidential information does not include information that d. becomes publicly known through no wrongful act; you received from a third party who did not breach confidentiality obligations to Microsoft or its suppliers; or you developed independently.
Term. The term of this agreement for pre-release versions is (i) the date which Microsoft informs you is the end date for using the beta version, or (ii) the commercial release of the final release version of the Licensed Content, whichever is first (beta term). Use. You will cease using all copies of the beta version upon expiration or termination of the beta term, and will destroy all copies of same in the possession or under your control and/or in the possession or under the control of any Trainers who have received copies of the pre-released version. Copies. Microsoft will inform Authorized Learning Centers if they may make copies of the beta version (in either print and/or CD version) and distribute such copies to Students and/or Trainers. If Microsoft allows such distribution, you will follow any additional terms that Microsoft provides to you for such copies and distribution.
e.
f.
ii. Virtual Hard Disks. The Licensed Content may contain versions of Microsoft XP, Microsoft Windows Vista, Windows Server 2003, Windows Server 2008, and Windows 2000 Advanced Server and/or other Microsoft products which are provided in Virtual Hard Disks. A. If the Virtual Hard Disks and the labs are launched through the Microsoft Learning Lab Launcher, then these terms apply: Time-Sensitive Software. If the Software is not reset, it will stop running based upon the time indicated on the install of the Virtual Machines (between 30 and 500 days after you install it). You will not receive notice before it stops running. You may not be able to access data used or information saved with the Virtual Machines when it stops running and may be forced to reset these Virtual Machines to their original state. You must remove the Software from the Devices at the end of each Authorized Training Session and reinstall and launch it prior to the beginning of the next Authorized Training Session. B. If the Virtual Hard Disks require a product key to launch, then these terms apply: Microsoft will deactivate the operating system associated with each Virtual Hard Disk. Before installing any Virtual Hard Disks on classroom Devices for use during an Authorized Training Session, you will obtain from Microsoft a product key for the operating system software for the Virtual Hard Disks and will activate such Software with Microsoft using such product key. C. These terms apply to all Virtual Machines and Virtual Hard Disks:
You may only use the Virtual Machines and Virtual Hard Disks if you comply with the terms and conditions of this agreement and the following security requirements: o o You may not install Virtual Machines and Virtual Hard Disks on portable Devices or Devices that are accessible to other networks. You must remove Virtual Machines and Virtual Hard Disks from all classroom Devices at the end of each Authorized Training Session, except those held at Microsoft Certified Partners for Learning Solutions locations. You must remove the differencing drive portions of the Virtual Hard Disks from all classroom Devices at the end of each Authorized Training Session at Microsoft Certified Partners for Learning Solutions locations. You will ensure that the Virtual Machines and Virtual Hard Disks are not copied or downloaded from Devices on which you installed them. You will strictly comply with all Microsoft instructions relating to installation, use, activation and deactivation, and security of Virtual Machines and Virtual Hard Disks. You may not modify the Virtual Machines and Virtual Hard Disks or any contents thereof. You may not reproduce or redistribute the Virtual Machines or Virtual Hard Disks.
o o o o
ii. Classroom Setup Guide. You will assure any Licensed Content installed for use during an
Authorized Training Session will be done in accordance with the classroom set-up guide for the Course. iii. Media Elements and Templates. You may allow Trainers and Students to use images, clip art, animations, sounds, music, shapes, video clips and templates provided with the Licensed Content solely in an Authorized Training Session. If Trainers have their own copy of the Licensed Content, they may use Media Elements for their personal training use. iv. iv Evaluation Software. Any Software that is included in the Student Content designated as Evaluation Software may be used by Students solely for their personal training outside of the Authorized Training Session.
b. Trainers Only:
i. Use of PowerPoint Slide Deck Templates. The Trainer Content may include Microsoft PowerPoint slide decks. Trainers may use, copy and modify the PowerPoint slide decks only for providing an Authorized Training Session. If you elect to exercise the foregoing, you will agree or ensure Trainer agrees: (a) that modification of the slide decks will not constitute creation of obscene or scandalous works, as defined by federal law at the time the work is created; and (b) to comply with all other terms and conditions of this agreement.
ii. Use of Instructional Components in Trainer Content. For each Authorized Training Session, Trainers may customize and reproduce, in accordance with the MCT Agreement, those portions of the Licensed Content that are logically associated with instruction of the Authorized Training Session. If you elect to exercise the foregoing rights, you agree or ensure the Trainer agrees: (a) that any of these customizations or reproductions will only be used for providing an Authorized Training Session and (b) to comply with all other terms and conditions of this agreement.
iii. Academic Materials. If the Licensed Content contains Academic Materials, you may copy and use the Academic Materials. You may not make any modifications to the Academic Materials and you may not print any book (either electronic or print version) in its entirety. If you reproduce any Academic Materials, you agree that:
The use of the Academic Materials will be only for your personal reference or training use You will not republish or post the Academic Materials on any network computer or broadcast in any media; You will include the Academic Materials original copyright notice, or a copyright notice to Microsofts benefit in the format provided below: Form of Notice: 2008 Reprinted for personal reference use only with permission by Microsoft Corporation. All rights reserved. Microsoft, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the US and/or other countries. Other product and company names mentioned herein may be the trademarks of their respective owners.
6. INTERNET-BASED SERVICES. Microsoft may provide Internet-based services with the Licensed
Content. It may change or cancel them at any time. You may not use these services in any way that could harm them or impair anyone elses use of them. You may not use the services to try to gain unauthorized access to any service, data, account or network by any means.
7. 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 allow you to use it in certain ways. You may not install more copies of the Licensed Content on classroom Devices than the number of Students and the Trainer in the Authorized Training Session; allow more classroom Devices to access the server than the number of Students enrolled in and the Trainer delivering the Authorized Training Session if the Licensed Content is installed on a network server; copy or reproduce the Licensed Content to any server or location for further reproduction or distribution; disclose the results of any benchmark tests of the Licensed Content to any third party without Microsofts prior written approval; work around any technical limitations in the Licensed Content; reverse engineer, decompile or disassemble the Licensed Content, except and only to the extent that applicable law expressly permits, despite this limitation; make more copies of the Licensed Content than specified in this agreement or allowed by applicable law, despite this limitation; publish the Licensed Content for others to copy;
transfer the Licensed Content, in whole or in part, to a third party; access or use any Licensed Content for which you (i) are not providing a Course and/or (ii) have not been authorized by Microsoft to access and use; rent, lease or lend the Licensed Content; or use the Licensed Content for commercial hosting services or general business purposes. Rights to access the server software that may be included with the Licensed Content, including the Virtual Hard Disks does not give you any right to implement Microsoft patents or other Microsoft intellectual property in software or devices that may access the server.
8. 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. Content marked as NFR or Not for Resale.
9. NOT FOR RESALE SOFTWARE/LICENSED CONTENT. You may not sell software or Licensed 10. ACADEMIC EDITION. You must be a Qualified Educational User to use Licensed Content marked as
Academic Edition or AE. If you do not know whether you are a Qualified Educational User, visit www.microsoft.com/education or contact the Microsoft affiliate serving your country. fail to comply with the terms and conditions of these license terms. In the event your status as an Authorized Learning Center or Trainer a) expires, b) is voluntarily terminated by you, and/or c) is terminated by Microsoft, this agreement shall automatically terminate. Upon any termination of this agreement, you must destroy all copies of the Licensed Content and all of its component parts.
11. TERMINATION. Without prejudice to any other rights, Microsoft may terminate this agreement if you
12. ENTIRE AGREEMENT. This agreement, and the terms for supplements, updates, Internet-
based services and support services that you use, are the entire agreement for the Licensed Content and support services.
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. You bear the risk of
using it. Microsoft gives no express warranties, guarantees or conditions. You may have additional consumer rights under your local laws which this agreement cannot change. To the extent permitted under your local laws, Microsoft excludes the implied warranties of merchantability, fitness for a particular purpose and non-infringement.
16. LIMITATION ON AND EXCLUSION OF REMEDIES AND DAMAGES. YOU CAN RECOVER FROM
MICROSOFT AND ITS SUPPLIERS ONLY DIRECT DAMAGES UP TO U.S. $5.00. YOU CANNOT RECOVER ANY OTHER DAMAGES, INCLUDING CONSEQUENTIAL, LOST PROFITS, SPECIAL, INDIRECT OR INCIDENTAL DAMAGES. This limitation applies to anything related to the Licensed Content, software, services, content (including code) on third party Internet sites, or third party programs; and 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.
xi
Acknowledgement
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.
xii
xiii
Contents
Module 1: Installing System Center Virtual Machine Manager
Lesson 1: Installing System Center Virtual Machine Manager Server Components Lesson 2: Introducing the VMM Administrator Console Lesson 3: Installing the VMM Self-Service Portal Lab 1: Installing System Center Virtual Machine Manager 1-3 1-15 1-25 1-36
xiv
xv
Course Description
This three-day instructor-led course teaches students how to implement a Microsoft System Center Virtual Machine Manager V2 solution in an organization. The course also discusses how to install, configure and deploy VMM.
Audience
The audience for this class would be Consultants or Integrators planning on doing Enterprise VMM implementations and advanced VMM administrators.
Student Prerequisites
In addition to their professional experience, students who attend this training should have technical knowledge and skills in the following areas: Windows Server 2000/2003 System Administration Basic understanding of System Center Virtual Machine Manager (VMM) (optional) Server Virtualization using Virtual Server 2005, Virtual PC, or VMWare Operating knowledge of System Center Operations Manager 2007
xvi
Course Objectives
After completing this course, students will be able to: Install System Center Virtual Machine Manager Server Components. Manage System Center Virtual Machine Manager using the VMM Administrator Console. Install the VMM Self-Service Portal. Configure Virtual Machine Hardware. Administer Virtual Machine Hosts. Configure User Roles. Maintain a Virtual Machine Manager Library. Deploy Virtual Machines. Convert physical computers to Virtual Machines. Convert Virtual Server 2005 or VMware Virtual Machines to Hyper-V. Deploy highly available Virtual Machines. Manage Virtual Machine checkpoints. Manage Virtual Machine updates. Monitor Virtual Machine status. Monitor Jobs.
Course Outline
This section provides an outline of the course: Module/Lab Goal Module 1 describes the installation prerequisites for VMM and describes the procedure for installing VMM. In addition, Module 1 describes the procedure to install the VMM Administrator Console and the VMM Self-Service Portal. Module 2 describes host server hardware configuration considerations. In addition, Module 2 describes general host server configuration procedures including security configuration procedures. Module 3 describes considerations and procedures for configuring the VMM SelfService Portal and Library. This includes enabling user or group-level access to the
xvii
Self-Service Portal, configuring quotas, and using the Self-Service Portal to selfprovision VMs. In addition, Module 3 describes procedures for maintaining VMM library servers and shares and the contents of library shares. Module 4 describes VM deployment and management tasks. This includes using VMM Intelligent Placement, VM Templates, and other automated VM deployment tools. In addition, Module 4 describes using VMM to move VMs between available hosts. Module 5 describes considerations for converting physical and virtual computers to Microsoft VMs. This includes procedures for using deployment agents to execute conversions to Microsoft VMs as well as converting from third-party formats. Module 6 describes considerations and procedures for deploying clustered VMs. Module 7 describes procedures for managing virtual machines using checkpoints and updates. This includes identifying scenarios for using VMM VM Checkpoints and procedures for creating VM Checkpoints. In addition, Module 7 describes update deployment using WSUS and SCCM tools. Module 8 describes procedures for integrating System Center Operations Manager with VMM to extend the capabilities of VMM. This includes using Operations Manager reporting with VMM. In addition, Module 8 describes using Operations Manager to select potential virtualization targets and to monitor and plan host server utilization. Module 9 describes procedures for monitoring and troubleshooting VMM jobs. This includes monitoring and verifying multiple job types as well as recovering from failed jobs.
xviii
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. Lab Answer Keys: Provide step-by-step lab solution guidance at your finger tips when its needed.
Course CD. Provides additional resources pertaining to this course. Resources. Include well-categorized additional resources that give you immediate access to the most up-to-date premium content on TechNet, MSDN, Microsoft Press. Lab Answer Keys: Include answer keys in digital form to use during lab time. Virtual Machine Build Guide: Provides the step-by-step information needed recreate the Virtual Machine/Server images with appropriate configuration. Send Us Your Feedback Instructions: Provide you with an opportunity to send feedback on the all aspects of the course. Student Course Files: Include the Allfiles.exe, a self-extracting executable file that contains all the files required for the labs and demonstrations.
Note: To open the Web page, insert the Course CD into the CD-ROM drive, and then in the root directory of the CD, double-click StartCD.exe.
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.
xix
Computer Configuration
In this course, you will use a physical computer running Windows Server 2008 to perform the labs.
Important: The labs are cumulative. This means that each lab may build on the configuration created during a previous lab.
The following table shows the role of each computer used in this course:
Computer 6331-SEA-VMM-## Role System Center Virtual Machine Manager 2008 (VMM) server and Hyper-V server
xx
Software Configuration
The following software is installed on each VM: Windows Server 2008 Enterprise Edition The Hyper-V role Microsoft SQL Server 2005 SP2 Windows Automated Installation Kit 1.1
Course Files
There are files associated with the labs in this course. The lab files are located in the folder E:\Allfiles\Labfiles on the student computers.
Classroom Setup
Each classroom computer will have the same operating system configured in the same way.
1-1
Module 1
Installing System Center Virtual Machine Manager
Contents:
Lesson 1: Installing System Center Virtual Machine Manager Server Components Lesson 2: Introducing the VMM Administrator Console Lesson 3: Installing the VMM Self-Service Portal Lab 1: Installing System Center Virtual Machine Manager 1-3 1-15 1-25 1-36
1-2
Module Overview
System Center Virtual Machine Manager (VMM) provides a comprehensive management solution for the virtualized data center that enables increased physical server utilization and centralized management of virtual machine infrastructure. VMM has several components that work together: the VMM server, the VMM Administrator Console, and the VMM Self-Service Portal. This module will describe the procedure for installing these components, and important considerations to prepare to install these components.
1-3
Lesson 1
The VMM server is the hub of a VMM deployment through which all other VMM components interact and communicate. Therefore, the VMM server must be installed first. The VMM server runs the VMM service, which runs commands, transfers files, and controls communications with other VMM. The VMM server also connects to a Microsoft SQL Server database that stores all VMM configuration information. Knowing the installation requirements for the VMM server will help you prepare for a successful server installation.
1-4
VMM Components
Key Points
VMM is made up of several components that work together. The VMM Administrator console is a Graphic User Interface (GUI) used to manage the VMM server. The VMM Self-Service Portal is a Web-based component that can allow end users to create and manage their own virtual machines.
Question: Describe one or more scenarios in which you would choose to install the VMM components on separate servers.
1-5
Key Points
Before installing the VMM server, ensure that the computer meets the minimum hardware requirements and that all prerequisite software is installed. The minimum and recommended hardware requirements for the VMM server depend on the number of hosts that the VMM server manages.
2 GB 2 GB
1-6
(continued)
Hardware Component Hard disk space (with the default local SQL Server 2005 Express Edition SP2 database installed) Minimum 10 GB Recommended 50 GB
4 GB 10 GB
Note: For better performance, when the VMM server is managing more than 150 hosts, it is recommended that you add one or more library servers and that you do not use the default library share on the VMM server. Note: The SQL Server 2005 Express Edition SP2 database size is limited to 4 GB, and so it is recommended that you use a full version of SQL Server when the VMM server is managing more than 150 hosts.
Question: In your environment, what preparation tasks will you need to execute before installing one or more VMM servers?
1-7
Key Points
VMM uses a Microsoft SQL Server database to store the information you view in the VMM Administrator Console, such as managed virtual machines, virtual machine hosts, virtual machine libraries, jobs, and other virtual machinerelated data. You can either specify a local or remote instance of an existing Microsoft SQL Server 2005 database or have the Setup Wizard install SQL Server 2005 Express Edition SP2 on the local computer. Actual system requirements vary based on your system configuration and the number of hosts and virtual machines that the VMM server manages.
1-8
80 GB
150 GB
Note: The SQL Server Express Edition database size is limited to 4 GB, and so it is recommended that you use a full version of SQL Server when the VMM server is managing more than 150 hosts.
Question: List two or more considerations for planning where to install the SQL Server that the VMM server will use.
1-9
Key Points
There are security considerations to remember when install a VMM server. If your Active Directory Domain Services (AD DS) installation has multiple forests, and you want to install VMM components in different forests, there must be a two-way trust relationship. If you use a remote instance of SQL Server, the SQL Server must run under an account other than the Local System account. VMM uses Virtual Machine Remote Control (VMRC) to control virtual machines. By default, VMRC connections are not encrypted. It is a best practice to use Secure Sockets Layer (SSL) to encrypt communications over the VMRC connection by uploading a certificate from an appropriate internal or third-party certification authority (CA).
1-10
Question: Describe two or three considerations for implementing SSL encryption for VMRC connections.
1-11
Key Points
After the VMM server component is installed, remember the following security considerations. By default, virtual machines run under the account of the user who started the virtual machine. For enhanced security, you can specify a user account under which to run virtual machines that has a low level of privileges. To create and manage virtual machines on a host, an administrator needs to belong only to the Virtual Machine Manager Administrator security group, and not be a local administrator on the host. Limiting access to hosts in this manner provides greater security for the hosts. File system access should be limited. The access control list (ACL) for library shares should contain only VMM administrators, the Virtual Machine Manager Servers account, and, where appropriate, self-service users.
1-12
When you add a virtual machine host or library server, VMM installs the Virtual Machine Manager Servers machine account as an administrator on the managed computer. Ensure that your Group Policy Restricted Group settings to not remove this account or VMM will not function correctly.
VMM uses three security groups to grant privileges to perform various VMM jobs:
Security Group Virtual Machine Manager Administrators Description Members in this group have administrative privileges on all resources that VMM manages. By default, all local administrators on the VMM server are also VMM administrators. You can add new VMM administrators by adding accounts as members of either group. Members in this group have privileges to delegate actions on behalf of self-service users. When you add a self-service Web server, VMM adds the machine account of that computer to this group on the VMM server. This enables the VMM server to communicate with the computer hosting the VMM Self-Service Portal. Members in this group have privileges to administer virtualization resources on the computer using the VMM agent. When you add a host or library server, VMM adds this security group to that managed computer and adds the machine account of the VMM server. These accounts enable the VMM server to communicate with and perform actions on the managed computers by using the VMM agent.
Question: Are these recommendations compatible with existing security practices in your work environment?
For more information, see "General Security Considerations." For more information, see "Required User Permissions."
1-13
Key Points
Be prepared to complete the VMM server setup by deciding on the installation path, the SQL Server settings, the VMM library settings, and the TCP port settings you will use before starting the VMM server setup.
Question: What ports would you use (or not use) in your organization?
1-14
Question: What considerations apply when choosing ports for the VMM server? Question: Describe some considerations for choosing between a full version of SQL Server and SQL Server Express.
1-15
Lesson 2
The VMM Administrator Console is a graphical user interface (GUI) which serves as the primary point of administration for VMM. Knowing the prerequisites and procedure for installing the VMM Administrator Console will help you prepare to successfully install this component.
1-16
Administrator Console
Key Points
The VMM Administrator Console is a graphical user interface (GUI) that you use to manage one or more VMM servers. You install the VMM Administrator Console after installing the VMM server. You can install the VMM Administrator Console on the same computer as the VMM server or on a different computer. Because using the Reporting feature of VMM requires a local installation of the Administrator Console, it is strongly recommended that you install a Virtual Machine Manager (VMM) Administrator Console on the same computer as the VMM server. You can install one or more VMM Administrator Consoles on other computers in order to manage VMM server. You install the VMM Administrator Console after installing the VMM server. You can install it on the same computer as the VMM server or on a different computer.
1-17
The VMM Administrator Console is used to create, deploy, and manage virtual machines, monitor and manage hosts and library servers, and manage global configuration settings.
Question: Describe one or more scenarios when you would choose to install the VMM Administrator Console on a separate computer from the VMM server.
1-18
Key Points
Before installing the VMM Administrator Console, ensure that the computer meets the minimum hardware requirements and that all prerequisite software is installed. Actual requirements vary based on your system configuration and the number of hosts and virtual machines that the VMM server manages. If you plan to use the reporting feature of VMM, you must install a VMM Administrator Console on the same computer as the VMM server. The reporting feature of VMM relies upon System Center Operations Manager 2007 (OpsMgr). For OpsMgr administrators to perform tasks on hosts and virtual machines from within the Server Virtualization Management Pack requires that the Windows PowerShell Virtual Machine Manager command shell be installed on the VMM server.
1-19
Question: In your environment, what preparation tasks will you need to execute before installing the VMM Administrator Console?
1-20
Key Points
The VMM server is the hub of Virtual Machine Manager. When you install the VMM server, you assign all the ports that it will use for communications and file transfers between the VMM components, including the VMM Administrator Console. Any firewalls controlling network traffic between the VMM server and other VMM components will need to be configured to support the ports used by these components. The VMM server communicates with VMM agents running on managed computers, which are hosts and library servers, by using Windows Remote Management (WinRM), and transfers data to and from the managed computers by using Background Intelligent Transfer Service (BITS). The VMM Administrator Console communicates with the VMM server by using Windows Communication Foundation (WCF) Services.
1-21
The VMM Self-Service Portal communicates with the VMM server by using WCF Services, and self-service users connect to the portal by using Hypertext Transfer Protocol (HTTP). The Self-Service user connects and interacts with the virtual machines by using Virtual Machine Remote Control (VMRC).
Question: List one or more benefits of using non-default port settings for VMM.
1-22
Key Points
Be prepared to complete the VMM Administrator Console setup by deciding on the installation path and the TCP port settings you will use before starting the VMM Administrator Console setup. Question: What ports would you use (or not use) in your organization?
1-23
On the product DVD or network share, double-click setup.exe. On the Setup menu, click Self-Service Portal. On the Prerequisites Check page, review any warnings about inadequate hardware or software prerequisites or alerts about uninstalled requirements. On the Installation Settings page, accept the default path for the location where you want the program files to be installed. On the Web Server Settings page, do the following: In the Virtual Machine Manager server area, specify the name of the VMM server you want the VMM Self-Service Portal to connect to and the port that you want the VMM Self-Service Portal to use to communicate with the VMM server. In the Web server area, specify the port that you want self-service users to use to connect to the Self-Service Portal.
1-24
On the Summary of Settings page, review your settings and click Install to install the VMM Self-Service Portal. On the Installation page, after setup completes, click the link in the Status window to check for the latest VMM updates.
Question: How are you likely to install the VMM Administrator Console in your organization? Question: List one or two reasons you might receive warnings or alerts on the Prerequisites Check page.
1-25
Lesson 3
The VMM Self-Service Portal is an optional, Web-based component that a VMM administrator can configure to allow end users to create and manage their own virtual machines within a controlled environment. Knowing the prerequisites and requirements for installing and configuring the VMM Self-Service Portal will help you successfully use this component.
1-26
Key Points
Before installing the VMM Self-Service Portal, ensure that the computer meets the minimum hardware requirements and that all prerequisite software is installed. The minimum and recommended hardware requirements for the VMM SelfService Portal depend on the number of concurrent connections that the SelfService Portal will support.
1-27
2 GB 10 GB
Question: In your environment, what preparation tasks will you need to execute before installing the VMM Self-Service Portal?
1-28
Key Points
In Microsoft Windows Server 2008, use Server Manager to add the required IIS role services. The VMM Self-Service Portal prerequisites check will determine whether necessary IIS components are installed. The list above shows required IIS 7.0 components that are not part of a default IIS 7.0 installation on a new server.
1-29
Key Points
By default, the Virtual Machine Manager (VMM) Self-Service Portal installs in a non-secure mode. To encrypt your communications with the Self-Service Portal, and enable users to confirm the identity of your Self-Service Portal, you should enable Secure Sockets Layer (SSL) on your Web server. To configure SSL in IIS 7.0, you must complete the following steps: 1. Obtain a certificate - If you want your users to be able to verify the Self-Service Portals identity with your certificate, you will need to send a certificate request to a CA. Otherwise, you can create a self-signed certificate, which is a certificate created by your computer. You can create a self-signed certificate using the IIS Manager user interface. Create an SSL binding - The bindings editor provided with IIS Manager walks you through adding an SSL binding.
2.
1-30
3.
Test the configuration - After you have created your binding, you should test your site. If you have used a self-signed certificate, you will encounter a security warning. To trust the certificate, you need to add it to the list of Trusted Root Certification Authorities in the certificates store on the local computer or in Group Policy for the domain. Configure SSL options - To require SSL for your site, open SSL settings, and select Require SSL.
4.
IIS allows you to assign any number of sites to a single IP address and distinguish them by using host headers. Use Internet Information Services (IIS) Manager to configure host headers on IIS 7.0. If the computer is on a private LAN, register it with the intranet's name resolution system. If the computer is on the Internet, register the host header name with the Domain Name System (DNS). Using host headers with VMM allows you to identify the Self-Service Portal in a way that is intuitive for users. An example of this would be assigning http://vmm-selfservice.contoso.com to the VMM Self Service Portal Web site.
Question: What considerations are relevant when deciding whether to use host headers?
For more information, see "How to add a custom HTTP response header to a Web site that is hosted by IIS." For more information, see "Configuring SSL for the Self-Service Portal." For more information, see "Configuring Windows Integrated Authentication for the Self-Service Portal."
1-31
Key Points
It is a best practice to not use default port settings for VMM component communication because the default ports may conflict with other network applications. The port setting that you assign must identically match the port settings that you assigned when installing the VMM server. If the default port setting (80) for the VMM Self-Service Portal is being used by another Web site, you must either use a different dedicated port setting or specify a host header for the portal.
Question: What considerations might apply when specifying a port for self-service users to use when connecting to the Self-Service Portal?
1-32
Key Points
Once the VMM Self-Service Portal prerequisites have been met, you can install the Self-Service Portal. Be prepared to complete the VMM Self-Service Portal setup by deciding on the installation path and the Web server settings you will use before starting the VMM Self-Service Portal setup. To Install the Self-Service Portal, you must be an administrator on the computer and be a member of the Virtual Machine Manager Administrators security group.
Self-service users might be asked for credentials when connecting to virtual machines. This is because the self-service portal Web page uses Microsoft Internet Explorer, which interprets a virtual machine host to be an external Internet resource. To avoid being asked for credentials, have the user add the Fully Qualified Domain Name (FQDN) of the host to the Local intranet sites in the Security settings of Internet Options for Internet Explorer by using the following procedure.
1-33
Question: What VMM Self-Service Portal configuration would you use (or not use) in your organization?
1-34
Question: How are you likely to install the VMM Self-Service Portal in your organization? Question: Describe any configuration steps that may need to occur after the SelfService Portal is installed.
1-35
Key Points
Discuss the questions in a classroom discussion, led by your instructor, and determine the answers. Question: How do you plan to install VMM in your environment? Question: What changes will be required in your environment to install VMM?
1-36
1-37
On the Port Assignments page, configure the following settings: VMM server connection: Decide on a port for this setting and use it for the rest of this lab. Agent connections: Decide on a port for this setting and use it for the rest of this lab. File transfers: Decide on a port for this setting and use it for the rest of this lab.
Results: After this exercise, you should have successfully installed the VMM server component.
1-38
Results: After this exercise, you should have successfully installed the VMM Administrator Console. You should be able to start the VMM Administrator Console and connect to the VMM server.
1-39
Exercise 3: Installing the VMM Self-Service Portal and Configuring a DNS Record
Scenario
In addition to managing all VMs from a single location, Contoso also wants to delegate VM creation. They want to do this using the VMM self-service portal. You have been given the task of installing the self-service portal. Contoso has decided to implement VMM to manage multiple virtualization hosts. In this exercise you will install the VMM Self-Service Portal on your Hyper-V server. The main tasks for this exercise are as follows: 1. 2. Installing the VMM Self-Service Portal. Configure a DNS Record.
1-40
Results: After this exercise, you should have successfully installed the VMM SelfService Portal and successfully configured the selfservice.contoso##.com DNS A record. You should be able to successfully browse to http://selfservice.contoso##.com.
2-1
Module 2
Configuring VM Hardware, Hosts, and User Roles
Contents:
Lesson 1: Adding Hosts to VMM Lesson 2: Configuring Hardware Lesson 3: Configuring VMM Settings Lesson 4: Managing VMM Settings Lab: Configuring VM Hardware, Hosts, and User Roles 2-3 2-13 2-26 2-36 2-41
2-2
Module Overview
When implementing a System Center Virtual Machine Manager (VMM) server, it is important to configure hardware in a way that best supports the running virtual machines (VMs) in your environment. In order for VMM to provide centralized administration and management of your virtual machine infrastructure, host server hardware and security configuration procedures must be considered. VMM Servers that are configured properly will provide better results when provisioning new VMs and will be able to maintain and manage VMs better.
2-3
Lesson 1
There are varying types of VMM hosts available, and each type has specific characteristics. These characteristics depend on the placement of the host with respect to a domain and the virtualization platform that each host runs. Until you add a host, you cannot create or manage virtual machines by using VMM and many of the actions in the VMM Administrator Console are not available. Knowing the different host types and their configuration requirements will help you in adding host to the VMM server.
2-4
Host Types
Key Points
A virtual machine host is a physical computer that hosts one or more virtual machines. You can add one or more hosts to System Center Virtual Machine Manager (VMM). Until you add a host, you cannot create virtual machines by using VMM and many of the actions in the VMM Administrator Console are not available. Hosts types have specific characteristics. Hosts in Trusted Domains: In the most common topology, the VMM server and hosts are members of a domain in Active Directory Domain Services (AD DS). Security is provided by the login authentication and account authorization of Active Directory. You can add one host at a time or add multiple hosts that all share a common set of configuration settings.
2-5
Hosts on a Perimeter Network A perimeter network is a network that is separate from an organization's internal network and the Internet and has the following characteristics: Allows external users to access specific computers located on the perimeter network. Can be set up to allow limited access from users on the internal network to computers located on the perimeter network. You can deploy virtual machines on a host on a perimeter network from within the internal network. The VMM server cannot directly access a host on a perimeter network, so you must install a VMM agent locally on the host before you can use the Add Hosts Wizard to add it to VMM.
Non-Window Hosts VMM supports non-window hosts such as VMWare. Non-Windows hosts can also be added by using the Add Hosts Wizard to add one or more non-Windows hosts to VMM.
Question: List one or more drawbacks to implementing a perimeter network that has a web server delivering web content to the internet. List one or more potential benefits to this scenario.
For more information, see "Planning for Hosts and Host Groups."
2-6
Key Points
Use the wizards that guide you through the process of adding a VM host. Virtual Machine Manager has the ability to add one or more virtual machine hosts in a trusted domain. When you add a Windows-based host, VMM automatically installs or upgrades the appropriate version of Virtual Server or Hyper-V virtualization software. When adding multiple hosts at one time, use a domain account that has administrative rights on all the selected hosts. VMRC is a feature which allows the remote management of running virtual machine. If you are planning to use Virtual Machine Remote Control (VMRC), the VMRC configuration can be set during the addition of a host.
2-7
Question: Describe at least one scenario when you would use VMRC.
2-8
Key Points
When you install a VMM agent locally on a host on a perimeter network, the Agent Setup Wizard prompts you for an encryption key and other information needed by VMM to access and manage the host and its virtual machines. The wizard generates a set of agent credentials and uses the key to encrypt the credentials and the other agent access information into a security file. You should note the encryption key that is used to create the security file. To successfully add the host, the security file must be transferred from the host computer to the computer on which you will use the VMM Administrator Console. When installing the VMM Agent, considerations for port settings and security will be addressed in the VMM Agent Wizard. Once the Agent is installed, you will add the host to a perimeter network and utilize the path to the security file. Once you have added the host, you should permanently delete the security file.
2-9
Question: Describe two ore three scenarios where you would choose to set up a Perimeter host.
For more information see "VMM System Requirements." For more information, see "How to Add a Host on a Perimeter Network."
2-10
Key Points
The System Center Virtual Machine Manager 2008 environment can support a VMWare Infrastructure 3 (VI3) environment. The VMWare Virtual Infrastructure and Microsoft virtualization technologies can be managed together using a single tool. 1. 2. 3. The workflow of managing VMWare starts from adding your VMWare Virtual Center Server (VCS) into VMM. When initiated, you will be asked to provide the administrator's credential for the Virtual Center Server. The new host state for the newly imported ESX hosts is "OK (Limited)." After the credentials are provided and verified, the host state will turn to an "OK" state, where the full set of VM operations in VMM is then supported. After the confirmed status of "OK," you can use the Add Host Wizard to add additional ESX hosts.
4.
2-11
Question: List one or more potential advantages of using VMM to manage VMWare host and Microsoft virtualization hosts together.
2-12
Key Points
The workflow for managing a VMWare VC Server is as follows: 1. 2. 3. 4. 5. Configure Virtualization Managers. Specify the VMWare VC server to add. Specify an account that is an administrator on the VMWare VC server. Provide credentials for the VMWare host. View VMWare host properties.
Question: After adding a VMWare Virtual Center Server to VMM, provide a scenario where you would not have host credential verified and host SSH root disabled.
2-13
Lesson 2
Configuring Hardware
In support of VMM management, hardware configurations are created and configured to match the needs of the VMs. Configurations can be created as a profile and can provide standardized VM hardware configurations. By configuring your hardware for specific or general instances of VMs, VMM manages VMs more efficiently.
2-14
Key Points
When configuring a network for virtual machines, the types of network adapters and their configurations influence the communication abilities of VMs using the network. There are two types of network adaptors: Emulated and Synthetic. Emulated network adapters are also known as Legacy network adapters. This network adapter type does not require Hyper-V Integration Components in the guest operating system and also provides compatibility for un-supported guest operating systems. Synthetic network adapters provide better performance than Legacy network adapters. Synthetic network adapters are able to communicate with physical hardware using a high-speed communication protocol known as VMBus. This network adapter type requires a compatible guest operating system.
2-15
Emulated devices create an exact software representation of a physical device. For example, an emulated disk controller is indistinguishable, to the guest operating system, from its physical counterpart. This means that the guest operating system will also experience the limitations of its physical counterpart. If a physical disk controller device is unable to support hot-addition of disks, its emulated counterpart will also have this limitation. Synthetic devices are virtual devices that are mapped to physical devices but do not emulate physical devices. Because synthetic devices do not emulate physical devices, they have been designed without the limitations found in many physical devices.
Traditional a software based NIC emulates the functionality of a hardware NIC as used in current versions of Virtual PC environment. By default, a virtual network adapter that you add is not connected to a virtual network. Optionally, you can configure virtual machines created from this hardware profile to use one or more virtual network adapters that connect the virtual machines to internal networks or to external networks once the virtual machines are deployed on a host. Virtual Local Area Networks (VLANs) give the ability to create more independent logical networks. Ethernet (MAC) address can be set dynamically or statically.
Question: Describe some considerations for choosing between a static and dynamic MAC address.
For more information, see "VMM System Requirements." For more information, see "Supported Guest OS on Windows Server 2008 Hyper-V."
2-16
Key Points
VMM supports all forms of direct attached storage, as well as providing support for a Fiber Channel or an iSCSI storage area network. Direct Attached Storage or DAS is a storage solution designed for connectivity with a small number of servers. Rather than present storage over a network like Storage Area Networks (SAN) solutions, a DAS solution is directly attached to servers over a SCSI or Fiber connection. Storage Area Networks or SANs provide block-level access to shared data storage. Block-level access refers to the specific blocks of data on a storage device as opposed to file-level access which refers to access at the file level. Conceptually a fiber channel switch is similar to a standard network switch. A Fiber Channel switch is compatible with the Fiber Channel protocol and enables the creation of Fabric Zones. Servers typically connect to a Fiber Channel switch via Host Bus Adapters (HBA). You can use a HBA to connect a host system (the computer) to other network and storage devices.
2-17
A Fiber or iSCSI SAN enables certain Hyper-V features such as Quick Migration, which facilitates the movement of virtual guests from one physical node to another with minimal downtime. Fiber Channel, or FC, is a gigabit-speed network technology primarily used for storage networking. In computing, iSCSI (for "Internet SCSI") is a protocol that allows clients (called initiators) to send SCSI commands to SCSI storage devices (targets) on remote servers. It is a popular Storage Area Network (SAN) protocol, allowing organizations to consolidate storage into data center storage arrays while providing hosts (such as database and web servers) with the illusion of locallyattached disks. Unlike Fiber Channel, which requires special-purpose cabling, iSCSI can be run over long distances using existing network infrastructure. Host Bus Adapter (HBA) technology connects a host system (the computer) to other network and storage devices. Each HBA has a unique World Wide Name (WWN), which is similar to an Ethernet MAC address in that it uses an Organizationally Unique Identifier (OUI) assigned by the Institute of Electrical and Electronic Engineers (IEEE). HBA VMs have there own virtual HBA port and can be independently zoned to a distinct and dedicated World Wide Port Name.
Question: List a scenario where you would use a Direct Attached, Fiber Channel Storage Area Network, and an iSCSI Storage Area Network.
2-18
Key Points
Depending on your need, there are benefits and drawbacks to using pass-through disks and iSCSI storage. Benefits: Disk performance: Like fixed-size disks, pass-through disks are very fast. Keep in mind that fixed -size virtual hard disks perform so well that theyre just about equal to pass-through disks. This is because of Hyper-Vs new driver architecture. Support for greater than 2 TB per disk: Virtual Hard Disks are limited to only up to 2 TB in size each. With pass-through disks, the limit per disk is whatever is supported by the guest operating system and the size of your physical storage. iSCSI: iSCSI can expose disks directly to the guest OS using an iSCSI initiator within the guest OS.
2-19
Drawbacks: Portability: Pass-Through disks are not as portable as virtual machines, because pass-through disk are not encapsulated in a file. When using a PassThrough disk a virtual machine writes directly to the Logical Unit Number (LUN) without encapsulating it in a Virtual Hard Disk file. Disk Limit: The limit per disk is determined by the guest operating system and the size of your physical storage. Booting to iSCSI: Hyper-Vs virtual BIOS does not support booting to iSCSI directly, although your other disks can be iSCSI LUNs.
Question: Describe any differences between Pass-Through and iSCSI storage types. Also describe some considerations for choosing between these two storage types.
For more information, see "VMM System Requirements." For more information, see "Storage options for Windows Server 2008 Hyper-V."
2-20
Key Points
Using the New Virtual Machine wizard, you can configure Pass-Through and iSCSI storage. Hardware profiles settings can be modified. The hardware profile includes a built-in IDE drive by default. You have the option to expose disks directly to the guest OS (without ever exposing it to the host) by using iSCSI. When considering moving between host, iSCSI data will easily move with if you use iSCSI directly exposed to the guest.
2-21
Question: Why would you choose IDE instead of SCSI on the guest, when configuring guest disk storage?
For more information, see "VMM System Requirements." For more information, see "Storage options for Windows Server 2008 Hyper-V."
2-22
Configuring Memory
Key Points
Use the New Template Wizard or the New Virtual Machine Wizard to customize the amount of memory allocated for new virtual machines. You can configure the memory for a virtual machine by creating or modifying a Virtual Machine Manager Hardware profile. You can select the total amount of memory on the host that you want to allocate to a virtual machine. The maximum amount of memory that is available to each virtual machine memory depends on the virtualization platform: Hyper-V: 64 GB Virtual Server: 3.6 GB VMWare: 64 GB
2-23
Question: Describe two or more considerations you use when determining how much memory to allocate to a virtual machine.
For more information, see "How to Configure the Amount of Memory for a Virtual Machine."
2-24
Configuring Processors
Key Points
You can configure the CPU requirements for a virtual machine by creating or modifying a Virtual Machine Manager hardware profile. These settings specify the processor resources on a host that you want a virtual machine to use. The CPU type determines the CPU requirements of virtual machines created from this hardware profile. Virtual Machine Manager uses this setting when placing new virtual machines on hosts.
2-25
For more information, see "How to Configure CPU Requirements for a Virtual Machine." For more information, see "Configuring CPU Resources for Virtual Machines."
2-26
Lesson 3
Virtual machine settings are influenced by the settings of Virtual Machine Manager. Virtual networks provide the communication link between virtual machines, and Intelligent Placement assures that the VMs are placed on appropriate host based on their configurations. By configuring the VMM settings to best represent the general environment, you will have more control and manageability of the host server and the VMs being placed on them.
2-27
Key Points
For a Hyper-V host, there are specific options available through VMM. When configuring Virtual Networks, Hyper-V Manager has two types of virtual network which can be created: External, and Internal. Creating a virtual network depends on how the switch bindings are configured in VMM. External Virtual Networks External virtual networks, or use of the Physical network adapter, are used where you want to allow communications between: A virtual machine to externally located servers (and visa-versa). (Optional) Parent partition to externally located servers (and visa-versa).
2-28
Internal Virtual Networks Internal virtual networks are used where you want to allow communications between: Virtual machine to virtual machine on the same physical server. Virtual machine to parent partition (and visa-versa).
Question: How does emulating a physical network switch benefit the network environment?
For more information, see "Managing Virtual Server Host Clustering with System Center Virtual Machine Manager 2007." For more information, see "Hyper-V: What are the uses for different types of virtual networks?"
2-29
Key Points:
To add and configure a virtual network on a host: 1. 2. 3. 4. 5. Select the host. Add a virtual network. Configure the name, and description of the host. Configure Network bindings. In this example, add a physical network. With a physical network, configure the switch binding from the host adapter list.
Note: In Virtual Machine Manager a warning will appear if there is one network adapter and it was chosen for the virtual network. There will be no physical network adapter dedicated to management of host communications.
2-30
Question: Explain how configuring switch bindings to a physical network card effect the communication of the VMs. Question: Explain the communication between the VMs if no network adapter was established.
For more information, see "How to Add or Modify Virtual Networks on a Host."
2-31
Key Points
Intelligent Placement is a capacity planning function. For a given VM, the Intelligent Placement function takes various performance data (CPU, memory, disk, and so on) collected from the VM and the host where the VM runs, calculates it with user-defined placement preferences (priority), and generates a set of ratings for hosts that are managed by VMM. Ratings include the placement settings for VMs, the resources available on the hosts, and the hardware and resource requirements of specific VMs. Define your rating criteria based on your workload requirements; VMM will calculate the ratings for all your available hosts.
2-32
Question: Your VMs run applications that require increased disk I/O. The Customize Ratings for Placement options are using the placement goals of Load Balancing. What additional changes would you make to produce a better placement rating?
For more information, see "How to Set Placement Options for a Host."
2-33
Key Points:
Configuring VMM Intelligent Placement configuration: 1. 2. 3. In the VMM Admin Console, configure the placement settings through the Administrator view. CPU usage is set to very important. Disk I/O is set to not important,
Adding a new VM to the host: 1. 2. 3. 4. 5. 6. Create a new virtual machine. Create a new blank virtual hard disk. Configure the virtual machines identity. Configure hardware. Place the virtual machine on a host. Select a Virtual Machine Host.
2-34
7. 8. 9.
Accept the default path. Select a network from the virtual network list. Configure additional properties.
Question: Describe a scenario when you might use resource maximization instead of load balancing. Question: Explain how a limited number of hosts can also effect the placement of VMs.
For more information, see "How to Set Placement Options for a Host."
2-35
Key Points
When configuring the Virtual Machine Manager, working with filters will assist with the management of the jobs you have created. Based on properties selected for the status, owner, and date, different filters provide a variety of views in the VMM Administrator Console. Question: Provide a practical example of how you may use a filter in VMM.
For more information, see "How to Filter Objects in the Results Pane."
2-36
Lesson 4
VMM has three types of User roles: Administrator, Delegated Administrator and Self-Service. These user roles are based on membership, profile, and scope. Each user role has VMM security settings, and representing what tasks can be performed. When utilizing the Self-Service portal, Self-Service user roles are created and configured by the member(s) of the Administrator or Delegated Administrator User role. Creating and configuring appropriate User roles will help you when you need to meet regional and functional administration delegation requirements within the VMM environment.
2-37
Key Points
In VMM 2008, you now have the ability to configure full role configurations by allowing further customization of the scope (what objects you can manage) and the profile (what actions you can take on the objects you have rights to manage). Based on this model, you have three user roles consisting of an Administrator, Delegated Administrator, and Self-Server User roles. The Delegated Administrator role is a new profile allowing users to divide their virtualization resources into segments. Delegated Administrator members can only view their created managed roles, but can not manage the role of which they are a member. The Administrator has access to all roles and configurations. The new User Role Wizard provides you the ability to setup user roles.
2-38
For more information, see "How to Create a Self-Service User Role." For more information see "How to Create a Delegated Administrator User Role."
2-39
Key Points
A Self-Service User Role results from the creation of a Self-Service role by the Administrator or Delegated Administrator. After the Self-Service role is created, so are the self-service polices for that role. Depending on how the Self Service role is configured, a member of that role can perform various tasks with VMs. A Self-Service member has the abilities to create, operate, manage, store, create checkpoints, and provides access to connect to their own virtual machines. It is a best practice in configuration to create one self-service policy for each individual self-service user. Self-Service User Role members can not manager their own User role. If you use domain groups, improved performance can be achieved by limiting the number of users in each group.
2-40
Question: Determine which of the three user roles are associated with each characteristic. 1. 2. 3. Aaron needs to be able to create Delegated Administrator and Self-Service User roles, within given objects. Jan is a domain administrator and installed VMM under her account. What was the role that was assigned to her? Susan is a member whose role is managed by the Administration role or a Delegated Administrator, and has access to specific VMs.
2-41
2-42
2-43
f Task 2: Create VMs with blank hard disk using hardware profiles
Create a VM named File Server, using the created FileServer hardware profile. It will be placed on the host, where you will customize the rating so that all resource options are at the second highest increment of Very Important. Create a VM. Named: SCSI-01, hardware profile SCSI -High Availability profile. Store in the library.
2-44
2-45
Test to see if user Aaron Conner (contoso##\aconner), Password: Pa$$w0rd can log into 6331-SEA-VMM-##. Open SCVMM administrator console.
2-46
Create a self-service role that he will manage called Developers SelfService. The member will be the developer Jan Blank. The scope ranges all hosts, all tasks are allowed, creation is allowed with a template called Windows Server 2008 and storage is placed in the SCCVMMlibrary under VHDs, only allowing a quota of 2.
Test to see if Jan Blank can access the self-service portal as contoso##\JBlank, Password: Pa$$w0rd. Verify the Quota available reflects the appropriate number of 2.
Log back into 6331-SEA-VMM-## as contoso##\administrator. Password: Pa$$w0rd. Open SCVMM administrator console, and review all user roles that were created.
Results: After this exercise, the users should have been able to log into the portal and seen that they have the ability to create the appropriate number of VM set by the quota. Logging back in as the Administrator you should see all user roles, IT Admin Support, Self Service Full, and Developers Self Service. These can be viewed in Administration view, User Roles results pane.
3-1
Module 3
Configuring the VMM Self-Service Portal and Library
Contents:
Lesson 1: Configuring the VMM Self-Service Portal Lesson 2: Maintaining a VMM Library Lesson 3: Managing Library Files Lab: Configuring the VMM Self-Service Portal and Library 3-3 3-11 3-17 3-21
3-2
Module Overview
This module describes considerations and procedures for configuring the Virtual Machine Manager (VMM) Self-Service Portal and Library. This includes enabling user or group-level access to the Self-Service Portal, configuring quotas, and using the Self-Service Portal to self-provision virtual machines (VMs). In addition, this module describes procedures for maintaining VMM library servers and shares and the contents of library shares.
3-3
Lesson 1
By configuring user roles and host groups, the administrator is able to determine how users are able to use the self-service portal. For example, developers may be allowed access to several VMs while other users may be limited to just one.
3-4
Key Points
To enable the self-service portal for users, they must be assigned a user role. Host groups are containers for hosts so that they can be grouped in a meaningful way. User roles are assigned access to specific host group(s). Users from Active Directory are assigned to specific user roles.
3-5
Key Points
The following list describes ways that you can create and use host groups to organize hosts for your environment: Basic organization when managing large numbers of hosts and virtual machines. Scoping administrative tasks such as the placement of virtual machines on hosts. Reserving resources for use by hosts. Automatically placing virtual machines on the most suitable host. Earmarking hosts on which users can create and operate their own virtual machines. Implementing Performance and Resource Optimization (PRO).
3-6
Question: Will your environment require multiple host groups? If so, why?
For more information, see "How to Modify the Properties of a Host Group."
3-7
Key Points
Self-service users can use existing virtual machines or, if they have the permissions to do so they can create their own virtual machine(s). During the user role creation process, select Allow users to create new virtual machines if they need the ability to create their own virtual machines. A virtual machine template is a library resource consisting of a guest operating system profile, a hardware profile, and one or more virtual hard disks (VHDs). You can use templates to create new virtual machines repeatedly with standardized hardware and software settings. Self-service users must use assigned templates to create their virtual machines.
3-8
Configuring Quotas
Key Points
The Self-Service user role may be assigned a quota to limit the number of virtual machines the user can create or deploy at one time. The quota applies to all virtual machines deployed on a host, including virtual machines that are not currently running. If the users are allowed to store their virtual machines when they are not in use, the virtual machines that are stored do not count against their quota.
Question: How and why might the quota set for different VMs differ? Question: What quota limits might you use for various users in your environment?
3-9
1. 2. 3.
Open Microsoft Internet Explorer and browse to http://selfservice.contoso.com. Log on as contoso\jblank. Create a new virtual machine.
3-10
3-11
Lesson 2
The VMM library is a catalog of resources used to create and configure virtual machines in VMM. The library contains files stored on library shares, and it contains operating system, hardware, and template configurations stored in the VMM database. Library resources are added, created, used, and managed in library view.
3-12
Adding a Library
Key Points
A library server must meet the following requirements: The library server must have either the Microsoft Windows Server 2008 operating system or the Microsoft Windows Server 2003 SP1 or later operating system. For highly available file servers, the failover cluster must have been created in Windows Server 2008. The library server must be in an Active Directory domain that has a two-way trust relationship with the VMM servers domain. VMM does not support file servers configured with the case-sensitive option for Windows Services for UNIX (NFS Case Control is set to Ignore).
3-13
To add a library server to VMM: 1. 2. 3. 4. In any view of the VMM Administrator Console, in the Actions pane, click Add library server. On the Enter Credentials wizard page, enter a domain account that has administrative credentials on all of the servers that you will add. On the Select Library Servers wizard page, type or select the server that you want to add, and then click Add to add the server to the list of selected servers. On the Add Library Shares wizard page, select each share that you want to add to the library. Only files on designated library shares will be indexed during library refreshes. On the Summary wizard page, click Add Library Servers.
5.
3-14
Key Points
Virtual Machine Manager indexes only files stored on designated library shares. If, after adding a library server, you want to add or remove library shares on the server from the library, you can use the Add library share action. Resources on the share are immediately indexed in VMM. If you are no longer using the resources on a library share, you can remove the library share to remove the resources from the Virtual Machine Manager library. Removing a library share does not delete the files; the resources simply are no longer indexed during library refreshes. This provides a way to temporarily remove resources that are not in use. When you remove a library share, VMM lists any files on the share that are linked to virtual machines, guest operating system profiles, hardware profiles, or virtual machine templates elsewhere in VMM. Removing files that are linked to other resources places the dependent resources in a Failed state.
3-15
3-16
1. 2. 3.
Create a new folder called Lab Library Share, and share the folder. Add the new shared folder to the Library. Review the new share.
Question: When might there be a need for a library share to reside on a highly available server?
3-17
Lesson 3
To be used in Virtual Machine Manager (VMM), files must be added to the VMM library. This is done by copying the files to a library share on a library server, and then refreshing the library share.
3-18
Key Points
Files which are indexed and added to the library: ISO images (.iso) Sysprep.exe information files (.inf) Extended Markup Language files (.xml) are added to scripts since they might be Windows Server 2008 or Microsoft Windows Vista scripts Virtual hard disks: .vhd (Virtual Server) and .vmdk (VMware) Virtual floppy disks (.vfd) Windows PowerShell scripts (.ps1) Configuration files from virtual machines created in VMware (.vmx), to enable virtual-to-virtual machine conversions (V2V conversions) Virtual hard disks (.vhd) that are attached to stored virtual machines. These files are indexed, but they are not displayed in the library because the files cannot be used in other virtual machines, templates, or profiles.
3-19
Files which are indexed and added as virtual machine objects: Virtual Server: .vmc (Virtual Server VM configuration file), .vmx (Virtual Server VM export format), and .vsv (VM saved state) Hyper-V: .vmtx (VM configuration file), .exp (export format)
Files which are not indexed: Hyper-V and VMware saved state files
For more information, see "File Types That Are Indexed During a Library Refresh."
3-20
3-21
3-22
4. 5.
Create the Developer Self-Service Full User Role. Test User Role Settings.
f Task 2: Edit the properties of the Developers Self Service Full user
Select the Developers Self Service Full user role. Open the properties of the user role. On the Scope tab, clear All Hosts and select Self Service.
f Task 3: Edit the properties of the Self Service Full user role
Select the Self Service Full user role. Open the properties of the user role. On the Scope tab, clear All Hosts and select Self Service.
3-23
3-24
4-1
Module 4
Deploying and Managing VMs
Contents:
Lesson 1: Deploying VMs Lesson 2: Moving VMs Between Hosts Lab: Virtual Machine Deployment 4-3 4-16 4-25
4-2
Module Overview
This module describes virtual machine (VM) deployment and management tasks. This includes using System Center Virtual Machine Manager (VMM) Intelligent Placement, VM Templates, and other automated VM deployment tools. In addition, this module describes using VMM to move VMs between available hosts.
4-3
Lesson 1
Deploying VMs
This lesson will discuss how to deploy virtual machines using multiple methods, including using Intelligent Placement to deploy virtual machines.
4-4
Key Points
There are several different ways in which you can create a virtual machine from a VHD file. First, from any view in the Virtual Machine Manager (VMM) you can click New virtual machine in the Actions pane and follow the steps below: 1. 2. 3. On the Actions pane in the Virtual Machine Manager Administrator Console, click New virtual machine. Complete the New Virtual Machine wizard. On the Select Source page, select the From an existing template, virtual machine, or virtual hard disk stored in the library option, and then click Select. In the Select Library Object dialog box, select the virtual hard disk that you want to use. Complete the rest of the wizard as normal.
4.
4-5
Another way to create a virtual machine is through the library view of the VMM console. 1. 2. 3. 4. Filter the view to show only Virtual Hard Disks. Select the Virtual Hard Disk to create the virtual machine from. In the Actions pane, under Virtual Hard Disk, click New virtual machine. Complete the New Virtual Machine wizard.
For more information, see "How to Create a Virtual Machine from an Existing Virtual Hard Disk."
4-6
Key Points
There are several different ways in which you can create a virtual machine from a template. First, from any view in the Virtual Machine Manager (VMM) you can click New virtual machine in the Actions pane and follow the steps below: 1. 2. 3. On the Actions pane in the Virtual Machine Manager Administrator Console, click New virtual machine. Complete the New Virtual Machine wizard. On the Select Source page, select the From an existing template, virtual machine, or virtual hard disk stored in the library option, and then click Select. In the Select Library Object dialog box, select the template that you want to use. Complete the rest of the wizard as normal.
4.
4-7
Another way to create a virtual machine is through the library view of the VMM console. 1. 2. 3. 4. Filter the view to show only templates. Select the template to create the virtual machine from. In the Actions pane, under Template, click New virtual machine. Complete the New Virtual Machine wizard.
Question: Are there scenarios when you could use templates in your organization?
4-8
Key Points
To deploy a virtual machine from the VMM library there are three basic steps. 1. 2. 3. In the VMM Library of the SCVMM Admin Consol, select the virtual machine you wish to deploy (or the VHD or Template to create a VM and deploy from). Launch the Deploy wizard (or the Create wizard if you are going to create and then deploy a virtual machine). Complete the wizard by choosing a host from the list.
Note: To successfully migrate a virtual machine that is in a saved state, or to deploy the virtual machine from a library server to a host, the processor architecture on the two hosts must be compatible.
4-9
4-10
Demonstration: Deploy a VM
In the VMM Administrator Console, display Library view. In the navigation pane, navigate to the library server on which the virtual machine is stored, and then expand VMs and Templates. In the Results pane, select the virtual machine, SCSI. In the Actions pane, under Virtual Machine, click Deploy. On the Select Virtual Machine Host wizard page, select a host to deploy the virtual machine on. Click Next. On the Select Path wizard page, in Save Path, click Browse, navigate to the folder in which you want to store the configuration files for the virtual machine, and then click OK.
4-11
On the Select Networks wizard page, modify the networks and attach them to None or to any of the virtual networks that are found on the selected host. On the Summary wizard page, review the settings. To change settings, click Previous. Click Cancel.
Question: What host rating values will be important to this virtual machine?
4-12
Key Points
In the following cases, a virtual machine is automatically placed on the most suitable host in a host group, in a process known as automatic placement: In virtual machine self-service, users' virtual machines are automatically placed on the most suitable host in the host group that is used for self-service. Automatic placement also occurs when the drag-and-drop method is used to migrate a virtual machine to a host group in Virtual Machines view. During automatic placement, the configuration files for the virtual machine are moved to the volume judged most suitable on the selected host. For automatic placement to succeed, a virtual machine path must be configured on the recommended volume.
4-13
Question: What host rating values might hosts in your environment be configured for?
4-14
Key Points
With VMM, you can manage the administrative permissions your users have by creating user roles. There are three user roles: Administrator: Able to perform all actions in the VMM Administrator Console. Members of this user role can create new Delegated Administrator and SelfService user roles. Only the members of the Administrator user role can add additional members. Delegated Administrator: Able to perform all actions in the VMM Administrator Console, but only within the scope defined in the role. Members of this user role can create new Delegated Administrator and Self-Service user roles. Self-Service: Able to sue the Self-Service console to perform tasks on their virtual machines as defined in the user role. Members of this user role cannot create new user roles.
4-15
Question: What steps would you take to plan and implement delegated provisioning?
4-16
Lesson 2
This lesson will help you to identify considerations for SAN VM migrations; examine how to perform a Quick Migration; and how to use Intelligent Placement to move a VM.
4-17
Key Points
Within the Virtual Machine Manager (VMM) console there are several different ways in which a virtual machine can be migrated from one host to another. In the Virtual Machines view of the VMM console, the following three methods are available to migrate a deployed virtual machine to a different host: Use the Migrate virtual machine action. Drag and drop the virtual machine onto a host. Drag and drop the virtual machine onto a host group.
Question: What are the benefits and drawbacks to the different methods?
For more information, see "How to Migrate a Virtual Machine to a Different Host."
4-18
Key Points
Below are some definitions of the terms used in the SAN topology: A logical unit number, LUN, is a unique identifier used on a SCSI bus to distinguish between devices that share the same bus. Small Computer System Interface, or SCSI, is a set of standards allowing computers to communicate with attached devices, such as storage devices (disk drives, tape libraries etc) and printers. SCSI also refers to a parallel interconnect technology which implements the SCSI protocol. Internet SCSI, or iSCSI, is a protocol that enables transport of block data over IP networks, without the need for a specialized network infrastructure, such as Fibre Channel. It is a popular Storage Area Network (SAN) protocol.
4-19
A storage area network (SAN) is a specialized network that provides access to high performance and highly available storage subsystems using block storage protocols. The SAN is made up of specific devices, such as host bus adapters (HBAs) in the host servers, switches that help route storage traffic, and disk storage subsystems. The main characteristic of a SAN is that the storage subsystems are generally available to multiple hosts at the same time, which makes them scalable and flexible.
The diagram above shows the different ways to expose a disk to a Hyper-V parent partition (host) and child partition (guest): C: = Using a VHD file on a directly attached disk (X:) on the host D: = Using pass-through to a directly attached disk on the host E: = Using a VHD file on a SAN LUN mounted as a volume (Y:) on the host F: = Using pass-through to a SAN LUN exposed to the host G: = Using an iSCSI LUN exposed directly to the guest
For more information, see "More on Storage Options for Windows Server 2008 Hyper-V."
4-20
Key Points
Storage Manager for SANs is a Microsoft Management Console (MMC) snap-in that helps you create and manage logical unit numbers (LUNs) on Fibre Channel and Internet SCSI (iSCSI) disk drive subsystems that support Virtual Disk Service (VDS) in your storage area network (SAN). To prepare your system to enable SAN transfers of virtual machines, you must do the following: Install Virtual Disk Service (VDS) 1.1. Install the Microsoft iSCSI Software Initiator 2.02. Install a hardware provider on the VMM server. Configure the SAN computers.
4-21
Question: Do you have a SAN environment? How will you prepare your environment for SAN transfers?
4-22
Question: What type of SAN topologies currently exist, or are planned to be deployed within your organization? Question: What are the reasons for deploying (or not deploying) a SAN within your environment? Question: Why would you move a virtual machine to another host?
4-23
Key Points
With Hyper-V hosts, Virtual Machine Manager (VMM) 2008 supports Quick Migration, which can move a virtual machine between Hyper-V hosts with minimal downtime. This requires a Windows Server 2008 cluster and shared storage, but VMM helps ease the management and configuration. Question: What sort of benefits would a planned migration using Quick Migration provide your organization?
For more information, see "Manage Your Virtual Environments with VMM 2008."
4-24
Key Points
To help administrators make placement decisions, VMM uses a holistic approach to selecting appropriate hosts based on these factors: The workloads resource consumption characteristics Minimum CPU, disk, RAM, and network capacity requirements Performance data from virtual machine hosts
Question: What processor, memory, and other specifications will affect the customization of Host Ratings for the machines in your organization?
4-25
4-26
Note: After creating the RODC server, you will receive an error that VMM can't locate the boot or system volume. This is expected behavior because an operating system is not installed on the virtual machine. You can ignore the error.
Results: After this exercise, you should have two newly deployed virtual machines on your host.
4-27
5-1
Module 5
Converting from Physical or Virtual Platforms
Contents:
Lesson 1: Converting Physical Computers to Virtual Machines Lesson 2: Migrating Virtual Machines to Hyper-V Lab: Converting Virtual Machines Using VMM 5-3 5-14 5-22
5-2
Module Overview
This module describes converting physical and virtual computers to Hyper-V virtual machines, and centralizing their management all within System Center Virtual Machine Manager (VMM) server. Converting physical and virtual machines to a VMM server will help to provide a straight forward and cost-effective solution for unified management. You will be able to consolidate underutilized physical servers, and create new virtual machines with the help of physical-to-virtual (P2V) and virtual-to-virtual (V2V) wizards.
5-3
Lesson 1
Many organizations have physical servers that are underutilized. VMM provides a way to turn these physical servers into virtual Hyper-V virtual machines (VMs). Prior to converting a physical computer into a virtual machine (P2V), the computer must meet the certain requirements, and you must decide which physical computers to convert.
5-4
Key Points
VMM simplifies P2V by providing a wizard to automate much of the conversion process. 1. 2. 3. 4. 5 6. Install the VMM Agent. The VMM agent gathers information about hardware, software, services, hot fixes, and the volume (file system, volume type, and sectors). The VMM agent exports this information to the VMM database as a machine configuration file in XML format. In the Imaging phase, each physical volume becomes a separate virtual hard disk. In the Fix up phase, VMM prepares the virtual hard disks and prepares for virtual machine creation. VMM creates the virtual machine, and attaches virtual hard disks, network adapters, CD-ROM, and memory.
5-5
Here are some additional key points to the P2V process: P2V can be processed online and offline. Offline P2V conversion does not create snapshots. Offline P2V source computer boots into Microsoft Windows PE instead of the base operating system.
P2V conversion can be performed through a wizard in the administrator console, or through the command line. You can perform a P2V conversion from Windows PowerShell by using the New-P2V cmdlet. Question: To perform a P2V conversion, describe the two services that need to be running for the capture of an image and how they contribute to the overall process.
For more information, see "P2V: Converting Physical Computers to Virtual Machines in VMM."
5-6
Key Points
The requirements for physical computers depend on whether you are performing an online or offline P2V. VMM does not support P2V on source computers running Windows NT Server 4.0. However, you can use the Microsoft Virtual Server 2005 Migration Toolkit (VSMT) or third-party solutions for converting computers running Windows NT Server 4.0. Pay close attention to memory requirements of the Host Server that will be handling the creation of VMs and images. To increase or decrease the allotted virtual machine memory of the Host Server, you must perform the P2V from the command line.
5-7
Question: What will be the outcome of converting a Windows Server 2003 Service Pack 1 machine with 512 MB of memory to a virtual machine on a host with 512 MB memory?
For more information, see "P2V: Converting Physical Computers to Virtual Machines in VMM."
5-8
Key Points
To successfully perform a P2V conversion, you must know which computers you can convert and which computers you want to convert. Use the Virtualization Candidates report to identify the best candidates for P2V conversions. When identifying the best candidates for P2V conversion, consider converting these types of computers, in order of preference: Non business-critical underutilized computers. Computers with low utilization that are hosting less critical in-house applications. Computers with higher utilization that are hosting less critical applications.
5-9
Question: When deciding which candidate to convert for a P2V conversion, explain why a file server may be chosen over an application server with two critical applications only utilized 10% of time?
For more information, see "P2V: Converting Physical Computers to Virtual Machines in VMM."
5-10
Key Points
Performing the best practices below prior to the P2V conversions will result in a smoother conversion process. Survey the hardware configuration of the source computer. The update cache should contain all necessary drivers and system files to support the configuration. Bad sectors on a disk cannot be transferred during a P2V conversion. Run disk maintenance, and take corrective actions prior to P2V conversion. Use dynamic Virtual Hard Disks to conserve disk space. Use the most recent drivers from vendors for offline conversion.
5-11
Question: Describe a scenario when you would choose to perform an offline P2V conversion.
For more information, see "P2V: Converting Physical Computers to Virtual Machines in VMM."
5-12
Key Points
Steps to perform a P2V conversion. 1. 2. 3. 3. 4. 5. In the Virtual Machine Manager Administrator Console, Convert physical server by running the Convert Physical Server Wizard. Select a source by providing a computer name or IP address. Provide the administrator password. Provide the virtual machine identity. Gather System Information by scanning system. Review any issues that the wizard reports that must be resolved before the conversion can succeed. Each issue in the list explains how to resolve the issue. After resolving all issues, click Check Again to check for additional issues. Review the volumes to copy.
6.
5-13
7. 8. 9.
Configure the virtual machine, with number of processors and memory. Select the host on which you want to deploy this virtual machine. Set the path, networks, and additional properties.
Note: This process may or may not complete during the span of this lesson. At the end the day, contact your instructor to see the outcome of the demonstration.
For more information, see "P2V: Converting Physical Computers to Virtual Machines in VMM."
5-14
Lesson 2
In addition to converting underutilized physical computers, VMM supports the management and conversions of other virtual machines created from Virtual Server 2005 or VMWare. These VMs are converted to Hyper-V VMs, and managed under the VMM Administrator Console. This process is known as virtual-to-virtual conversion (V2V).
5-15
Key Points
System Center Virtual Machine Manager provides a single point of management and allows you to manage virtual machines that exist on both Virtual Server 2005 and VMWare servers. 1. Copy the Virtual Server 2005 or VMWare files to C:\ProgramData\Virtual Machine Library Files, which commonly is a hidden folder, and the default library share. Using the Virtual Machine Manager Console, create new Virtual machines with the Virtual Server 2005 file, or Convert the VMWare files using the Convert Virtual Machine wizard. Use the command line to perform the Virtual to Virtual (V2V) conversion. You can perform a V2V conversion from Windows PowerShell by using the New-V2V cmdlet.
2.
3.
5-16
Here are some additional key points to the V2V process: When moving or converting, the library contains files stored on library shares. Library shares contain operating systems, hardware, and template configurations, and are stored in the Virtual Machine Manager database. When considering transferring files to library shares, distributed library shares are an option, then transfers within the remote location could be localized, while continuing to manage the components centrally.
Question: What is a complication of having a single library share when dealing with remote locations?
For more information, see "V2V: Converting Virtual Machines in VMM." For more information, see "Managing the VMM Library." For more information, see "How to Convert Virtual Machines Using a Script."
5-17
Key Points
Certain capabilities and features of virtual machines are implemented differently in VMM. To take full advantage of the capabilities of VMM, you must update a few configurations and understand the differences. Undo and Differencing disks are not supported, and must be merged with VHD file prior to converting. There are network configuration files (.vnc) that are stored on a path specified in the host properties. VMM monitors jobs not alerts. When moving Virtual Server 2005 VMs to VMM with Hyper-V it is strongly recommended that you remove VM Additions before proceeding.
5-18
Question: Provide a scenario where checkpoints benefit the management of VMs in VMM with Hyper-V.
For more information, see "Moving from Virtual Server to Virtual Machine Manager." For more information, see "System Center Virtual Machine Manager 2007 screencast: Checkpoints."
5-19
Key Points
The following list of prerequisites must be met before beginning a V2V conversion of a VMWare virtual machine. The source virtual machine must contain one of the following operating systems: Microsoft Windows 2000 Server Service Pack 4 (SP4) The Windows Server 2003 operating systems with Service Pack 1 (SP1) The Windows Server 2003 R2 Standard Edition operating system The Windows Vista x64
5-20
Note: The Virtual Machine Library directory is under a hidden folder named C:\programdata\Virutal Machine Manager Library Files.
The VMM V2V Windows PowerShell cmdlet new-v2v supports monolithicSparse, monolithicFlat, twoGbMaxExtentSparse, and twoGbMaxExtentFlat hard disk formats.
Question: Does the V2V conversion process work with online .vmdk files?
For more information, see "V2V: Converting Virtual Machines in VMM." For more information, see "System Center Real Control with Virtual Machine Manager 2007."
5-21
Key Points
Use the Convert Virtual Machine Wizard after you have moved the VMWare VM files to the VMM library. The .vmx file and each .vmdk file for the VMWare VM must be in the VMWare library. The .vmdk files are converted into a Virtual Server disk (.vhd) that resides on the destination host.
Question: What are the benefits of using PowerShell for V2V conversions?
For more information, see "V2V: Converting Virtual Machines in VMM." For more information, see "VMM and PowerShell."
5-22
5-23
f Task 1: Copy the Virtual Server 2005 R2 VHD file to the Virtual
Machine Library
The WS2003NoVMAdd.vhd file is located in E:\Allfiles\Mod05\Labfiles\ to C:\ProgramData\Virtual machine Manager Library Files\VHDs. Refresh the library server 631-SEA-VMM-##.contoso.com. Verify that WS2003NoVMAdd.vhd is listed in the library.
f Task 2: Use the Virtual Server 2005 R2 VHD file to create a new VM in
VMM
In the Admin console, create a new virtual machine using, using the WS2003NoVMAdd.vhd file. Accept all defaults and place on the 6331 Virtual Network. Using Jobs view, verify completion.
5-24
f Task 1: Store the .vmx and .vmdk files in the VMM library
Minimize Virtual Machine Manager, and copy SEA-APP-01.vmdk and Windows Server 2003 Enterprise Edition.vmx files located in E:\Allfiles\Mod05\Labfiles\ to C:\ProgramData\Virtual machine Manager Library Files. Refresh the library server 631-SEA-VMM-##.contoso.com. Verify that SEA-APP-01 is listed in the library.
5-25
6-1
Module 6
Deploying Highly Available Virtual Machines
Contents:
Lesson 1: Introducing Virtual Machine High Availability Lesson 2: Deploying Host Clustering Lesson 3: Deploying Guest Clustering Lab: Planning for Highly Available Virtual Machines 6-3 6-10 6-16 6-22
6-2
Module Overview
Virtual Machine Manager (VMM) 2008 has added management support for Microsoft Windows Server 2008 Failover Clusters for Windows Server 2008 Hyper-V. VMM is cluster-aware when adding hosts, meaning you can discover what clusters are available through Active Directory. Additionally, you can easily create highly available virtual machines that run on a Windows Server 2008 cluster. This module will describe considerations for virtual machine high availability the procedures for deploying host clustering, and the procedures for deploying guest clustering.
6-3
Lesson 1
In this lesson, you will be introduced to virtual machine high availability. You will learn about the clustering types available for use with Hyper-V. You will see why high availability is useful and also examine configuring library shares for high availability. Knowing this prerequisite information will help you to successfully deploy highly available virtual machines.
6-4
Key Points
High availability can be defined as the implementation of a system design that ensures a high level of operational continuity over a given time. Planned downtime is the result of management-initiated events, such as maintenance. Unplanned downtime is the result of events not within direct control of IT administrators. Availability is often expressed numerically as the percentage of time that a service is available for use. Microsoft provides failover clustering in Windows Server 2008 Enterprise and Windows Server 2008 Datacenter, which keeps both applications and operating systems highly available.
6-5
Question: Describe a scenario in which virtual machine (VM) high availability might be implemented.
6-6
Key Points
A high-availability system is concerned with maximizing resource availability. A highly available resource is available a very high percentage of the time and may even approach 100% availability, but a small percentage of down time is acceptable and expected. A highly available resource is almost always operational and accessible to clients.
For more information, see "Windows Server 2008 Hyper-V Failover Clustering Options."
6-7
Key Points
You can combine the Windows Server 2008 server cluster feature with the Hyper-V role to create virtualized failover cluster environments for high availability. Hyper-V is supported in either a host cluster configuration or in a guest cluster configuration. With host clustering, physical machines are cluster nodes. With guest clustering, virtual machines are cluster nodes.
Question: Describe a scenario where you would use host clustering instead of guest clustering.
For more information, see "Hyper-V Part 5 - High Availability - Interview with PMs."
6-8
Key Points
The VMM library is a catalog of resources used to create and configure virtual machines in VMM. The library contains files stored on library shares, and it contains operating system, hardware, and template configurations stored in the VMM database. Library resources are added, created, used, and managed in library view. The highly available library servers and shares are managed like any other library servers and shares. Unlike with highly available host clusters, VMM does not detect when a new node is added or removed from the cluster; you must add or remove the node from SCVMM manually.
6-9
Question: What kinds of resources can be stored in the VMM Library? What about virtual machines?
6-10
Lesson 2
In this lesson, you will learn how to configure storage, networking and the operating system for host clustering. You will also learn the procedure for configuring host clustering. Knowing how to configure hardware devices effectively will help you to successfully deploy host clustering.
6-11
Key Points
The types of storage connections that failover clusters support are Serial Attached SCSI (SAS), iSCSI, and Fibre Channel. It is also possible to use a CIFS/SMB file server share as an option for Failover Clustering storage. You must however take steps to ensure that the file share is highly available.
Question: Does your company meet the hardware requirements for host clustering storage? If not, what would you need to do to get host clustering configured in your organization?
For more information, see "Quick Migration with Hyper-V Whitepaper." For more information, see "Storage Glossary."
6-12
Key Points
The network hardware, like other components in the failover cluster solution, must be compatible with Windows Server 2008. It is important to use Certified for Windows Server 2008 hardware. While it is not required, it is highly recommended using multiple network cards. If you have a single network card, you have a single point of failure. When creating a failover cluster solution, you should have redundancy to reduce the chance of failure. You can do this with multiple network cards.
Question: List one or more benefits of clustering two servers running Hyper-V.
For more information, see "Failover Cluster Step-by-Step Guide: Configuring a Two-Node File Server Failover Cluster."
6-13
Key Points
There is a change in the way the Cluster service runs in Windows Server 2008, as compared to Windows Server 2003. In Windows Server 2008, there is no Cluster service account. Instead, the Cluster service automatically runs in a special context that provides the specific permissions and privileges that are necessary for the service (similar to the local system context, but with reduced privileges. The DNS dynamic update protocol can be used. As a best practice all clustered servers should have the same role. The recommended role is Member server.
6-14
Key Points
The workflow for configuring Host Clustering is as follows: 1. 2. 3. 4. 5. Use Failover Cluster Management to configure the WS08 Server Core Virtual Machine as highly available. Bring the WS08 Server Core Virtual Machine online. Connect to the WS08 Server Core Virtual Machine. Use Failover Cluster Management to move the WS08 Server Core Virtual Machine to another cluster node. Verify that the Virtual Machine migration was successful.
6-15
Question: After configuring host clustering, provide additional scenarios where you would implement host clustering.
For more information, see "Configuring Host Clusters to Support Highly Available Virtual Machines."
6-16
Lesson 3
In this lesson, you will learn about deploying guest clustering. You be introduced to host server considerations for guest clustering. You will examine storage devices available for guest clustering. You will look at virtual machine considerations for guest clustering such as which operating system to use in the cluster, which services will be clustered and hardware considerations. You will learn the procedures for configuring guest clustering. Knowing these considerations and procedures, you will be able to successfully deploy guest clustering.
6-17
Key Points
When deploying guest clustering, it is important to consider the host server. Use highly available, redundant storage. Consider the type of clustering you will deploy. Remember that all nodes must use the same hardware.
Question: Discuss the important consideration of equal hardware for the host servers in guest clustering.
6-18
Key Points
For a Hyper-V guest cluster, iSCSI shared storage is required. At least one IDE disk must be available to the guest in order to boot up the system. The Microsoft iSCSI software initiator should be installed on each node.
For more information, see "Storage Options for Windows Server 2008 Hyper-V."
6-19
Key Points
There are a few things to consider when configuring virtual machines in guest clusters: It is important to consider an operating system designed for clustering such as Windows Server 2008 Enterprise Edition or Data Center Edition. In order to take advantage of clustering, it is important to consider the services you will be running in the cluster. Hardware configuration is important for intelligent placement of workloads to ensure performance.
Question: Discuss the importance of the services which will run in the cluster.
For more information, see "Configuring Host Clusters to Support Highly Available Virtual Machines."
6-20
Key Points
Configuring guest clustering on Windows Server 2008 is different than configuring guest clustering on Windows Server 2003. Avoid having single points of failure. Servers must be running Windows Server 2008. It is highly recommended that you validate your configuration.
Question: What is an alternative way to avoid having a single point of failure in your failover cluster network?
For more information, see "Failover Cluster Step-by-Step Guide: Configuring a Two-Node File Server Failover Cluster."
6-21
Key Points
To configure guest clustering: 1. 2. 3. 4. 5. Connect the cluster servers to the networks and storage. Validate the cluster configuration. Run the Create Cluster Wizard. Create a highly available shared folder. Test the highly available shared folder.
Question: Describe at least one way to make the solution in this demonstration truly highly available.
For more information, see "Failover Cluster Step-by-Step Guide: Configuring a Two-Node File Server Failover Cluster."
6-22
6-23
The VMs that you must provide high availability for are described in the table below:
VM Name SEA-SQL-01 Role SQL Server for internal and customer-facing database application Virtual Hardware Configuration 4 virtual processors 2 GB RAM SQL data storage on dedicated LUN in iSCSI SAN 2 Virtual NICs SEA-SQL-02 SQL Server for internal and customer-facing database application 4 virtual processors 2 GB RAM SQL data storage on dedicated LUN in iSCSI SAN 2 Virtual NICs SEA-DC-02 Domain Controller (secondary; primary Domain Controller is a physical server) Application server, uses SEA-SQL-01 for database storage Application server, uses SEA-SQL-02 for database storage 1 virtual processor 1 GB RAM 1 Virtual NIC 2 virtual processors 2 GB RAM 2 Virtual NICs 2 virtual processors 2 GB RAM 2 Virtual NICs 99.9% 99.9% 99% 99.9% Uptime Requirements 99.9%
SEA-APP-01
SEA-APP-02
6-24
(continued)
VM Name SEA-WEB-01 Role Customer-facing web farm member, uses SEA-SQL-01 and SEA-SQL-02 for database storage Customer-facing web farm member, uses SEA-SQL-01 and SEA-SQL-02 for database storage Customer-facing web farm member, uses SEA-SQL-01 and SEA-SQL-02 for database storage Virtual Hardware Configuration 2 virtual processors 2 GB RAM 2 Virtual NICs 2 virtual processors 2 GB RAM 2 Virtual NICs 2 virtual processors 2 GB RAM 2 Virtual NICs 99% 99% Uptime Requirements 99%
SEA-WEB-02
SEA-WEB-03
6-25
Results: After this exercise, you should have reviewed hardware options and platform and selected hardware for host clustering.
6-26
In this exercise, you will use a worksheet to select the guest clustering type. The main task for this exercise is to: 1. Select the Guest Clustering type.
6-27
Use the following worksheet to record a configuration that meets the development team's requirements:
Computer Name Clustering Configuration and VM Assignment
6-28
(continued)
Computer Name General Configuration Notes Clustering Configuration and VM Assignment
Results: After this exercise, you should have selected the Guest Clustering type.
7-1
Module 7
Managing Virtual Machine Checkpoints and Updates
Contents:
Lesson 1: Managing Virtual Machine Checkpoints Lesson 2: Managing Virtual Machine Updates Lab: Managing Virtual Machine Checkpoints and Updates 7-3 7-11 7-20
7-2
Module Overview
With Virtual Machine Manager 2008, it is easy to create and manage virtual machine checkpoints. Using Windows Server Update Services (WSUS) you can automate installation of updates on Hyper-V hosts and virtual machines. This module will describe considerations and procedures for successfully managing virtual machine checkpoints as well as considerations and procedures for successfully automating updates to your physical and virtual environments.
7-3
Lesson 1
The VMM Administrator Console is a graphical user interface (GUI) which serves as the primary point of administration for VMM. For example, with it you can manage virtual machine checkpoints. Knowing the prerequisites and procedures for managing virtual machine checkpoints will help you prepare to successfully restore virtual machine checkpoints when a virtual machine needs to be restored to a prior state.
7-4
Key Points
Snapshots are a new feature of Microsoft Windows Server 2008 Hyper-V. Snapshots do not affect the running state of the virtual machine. The snapshot files consist of the following: A copy of the VM configuration .xml file. Any save state files. A differencing disk (.avhd) which is the new working disk for all writes that are the child of the working disk prior to the snapshot.
7-5
Key Points
The process of creating a snapshot begins when the virtual machine is paused. The process of pausing and resuming the virtual machine happens so quickly that you do not know that the virtual machine was paused at all. Once the virtual machine is running again, it starts saving the contents of the virtual machine's memory to disk. While this is happening, memory activity inside the virtual machine is monitored and if the guest operating system attempts to modify memory that is not copied, the write attempt is intercepted and the original memory contents are copied and then the write is allowed to go through.
7-6
Key Points
A checkpoint can serve as temporary backup before updating an operating system on a virtual machine so that you can roll back if the update has any adverse effects. Do not use checkpoints for disaster recovery. Checkpoints do not create full duplicates of the hard disk contents nor do they copy data to a separate volume. You should use a backup application to back up and recover your data in case of catastrophic data loss.
7-7
Key Points
For checkpoints created when the virtual machine is running: The checkpoint contains the state of the hard disks and the data in memory. On the Checkpoints tab, the icon for the checkpoint has a small green triangle.
For checkpoints created when the virtual machine is stopped: The checkpoint contains the state of the hard disks only. On the Checkpoints tab, the icon for the checkpoint has a small red square.
Question: How many virtual machine checkpoints and branches does VMM support?
7-8
Key Points
To manage checkpoints for a virtual machine, click: New to create a new checkpoint that can be used to restore a virtual machine to its current state. Remove to delete a checkpoint to free disk space when the checkpoint is no longer needed. Restore to return a virtual machine to its state when a checkpoint was created. Properties to modify the description of a checkpoint.
Question: Describe at least two scenarios where you use virtual machine checkpoints.
7-9
To create a virtual machine checkpoint: In Virtual Machines view, expand All Hosts in the navigation pane, and click 6331-SEA-VMM-##. In the Details pane, click File Server, in the Actions pane, click New checkpoint. The New Checkpoint dialog box appears. In the Description field, type Initial checkpoint, and then click Create. Allow the job to complete. Double-click File Server. The Virtual Machine Properties for File Server dialog box appears. Click the Checkpoints tab. Verify the checkpoint creation. Click Cancel.
7-10
Question: Describe why Virtual Machine Checkpoints are not a valid backup solution.
7-11
Lesson 2
You can use Windows Server Update Services (WSUS) 3.0 to manage downloading software updates from Microsoft Update and distributing them to computers in your network. Knowing the prerequisites and procedures for managing software updates will help you prepare to successfully install automatic updates to physical and virtual machines within your environment.
7-12
Key Points
You can use Windows Server Update Services (WSUS) 3.0 to manage downloading software updates from Microsoft Update and distributing them to computers in your network. WSUS Server can be configured to download based on products and categories specified. Use targeting to deploy updates to specific computers or groups of computers. Use Automatic Update with WSUS to download and install specific updates applicable to the client computer.
For more information, see "Microsoft Windows Server Update Services 3.0 SP1 Operations Guide."
7-13
Key Points
Because computers can be assigned to multiple groups, it is possible for a single update to be approved more than once for the same computer. Updates will be deployed only once. Conflicts will be resolved by the WSUS server.
Question: Describe the difference between using WSUS to update virtual machines over physical machines.
For more information, see "Microsoft Windows Server Update Services 3.0 SP1 Operations Guide."
7-14
Key Points
The Offline Virtual Machine Servicing Tool works with VMM and with software update management systems: WSUS and System Center Configuration Manager (SCCM). The Offline Virtual Machine Servicing Tool (OVMST) can be used to update virtual machines that are left offline (stored in a non-operating state) for extended periods of time. These offline machines do not automatically receive operating system, antivirus, or application updates that would keep them compliant with current IT policy. The OVMST works by temporarily bringing a virtual machine online, applying the necessary updates, and then storing it again. You can also use this tool to update virtual machines that aren't connected to the internet, for example, computers that are only connected to an internet network.
7-15
For more information, see "Offline Virtual Machine Servicing Tool Executive Overview."
7-16
Key Points
The OVMST is straightforward to use. To use the tool: 1. Install the tool in your environment. A configuration wizard guides you through the process of connecting the tool to VMM and your software update management system. Configure virtual machine groups. You have the option to group your virtual machines to simplify the process of creating servicing jobs. Create and schedule servicing jobs. A servicing job specifies which virtual machines to update, what resources to use for the update process, and when to start the servicing job.
2. 3.
7-17
For more information, see "Utility Spotlight: Offline Virtual Machine Servicing Tool."
7-18
Deploying Updates
Key Points
The software update point (SUP) is a new site role in SCCM. A SUP is a server running WSUS services that has been designated in the Configuration Manager console to be a SUP. When a server is designated as a SUP, a SCCM component is installed on the SUP. This component is used to configure and manage the WSUS services. Because the software update distribution capabilities of WSUS are not used, each SUP can support an increased number of clients. Up to 25,000 clients supported per SUP on a standalone server. Up to 100,000 clients for a SUP on four servers configured as an NLB cluster.
7-19
The role of the SUP in SCCM is to facilitate the client scan process. Using SCCM and WSUS setting up update management involves the following steps: Enabling the client agent - The Software Updates Client Agent in SCCM is enabled by default and client agent components are installed on client computers with the other SCCM client components. The Software Updates Client Agent handles compliance assessment scan requests, software update evaluation requests, deployment policies for the client, and content download requests. The Software Updates Client Agent properties contain several sitewide client agent settings. Configuring the SUP. Configuring Updates for Distribution.
Question: Describe a scenario where you would benefit from using System Center Configuration Manager to deploy updates.
For more information, see "System Center: New Software Update Management Tools." For more information, see "About the Software Updates Client Agent." For more information, see "About the Software Update Point." For more information, see "How to Install Windows Server Update Services 3.0."
7-20
7-21
4. 5. 6. 7.
Installing Virtual Machine Guest Services. Creating a Pre-Restore Virtual Machine Checkpoint. Restoring a Virtual Machine Checkpoint. Verifying the Virtual Machine Checkpoint Restore.
Refresh the library server 631-SEA-VMM-##.contoso.com. Verify that en_win_srv_2003_r2_enterprise_cd1.iso is listed in the library.
7-22
Note: It is a best practice to create a checkpoint prior to performing a checkpoint restore procedure.
Results: After this exercise, you should have you should have successfully created virtual machine checkpoints. You will be able to verify successful restore of virtual machine checkpoint.
7-23
10. Forcing an Update of Host Group Policy Settings. 11. Assigning Client Computers to WSUS Groups. 12. Approving Virtual Machine WSUS Updates. 13. Updating Virtual Machine using WSUS. 14. Approving Hyper-V Host WSUS Updates. 15. Updating Hyper-V Host using WSUS.
7-24
7-25
Restart the Virtual Machine and log on to the Contoso## Domain using the following settings: User name: contoso##\administrator Password: Pa$$w0rd
7-26
7-27
8-1
Module 8
Implementing and Monitoring Reporting
Contents:
Lesson 1: Integrating System Center Operations Manager Lesson 2: Performance and Resource Optimization Lesson 3: Planning and Managing Hyper-V Lab: Configuring VMM and Operations Manager for Reporting 8-3 8-15 8-24 8-31
8-2
Module Overview
Microsoft provides a virtualization solution with management and reporting capabilities. These capabilities are realized through the integration of System Center Operations Manager (Operations Manager) and System Center Virtual Machine Manager (VMM). VMM provides a management solution for the virtualized data center that helps enable centralized management of IT infrastructure, increased server utilization, and dynamic resource optimization across multiple virtualization platforms. The newest version of VMM, Virtual Machine Manager 2008, supports Windows Server 2008 Hyper-V. By integrating Operations Manager with VMM, you can utilize the reporting capabilities in Operations Manager to create reports in VMM. In addition, VMM introduces Performance and Resource Optimization (PRO).
8-3
Lesson 1
System Center Operations Manager (Operations Manager) 2007 is a software solution to meet the need for end-to-end service monitoring in the enterprise IT environment. Operations Manager 2007 builds on previous versions of Microsoft's monitoring solutions by adding key features and functionality that customers and the market have been demanding. By integrating Operations Manager with VMM, you are able to view reports within the VMM administrator console.
8-4
Key Points
Microsoft enhanced the monitoring software by designing Operations Manager around three pillars: end-to-end service management, increased efficiency and control, and best-of-breed for Windows. End-to-end service management - In Operations Manager, Microsoft has introduced or improved features such as Distributed Application monitoring, Synthetic Transactions, Client monitoring, SDM-based system and health models, and Agentless Exception Monitoring to assist administrators with monitoring and managing end-to-end services. Best-of-breed for Windows - Improvements in Management Packs for Microsoft products have increased knowledge and reports based on the best practices of Microsoft IT and Product Support Services. Increased Efficiency and Control - Operations Manager has added features to increase the operational efficiency of the management and monitoring environment.
8-5
Question: Have you used previous Microsoft monitoring solutions, or any other monitoring solutions? Question: If you have used Microsoft monitoring solutions, what benefits and problems have you experienced with the solution?
For more information, see "Microsoft System Center Operations Manager 2007 Overview." For more information, see "About Operations Manager 2007."
8-6
Key Points
Operations Manager reports can be viewed directly in the System Center Virtual Machine Manager (VMM) 2008 console if these two products are integrated. In order to deliver integrated reporting, VMM uses the Operations Manager Connector Framework to connect to a Management Group. The scope of the reporting data available from that connection is limited to VM hosts within that Management Group. Therefore, if more than one Management Group contains a VM host, there are two options for delivering integrated reporting on those VM hosts: multiple VMM instances or dedicated management group for VMM. The first option is multiple VMM instances. In this scenario, multiple VMM servers will be deployed; each server is a VMM instance. With multiple VMM instances, there will be at least one VMM instance for each Operations Manager Management Group that contains VM hosts. There is a separate VMM instance for each Management Group that contains VM hosts. The VMM server in each VMM instance will be connected to the Root Management Server (RMS) in the Operations Manager Management Group.
8-7
The second option is to dedicate an Operations Manager Management Group to VMM and multi-home the Operations Manager agents that are on VM hosts. In this scenario, the organization will maintain the additional Management Group with its associated reporting database. The Operations Manager agent can be configured to multi-home so that it simultaneously sends event, alert, and performance data to more than one Management Group; therefore, a new Management Group will need to be defined that will be dedicated to integration with VMM. The Operations Manager agents that are running on VM hosts are then configured to multi-home so that they provide performance data to both their regular Management Group and to the Management Group that is connected to VMM. The Operations Manager product currently supports a maximum of 10 multi-homing agents in a Management Group.
Integrating VMM with Operations Manager enables users to seamlessly view Operations Manager reports in the VMM console. However, each VMM instance can display reporting data from only one Operations Manager Management Group. So if the VM hosts that are to be managed exist in more than one Management Group, you must chose whether to design additional VMM instances or to multi-home the Operations Manager agents that are on the VM hosts to an additional VMM-connected Management Group.
Question: In your organization, which of these options would you use? Question: Why would you use this solution instead of the other option?
For more information, see "Infrastructure Planning and Design: Microsoft System Center Virtual Machine Manager 2008."
8-8
Setting up Reporting
Key Points
To set up reporting with Operations Manager for VMM, there are several steps you need to follow: 1. 2. The first step is to deploy Operations Manager 2007 and Operations Manager Reporting. You also need to set up your reporting server. Use the Configure Operations Manager option of the VMM Setup wizard to configure Operations Manager to work with VMM.
Note: The Setup wizard requires some prerequisite management packs: SQL Server Management Pack and Windows Server Internet Information Services 2000 and 2003.
3.
Deploy the System Center Virtual Machine manager 2008 Reporting Management Pack for Operations Manager 2007 - This management pack can be downloaded from the System Center Operations Manager 2007 Online Catalog.
8-9
4.
Add VMM administrators to the Report Operator role in Operations Manager Unless VMM administrators have the Report Operator role, they cant see and open reports in VMM. Enable reporting in VMM - Once you enable reporting, the Reporting view is added to the VMM Administrator console.
5.
For more information, see "Setting up Reporting in VMM." For more information, see "Configuring Operations Manager Integration with VMM 2008."
8-10
Key Points
One of the VMM reports is the Virtualization Candidates reports. This report helps indentify physical computers that are good candidates for conversion to VMs. You can use the Virtualization Candidates report to identify little-used servers and display average values for a set of commonly requested performance counters for CPU, memory, and disk usage, along with hardware configurations, including processor speed, number of processors and total RAM.
Question: What would be the benefits of converting a physical computer to a virtual machine?
8-11
Key Points
Another report available for VMM is the Virtual Machine Allocation report. This report provides information that you can use to calculate chargeback to cost centers for VMs. This information can be used to evaluate whether workloads should be moved, allowing you to keep the optimum performance on your servers. If an administrator runs the Virtual Machine Allocation report and performance issues are presented, the administrator can use this information to make changes to the environment to provide a consistent end-user experience. The administrator can move workloads, or virtual machines, from one host to another to optimize performance.
8-12
Question: In what ways can the Virtual Machine Allocation report save administrator time?
8-13
Key Points
In this demonstration, you will see how to run the Configure Operations Manager wizard to integrate Operations Manager and VMM. 1. 2. 3. 4. View installed Management Packs in the Open System Center Operations Manager 2007 Console. Stop the Virtual Machine Manager service. Open Windows Explorer and browse to E:\Mod8\Labfiles\SCVMMRC0. Double-click setup.exe.
8-14
5. 6.
Start the Configure Operations Manager wizard to uninstall the Virtual Machine Manager Administrator console. Restart the Configure Operations Manager wizard. Accept all defaults, except on the Port Assignment page, in the VMM server field, type contoso##\6331-SEA-VMM-##.
8-15
Lesson 2
A new feature with VMM is Performance Resource Optimization (PRO). PRO can dynamically respond to failure scenarios or poorly configured components that are identified in hardware, operating systems, or applications. PROs capabilities are also available to VMware ESX or Virtual Server hosts, thus allowing administrators to manage their entire virtualized environment regardless of the virtualization platform they are using.
8-16
Key Points
Performance and Resource Optimization (PRO) helps administrators ensure that VM hosts and their VM guests are operating in the most efficient possible manner. When an event occurs that triggers a policy, PRO can be configured to present the issues to the administrator along with recommended resolutions. PRO can also be configured to automatically implement the preconfigured corrective actions. Because PRO is a part of VMM 2008, it can extend these automated management capabilities to both Microsoft and VMware hosts. When managing VMware hosts, PRO can take full advantage of VMwares VMotion capability to move VMs between hosts with no downtime. When managing Microsoft hosts, PRO is able to use Quick Migration to rapidly move VMs between hosts.
8-17
For more information, see "About Performance and Resource Optimization (PRO)."
8-18
Key Points
To activate PRO, you must deploy Operations Manager, which provides the performance and health monitors that are leveraged to recommend and implement PRO tips. 1. You need to run the Configure Operations Manager wizard from the VMM setup which: Installs PRO management packs. Installs a VMM Administrator Console on the Operations Manager root management server. Configures the required accounts and groups to enable communication between the two applications.
After activating PRO, the following are steps you need to take to configure VMM for PRO:
8-19
2.
Add the Action Account for Operations Manager to the VMM Administrator user role. You can determine the Action Account in the Administration view of Operations Manager. This account is listed under User Roles. In Administration view of the VMM console, specify the Operations Manager root management server. Enable PRO: Enable PRO for individual host clusters. In the host group properties, enter options on the PRO tab. Enable PRO for individual host groups. In the host cluster properties, enter options on the PRO tab. Enable PRO tips for system wide monitors. In Administration view, enter PRO Settings in the General node.
3. 4.
If you would like to exclude a virtual machine from host-level PRO actions, select the Exclude virtual machine from PRO host-level actions option in the virtual machine.
Question: Would you choose to enable PRO for clusters or for system wide monitors in your organization?
For more information, see "Enabling PRO in VMM 2008." For more information, see "Configuring Operations Manager Integration with VMM 2008."
8-20
Key Points
PRO Tips are integrated into the VMM console. PRO tips can recommend or automatically implement actions, such as VM migration or VM right sizing, based on policies implemented through Operations Manager. PRO can notify administrators when predefined operational boundaries are exceeded, and can then automatically take corrective actions. If PRO has been set up to use manual corrective actions, a Tip detailing a reported problem and suggesting corrective actions will display in the VMM console. The administrator can then implement the corrective actions by clicking a button in the VMM console. Use the PRO Tips window in VMM to monitor and implement PRO tips for host clusters that are managed by VMM. In this window, only active PRO tips are displayed; after an issue is resolved, the PRO tip is removed.
8-21
Question: Would you want VMM to automatically take actions based on the PRO tips recommendation, or would you choose to manually approve the actions?
For more information, see "How to Monitor and Implement PRO Tips."
8-22
Key Points
In this demonstration, you will see how to enable PRO, and how to monitor PRO tips. Enable PRO 1. 2. 3. 4. In the Administration view, click General. In the Details pane, double-click PRO Settings. Select Enabled PRO tips. Click OK.
8-23
Monitor and Implement PRO tips 1. 2. On the VMM toolbar, click PRO tips. Take any of the following actions on a PRO tip: To view details about a PRO tip, select the PRO tip. The Summary tab displays a description of the issue and provides knowledge for resolving the issue. To implement a PRO tip, select the PRO tip and click Implement. To remove a PRO tip from the display without taking any action, select the PRO tip and click Ignore.
For more information, see "How to Monitor and Implement PRO Tips."
8-24
Lesson 3
Utilizing reports available in Operations Manager for VMM, allows administrators to plan and manage Hyper-V. In addition, the Microsoft Assessment and Planning Toolkit (MAP) provides planning tools for implementing Hyper-V.
8-25
Key Points
The Microsoft Assessment and Planning Toolkit (MAP) makes it easy for you to assess your current IT infrastructure and determine the right Microsoft technologies for your IT needs. MAP is an inventory, assessment, and reporting tool that can securely run in small or large IT environments without requiring the installation of agent software on any computers or devices. MAP performs three key functions; hardware inventory, compatibility analysis, and readiness reporting. Hardware Inventory - MAP provides secure, agent-less and network-wide inventory that scales from small business to large enterprises. It collects and organizes system resources and device information from a single networked computer without requiring users to deploy software agents on all computers. MAP uses technologies already available in your IT environment to perform inventory and assessments. Compatibility Analysis -Once a sufficient performance metric sample has been gathered, you will configure a model virtual host server and identify candidates to place on this type of host server using the Server Virtualization and Consolidation wizard.
8-26
Readiness Reporting -MAP generates reports containing both summary and detailed assessment results for each migration scenario. The results are provided in both Microsoft Excel and Microsoft Word documents. Once the Server Consolidation and Virtualization wizard is complete, it provides detailed reports and proposals describing which servers can be virtualized and on which virtual server host computers the consolidation process can be carried out.
Case Study: Sporton Lab Sporton International is a mobile communications certification company in Taiwan. Sporton had an overcrowded data center, incurring rising electricity and cooling costs for underutilized servers. Using manual provisioning and administration processes, IT employees were unable to respond quickly to requests from Sporton's developers for test environments. All that changed when Sporton deployed a virtualization solution with the Microsoft Windows Server 2008 Hyper-V technology. Sporton virtualized servers in the production environment, increasing performance and reliability while saving 70 percent in server costs and improving server utilization up to 60 percent. IT staff use Hyper-V to provision servers in minutes and perform quick migration of virtual machines for robust business continuityenhancements that are turning Sportons IT department into a business enabler instead of a cost center. In November 2007, the Systex team evaluated server workload using the Microsoft Assessment and Planning Solution Accelerator tool, called MAP, to begin the virtualization assessment and migration project for Sporton. Team members used the tool to collect the performance metrics of every server in the data center to identify which servers were capable of running Hyper-V. The MAP tool decreased the planning time for this project by 60 percent, says Feng. Question: In what ways can MAP be used in your organization to improve your virtualization environment?
For more information, see "Microsoft Assessment and Planning Toolkit Solution Accelerator." For more information, see "Case Study: Sporton Lab."
8-27
Key Points
Discuss the questions in a classroom discussion, led by your instructor, and determine the answers.
8-28
Key Points
Once an organization has implemented Hyper-V and VMM, ongoing monitoring is necessary to ensure optimal performance. The Virtual Machine Utilization report available in VMM with Operations Manager provides information about resource utilization by VMs. For a specified time period, this report shows average usage and total or maximum values for VM processors, memory, and disk space. You can use this report to identify underutilized or over-utilized VMs and determine whether any changes are necessary. Question: Describe a scenario where you use the Virtual Machine Utilization report to manage your virtual environment.
8-29
Key Points
The Host Utilization report shows the number of VMs running on each host and the average usage and total or maximum values for host processors, memory and disk space. For the specified time period and host group, this report shows the number of VMs running on each host and the average usage and total or maximum values for host processors, memory and disk space. You can doubleclick a host in the list to open a Host Performance report with details about resource usage on the host. Question: Describe a scenario where you use the Host Server Utilization report to manage your virtual environment.
8-30
Key Points
You can use the Host Utilization Growth report to plan for future growth. The Host Utilization Growth report shows the percentage of change in resource usage and the number of VMs running on selected hosts during a specified time period. Question: List some changes you could make to your virtual environment to plan for future growth.
8-31
8-32
5. 6. 7. 8.
Deploy Virtual Machine Manager 2008 Reporting Management Pack. Add VMM Administrator to Report Operator Role. Enable Reporting in VMM. Reopen Virtual Machine Manager Console.
8-33
Note: The wizard will first uninstall the existing installation of the Virtual Machine Manager administrator console, and then you will need to restart the Configure Operations Manager installation.
On the Virtual Machine Manager Administrator Console Setup wizard appears. Click I accept the terms of this agreement. Click Next four times. On the Port Assignment page, in the VMM server field, type contoso##\6331-SEA-VMM-##. Finish the rest of the wizard.
8-34
8-35
Note: This is the same account used for VMM, so this account should already be listed. Why is this not ideal in real-world environment?
8-36
8-37
In the left pane, click Reporting. In the Reports pane, double-click Virtualization Candidates. In the Computer Group list, click All Computers. Click View Report.
Results: After this exercise, you should have generated and viewed the Virtualization Candidates report for All Computers.
9-1
Module 9
Monitoring and Troubleshooting Jobs
Contents:
Lesson 1: Monitoring Jobs Lesson 2: Troubleshooting and Repairing Jobs Lab: Troubleshooting Jobs 9-3 9-12 9-22
9-2
Module Overview
Virtual Machine Manager (VMM) provides a comprehensive solution to managing your virtual environment. Effectively managing your environment includes quickly identifying failures and correcting them to minimize or eliminate downtime. VMM provides a central place for monitoring actions taken in VMM with Jobs. Jobs are viewed directly in the VMM administrator console. Each failed job has troubleshooting tips to help you resolve failures. By integrating jobs with the VMM console, you have a single place to monitor your virtual environment.
9-3
Lesson 1
Monitoring Jobs
Jobs are displayed for each action performed in VMM. There are several places to view jobs in the VMM administrator console. You have the ability to sort, filter and group jobs to easily find jobs that meet specific criteria.
9-4
Introducing Jobs
Key Points
A job is created whenever you perform any action that changes the status of a managed object in Virtual Machine Manager (VMM). These units of work are tracked in Jobs view. Jobs are composed of steps that are performed sequentially to complete an action. For many simple jobs, such as stopping a virtual machine, the job contains only one step. For more complex jobs, such as running a physical-to-virtual machine conversion on a server, the resulting job is actually a job group comprising several other jobs, which themselves contain numerous steps. The Details tab in the job details in Jobs view shows the status of each step in a job.
9-5
A wizard might create multiple jobs. For example, the Add Hosts wizard can be used to add multiple hosts to be managed by VMM. For each host added in this way, a separate job is created and can be tracked individually. Each job is independent. A job cannot depend on the status of another job. Therefore, if you are using Add Hosts to add multiple hosts, the failure to add one host does not affect the remaining jobs. Certain jobs require credentials to complete successfully. For example, the job created by the Add Hosts wizard uses those credentials on the virtual machine host to install the Virtual Machine Manager agent.
Question: What are some troubleshooting tools you currently use for applications in your organization? Question: In what ways could using Jobs in VMM save you troubleshooting time?
9-6
Key Points
There are three places to monitor jobs: the Jobs view, Jobs window and the Latest Job tab. Jobs View The Jobs view is accessible through the left navigation pane. Jobs view displays a complete listing of VMM jobs that you can search, sort, filter, and group. You can view detailed status for a job and an audit of changes that the job makes to objects in VMM. By default, the Results pane in Jobs view displays jobs from the most recent to the oldest, so recently requested jobs are displayed prominently. In the Jobs view, select the job that you want to view in the Results pane. Click the Details tab in the Details pane to view the status of each step in the job. The steps are displayed hierarchically. Progress and status are displayed for each step. The step progress and the overall job progress are updated automatically as the job progresses.
9-7
Jobs Window The Jobs window opens by default when a wizard closes. You can open the Jobs window at any time by clicking Jobs on the VMM toolbar. By opening the Jobs window, you can monitor your own current jobs while you work in any view. This can be useful for monitoring jobs that run a long time, such as converting a physical server. The Jobs window displays your own jobs from the current VMM session from most recent to oldest. You can click any column header to sort by that property. You can click the Progress tab in the Details pane to view the status of each step in the job. The step progress and the overall job progress are updated automatically as the job progresses.
Latest Job tab To help you diagnose issues with virtual machines and library resources, in Virtual Machines view and Library view, the Latest Job tab in the Details pane displays summary information for the most recent job that was performed on the selected object.
Question: Where would you look if you wanted to view the last job performed on a virtual machine?
9-8
Filter Jobs
Key Points
You can limit the objects displayed in the VMM Administrator Console Results pane based on properties of the objects. Different filters are available in each view. When you move to a different view, the filters for the current view remain selected until you change the selection of filters, clear all filters, or exit the console. In Jobs view, you can display filters for Status, Owner, and Start date. Under status, the options are running, failed, canceled and completed. If you wanted to monitor the jobs created by a certain VMM administrator, you would select the Owner filter and show only the jobs created by that administrator. If you wanted to view all completed jobs since yesterday, you could select Completed under Status, and also select yesterday's start date.
9-9
For more information, see "How to Filter Objects in the Results Pane."
9-10
Change Tracking
Key Points
When a job completes, an audit record is saved that lists the changes that the job made to the VMM object. You can view the audit record in Jobs view by displaying the Change Tracking tab in the Details pane. The Change Tracking tab can be useful if you want to view the changes made to a virtual machine. For example, you want to use a virtual machine but you notice a job performed on that virtual machine. Before using the virtual machine, you can view the Change Tracking tab to see what changes were made to ensure the virtual machine will still perform correctly.
Question: In what situations would you want to view the Change Tracking tab instead of the Latest Job tab?
9-11
Key Points
In this demonstration, you will see the different places to view jobs, and how to sort and filter jobs. 1. 2. 3. 4. 5. 6. Open the Virtual Machine Manager administrator console. In the left pane, click Jobs. In the Jobs view, sort and filter jobs. On the VMM toolbar, click Jobs to view the Jobs window. In the left pane, click Virtual Machines. Select a Virtual Machine, and then in the lower pane, click the Latest Job tab.
9-12
Lesson 2
In addition to viewing jobs, in the VMM administrator console you can perform actions on the jobs. You have the option to cancel or restart a job. Jobs that have failed have an associated error message and recommended action to assist in troubleshooting tasks. Once you have resolved the error, you can attempt to restart the job. You can also restart most jobs that have been canceled.
9-13
Cancel a Job
Key Points
In Jobs view or in the Jobs window, you can cancel a job that is running. An example of when you would want to cancel a long-running job is when you have attempted to migrate a virtual machine between hosts and the process has been taking a long time to complete. You need to access the virtual machine so you need to stop the migration. Question: List another situation where you would want to cancel a job.
9-14
Restart a Job
Key Points
You can restart most jobs that fail or are canceled. For jobs that can put a virtual machine into a Failed state, only the most recent job of that type for the virtual machine can be restarted. For jobs that run for a long time, such as virtual machine migration, intermediate results are stored periodically while the job is running, and the Restart action attempts to resume the job from the last known state. For certain jobs, such as starting a virtual machine, no intermediate results are created, and the job starts from the beginning.
Question: Describe a scenario where you would start a task that resulted in a failed job from the beginning instead of restarting the job.
9-15
Key Points
You can use jobs to view detailed information about a failed virtual machine and 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 its state before the job ran. You have three options for repairing a virtual machine: Click Retry to restart the job that caused the virtual machine to fail. Click Undo to return the virtual machine to its previous state before the job that caused it to fail. Click Ignore to refresh the metadata for the virtual machine and update its status if you fixed the issue that caused the virtual machine to fail outside Virtual Machine Manager. For example, you might have copied a missing virtual hard disk file to the appropriate folder.
9-16
Repairing a missing differencing disk that has been deleted outside VMM will permanently delete the parent virtual hard disk. If you want to save the parent virtual hard disk, you must make a copy of the disk before you repair the virtual machine. Question: Describe a situation in which you would use each of the Repair Virtual Machine options.
9-17
Key Points
For even greater automation and control, VMM is fully scriptable using Windows PowerShell. With this tool, IT administrators can run remote scripted services against many virtual machines, thus avoiding labor-intensive manual processes. The Summary page of each wizard contains a View Script button that displays the Windows PowerShell cmdlets that the wizard will use to create and configure the new object based on your specifications. You can copy the cmdlets to use in creating Windows PowerShell scripts. The script is the actual script that VMM will run when it completes the wizard. You can save the scripts directly to the Library. It is easy to parameterize the scripts to make them flexible. If you store your Windows PowerShell scripts in the VMM library, you can view, edit, or run the scripting in Library view. Scripts are automatically pulled into the VMM library. Scripts can be executed directly from the Library. One administrator can create powerful scripts that others can use. Scripts are stored in a centralized location. Delegation model provides control on who has access.
9-18
Commands and Cmdlets Windows PowerShell and VMM each provide commands (called cmdlets) that you can use separately to perform simple administrative tasks, or together with other cmdlets or command-line elements, to perform complex tasks. The VMM command shell includes all of the standard Windows PowerShell cmdlets and also provides a comprehensive set of cmdlets that are designed specifically for use with VMM. You can use these cmdlets to manage all functions in a VMM environment, including the following tasks: Adding and working with virtual machine hosts and host groups. Adding the VMM library and maintaining the resources that it stores. Creating and working with virtual machines that are deployed on a host or stored in the library. Managing the virtual machine environment. Creating virtual machine checkpoints. Backing up the VMM database. Administering the virtual machine self-service feature.
Before running scripts in PowerShell, you need to ensure the execution policy is set to a sufficient level to allow the script to run. The table below summarizes the different execution policy settings.
Execution Policy Restricted Allsigned Description Permits interactive commands only (no scripts) Permits scripts but requires a digital signature from a trusted publisher on all scripts and configuration files Permits scripts but requires a digital signature from a trusted publisher on all scripts and configuration files that are downloaded from the Internet Permits scripts, including unsigned scripts
Remotesigned
Unsigned
9-19
Question: Do you have experience working with PowerShell? Question: List some advantages of using PowerShell to manage VMM.
For more information, see "About Windows PowerShell for Virtual Machine Manager." For more information, see "Managing Objects in Virtual Machine Manager." For more information, see "Using the VMM Cmdlets." For more information, see "Running Scripts." For more information, see "Appendix A: About Windows PowerShell for Virtual Machine Manager." For more information, see "Getting Started with PowerShell Scripting for VMM."
9-20
Key Points
There are three PowerShell cmdlets you can use to manage VMM jobs. Get-Job - Gets VMM job objects on the VMM server. Stop-Job - Stops one or more VMM jobs that are running and returns the object for each job in a stopped state. If the VMM job is not currently running, this cmdlet has no effect.
Restart-Job - Restarts one or more VMM jobs that have failed or that have been canceled by a user. Jobs that are currently running must be canceled before they can be restarted. All restarted jobs start from the last known good checkpoint before a failure or a cancellation (some jobs have only a single checkpoint). Restarting a job displays the object properties of the job to the user and shows the Status property as Running.
9-21
Question: In what situations would it be helpful to use PowerShell to manage jobs instead of the VMM Administrator Console?
For more information, see "Using the Virtual Machine Manager Command Shell." For more information, "Sample Job-Related Scripts."
9-22
9-23
f Task 3: Use get-job cmdlet to list all completed jobs in a text file
Type get-vmmserver Get-VMMServer -ComputerName "6331-SEA-VMM##.Contoso##.com". Type Get-Job | where { $_.Status -eq "Completed" } | out-file c:\completedjobs.txt.
9-24
9-25
Note: If the Execution Policy is already set to unrestricted skip task 5 and continue with task 6.
Note: There will be errors that appear. These errors are there by design, so you can ignore them.
Results: After this exercise, you should have successfully modified and ran the generatejobs.ps1 script.
9-26
f Task 3: Filter jobs to view running jobs f Task 4: Cancel long-running jobs
Cancel the Move virtual machine from 6331-SEA-VMM-## to 6331-SEAVMM-## job.
9-27
9-28
9-29
Note: A new job will be created when restarting the failed job.
Read through the Error and Recommended Action sections to determine the steps needed to restart the job.
Note: This virtual machine was created using the 6331_\Module9_Template template.
Note: VMM will display another Failed job for this task. Read over the error message for the failed job.
9-30
9-31
Course Evaluation
Your evaluation of this course will help Microsoft understand the quality of your learning experience. Please work with your training provider to access the course evaluation form. Microsoft will keep your answers to this survey private and confidential and will use your responses to improve your future learning experience. Your open and honest feedback is valuable and appreciated.
L1-1
2. 3. 4. 5. 6.
7. 8. 9.
10. On the Prerequisites Check page, ensure that the prerequisites check is successful, and then click Next. 11. On the Installation Settings page, click Next.
L1-2
12. On the SQL Server Settings page, configure the following settings: Use an existing SQL Server 2005: selected Server name: 6331-SEA-VMM-## Use the credentials below: checked User name and domain: contoso##\administrator Password: Pa$$w0rd Select or enter a SQL instance: MSSQLSERVER Select or enter a database: VMM Create a new database: checked
13. Click Next. 14. On the Library Share Settings page, click Next. 15. On the Port Assignments page, configure the following settings: VMM server connection: Choose a port for this setting and use it for the rest of this lab. Agent connections: Choose a port for this setting and use it for the rest of this lab. File transfers: Choose a port for this setting and use it for the rest of this lab.
16. Click Next. 17. On the Summary of Settings page, click Install. 18. Allow the installation to complete, and then click Close.
Results: After this exercise, you should have successfully installed the VMM Server component.
L1-3
3. 4. 5. 6. 7. 8.
Results: After this exercise, you should have successfully installed the VMM Administrator Console. You should be able to start the VMM Administrator Console and connect to the VMM Server.
L1-4
Exercise 3: Installing the VMM Self-Service Portal and Configuring a DNS Record
You will install the VMM Self-Service Portal on your Hyper-V server. You will also configure a DNS record.
3. 4. 5.
Click Next. On the Summary of Settings page, click Install. Allow the installation to complete, and then click Close.
L1-5
4. 5.
Click Start, and then click Server Manager. The Server Manager window appears. In the console tree, expand Roles | DNS Server | DNS | 6331-SEA-VMM-## | Forward Lookup Zones | contoso##.com. Right-click contoso##.com and then click New Host (A or AAAA). In the Name field, type selfservice. In the IP Address field, type your computers IP address as recorded in step 4 of this task. Click Add Host.
6. 7. 8. 9.
10. The DNS dialog box appears. 11. Click OK, and then click Done. 12. Close Server Manager.
Results: After this exercise, you should have successfully installed the VMM SelfService Portal and successfully configured the selfservice.contoso##.com DNS A record. You should be able to successfully browse to http://selfservice.contoso##.com.
L2-7
2. 3. 4. 5. 6.
L2-8
7. 8. 9.
On the Host Servers page, click Search. The Computer Search dialog box appears, click Search. In Search results, click 6331-SEA-VMM-##.contoso.com, and then click Add.
10. Click OK, and then click Next. 11. A Virtual Machine Manager dialog box appears. Click Yes. 12. On the Configuration Settings page, in the Add the selected hosts to following host group list, click All Hosts, and then click Next. 13. On the Host Properties page, accept defaults, and click Next. 14. On the Summary page, click Add Hosts. 15. A Jobs window appears. Monitor the status to completion. 16. Once complete, close the Jobs window.
L2-9
3. 4.
Slide CPU utilization marker to the highest increment of importance. Slide Network utilization marker to the middle increment, and then click OK.
Results: After this exercise, your VMM server should be listed as a host in the VMM Administrator Console. A virtual network has been created for guest networking named 6331 Virtual Network, and Intelligent Placement Settings have been set for CPU at the highest priority and Network Utilization at mid range of importance.
L2-10
10. Click the Hardware Settings tab, and then top tool bar click SCSI Adapter. 11. In left pane, click Availability, and then in details pane click Make this VM highly available, and then click OK.
Task 2: Create VMs with blank hard disk using hardware profiles
1. 2. Click Virtual Machine view, in the Actions pane, click New virtual machine. The New Virtual Machine wizard appears. On the Select Source page, click Create the new virtual machine with a blank virtual hard disk and then click Next. On the Virtual Machine Identity page, in the Virtual machine name field type File Server, and then click Next. On the Configure Hardware page, in the Hardware profile list, click FileServer. Click Next. On the Select Destination page, verify that Place the virtual machine on a host is selected and then click Next.
3. 4. 5. 6.
L2-11
7. 8.
On the Select Virtual Machine Host page, click Customize Ratings. The Customize Ratings dialog box appears. Slide all resource option markers to the second highest increment of Very Important, and then click OK and then click Next. On the Select Path page, accept defaults, and then click Next.
9.
10. On the Select Networks page, in Virtual Network list, click Internal Network - 6331 Virtual Network, and then click Next. 11. On the Additional Properties page, accept the defaults, and then click Next. 12. On the Summary page, click Create. 13. A Jobs window appears. Close the window. 14. Click Virtual Machine view, in the Actions pane, click New virtual machine. 15. The New Virtual Machine wizard appears. On the Select Source page, click Create the new virtual machine with a blank virtual hard disk and then click Next. 16. On the Virtual Machine Identity page, in the Virtual machine name field type SCSI, and then click Next. 17. On the Configure Hardware page, in the Hardware profile list, click SCSI High Availability, and then click Next. 18. On the Select Destination page, click Store the virtual machine in the library, and then click Next. 19. On the Select Library Server page, accept defaults, and then click Next. 20. On the Select Path page, click Browse 21. The Select Destination Folder dialog box appears. Expand MSSCVMMLibrary, click VHDs, and then click OK, and then click Next. 22. On the Summary page, click Create. 23. A Jobs window appears. Close the window.
L2-12
Results: After this exercise, you should have two hardware profiles located in the library under profiles. Two virtual machines have been created, one is stopped and located on the host; the other is located in the library. When checking on the jobs you should see one running and one complete. In some instance you will not be able to see the running of a job depending on the speed of the server, and you will just notice the completion.
L2-13
L2-14
10. The Select a Template dialog box appears. Click Blank Template Large, and then click OK. 11. Select Set quota for deployed virtual machines. 12. Verify Maximum quota points allowed is set to 1, and then click Next. 13. On Library Settings page, click Allow users to store virtual machines in a library. 14. For Library Path field, click Browse. 15. The Select Destination Folder dialog box appears. Expand SCVMMLibrary, click VHDs, and then click OK, and then click Next. 16. On the Summary page, click Create.
4. 5. 6. 7. 8. 9.
10. Log on as Contoso##\Aconner, Password: Pa$$w0rd. 11. Close the Server Manager window. 12. On the desktop, double-click SCVMM Admin Console. 13. The Connect to Server dialog box appears.
L2-15
14. Click Connect. 15. Click Administration view, click User Roles. 16. In the Actions pane, click New user role. 17. The Create User Role wizard appears. On General page, in User role name field type Developers Self Service Full. 18. In the User role profile list, verify that Self Service User is selected, and then click Next. 19. On the Add Members page, click Add. 20. The Select User or Groups dialog box appears, type Jan Blank, and then click Check names, and then click OK, and then click Next. 21. On the Object Scope page, select All Hosts, and then click Next. 22. On the Virtual Machine Permission page, click All actions, and then click Next. 23. On Virtual Machine Creation Settings page, click Allow users to create new virtual machines, and then click Add. 24. The Select a Template dialog box appears. Click Blank Template Large, and then click OK. 25. Select Set quota for deployed virtual machines. 26. Click up arrow twice for Maximum quota points allowed, and verify quota is set to 2, and then click Next. 27. On Library Settings page, click Allow users to store virtual machines in a library. 28. For Library Path field, click Browse. 29. The Select Destination Folder dialog box appears. Expand SCVMMLibrary, click VHDs, and then click OK, and then click Next. 30. On the Summary page, click Create. 31. Close Virtual Machine Manager Console. 32. On the Start menu, click Run type http://selfservice.contoso##.com, and then click OK. 33. The Virtual Machine Manger Self-Service Portal window appears. In the user name field, type contoso##\Jblank. In Password field type Pa$$w0rd, and then click Log On.
L2-16
34. The Microsoft System Center Virtual Machine Manager page appears, click New Computer. 35. The New VM Windows Internet Explorer windows appears. Verify quota point available is (2). 36. Click Cancel. 37. Close the Virtual Machine Manager Self-Service window. 38. Click Start, click right arrow, and then click Log Off. 39. Log on as Contoso##\Administrator, Password: Pa$$w0rd. 40. Close the Server Manager window. 41. On the desktop, double-click SCVMM Admin Console. 42. Click Administration view, click User Roles. 43. Verify that Administrator, IT Admin Support, Self Service Full, Developers Self Service, user roles are in details pane. 44. Close the Virtual Machine Manager Console.
Results: After this exercise, the users should have been able to log into the portal and seen that they have the ability to create the appropriate number of VM set by the quota. Logging back in as the Administrator you should see all user roles, IT Admin Support, Self Service Full, and Developers Self Service. These can be viewed in Administration view, User Roles results pane.
L3-17
2. 3. 4. 5. 6. 7. 8. 9.
Task 2: Edit the Properties of the Developers Self Service Full User Role
1. 2. 3. In the Administration view, click User Roles. In the User Roles pane, right-click Developers Self Service Full, and then click Properties. The User Role Properties for Developers Self Service Full (Self-Service User) dialog box appears.
L3-18
4. 5.
Click the Scope tab, and then clear the All Hosts check box. Select the Self Service check box.
6.
Click OK.
Task 3: Edit the Properties of the Self Service Full User Role
1. 2. 3. 4. 5. 6. In the Administration view, click User Roles. In the User Roles pane, right-click Self Service Full, and then click Properties. The User Role Properties for Self Service Full (Self-Service User) dialog box appears. Click the Scope tab, and then clear the All Hosts check box. Select the Self Service check box. Click OK.
4. 5. 6. 7. 8.
L3-19
9.
In the OS Product Key field, the product key provided by the instructor.
10. Click Create. 11. The Windows Internet Explorer dialog box appears. Click OK. 12. Minimize the Virtual Machine Manager Self-Service window. 13. Restore the Virtual Machine Manager console.
L3-20
L3-21
L3-22
10. In the Virtualization platform list, click Microsoft Hyper-V. 11. In the Owner field, type Contoso##\jblank, and then click OK.
10. Select Share image file instead of copying it. 11. Click OK. 12. Close the Virtual Machine Manager console.
L4-23
2. 3. 4. 5. 6. 7.
8. 9.
10. The Select Destination page appears. Make sure Place the virtual machine on a host is selected, and then click Next. 11. The Select Host page appears. Click Next. 12. The Select Path page appears. Click Next. 13. The Select Networks page appears. In the Virtual Network list, click Internal Network 6331 Virtual Network, and then click Next. 14. The Additional Properties page appears. Under Automatic start action, in the Action when physical server starts list, click Never automatically turn on the virtual machine.
L4-24
15. Under Operating system, in the Specify the operating system you will install in the virtual machine, click Windows Server 2008 Enterprise 32-Bit. 16. Click Next. 17. The Summary page appears. Click Create.
10. Click Next. 11. The Guest Operating System page appears. In the left pane, under General Settings, click Admin Password. 12. In the Password and Confirm fields, type Pa$$w0rd. 13. In the left pane, under General Settings, click Operating System. 14. In the Operating system list, click 64-bit edition of Windows Server 2008 Enterprise. 15. In the left pane, under Networking, click Domain / Workgroup. 16. Click Domain. 17. In the Domain field, type Contoso##.com. 18. In the Domain user field, type Contoso##\Administrator.
L4-25
19. In the Password and Confirm fields, type Pa$$w0rd. 20. In the left pane, under Scripts, click Answer File. 21. Click Next. 22. The Summary page appears. Click Create.
10. Click Next. 11. The Select Destination page appears. Make sure Place the virtual machine on a host is selected, and then click Next. 12. The Select Host page appears. Click Next. 13. The Select Path page appears. Click Next. 14. The Select Networks page appears. In the Virtual Network list, click Internal Network 6331 Virtual Network, and then click Next. 15. The Additional Properties page appears. Under Automatic start action, in the Action when physical server starts list, click Never automatically turn on the virtual machine. 16. Click Next. 17. The Summary page appears. Click Create.
L4-26
Note: After creating the RODC server, you will receive an error that VMM can't locate the boot or system volume. This is expected behavior because an operating system is not installed on the virtual machine. You can ignore the error.
L4-27
10. Once you have reviewed the documentation, close Internet Explorer. 11. Click Customize Ratings. 12. The Customize Ratings dialog box appears. 13. Under Placement goal, click Resource maximization. 14. Maximize the slider for CPU usage, Memory free, Disk I/O, and Network utilization. 15. Click the VM Load tab. 16. Under CPU, change Expected utilization (%), to 50. 17. Under Disk, change Required physical disk space (GB), to 20. 18. Click OK. 19. Examine the new Rating. 20. Click Cancel, and then click Yes.
L5-29
2.
Note: C:\Programdata\Virtual Machine Manager Library Files is a hidden directory and can be accessed but not seen. The method below is used, so you do not have to show all hidden files.
3. 4. 5. 6. 7. 8. 9.
Click Start, in Search box type E:\Allfiles\Mod05\Labfiles\, and then press ENTER. Right-click WS03NoVMAdd.vhd, and then click Copy. Click Start, in Search box type C:\Programdata\Virtual Machine Manager Library Files\VHDs, and then press ENTER. Right-click on empty space, and then click Paste. Close the C:\ProgramData\Virtual Machine Library Files\VHDs window. Close the E:\Allfiles\Mod05\Labfiles window. On the desktop, double-click SCVMM Admin Console.
10. In Library view, click 6331-SEA-VMM-##.contoso.com, and then in Actions pane, under Library Server, click Refresh library server. 11. Verify the WS03NoVMAdd.vhd is listed in the Details pane.
L5-30
Task 2: Use the Virtual Server 2005 R2 VHD file to create a new VM in VMM
1. 2. 3. 4. 5. 6. 7. 8. 9. In the Actions pane, click New virtual machine. The New Virtual Machine wizard appears. On the Select Source page, click Browse. The Select Library Resources dialog box appears. Click WS03NoVMAdd, and then click OK, and then click Next. On the Virtual Machine Identity page in the Virtual machine name field, type WS2003, and then click Next. On the Configure Hardware page, accept defaults, and then click Next. On the Select Destination page, accept defaults, and then click Next. On the Select Virtual Machine Host page, accept defaults, and then click Next. On the Select Path page, accept defaults, and then click Next. On the Select Network page, in Virtual Network list, select Internal Network - 6331 Virtual Network, and then click Next.
10. On the Additional Properties page, accept defaults, and then click Next. 11. On the Summary page, review configuration, and then click Create. 12. The Jobs window appears. Verify the completion of creation of VM, in the Details pane.
L5-31
7. 8. 9.
In the Actions pane, under Virtual Machine, click Start. Verify that WS2003 starts in Details view, and at log on screen. In the Actions pane, under Virtual Machine, click Stop.
10. A Virtual Machine Manager dialog box appears. Click Yes. 11. Verify that WS2003 in the Details pane, WS2003 has a status of Stopped.
Results: After this exercise, you will have a Hyper-V VM managed by VMM, created from a Virtual Server 2005 R2 .vhd file. You have the ability to start, stop, and save the state successfully, showing that the VM can be managed by VMM Administrator Console.
L5-32
Note: C:\Programdata\Virtual Machine Manager Library Files is a hidden directory and can be accessed but not seen. The method below is used, so you do not have to show all hidden files.
2. 3. 4. 5. 6. 7. 8. 9.
Click Start, in Search box type E:\Allfiles\Mod05\Labfiles\, and then press ENTER. Copy Windows Server 2003 Enterprise Edition.vmx and SEA-APP-01.vmdk. Click Start, in Search box type C:\Programdata\Virtual Machine Manager Library Files, and then press ENTER. Right-click on empty space, and then click Paste. Close the C:\ProgramData\Virtual Machine Library Files window. Close the E:\Allfiles\Mod05\Labfiles window. Restore Virtual Machine Manager. In Library view, click 6331-SEA-VMM-##.contoso.com, and then in Actions pane, under Library Server, click Refresh library server.
L5-33
6. 7. 8. 9.
On the Virtual Machine Configuration page, accept defaults, and then click Next. On the Select Virtual Machine Host page, accept defaults, and then click Next. On the Select Path page, accept defaults, and then click Next. On the Select Network page, in Virtual Network list, select Internal Network -6331 Virtual Network, and then click Next.
10. On the Additional Properties page, accept defaults, and then click Next. 11. On the Summary page, review configuration, and then click Create. 12. The Jobs window appears. Verify the completion of virtual to virtual conversion.
L5-34
10. A Virtual Machine Manager dialog box appears. Click Yes. 11. Verify that SEA-APP-01 has a status of Stopped. 12. Close the Virtual Machine Manager window.
Results: After this exercise, you will have converted a VMWare VM using the .vmdk and .vmx files to a Hyper-V VM managed by VMM. You have the ability to start, stop, and save the state successfully, showing that the VM can be managed by VMM Administrator Console.
L6-35
The VMs that you must provide high availability for are described in the table below:
VM Name SEA-SQL-01 Role SQL Server for internal and customer-facing database application Virtual Hardware Configuration 4 virtual processors 2 GB RAM SQL data storage on dedicated LUN in iSCSI SAN 2 Virtual NICs SEA-SQL-02 SQL Server for internal and customer-facing database application 4 virtual processors 2 GB RAM SQL data storage on dedicated LUN in iSCSI SAN 2 Virtual NICs SEA-DC-02 Domain Controller 1 virtual processor (secondary; primary 1 GB RAM Domain Controller is 1 Virtual NIC a physical server) 99% 99.9% Uptime Requirements 99.9%
L6-36
(continued)
VM Name SEA-APP-01 Role Application server, uses SEA-SQL-01 for database storage Application server, uses SEA-SQL-02 for database storage Customer-facing web farm member, uses SEA-SQL-01 and SEA-SQL-02 for database storage Customer-facing web farm member, uses SEA-SQL-01 and SEA-SQL-02 for database storage Customer-facing web farm member, uses SEA-SQL-01 and SEA-SQL-02 for database storage Virtual Hardware Configuration 2 virtual processors 2 GB RAM 2 Virtual NICs 2 virtual processors 2 GB RAM 2 Virtual NICs 2 virtual processors 2 GB RAM 2 Virtual NICs 99% 99.9% Uptime Requirements 99.9%
SEA-APP-02
SEA-WEB-01
SEA-WEB-02
99%
SEA-WEB-03
99%
L6-37
Example Answer Rationale The example answer design provisions two clusters to support the VMs in this environment. The VMs that require the highest level of availability are located on SEA-CLU-01 nodes. The VMs that require a lower level of availability are located on SEA-CLU-02 nodes. Note that because the cluster must survive the failure of a single node, each node must be able to run all the VMs assigned to that node. Because of this, each node is provisioned with enough memory and processor capacity to host all of the VMs assigned to that cluster. A ratio of 1 physical processor to 1 virtual processor has been used.
L6-38
Note that SEA-CLU-01-N1 and SEA-CLU-01-N2 have been configured with a large number of NIC ports. A ratio of 1 physical NIC port to 1 virtual NIC has been used. In addition, at least one NIC port is reserved for use by the host operating system. This decision is intended to support NIC teaming. NIC teaming is implemented in this cluster to support the higher uptime requirements of the VMs on this cluster node. In addition, the physical computers in this cluster should use other technologies designed to support high uptime. For example, redundant power supplies should be used on these computers. Also note that in this design, the VMs which host the customer-facing web farm are located on the same Hyper-V host as VMs which are intended for internal-only use. This design choice implies that a firewall will be used to secure the internal-only VMs. Because Hyper-V supports VLAN tagging, this technology may also be used to secure access to the internal-only VMs.
L6-39
The development team for Contoso must replicate the production environment described in Exercise 1 of this lab. They must also replicate the clustering configuration of the production environment, but they must do this using fewer, less powerful computers. The following considerations apply to the development team: The SQL databases they use for development are significantly smaller than those used in production. They are not testing application speed. They have no uptime requirements to meet. However, they must simulate the effect of cluster failovers on the application that runs on SEA-APP-01, SEA-APP02, and the web server farm. They have two servers available for their test configuration. The servers have the following hardware: 1 Quad-core processor 4 NIC ports 8 GB of RAM
L6-40
Use the worksheet below to record a configuration that meets the development team's requirements:
Computer Name SEA-TES-N1 Clustering Configuration and VM Assignment VMs hosted:
SEA-SQL-01
SEA-TES-N2 VMs hosted:
General Configuration Notes
SEA-SQL-01 and SEA-SQL-02 are configured as a host cluster. To test the effect of a failover, SEA-TES-N1 is failed. Because the application VMs that use these databases are hosted on SEA-TESN2 , the development team is able to observe the effect of the database failover on these applications. To support the larger number of VMs hosted on SEA-TES-N2, 4 GB of RAM may be removed from SEA-TES-N1 and installed on SEA-TES-N2 if the hardware design of SEA-TES-N2 supports this. In the development environment, each VM will be configured with a smaller RAM and processor allocation. Because maximum VM performance is not required, the host server resources may be more heavily used in this scenario. During other development scenarios where the effect of database failover is not being tested, VMs may be divided more equally between the two host servers.
L7-41
2. 3. 4. 5. 6. 7.
L7-42
7. 8. 9.
Close the Virtual Machine Library Files window. Close the Mod07 window. Restore the Virtual Machine Manager 6331-SEA-VMM-##.contoso##.com window.
10. In Library view, click 6331-SEA-VMM-##.contoso##.com, and then in Actions pane, under Library Server, click Refresh. 11. Verify the en_win_srv_2003_r2_enterprise_cd_1.iso file is listed in the Details pane.
L7-43
9.
10. The Display Settings notification appears, click the notification balloon. 11. The Display Settings dialog box appears, click Yes. 12. The Monitor Settings dialog box appears, click Yes. 13. Minimize the Virtual Machine Viewer WS2003 on server 6331-SEA-VMM##.contoso##.com window.
Note: It is a best practice to create a checkpoint prior to performing a checkpoint restore procedure.
L7-44
Note: Notice the mouse cursor, the virtual machine guest services are no longer installed due to the restore operation.
3. 4. 5. 6. 7. 8. 9.
In the toolbar, press CTRL+ALT+DEL. The Log On to Windows dialog box appears, in the Password field, type Pa$$w0rd and click OK. The Files Needed dialog box appears, click Cancel. Click Start, click Shut Down. The Shut Down Windows dialog box appears. In the What do you want the computer to do? list, click Shut Down. In the Option: list, click Operating System: Reconfiguration (Planned). Click OK.
10. Allow the WS2003 VM to shut down. 11. Press CTRL+ALT+Left Arrow to release the mouse cursor. 12. Close the Virtual Machine Viewer WS2003 on server 6331-SEA-VMM##.contoso##.com window.
L7-45
L7-46
L7-47
11. The Display Settings notification appears, click the notification balloon. 12. The Display Settings dialog box appears, click Yes. 13. The Monitor Settings dialog box appears, click Yes.
10. Click OK and then click Close. 11. Close the Network Connections window. 12. Click Start and then Shut Down. 13. The Shut Down Windows dialog box appears. In the What do you want the computer to do? list, click Restart. 14. In the Option: list, click Operating System: Reconfiguration (Planned). 15. Click OK. 16. Allow the WS2003 VM to restart.
L7-48
10. In the Password field, type Pa$$w0rd and then click OK four times. 11. The System Settings Change dialog box appears. Click Yes. 12. Allow the WS2003 VM to restart.
Task 7: Configuring Virtual Machine WSUS Client Settings using Group Policy
1. 2. 3. 4. 5. 6. 7. 8. The Log On to Windows dialog box appears, in the Password field, type Pa$$w0rd. In the Log on to: list, click CONTOSO##, and then click OK. The Manage Your Server window opens. Select Dont display this page at logon. Close the window. Click Start | Run, the Run dialog box appears. In the Open field, type gpedit.msc and then click OK. The Group Policy Object Editor window opens. In the navigation pane, expand Computer Configuration | Administrative Templates | Windows Components and click Windows Update.
L7-49
9.
10. The Configure Automatic Updates Properties dialog box appears. 11. Select Enabled. In the Configure automatic updating: list, click 2 Notify for download and notify for install. 12. Click Next Setting. 13. The Specify intranet Microsoft update service location Properties dialog box appears, select Enabled. 14. In the Set the intranet update service for detecting updates: field, type http://6331-SEA-VMM-##. 15. In the Set intranet statistics server: field, type http://6331-SEA-VMM-##, and click Next Setting. 16. The Enable client-side targeting Properties dialog box appears. 17. Select Enabled, in the Target group name for this computer field, type VM. 18. Click OK. Close the Group Policy Object Editor window.
L7-50
Task 9: Configuring Hyper-V Host WSUS client settings using Group Policy
1. 2. 3. 4. 5. 6. 7. 8. 9. Click Start | Run, the Run dialog box appears. In the Open field, type gpedit.msc and then click OK. The Group Policy Object Editor window opens. In the navigation pane, expand Computer Configuration | Administrative Templates | Windows Components and click Windows Update. In the Details pane, double-click Configure Automatic Updates. The Configure Automatic Updates Properties dialog box appears. Select Enabled. In the Configure automatic updating: list, click 2 Notify for download and notify for install. Click Next Setting. The Specify intranet Microsoft update service location Properties dialog box appears, select Enabled.
10. In the Set the intranet update service for detecting updates: field, type http://6331-SEA-VMM-##. 11. In the Set intranet statistics server: field, type http://6331-SEA-VMM-##, and click OK. 12. In the Details pane, double-click Enable client-side targeting. 13. The Enable client-side targeting Properties dialog box appears. 14. Select Enabled, in the Target group name for this computer field, type Host. 15. Click OK. Close the Group Policy Object Editor window.
L7-51
L7-52
10. The Shut Down Windows dialog box appears, in the What do you want the computer to do? list, click Restart. 11. In the Option: list, click Operating System: Reconfiguration (Planned). 12. Click OK. 13. Allow the WS2003 VM to restart.
Note: It may take a few minutes for the Automatic Update notification icon to appear.
3. 4. 5. 6. 7. 8. 9.
In the notification area, click the Automatic Update notification icon. The Automatic Updates dialog box appears. Click Download. Verify the notification icon disappears. Click Start, click Shut Down. The Shut Down Windows dialog box appears. In the What do you want the computer to do? list, click Shut Down. In the Option: list, click Operating System: Reconfiguration (Planned). Click OK. Allow the WS2003 VM to shut down.
10. Close the Virtual Machine Viewer 6331-SEA-VMM-##.contoso##.com window. 11. Close the Virtual Machine Manager 6331-SEA-VMM-##.contoso##.com window.
L7-53
10. The Shut Down Windows dialog box appears, in the Option: list, click Operating System: Reconfiguration (Planned). 11. Click OK. 12. Allow the 6331-SEA-VMM-## host to restart.
Note: It may take a few minutes for the Automatic Update notification icon to appear.
3. 4.
In the notification area, click the Automatic Update notification icon. The Automatic Updates dialog box appears. Click Download. Verify the notification icon disappears.
L8-55
6. 7. 8.
9.
10. The Select Management Packs to Import dialog box appears. Browse to E:\Allfiles\Mod08\Labfiles\Management Packs\Windows Server Internet Information Services 2000 and 2003. 11. Perform the steps to add all the management packs in this folder. 12. On the Import Management Packs dialog box, click Import. 13. When you receive the following message All Management Packs successfully imported, click Close. 14. Close System Center Operations Manager 2007.
L8-56
10. Click Next. 11. On the Customer Experience Improvement Program page, click Next. 12. On the Prerequisites Check page, click Next. 13. On the Installation Location page, click Next. 14. On the Port Assignment page, in the VMM server field, type contoso##\6331-SEA-VMM-##. 15. Click Next.
L8-57
16. On the Summary of Settings page, click Install. 17. On the Installation page, clear Check for the latest Virtual Machine Manager update, and then click Close. 18. On the System Center Virtual Machine Manager 2008 splash screen click Exit.
6. 7. 8.
L8-58
L8-59
L8-60
L8-61
1. 2. 3. 4. 5. 6.
In the left pane, click Reporting. Under Reporting, click Reports. In the Reports pane, double-click Virtualization Candidates. The Virtualization Candidates window opens. In the Computer Group list, click All Computers. Click View Report. Close the Virtualization Candidates window.
L9-63
Task 3: Use get-job cmdlet to list all completed jobs in a text file
1. 2. Type get-vmmserver Get-VMMServer -ComputerName "6331-SEA-VMM##.Contoso##.com", and then press ENTER. Type Get-Job | where { $_.Status -eq "Completed" } | out-file c:\completedjobs.txt, and then press ENTER.
L9-64
Note: If the Execution Policy is already set to unrestricted skip task 5 and continue with task 6.
L9-65
Note: There will be errors that appear. These errors are there by design, so you can ignore them.
2.
L9-66
L9-67
10. Ensure Back up the Virtual Machine Manager database job is listed at the top of the details pane with a Completed status.
L9-68
3.
Note: This virtual machine was created using the 6331_Module9_Template template.
10. The Virtual Machine Manager dialog box appears. Click Yes.
Note: VMM will display another Failed job for this task. Read over the error message for the failed job.
L9-69
3.