40,79 €
Mehr erfahren.
- Herausgeber: Packt Publishing
- Kategorie: Wissenschaft und neue Technologien
- Sprache: Englisch
Maximize your administration skills effectively and efficiently
Key Features
- Implement cost-effective virtualization solutions for your organization with actionable recipes
- Explore the concepts of VMM with real-world use cases
- Use the latest features with VMM 2016 such as Cluster OS Rolling Upgrade, Guarded Fabric and Storage Spaces Direct
Book Description
Virtual Machine Manager (VMM) 2016 is part of the System Center suite to configure and manage datacenters and offers a unified management experience on-premises and Azure cloud.
This book will be your best companion for day-to-day virtualization needs within your organization, as it takes you through a series of recipes to simplify and plan a highly scalable and available virtual infrastructure. You will learn the deployment tips, techniques, and solutions designed to show users how to improve VMM 2016 in a real-world scenario. The chapters are divided in a way that will allow you to implement the VMM 2016 and additional solutions required to effectively manage and monitor your fabrics and clouds. We will cover the most important new features in VMM 2016 across networking, storage, and compute, including brand new Guarded Fabric, Shielded VMs and Storage Spaces Direct. The recipes in the book provide step-by-step instructions giving you the simplest way to dive into VMM fabric concepts, private cloud, and integration with external solutions such as VMware, Operations Manager, and the Windows Azure Pack.
By the end of this book, you will be armed with the knowledge you require to start designing and implementing virtual infrastructures in VMM 2016.
What you will learn
- Plan and design a VMM architecture for real-world deployment
- Configure fabric resources, including compute, networking, and storage
- Create and manage Storage Spaces Direct clusters in VMM
- Configure Guarded Fabric with Shielded VMs
- Create and deploy virtual machine templates and multi-tier services
- Manage Hyper-V and VMware environments from VMM
- Enhance monitoring and management capabilities
- Upgrade to VMM 2016 from previous versions
Who this book is for
If you are a solutions architect, technical consultant, administrator, or any other virtualization enthusiast who needs to use Microsoft System Center Virtual Machine Manager in a real-world environment, then this is the book for you.
Roman Levchenko: Roman Levchenko is a systems architect, VMware vExpert, and a Microsoft MVP. With over 15 publications, 11 certifications and 10 years of experience, Roman has also been associated with various successful projects through out his career for which he was honored and awarded many times. He believes in decoding the complexity of information technology, so that it is easily accessible and understood by everybody. Edvaldo Alessandro Cardoso: Edvaldo Alessandro Cardoso is a former Microsoft MVP, international speaker, author, evangelist, and a subject matter expert in cloud, virtualization, management, and identity, working for Microsoft as a secure infrastructure architect for Asia Pacific, Greater China, India, and Japan. He has more than 27 years of experience in the IT industry working with LBDMs, building trust, demonstrating business value, solving complex business problems, and transforming business strategy into technology utilizing existing and innovative technologies. He is a reviewer on this book.Sie lesen das E-Book in den Legimi-Apps auf:
Seitenzahl: 526
Veröffentlichungsjahr: 2018
Ähnliche
System Center 2016 Virtual Machine Manager Cookbook Third Edition
Copyright © 2018 Packt Publishing
All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews.
Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the authors, nor Packt Publishing or its dealers and distributors, will be held liable for any damages caused or alleged to have been caused directly or indirectly by this book.
Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information.
Commissioning Editor: Kartikey PandeyAcquisition Editor:Heramb BhavsarContent Development Editor:Devika BattikeTechnical Editor:Manish ShanbhagCopy Editor:Safis Editing, Dipti MankameProject Coordinator:Judie JoseProofreader: Safis EditingIndexer:Rekha NairGraphics:Tom ScariaProduction Coordinator: Nilesh Mohite
First published: March 2013 Second edition: June 2014Third edition: February 2018
Production reference: 1190218
Published by Packt Publishing Ltd. Livery Place 35 Livery Street Birmingham B3 2PB, UK.
ISBN 978-1-78588-148-0
www.packtpub.com
Mapt is an online digital library that gives you full access to over 5,000 books and videos, as well as industry leading tools to help you plan your personal development and advance your career. For more information, please visit our website.
Why subscribe?
Spend less time learning and more time coding with practical eBooks and Videos from over 4,000 industry professionals
Improve your learning with Skill Plans built especially for you
Get a free eBook or video every month
Mapt is fully searchable
Copy and paste, print, and bookmark content
PacktPub.com
Did you know that Packt offers eBook versions of every book published, with PDF and ePub files available? You can upgrade to the eBook version at www.PacktPub.com and as a print book customer, you are entitled to a discount on the eBook copy. Get in touch with us at [email protected] for more details.
At www.PacktPub.com, you can also read a collection of free technical articles, sign up for a range of free newsletters, and receive exclusive discounts and offers on Packt books and eBooks.
Contributors
About the authors
Roman Levchenko is a Microsoft MVP, VMware vExpert, and systems architect working for a leading international IT integrator. He focuses mainly on Microsoft technologies, including Windows Server, System Center, PowerShell, and Azure. Furthermore, he is certified as Microsoft MCSE, MCSA, MCS, MCITP, and VMware VCP6-DCV. As a technical reviewer, he has also participated in the making of some recent and well-known books by Manning. He runs his own blog, and you can follow him on Twitter at @rlevchenko to keep in touch and receive the latest news.
Edvaldo Alessandro Cardoso is a former Microsoft MVP, international speaker, author, evangelist, and a subject matter expert in cloud, virtualization, management, and identity, working for Microsoft as a secure infrastructure architect for Asia Pacific, Greater China, India, and Japan.
He has more than 27 years of experience in the IT industry working with LBDMs, building trust, demonstrating business value, solving complex business problems, and transforming business strategy into technology utilizing existing and innovative technologies. He is a reviewer on this book.
About the reviewer
Tomica Kaniski is a Microsoft MVP for Cloud and Datacenter Management (since 2010). He is fully engaged with (but not limited to) Microsoft products and technologies. In his spare time, he plays the bass guitar and also likes to read and travel. He currently works in the telecommunications industry for VIPnet d.o.o. in Croatia (A1 Telekom Austria Group/América Móvil company).
Packt is searching for authors like you
If you're interested in becoming an author for Packt, please visit authors.packtpub.com and apply today. We have worked with thousands of developers and tech professionals, just like you, to help them share their insight with the global tech community. You can make a general application, apply for a specific hot topic that we are recruiting an author for, or submit your own idea.
Table of Contents
Title Page
Copyright and Credits
System Center 2016 Virtual Machine Manager Cookbook Third Edition
Packt Upsell
Why subscribe?
PacktPub.com
Contributors
About the authors
About the reviewer
Packt is searching for authors like you
Preface
Who this book is for
What this book covers
To get the most out of this book
Download the color images
Conventions used
Get in touch
Reviews
VMM 2016 Architecture
Introduction
Knowing your current environment – assessment
Designing the solution
Creating the private cloud fabric
Understanding each component for a real-world implementation
Getting ready
How to do it...
How it works...
There's more...
Windows Azure Pack
Service Provider Foundation
Service Reporting
Domain controllers
Windows Server Update Service – WSUS
System Center App Controller
Microsoft Azure Stack
System Center components scenarios
Planning for high availability
Getting ready
How to do it...
How it works...
There's more...
SQL Server
VMM library
Designing the VMM server, database, and console implementation
Getting ready
How to do it...
How it works...
There's more...
Storage providers – SMI-S and SMP
Bare metal
Configuring security
Run As accounts in VMM
Communications poand protocols for firewall configuration
VM storage placement
Management cluster
Small environment
Lab environments
Medium and enterprise environments
Private cloud sample infrastructure
Hosting environments
New networking features in VMM 2016
New storage features in VMM 2016
See also
Specifying the correct system requirements for a real-world scenario
Getting ready
How to do it...
How it works...
Hardware requirements
Software requirements
See also
Licensing the System Center
Getting ready
How to do it...
How it works...
Troubleshooting VMM and supporting technologies
Getting ready
How to do it...
How it works...
There's more...
Verifying WMI providers
Troubleshooting tools
Background Intelligent Transfer Service (BITS) troubleshooting
Data collection tools
See also
Upgrading from Previous Versions
Introduction
Reviewing the upgrade options
How to do it...
In-place upgrade from VMM 2008 R2 SP1 to VMM 2012
Upgrading VMM on a different computer
Upgrading from VMM 2012 to VMM 2012 SP1
Upgrading from VMM 2012 SP1 to VMM 2012 R2
Upgrading from VMM 2012 R2 to VMM 2016
More planning considerations
How it works...
There's more...
See also
Checking the VMM system requirements and preparing for the upgrade
Getting ready
How to do it...
Uninstalling previous versions of Windows Automated Installation Kit (WAIK)
Checking whether Windows Remote Management (WinRM) is started
How it works...
There's more...
Upgrading to VMM 2016
Getting ready
How to do it...
Upgrading to VMM 2012 SP1 or to VMM 2012 R2
Upgrading VMM 2012 R2 to VMM 2016
How it works...
There's more...
Upgrading VMM with configured AlwaysOn Availability Groups
Upgrading a highly available VMM 2012 R2 to VMM 2016
Upgrading a VMM console
Upgrading the VMM Self-Service Portal
Uninstalling the VMM Self-Service Portal
Upgrading the App Controller
See also
Re-associating hosts after upgrading
How to do it...
How it works...
There's more...
See also
Updating the VMM agents
How to do it...
How it works...
See also
Performing other post-upgrade tasks
How to do it...
How it works...
There's more...
Re-adding PXE servers
Updating driver packages
Relocating the VMM library
See also
Installing VMM 2016
Introduction
Creating service accounts
Getting ready
How to do it...
How it works...
There's more...
Deploying a Microsoft SQL Server for VMM implementation
Getting ready
How to do it...
How it works...
There's more...
How to easily get the SQL configuration file
Installing a SQL failover cluster using the configuration file
Configuring SQL Server with AlwaysOn AGs
See also
Installing VMM dependencies
Getting ready
How to do it...
How it works...
There's more...
SQL Server Connectivity Feature Pack components
The Telnet client
See also
Configuring Distributed Key Management
Getting ready
How to do it...
How it works...
See also
Installing a VMM management server
Getting ready
How to do it...
How it works...
There's more...
Installing VMM 2016 on Server Core
See also
Installing the VMM console
Getting ready
How to do it...
How it works...
Connecting to a VMM management server by using the VMM console
How to do it...
How it works...
See also
Creating a Run As account credentials in VMM
How to do it...
How it works...
There's more...
Disabling a Run As account
Enabling a disabled Run As account
Deleting a Run As account
Configuring ports and protocols on the host firewall for each VMM component
Getting ready
How to do it...
See also
Installing a Highly Available VMM Server
Introduction
Installing a highly available VMM management server
Getting ready
How to do it...
How it works...
There's more...
Configure the VMM database with AlwaysOn AGs
See also
Installing a VMM management server on an additional node of a cluster
Getting ready
How to do it...
How it works...
See also
Connecting to a highly available VMM management server by using the VMM console
Getting ready
How to do it...
How it works...
See also
Deploying a highly available library server on a file server cluster
Getting ready
How to do it...
How it works...
See also
Uninstalling a highly available VMM management server
How to do it...
How it works...
There's more...
Configuring Fabric Resources in VMM
Introduction
Creating host groups
Getting ready
How to do it...
How it works...
There's more...
Moving a host group to another location
Configuring host group properties
See also
Setting up a VMM library
Getting ready
How to do it...
How it works...
There's more...
Adding a library share
Adding file-based resources to a VMM library share
Creating or modifying equivalent objects in the VMM library
Marking (creating) objects as equivalent
Modifying equivalent objects
See also
Configuring Networks in VMM
How to do it...
There's more...
Designing for converged networks
Networking: Configuring Logical Networks
Getting ready
How to do it...
How it works...
There's more...
Creating an IP address pool
Automating the network configuration
Associating the VMM Logical Network with the physical adapter
See also
Networking – Configuring VM Networks and Gateways
Getting ready
How to do it...
How it works...
There's more...
Deploying a Network Controller using VMM
Adding a Gateway device, a virtual switch extension or network controller in VMM 2016
Validating a Network Controller deployment
See also
Networking: Configuring logical switches, port profiles and port classifications
How to do it...
How it works...
There's more...
Creating port profiles for VM adapters
Creating a Port Classification
Creating a logical switch
Configuring the Network Adapter for VMs and host management
Applying a logical switch to host network adapters
Converting a standard switch to a logical switch
See also
Integrating and configuring the storage
Getting ready
How to do it...
How it works...
There's more...
Creating an iSCSI session on a host
Bringing the storage pools under management and assigning classifications
Configuring the allocation method for a storage array
Creating logical units (LUN)
Allocating logical units and storage pools to a host group
See also
Creating physical computer profile – host profile
Getting ready
How to do it...
How it works...
See also.
Provisioning a physical computer as a Hyper-V host – Bare metal host deployment
Getting ready
How to do it...
How it works...
See also
Adding and Managing Hyper-V hosts and host clusters
Getting ready
How to do it...
How it works...
There's more...
Adding Hyper-V hosts in a disjointed namespace
Adding Hyper-V hosts in a perimeter network
Installing the agent on the standalone server
Adding perimeter hosts to VMM
See also
Deploying a hyper-converged cluster with S2D and Hyper-V
Getting ready
How to do it...
How it works...
There's more...
Managing the storage pool
Creating cluster shared volumes
Setting storage QoS policies
See also
Configuring Guarded Fabric in VMM
Introduction
Deploying the host guardian service
How to do it...
How it works...
There's more...
Configuring additional HGS cluster nodes
See also
Deploying guarded hosts
How to do it...
How it works...
There's more...
Preparing shielding helper VHD
See also
Deploying shielded VMs
How to do it...
Preparing and protecting a template disk
Creating and importing a shielded data file
Creating a shielded VM template
Deploying a shielded VM from a template
Converting an existing VM to a shielded VM
How it works...
See also
Deploying Virtual Machines and Services
Introduction
Creating private clouds
Getting ready
How to do it...
How it works...
There's more...
Assigning the private cloud to a user role
See also
Creating hardware, guest OS, application, and SQL profiles
Getting ready
How to do it...
How it works...
There's more...
Creating a guest OS profile
Creating an application profile
Creating a SQL Server profile
See also
Creating user roles in VMM
Getting ready
How to do it...
How it works...
There's more...
Creating a delegated or read-only administrator user role
Creating a tenant administrator role
Creating an application administrator (self-service user) role
Configuring self-service user roles to share and receive resources
See also
Creating and deploying virtual machines
Getting ready
How to do it...
How it works...
There's more...
Generalizing the guest OS using Sysprep
See also
Creating virtual machine templates
Getting ready
How to do it...
How it works...
There's more...
Deploying virtual machines from virtual machine templates
See also
Creating and deploying service templates
Getting ready
How to do it...
How it works...
There's more...
Deploying a service from the VMs and Services workspace
Scaling out a service in VMM
Updating a service in VMM
See also
Rapidly provisioning a virtual machine by using SAN Copy
Getting ready
How to do it...
How it works...
There's more...
Creating a SAN Copy-capable template
See also
Managing VMware ESXi hosts
Introduction
Adding a VMware vCenter Server to VMM
Getting ready
How to do it...
Importing the VMware self-signed SSL certificate
Adding vCenter to VMM
How it works...
See also
Adding VMware ESXi hosts or host clusters to VMM
Getting ready
How to do it...
How it works...
There's more...
Updating the host status to OK
See also
Configuring network settings on a VMware ESXi host
How to do it...
How it works...
There's more...
Verifying the settings for a virtual switch
Viewing compliance information for a physical network adapter
See also
Configuring host BMC settings
How to do it...
How it works...
There's more...
Powering a computer on or off through VMM
See also
Importing VMware templates
How to do it...
How it works...
See also
Converting VMware VMs to Hyper-V
How to do it...
How it works...
See also
Managing Clouds, Fabric Updates, Resources, Clusters, and New Features of VMM 2016
Introduction
Creating Hyper-V clusters
Getting ready
Prerequisites for cluster creation using VMM 2016
Prerequisites for fabric configuration
Prerequisites for networking
How to do it...
How it works...
There's more...
Adding a Hyper-V host as a cluster node
See also
Cluster OS rolling upgrade
Getting ready
Prerequisites for cluster rolling upgrade using VMM 2016
How to do it...
How it works...
See also
Managing fabric updates
Getting ready
How to do it...
Installing WSUS for VMM 2016
Integrating WSUS with VMM
How it works...
There's more...
Scanning servers for compliance
Remediating updates for a standalone server in VMM
Remediating updates for a Hyper-V cluster in VMM
See also
Configuring Dynamic Optimization and Power Optimization
Getting ready
How to do it...
Configuring settings for Dynamic Optimization (DO)
Configuring settings for Power Optimization
How it works...
There's more...
Performing DO on the host cluster
See also
Live migrating virtual machines
Getting ready
Requirements for Live migration
Requirements for Live storage migration
Requirements for Live system migration
How to do it...
How it works...
There's more...
Performing live migration of a VM between hosts in two clusters
Performing live storage migration between standalone hosts
Performing concurrent live migrations
See also
Managing Linux virtual machines
Getting ready
How to do it...
How it works...
See also
Configuring availability options and virtual NUMA for VMs
How to do it...
How it works...
There's more...
Configuring availability sets for a VM running on a host cluster
Configuring preferred and possible owners for a VM
Configuring virtual NUMA in VMM 2016
Configuring checkpoints in VMM 2016
Adding a virtual adapter to a running VM in VMM 2016
Managing static memory on a running VM in VMM 2016
See also
Configuring resource throttling
How to do it...
How it works...
There's more...
Configuring memory throttling
Configuring memory weight
See also
Integrating with IPAM Server for IP management
Getting ready
How to do it...
How it works...
There's more...
IPAM and VMM Time Synchrony
Deploying Windows Azure Pack for cloud management
Getting ready
How to do it...
How it works...
There's more...
Windows Azure Pack: integrating with VMM 2016
See also
Configuring Synthetic Fiber Channel
Getting ready
How to do it...
How it works...
There's more...
Creating virtual SANs
Creating a VM or VM Template with virtual fiber Channel
Editing vSAN port assignments
Removing a vSAN
Adding a new vHBA
Editing vHBA WWNN and WWPN Dynamic Settings
See also
Integration with System Center Operations Manager 2016
Introduction
Installing System Center Operations Manager 2016
Getting ready
How to do it...
How it works...
There's more...
See also
Installing management packs
Getting ready
How to do it...
How it works...
See also
Managing discovery and agents
How to do it...
How it works...
See also
Configuring the integration between Operations Manager 2016 and VMM 2016
Getting ready
How to do it...
How it works...
There's more...
Enabling PRO tips and maintenance mode integration in VMM 2016
See also
Enabling reporting in VMM
Getting ready
How to do it...
How it works...
There's more...
Other Books You May Enjoy
Leave a review - let other readers know what you think
Preface
System Center 2016 is a comprehensive IT infrastructure, virtualization, and cloud management platform. With System Center 2016, you can easily and efficiently deploy, manage, and monitor a virtualized infrastructure, services, and applications across multiple hypervisors, as well as public and private cloud infrastructures, to deliver flexible and cost-effective IT services for your business.
This book has plenty of recipes to help you design, plan, and improve Virtual Machine Manager (VMM) deployment; integrate and manage the fabric (compute, storage, network controller, gateway, and networking), services, and resources; deploy different types of clusters; configure integration with the operations manager and Windows Azure Pack; and carry out vital tasks quickly and easily.
Who this book is for
This book is essentially intended at system engineers, solution architects, administrators and anyone who wants to learn and master VMM 2016. If you are not familiar with VMM, don't worry. Start from the beginning, and the book will also help you to get insight into the virtualization platform, its management, and other techniques related to the private cloud.
What this book covers
Chapter 1, VMM 2016 Architecture, provides an understanding of the VMM modular architecture, which is useful when designing VMM and troubleshooting deployment. This chapter also covers all the requirements that must be satisfied to make a private cloud.
Chapter 2, Upgrading from Previous Versions, walks you through all the necessary steps to upgrade the previous version of VMM to the new VMM 2016, covering its database, highly available configurations, and post-upgrade tasks.
Chapter 3, Installing VMM 2016, focuses on deploying VMM and its dependencies. It also gives plenty of tips and tricks to install and automate VMM and SQL Server deployments in both Windows Server Core and Full environments.
Chapter 4, Installing a High Available VMM Server, dives into more advanced VMM configuration, and provides an understanding of how VMM has become a critical part of the private cloud infrastructure. You will also learn how to make a highly available library server and VMM configuration database.
Chapter 5, Configuring Fabric Resources in VMM, discusses building a new fabric in VMM by configuring compute, storage, and networking resources. It starts by adding host groups and ends by creating a hyper-converged cluster with Storage Spaces Direct and Hyper-V. It also covers the deployment of a network controller providing a good starting point for network virtualization implementation.
Chapter 6, Configuring Guarded Fabric in VMM, walks you through the recipes to help protect confidential data by deploying new shielded VMs as a part of a Guarded Fabric consisting of Guarded Hosts and a Host Guardian Service. It also discusses how to convert existing VMs to shielded and manage them through VMM.
Chapter 7, Deploying Virtual Machines and Services, provides information to help the administrator to create, deploy, and manage private clouds, virtual machines, templates, and services in VMM 2016; it provides recipes to assist you in getting the most of our deployment.
Chapter 8, Managing VMware ESXi Hosts, shows you how to manage and make VMware resources available to private cloud deployments. It also covers converting VMware machines to Hyper-V (V2V), deploying virtual machines and templates, all from the VMM console.
Chapter 9, Managing Clouds, Fabric Updates, Resources, Cluster and the New Features of 2016, covers other new features of VMM 2016 such as Cluster OS Rolling upgrade and Production Checkpoints. You will also learn how to integrate VMM 2016 with Windows Azure Pack for VM cloud management.
Chapter 10, Integration with System Center Operations Manager 2016, guides you through the steps required to complete integration of SCOM 2016 with VMM in order to enable monitoring of the private cloud infrastructure.
To get the most out of this book
This book assumes a medium level of expertise on Windows Server and Hyper-V, basic knowledge on cloud computing and networking, and a moderate experience with PowerShell. To evaluate all the recipes in the book, you will need System Center 2016 Virtual Machine Manager, SQL Server (2016 version is used throughout the book), as a minimum requirement. The book also covers integration with VMware vCenter 6.0; therefore, you need to have it deployed beforehand. Although the recipes provide exceptional step-by-step guides, prepare Windows Azure Pack, Service Provider Foundation, and System Center Operations Manager 2016 media files at least.
Actually, some of the chapters were made in Azure, and you can also use public IaaS services and its free trial to deploy and check some of the explained scenarios. In addition, Azure is required if you plan to protect virtual machines via the Azure Site Recovery service.
Download the color images
We also provide a PDF file that has color images of the screenshots/diagrams used in this book. You can download it here: https://www.packtpub.com/sites/default/files/downloads/SystemCenter2016VirtualMachineManagerCookbookThirdEdition_ColorImages.pdf.
Conventions used
There are a number of text conventions used throughout this book.
CodeInText: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: "In addition, it will add the ApplicationFrameworks folder to the library share."
A block of code is set as follow
;SQL Server 2016 Configuration File [OPTIONS] ; SQL Server License Terms IAcceptSQLServerLicenseTerms="True" ; Setup Work Flow: INSTALL, UNINSTALL, or UPGRADE. ACTION="Install"
When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:
;SQL Server 2016 Configuration File [OPTIONS]
; SQL Server License Terms
IAcceptSQLServerLicenseTerms="True" ; Setup Work Flow: INSTALL, UNINSTALL, or UPGRADE. ACTION="Install"
Any command-line input or output is written as follows:
Set-ItemProperty -Path 'HKLM:SoftwareMicrosoftMicrosoft
System Center Virtual Machine Manager ServerSetup' -Name VmmServicePrincipalNames -Value "SCVMM/vmm-mgmt01,SCVMM/vmm- mgmt01.rllab.com"
Bold: Indicates a new term, an important word, or words that you see onscreen. For example, words in menus or dialog boxes appear in the text like this. Here is an example: "Launch the SQL Server setup and choose the New SQL Server failoverclusterinstallation option."
Get in touch
Feedback from our readers is always welcome.
General feedback: Email [email protected] and mention the book title in the subject of your message. If you have questions about any aspect of this book, please email us at [email protected].
Errata: Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you have found a mistake in this book, we would be grateful if you would report this to us. Please visit www.packtpub.com/submit-errata, selecting your book, clicking on the Errata Submission Form link, and entering the details.
Piracy: If you come across any illegal copies of our works in any form on the Internet, we would be grateful if you would provide us with the location address or website name. Please contact us at [email protected] with a link to the material.
If you are interested in becoming an author: If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, please visit authors.packtpub.com.
Reviews
Please leave a review. Once you have read and used this book, why not leave a review on the site that you purchased it from? Potential readers can then see and use your unbiased opinion to make purchase decisions, we at Packt can understand what you think about our products, and our authors can see your feedback on their book. Thank you!
For more information about Packt, please visit packtpub.com.
VMM 2016 Architecture
In this chapter, we will cover:
Understanding each component for a real-world implementation
Planning for high availability
Designing the VMM server, database, and console implementation
Specifying the correct system requirements for a real-world scenario
Licensing the System Center VMM 2016
Troubleshooting VMM and supporting technologies
Introduction
This chapter has been designed to provide an understanding of the underlying Virtual Machine Manager (VMM) modular architecture, which is useful to improve the implementation and troubleshooting VMM.
The first version of VMM was launched in far 2007 and was designed to manage virtual machines and to get the most efficient physical server utilizations. It has been dramatically grown from the basic tool to the one of the most advanced tool, with abilities to work even with different type of clouds.
The new VMM 2016 allows you to create and manage private clouds, retain the characteristics of public clouds by allowing tenants and delegated VMM administrators to perform functions, and abstract the underlying fabric to let them deploy the VM's applications and services. Although they have no visibility into the underlying hardware, there is a uniform resource pooling which allows you to add or remove capacity as your environment grows. Additionally, it supports the new Windows Server 2016 capabilities including software-defined storage, networks and shielded VMs (simply put, Software-Defined Datacenters (SDDC's)). VMM 2016 can manage private clouds across supported hypervisors, such as Hyper-V and VMware, which can be integrated with Azure public cloud services as well.
The main strategies and changes of VMM 2016 are as follows:
Application focus
: VMM abstracts fabric (hosts servers, storage, and networking) into a unified pool of resources. It also gives you the ability to deploy web applications and SQL Server profiles to configure customized database servers along with data-tier applications. However, virtual application deployment based on Server App-V, which was available in older versions of VMM, is no longer existing in VMM 2016. Although, if you upgrade VMM 2012 R2 to VMM 2016, your current service templates with Server App-V will continue to work with some limitations related to scale-out scenarios.
Service deployment
: One of the powerful features of VMM is its capability to deploy a service to a private cloud. These services are dependent on multiple VMs tied together (for example, web frontend servers, application servers, and backend database servers). They can be provisioned as simply as provisioning a VM, but all together.
Dynamic optimization
: This strategy will balance the workload in a cluster, while a feature called
power optimization
can
turn off
physical virtualization host servers when they are not needed. It can then turn them
back on
when the load increases. This process will automatically move VMs between hosts to balance the load. It also widens and replaces the VM Load Balancing feature that is available for Windows Server 2016 Failover Clusters.
Software
-Defined Datacenter
: Network virtualization (software-defined networking or simply SDN) was introduced in VMM 2012 SP1 and quickly became popular due to a possibility to define and run multiple isolated networks on a single physical network fabric. It was based on NVGRE abstraction mechanism. VMM 2016 goes beyond and brings Azure's network model closer to your datacenter by introducing network controller as a central point, VXLAN for abstraction from the underlying physical network and integration with software load-balancers and gateways. In addition to SDN, Windows Server 2016 features like
Storage Spaces Direct
(
S2D
),
Storage Replica
, and
Quality of Service
(
QoS
) complement each other and are also supported by VMM 2016.
Advanced Security
:
M
odern data center
requires protection for customer's sensitive data from hackers and even technical staff or other persons who can somehow access such data without your permission. To help protect against that problem, VMM supports managing and creating a new guarded fabric with a set of shielded VMs, guarded hosts and hosts with guardian services.
Multivendor hypervisor support
: If we compare the
list of managed hypervisors in VMM 2012 R2 to VMM 2016, it's been cut. VMM 2016 now manages only
Hyper-V and VMware
, covering all of the major hypervisors on the market so far. Support for Citrix XenServer has been removed:
Knowing your current environment – assessment
This is the first step. You need to do an assessment of your current environment to find out how and where the caveats are. You can use the Microsoft MAP toolkit (download it from http://www.microsoft.com/en-us/download/details.aspx?id=7826) or any other assessment tool to help you carry out a report assessment by querying the hardware, OS, application, and services. It is important to define what you can and need to address and, sometimes, what you cannot virtualize.
Currently, Microsoft supports the virtualization of all MS infrastructure technologies (for example, SQL, Exchange, AD, Skype for Business, IIS, and File Server).
Designing the solution
With the assessment report in hand, it is recommended that you spend a reasonable amount of time on the solution design and architecture, and you will have a solid and consistent implementation. The following figure highlights the new VMM 2016 features and others, which have been carried over from older versions, for you to take into consideration when working on your private cloud design:
Creating the private cloud fabric
In VMM, before deploying VMs and services to a private cloud, you need to set up the private cloud fabric.
There are three resources that are included in the fabric in VMM 2016:
Servers
: These contain virtualization hosts (Hyper-V and VMware servers) and groups, PXE, update servers (that is, WSUS), and other servers.
Networking
: This contains the network fabric and devices configuration (for example, gateways, virtual switches, network virtualization); it presents the wiring between resource repositories, running instances, VMs, and services.
Storage
: This contains the configuration for storage connectivity and management, simplifying storage complexities, and how storage is virtualized. For example, you can configure the SMI-S and SMP providers or a Windows 2016 SMB 3.0 file server.
If you are really serious about setting up a private cloud, you should carry out a virtualization assessment using MAP, as discussed above and work on a detailed design document covering hardware, hypervisor, fabric, and management. With this in mind, the implementation will be pretty straightforward.
System Center 2016 will help you install, configure, manage, and monitor your private cloud from the fabric to the hypervisor and up to service deployment. It can also be integrated with public cloud services( for instance, Azure Site Recovery to protect and replicate your VMs to Azure public cloud).
Understanding each component for a real-world implementation
System Center 2016 VMM has six components. It is important to understand the role of each component in order to have a better design and implementation.
Getting ready
For small deployments, test environments, or a proof of concept, you can install all of the components in one server, but as is best practice in production environments, you should consider separating the components.
How to do it...
Let's start by reviewing each component of VMM 2016 and understanding the role it plays:
VMM console
: This application connects to the VMM management server to allow you to manage VMM, to centrally view and manage physical and virtual resources (for example, hosts, VMs, services, the fabric, and library resources), and to carry out tasks on a daily basis, such as VM and services deployment, monitoring, and reporting.
By using the VMM console from your desktop, you will be able to manage your private cloud without needing to remotely connect it to the VMM management server.
VMM management server
: The management server is the core of VMM. It is the server on which the Virtual Machine Manager service runs to process commands and control communications with the VMM console, the database, the library server, and the hosts.
Think of VMM management server as the heart, which means that you need to design your computer resources accordingly to accommodate such an important service.
As is the best practice for medium and enterprise production environments, keep the VMM management server on a separate cluster from the production cluster, due to its crucial importance for your private cloud.
Database
: The database server runs SQL Server and contains all of the VMM data. It plays an important role when you have a clustered VMM deployment by keeping the shared data. The best practice is to also have the SQL database in a cluster or an availability group.
VMM library
: The VMM library servers are file shares, a catalog that stores resources, such as VM templates, virtual hard drive files, ISOs, scripts, and custom resources with a
.cr
extension, which will all be visible and indexed by VMM and then shared among application packages, tenants, and self-service users in private clouds.
The library has been enhanced to support services and the sharing of resources. It is a store for drivers for Bare Metal deployments, SQL data-tier apps, (SQLDAC), and web deploy packages.
In a distributed environment, you can group equivalent sets of resources and make them available in different locations by using resource groups. You can also store a resource in a storage group that will allow you to reference that group in profiles and templates rather than in a specific virtual hard disk (VHD); this is especially important when you have multiple sites and VMM will automatically select the right resource from a single reference object. This essentially enables one template that can reference an object that can be obtained from multiple locations.
You can also have application profiles and SQL profiles(answer files for configuration of the application or SQL) to support the deployment of applications and databases to a VM after the base image is deployed. Application profiles can be web applications, SQL data-tier, or a general for deploying both application types and running any scripts.
Self-service portal
: The web-based self-service portal, was removed from SC 2012. In System Center 2012 SP1/R2, App Controller was being used as a replacement to the self-service portal, however, it was also finally removed in System Center 2016.
VMM command shell
: VMM is based on PowerShell. Everything you can do on GUI, you can do by using PowerShell. VMM PowerShell extensions make available the
cmdlets
that perform all of the functions in VMM 2016.
How it works...
As you may have noticed, although VMM management is the core, each component is required in order to provide a better VMM experience. In addition to this, for a real-world deployment, you also need to consider implementing other System Center family components to complement your design. Every System Center component is designed to provide part of the private cloud solution. The Microsoft private cloud solution includes the implementation of VMM 2016 plus the following utilities:
System Center 2016 Configuration Manager
: This provides comprehensive configuration management for the Microsoft platform that can help users with the devices and applications they need to be productive while maintaining corporate compliance and control
System Center 2016 Data Protection Manager
: This provides unified data protection for the Windows and also VMware environment, delivering backup and restore scenarios from disk, tape, off-premise, and from the cloud
System Center 2016 Endpoint Protection
: This is built on the System Center Configuration Manager and provides threat detection of malware and exploits as part of a unified infrastructure for managing client security and compliance to simplify and improve endpoint protection
System Center 2016 Operations Manager
: This provides deep application diagnostics and infrastructure monitoring to ensure the predictable performance and availability of vital applications, and offers a comprehensive view of the datacenter, private cloud, and public clouds
System Center 2016 Orchestrator
: This provides the orchestration, integration, and automation of IT processes through the creation of
runbooks
to define and standardize best practices and improve operational efficiency
System Center 2016 Service Manager
: This provides flexible self-service experiences and standardized datacenter processes to integrate people, workflows, and knowledge across enterprise infrastructure and applications
There's more...
When deploying System Center, there are some other systems and configurations you need to consider. There are some old components that have also been described here in order to help you to understand your current infrastructure before, for instance, migration to the new VMM from older versions.
Windows Azure Pack
WAP is a free solution to manage resources that integrates with System Center and Windows Server to provide a customizable self-service portal for managing services such as websites, Virtual Machines, SQL or MySQL servers, and Service Bus; it also includes capabilities for automating and integrating additional custom services. For more info see http://www.microsoft.com/en-us/server-cloud/products/windows-azure-pack/.
Service Provider Foundation
Service Provider Foundation (SPF) is provided with System Center Orchestrator, a component of System Center since 2012 SP1. Service Provider Foundation exposes an extensible OData web service that interacts with Virtual Machine Manager (VMM). It's main interface for communication between WAP, SCOM, and VMM.
Service Reporting
Service Reporting, an optional component of System Center 2012 R2, enables IT (particularly hosting providers) to create detailed views, for each customer (tenant), of the virtual machine's consumption of the resources (CPU, memory, storage, and networking). For more info see http://technet.microsoft.com/en-us/library/dn251058.aspx.
Domain controllers
Although the domain controller is not part of the System Center family and it is not a VMM component, it plays an important role in the deployment of a private cloud as VMM requires it to be installed on a domain environment.
Windows Server Update Service – WSUS
WSUS plays an important role with reference to the private cloud as it is used to update the Hyper-V hosts, library servers, or any other role for compliance and remediation.
System Center App Controller
The App Controller provides a self-service experience through a web portal that can help you easily configure, deploy, and manage VMs and services across private, third-party hosters (that support Microsoft Hyper-V) and public clouds (Azure). For example, moving a VM from a private cloud to Azure, creating checkpoints, granting access, scaling out deployed services, and so on.
The App Controller has been used as a replacement of the VMM self-service portal since SC 2012 SP1. It was deprecated in the SC 2012 R2 time and finally removed in SC 2016. As noted above, you should plan Azure Pack deployment instead of current App Controller instance.
Microsoft Azure Stack
Azure Stack is a hybrid-cloud platform, bringing core public Azure services to your datacenter. These services are mostly dedicated to Azure PaaS and IaaS and help you out with building unified ecosystems between private and public clouds. Azure Stack is delivered as an integrated system, with software installed on the hardware built by partners like HPE and Cisco. Azure's familiar pay-as-you-go model is mainly being used in Azure Stack and you can stretch the same subscriptions out for both Azure and Azure Stack clouds. If you have unstable or restricted connection to Azure, you may choose to use Azure Stack in disconnected mode with a capacity model pricing package - a fixed fee annual subscription based on the number of physical cores. It's important to note that you can manage WAP VMs from Azure Stack using a special connector, though it's under review and not recommended for production use: https://aka.ms/wapconnectorazurestackdlc.
System Center components scenarios
The following table will guide you through choosing which System Center component is necessary as per your deployment:
Planning for high availability
High availability is important when your business requires minimum or no downtime, and planning for it in advance is very important.
Getting ready
Based on what we learned about each component, we now need to plan the high availability (HA) for each VMM component.
How to do it...
Start by planning the HA for the core component, followed by every VMM component of your design. It is important to consider hardware and other System Center components, as well as the OS and software licenses.
How it works...
When planning for highly available VMM management servers, you should first consider where to place the VMM cluster. As per best practices, the recommendation is to install the VMM cluster on a management cluster, preferably on some physical servers, if using converged network for your virtual network. However, if you plan to install highly available VMM management servers on the managed cluster, you need to take into consideration the following points:
Only one highly available VMM management server is allowed per Failover Cluster.
Despite the possibility to have a VMM management server installed on all cluster nodes, only one node can be active at a time.
To perform a planned failover, use
Failover Cluster Manager
. The use of the VMM console is not supported.
In a planned failover situation, ensure that there are no running tasks on the VMM management server, as it will fail during a failover operation and will not automatically restart after the failover operation.
Any connection to a highly available VMM management server from the VMM console will be disconnected during a failover operation, reconnecting right after.
The Failover Cluster must be running Windows Server 2016 in order to be supported.
The highly available VMM management server must meet system requirements. For information about system requirements for VMM, see the
Specifying the correct system requirements for a real-world scenario
recipe in this chapter.
In a highly available VMM management deployment, you will need a domain account to install and run the VMM management service. You are required to use
distributed key management
(
DKM
) to store the encryption keys in Active Directory.
A dedicated and supported version of Microsoft SQL Server should be installed. For supported versions of SQL Server for the VMM database, see the
Specifying the correct system requirements for a real-world scenario
recipe.
There's more...
The following sections are the considerations for SQL Server and the VMM library in an HA environment.
SQL Server
In an enterprise deployment of VMM, it is recommended that you have a SQL Server cluster to support the HA VMM, preferably on a cluster separated from the VMM cluster. VMM 2016 supports SQL Server Always On Availability Groups. The following link will show you a good example of how to set it up: See the Configure SQL Server with AlwaysOn AGs recipe in Chapter 3, Installing VMM 2016.
Although the latest SQL Server versions support basic availability groups (AGs) available in Standard edition, SQL Server Enterprise and advanced AGs are recommended and will be used throughout the book.
VMM library
As it is the best practice in an enterprise deployment, a highly available file server for hosting the VMM library shares is highly recommended as VMM does not provide a method for replicating files in the VMM library, and they need to be replicated outside of VMM.
As a suggestion, you can use the Microsoft Robocopy tool to replicate the VMM library files if you have distributed the library type.
Designing the VMM server, database, and console implementation
When planning a VMM 2016 design for deployment, consider the different VMM roles, keeping in mind that VMM is part of the Microsoft private cloud solution. If you are considering a private cloud, you will need to integrate VMM with the other System Center family components.
In VMM, you can add the hardware, guest operating system, SQL Server, and application profiles that will be used in a template to deploy virtual machines. These profiles are essentially answer files to configure the application or SQL during the setup.
Getting ready
You can create a private cloud by combining hosts, even from different hypervisors (for example, Hyper-V and VMware), with networking, storage, and library resources.
To start deploying VMs and services, you first need to configure the fabric.
How to do it...
Create a spreadsheet with the server names and the IP settings, as seen in the following table, of every System Center component you plan to deploy. This will help you manage and integrate the solution:
Server name
Role
IP settings
vmm-mgmt01
VMM Management Server 01
IP: 10.16.254.20/24
GW: 10.16.254.1
DNS: 10.16.254.2
vmm-mgmt02
VMM Management Server 02
IP: 10.16.254.22/24
GW: 10.16.254.1
DNS: 10.16.254.1
vmm-console01
VMM Console
IP: 10.16.254.50/24
GW: 10.16.254.1
DNS: 10.16.254.2
vmm-lib01
VMM Library
IP: 10.16.254.25/24
GW: 10.16.254.1
DNS: 10.16.254.2
w2016-sql01
SQL Server 2016
IP: 10.16.254.40/24
GW: 10.16.254.1
DNS: 10.16.254.2
How it works...
The following rules need to be considered when planning a VMM 2016 deployment:
The computer name cannot contain the character string
SCVMM
(for example,
srv-scvmm-01
) and cannot exceed 15 characters.
Your VMM database must use a supported version of SQL Server to perform a VMM 2016 deployment. Express editions of Microsoft SQL Server are no longer supported for the VMM database. For more information, check the system requirements specified in the
Specifying the correct system requirements for a real- world scenario
recipe in this chapter.
VMM 2016 does not support a library server on a computer that is running Windows Server 2012; it now requires Windows Server 2012 R2 as a minimum, but for consistency and standardization, I do recommend that you install it on a Windows Server 2016.
VMM 2016 no longer supports creating and importing templates with the Server App-V packages. If you are upgrading from a previous version of VMM that has templates with such applications, you will continue to manage them with VMM, but you will not be able to upgrade the application.
Hosts running the following versions of VMware ESXi and VMware vCenter Server are supported:
ESXi 5.1
ESXi 5.5
ESXi 6.0
vCenter 5.1
vCenter 5.5
vCenter 6.0
Upgrading a previous version of VMM to a highly available VMM 2016 requires additional preparation. See
Chapter 2
,
Upgrading from Previous Version
of VMM,
for this purpose.
If you're planning for high availability of VMM 2016, be sure to install SQL Server on a cluster and on separate servers as it cannot physically be located on the same servers as your VMM 2016 management server. In addition, AlwaysOn availability groups can be used for the VMM database.
The VMM management server must be a member of a domain. (This rule does not apply to the managed hosts, which can be on a workgroup.)
The startup RAM for the VMM management server (if running on a VM with dynamic memory enabled) must be at least 2048 MB.
VMM library does not support
DFS Namespaces
(
DFSN
) or
DFS Replication
(
DFSR
). This support is being planned.
VMM does not support file servers configured with the
case-insensitive option
for Windows Services for Unix, as the network filesystem case control is set to
ignore
. Refer to the
Windows Services for UNIX 2.0 NFS Case Control
article available at
http://go.microsoft.com/fwlink/p/?LinkId=102944
to learn more.
The VMM console machine must be a member of a domain.
There's more...
For a complete design solution, there are more items you need to consider.
Storage providers – SMI-S and SMP
VMM provides support for both Block level storage (Fibre Channel, iSCSI, and Serial Attached SCSI (SAS) connections) and File storage (on SMB 3.0 network shares, residing on a Windows file server or on a NAS device).
By using storage providers, VMM enables discovery, provisioning, classification, allocation, and decommissioning.
Storage classifications enable you to assign user-defined storage classifications to discovered storage pools for Quality of Service (QoS) or chargeback purposes.
In order to use this feature, you will need the SMI-S provider.
VMM 2016 can discover and communicate with SAN arrays through the Storage Management Initiative (SMI-S provider) and Storage Management Provider (SMP) provider.
If your storage is SMI-S compatible, you must install the storage provider on a separately available server (do not install on the VMM management server) and then add the provider to VMM management. Some devices come with built-in SMI-S provider and no extra are tasks required in that case. If your storage is SMP-compatible, it does not require a provider installation either.
CIM-XML is used by VMM to communicate with the underlying SMI-S providers since VMM never communicates with the SAN arrays themselves.
By using the storage provider to integrate with the storage, VMM can create LUNs (both GPT and MBR) and assign storage to hosts or clusters.
VMM 2016 also supports the SAN snapshot and clone feature, allowing you to duplicate a LUN through a SAN Copy-capable template to provide for new VMs, if you are hosting those in a Hyper-V platform. You will need to provision outside of VMM for any other VMs hosted with VMware hosts, for example.
Bare metal
This capability enables VMM 2016 to identify the hardware, install the operational system (OS), enable the Hyper-V or file server role, and add the machine to a target-host group with streamlined operations in an automated process.
PXE capability is required and is an integral component of the server pool. The target server will need to have a baseboard management controller (BMC) supporting one of the following management protocols:
Data Center Management Interface
(
DCMI
)
1.0
Systems Management Architecture for Server Hardware
(
SMASH
)
1.0
Intelligent Platform Management Interface
(
IPMI
)
1.5
or
2.0
Custom protocols such as HPE
Integrated Lights-Out
(
iLO
) or
Integrated Dell Remote Access
(
iDRAC
)
Enterprise and hosting companies will benefit from the ability to provide new Hyper-V servers without having to install the operational system manually on each machine. By using BMC and integrating with Windows Deployment Services (WDS), VMM deploys the OS to designated hosts through the boot from the VHD(X) feature. The right BMC configuration presence is also a requirement for one of the most interesting features, called OS Rolling Upgrade, which will be discussed in detail later.
