Adding Windows Servers as Hyper-V Hosts in VMM Overview
Updated: May 13, 2016
Applies To: System Center 2012 SP1 - Virtual Machine Manager, System Center 2012 R2 Virtual Machine Manager, System Center 2012 - Virtual Machine Manager
The procedures in this section describe how to add an existing Windows Server computer or a Windows Server failover cluster as one or more managed Hyper-V hosts in Virtual Machine Manager (VMM). You can add Windows Server computers that are in a trusted or untrusted Active Directory domain, in a disjointed namespace, and in a perimeter network (also known as DMZ, demilitarized zone, and screened subnet). Realize that you can add only stand-alone hosts in a perimeter network. VMM does not support managing a host cluster in a perimeter network. If you want to manage a stand-alone host that is in a workgroup and not part of a domain, you can use the method to add a host in a perimeter network.
Starting with System Center 2012 – Virtual Machine Manager, you can manage Hyper-V host clusters in untrusted Active Directory domains.
The computers that you want to add as Hyper-V hosts must be running one of the operating systems that is listed in Preparing your environment for System Center 2012 R2 Virtual Machine Manager.
If the Windows Server computer that you want to add does not already have the Hyper-V role installed, make sure that the BIOS on the computer is configured to support Hyper-V. If the Hyper-V role is not already installed on the server, VMM automatically adds and enables the Hyper-V role when you add the server. For more information, see Hyper-V Installation Prerequisites.
The example scenarios that are used in this section assume that you have the basic VMM infrastructure in place, such as a VMM management server and a library server. The examples in this section build on example scenarios from the Preparing the Fabric in VMM section, and uses the same example host group structure.
The example resource names and configuration are used to help demonstrate the concepts. You can adapt them to your test environment.
The example scenarios walk you through how to add a Hyper-V host in a trusted Active Directory domain, an untrusted Active Directory domain, in a disjointed namespace, and in a perimeter network.
The following table summarizes the example resources that are used.
|Windows Server in a trusted Active Directory domain||HyperVHost01.contoso.com|
|Windows Server in an untrusted Active Directory domain||HyperVHost02.fabrikam.com|
|Windows Server in a disjointed namespace||HyperVHost03.contosocorp.com|
|Windows Server in a perimeter network||HyperVHost04|
|Host groups||- HyperVHost01.contoso.com is added to the host group Seattle\SEA_Tier0|
- HyperVHost02.fabrikam.com is added to the host group New York\NY_Tier2
- HyperVHost03 is added to the host group New York\NY_Tier1
- HyperVHost04 is added to the host group Seattle\SEA_Tier2
|Run As accounts||- Trusted Hyper-V Hosts Note: This Run As account is optional, as you can also specify a user name and password.|
- Untrusted Hyper-V Hosts
Follow these procedures to add Windows Server computers as managed Hyper-V hosts.
|How to Add Trusted Hyper-V Hosts and Host Clusters in VMM||Describes how to add Hyper-V hosts and host clusters that are in a trusted Active Directory domain.|
|How to Add Hyper-V Hosts in a Disjointed Namespace in VMM||Describes how to add Hyper-V hosts and host clusters that are in a disjointed namespace.|
|How to Add Untrusted Hyper-V Hosts and Host Clusters in VMM||Describes how to add Hyper-V hosts and host clusters that are in an untrusted Active Directory domain.|
|How to Add Hyper-V Hosts in a Perimeter Network in VMM||Describes how to add Hyper-V hosts that are in a perimeter network.|