Book Image

Hyper-V 2016 Best Practices

By : Romain Serre, Benedict Berger
Book Image

Hyper-V 2016 Best Practices

By: Romain Serre, Benedict Berger

Overview of this book

Hyper-V Server and Windows Server 2016 with Hyper-V provide best-in-class virtualization capabilities. Hyper-V is a Windows-based, very cost-effective virtualization solution with easy-to-use and well-known administrative consoles. This book will assist you in designing, implementing, and managing highly effective and highly available Hyper-V infrastructures. With an example-oriented approach, this book covers all the different tips and suggestions to configure Hyper-V and provides readers with real-world proven solutions. This book begins by deploying single clusters of High Availability Hyper-V systems including the new Nano Server. This is followed by steps to configure the Hyper-V infrastructure components such as storage and network. It also touches on necessary processes such as backup and disaster recovery for optimal configuration. The book does not only show you what to do and how to plan the different scenarios, but it also provides in-depth configuration options. These scalable and automated configurations are then optimized via performance tuning and central management ensuring your applications are always the best they can be.
Table of Contents (15 chapters)
Hyper-V 2016 Best Practices
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Preface

Implementing failover clusters


Having prepared our Hyper-V hosts, we will now create a Failover Cluster using PowerShell. I'm assuming that your hosts are installed, the storage and network connections are prepared, and the Hyper-V role is already active utilizing up-to-date drivers and firmware on your hardware:

  1. First, we need to ensure that the server name, date, and time of our hosts are correct. Time and time zone configurations should occur via Group Policy.

  2. For automatic network configuration later on, it's important to rename the network connections from the defaults to their designated roles using PowerShell, as shown in the following commands:

    Rename-NetAdapter -Name "Ethernet" -NewName "Host"
    Rename-NetAdapter -Name "Ethernet 2" -NewName
         "LiveMig"
    Rename-NetAdapter -Name "Ethernet 3" -NewName "VMs"
    Rename-NetAdapter -Name "Ethernet 4" -NewName
         "Cluster"
    Rename-NetAdapter -Name "Ethernet 5" -NewName
         "Storage"
    

    The Network Connections window should look...