New tools were added for moving around Hyper-V servers in Microsoft Virtual Machine Manager 2012. By using Microsoft Virtual Machine Manager 2012, admins can manage both individual servers and shared resources, which makes controlling core resources such as storage and networking easier. Microsoft's stated purpose for VMM 2012 is to manage private cloud deployments on top of virtual infrastructure.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Making private cloud computing administration easier for customers will help as businesses take advantage of the scalability and flexibility of cloud computing but do so within a private cloud in their own data center. In this excerpt from Chapter 7 of Microsoft Private Cloud Computing from John Wiley and Sons, learn how to add an existing Hyper-V server to the Virtual Machine Manager (VMM) fabric using both trusted and untrusted domains.
Adding a Hyper-V server in a trusted domain
The large majority of servers that you add to VMM 2012 are Hyper-V servers that are members of the same domain as the VMM server or a domain that is trusted by the domain containing the VMM server.
Before you can add Hyper-V servers that are located in a trusted domain, the following steps must be taken:
- Have one or more servers available that are joined to the same domain, or trusted by the domain that contains the VMM server.
- Check the requirements for supported versions of Hyper-V virtual-machine hosts (see Chapter 4).
- Check network access to the Hyper-V hosts that are added.
- Validate Hyper-V clusters before you add them to VMM (although you can do this from VMM later).
Do not add a Windows server without Hyper-V if the server is not available for a reboot (see the "Adding New Hyper-V Servers" section). To add one or more Hyper-V servers or clusters to the fabric of your VMM environment, follow these steps:
1. In the VMM 2012 console, select Fabric, and choose Servers from the Navigation pane. Select Fabric Resources from the ribbon, click Add Resources, and select Hyper-V Hosts and Clusters (Figure 7.1).
2. In the Add Resource Wizard in the Resource Location tab, choose Windows Server Computers In A Trusted Active Directory Domain. Click Next.
3. On the Credentials tab, enter the appropriate credentials to discover and add a Hyper-V host or cluster or, alternatively, select a Run As account. These credentials will allow you to add the VMM service account to the local Administrators group on the Hyper-V hosts. Click Next.
4. On the Discovery Scope tab, specify one or more Hyper-V servers and clusters. Each server or cluster must be on a separate line. You can identify the hosts by their name, their FQDN, their IPv4 address, or their IPv6 address. By default, the discovery process uses Active Directory (AD), but you can avoid this by checking the Skip AD Verification box. When you have finished your list, click Next.
If you have hundreds of servers, you might not want to specify the hosts for discovery by name; you can specify an Active Directory query to search for the Windows Serve computers. For example, you could search for hosts and clusters that start with the letters hv (hv*) (as shown in Figure 7.2) or that contain the letters hv (*hv*).
5. The Add Resource Wizard will generate a list of discovered computers; it is up to you to select which computers you want to add as hosts. The wizard will specify the FQDNs of the hosts, the clusters they are in, the OS, and the discovered hypervisor (in this case Hyper-V). As you can see in Figure 7.3, you can discover and add Hyper-V servers in the same step. Click Next.
6. On the Host Settings tab, you can specify the host group and VM placement settings. All of these selections can be changed later, so you can ignore most of the other fields. Interestingly, if you want to add a host previously managed by another VMM server, you can select Reassociate This Host With This VMM Environment. This could save some time because the VMM agent might still be installed. When you are done, click Next.
7. When you are satisfied with the results shown on the Summary tab, click Finish.
Adding a Hyper-V server in an untrusted domain
Some of your Hyper-V servers and clusters may be part of an untrusted AD domain. An example of this type of setup would be a hosting provider managing a customer's Hyper-V hosts from their own management domain without trusting the customer's domains.
To set up this type of Hyper-V host, take the following steps to integrate the hosts and clusters:
1. In the VMM 2012 console, select Fabric, and choose Servers from the Navigation pane. Right-click the host group to which you want to add the hosts or clusters; or select Fabric Resources from the ribbon, click Add Resources, and select Hyper-V Hosts and Clusters.
2. In the Add Resource Wizard in the Resource Location tab, choose Windows Server Computers In An Untrusted Active Directory Domain. Click Next.
3. On the Credentials tab, specify the appropriate credentials to discover the host in the untrusted AD domain. If the Run As account does not exist yet, you can create one. Select a suitable Run As account, and click Next.
4. Enter the FQDN or IP address of the Hyper-V host in the untrusted domain, and click Add. When you are done adding hosts, click Next.
5. Choose a host group and click Next.
6. Confirm the summary and click Finish. After a minute or so, you will see the Hyper-V in an untrusted AD domain in your Hosts view, as shown in Figure 7.4.
About the authors: Aidan Finn is an MVP in Virtual Machine: System Administration and leader of the Windows User Group in Ireland. Hans Vredevoort is a Cluster MVP and an infrastructure consultant. Patrick Lownds is leader of the Microsoft Virtualization User Group in the UK. Damian Flynn is infrastructure architect for Lionbridge Technologies and acting manager of Core Infrastructure Group.
Printed with permission from Sybex Inc. Copyright July 2012.Microsoft Private Cloud Computing by Aidan Finn, Hans Vredevoort, Patrick Lownds and Damian Flynn. For more information about this title and similar books, please visit www.Sybex.com/WileyCDA/.