Figure 5.12 All key Hyper-V management environments running on a Windows 10
client
http://technet.microsoft.com/en-us/library/gg610640.aspx
However, the Windows Server 2016 Hyper-V Manager is only part of Windows 10, and
the RSAT for Windows Server 2016 will install only on Windows 10. If you really need
to manage Windows 2016 servers from an older client, there are some workarounds. I
walk through a solution in a video at http://youtu.be/_dkxyr03Er4. The solution is to
configure a Remote Desktop Session Host, which has the administration tools
installed, and then publish them to other client operating systems. It’s not ideal, but it
does work.
Using Hyper-V Manager
Many aspects of Hyper-V Manager are covered throughout this book. For example,
virtual switches are covered in Chapter 3, virtual SANs are covered in Chapter 4,
“Storage Configurations,” and migration and replication settings are covered in future
chapters. In this section, I cover the main components of Hyper-V Manager and some
core configurations. If I don’t cover a feature, it means that it’s covered elsewhere in
the book in a section that’s more specific to the topic.
Figure 5.13 shows the Hyper-V Manager interface with the five main panes of
information and capabilities exposed. Notice in the far-left server inventory pane that
it is possible to add multiple Hyper-V servers to Hyper-V Manager. It is not possible to
specify alternate credentials prior to Windows Server 2016, which means that only
Hyper-V servers in trusting domains can be added where your current credentials have
administrative rights. In Windows Server 2016, alternate credentials can be specified,
enabling Hyper-V servers from different domains and even workgroups to be
managed. To add a new Hyper-V server to Hyper-V Manager, select the Connect To