Book Image

System Center 2016 Virtual Machine Manager Cookbook - Third Edition

By : Roman Levchenko, EDVALDO ALESSANDRO CARDOSO
Book Image

System Center 2016 Virtual Machine Manager Cookbook - Third Edition

By: Roman Levchenko, EDVALDO ALESSANDRO CARDOSO

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.
Table of Contents (16 chapters)
Title Page
Packt Upsell
Contributors
Preface
Index

Introduction


This chapter is about guiding you through the requirements and steps to upgrade older VMM versions to VMM 2016. We will start from the VMM 2008 R2 SP1 and end on current VMM 2016.

Note

There is no direct upgrade path from VMM 2008 R2 SP1 or VMM 2012 to VMM 2016. You must first upgrade VMM 2008 R2 to VMM 2012, and then to VMM 2012 R2. VMM 2008 R2 SP1 -> VMM 2012 -> SCVMM 2012 SP1 -> VMM 2012 R2 -> VMM 2016 is the correct upgrade path.

The main reasons for upgrading might be different:

  • Evaluation copy has expired and you need to re-install or upgrade VMM:
  • New functionality and the necessity of managing hosts running on a newer version of Windows Server or ESXi. You can't manage, for instance, Windows Server 2016 hosts in VMM 2012 R2.
  • Product life cycle is coming to an end. Knowing the life cycle of your existing VMM helps you plan the upgrade and other infrastructure changes related to a virtualization platform including hosts, libraries, and so on. The following table shows...