System Center 2016 Virtual Machine Manager Cookbook

By : Levchenko, EDVALDO ALESSANDRO CARDOSO

4 (6)

Buy this Book

System Center 2016 Virtual Machine Manager Cookbook

4 (6)

By: Levchenko, EDVALDO ALESSANDRO CARDOSO

Buy this Book

Overview of this book

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.

Preface

Who this book is for

What this book covers

To get the most out of this book

Get in touch

Free Chapter

VMM 2016 Architecture

Introduction

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

Troubleshooting VMM and supporting technologies

Upgrading from Previous Versions

Introduction

Reviewing the upgrade options

Checking the VMM system requirements and preparing for the upgrade

Upgrading to VMM 2016

Re-associating hosts after upgrading

Updating the VMM agents

Performing other post-upgrade tasks

Installing VMM 2016

Introduction

Creating service accounts

Deploying a Microsoft SQL Server for VMM implementation

Installing VMM dependencies

Configuring Distributed Key Management

Installing a VMM management server

Installing the VMM console

Connecting to a VMM management server by using the VMM console

Creating a Run As account credentials in VMM

Configuring ports and protocols on the host firewall for each VMM component

Installing a Highly Available VMM Server

Introduction

Installing a highly available VMM management server

Installing a VMM management server on an additional node of a cluster

Connecting to a highly available VMM management server by using the VMM console

Deploying a highly available library server on a file server cluster

Uninstalling a highly available VMM management server

Configuring Fabric Resources in VMM

Introduction

Creating host groups

Setting up a VMM library

Configuring Networks in VMM

Networking: Configuring Logical Networks

Networking – Configuring VM Networks and Gateways

Networking: Configuring logical switches, port profiles and port classifications

Integrating and configuring the storage

Creating physical computer profile – host profile

Provisioning a physical computer as a Hyper-V host – Bare metal host deployment

Adding and Managing Hyper-V hosts and host clusters

Deploying a hyper-converged cluster with S2D and Hyper-V

Configuring Guarded Fabric in VMM

Introduction

Deploying the host guardian service

Deploying guarded hosts

Deploying shielded VMs

Deploying Virtual Machines and Services

Introduction

Creating private clouds

Creating hardware, guest OS, application, and SQL profiles

Creating user roles in VMM

Creating and deploying virtual machines

Creating virtual machine templates

Creating and deploying service templates

Rapidly provisioning a virtual machine by using SAN Copy

Managing VMware ESXi hosts

Introduction

Adding a VMware vCenter Server to VMM

Adding VMware ESXi hosts or host clusters to VMM

Configuring network settings on a VMware ESXi host

Configuring host BMC settings

Importing VMware templates

Converting VMware VMs to Hyper-V

Managing Clouds, Fabric Updates, Resources, Clusters, and New Features of VMM 2016

Introduction

Creating Hyper-V clusters

Cluster OS rolling upgrade

Managing fabric updates

Configuring Dynamic Optimization and Power Optimization

Live migrating virtual machines

Managing Linux virtual machines

Configuring availability options and virtual NUMA for VMs

Configuring resource throttling

Integrating with IPAM Server for IP management

Deploying Windows Azure Pack for cloud management

Configuring Synthetic Fiber Channel

Integration with System Center Operations Manager 2016

Introduction

Installing System Center Operations Manager 2016

Installing management packs

Managing discovery and agents

Configuring the integration between Operations Manager 2016 and VMM 2016

Enabling reporting in VMM

Other Books You May Enjoy

Leave a review - let other readers know what you think

Customer Reviews

4 (6)

5 star

66.7%

4 star

3 star

16.7%

2 star

1 star

16.7%

Configuring Distributed Key Management

Distributed Key Management (DKM) is used to store VMM encryption keys in an Active Directory Domain Services (AD DS) container.

When installing VMM, for security reasons (recommended, as it encrypts the information on AD) and when deploying HA VMM (required), choose to use DKM on the Configure service account and distributed key management page.

Why do we need DKM? By default, using the Windows Data Protection API (DPAPI), VMM encrypts some data in the VMM database (for example, the Run As account credentials and passwords), and this data is tied to the VMM server and the service account used by VMM. However, with DKM, different machines can securely access the shared data.

Once an HA VMM node fails over to another node, it will start accessing the VMM database and use the encryption keys conveniently stored under a container in AD to decrypt...