VMM

This article was sent around internally a week or so back, and having given it a quick read, I thought it was useful to share.

http://technet.microsoft.com/en-us/library/cc793146.aspx

The article is divided into a couple of key sections:

  • Planning for the VMM Server
  • Planning for the VMM Library
  • Planning for Hosts and Host Groups
  • Planning for High Availability
  • Planning for Branch Offices or Remote Sites

Each is as important as another, however I’d like to draw your attention to the ‘Planning for Hosts and Host Groups’ section, as this gives some interesting information on how your hosts can be distributed within Active Directories, or even, across Active Directories.  The full list of supported host types is as follows:

  • Windows Server–based hosts that are located in an Active Directory Domain Services (AD DS) domain that has two-way trust with the VMM server’s AD domain.
  • Windows Server–based hosts that are located in an AD domain that does not have a two-way trust with the VMM server’s AD domain.
  • Windows Server–based hosts that are located on a perimeter network.
  • Windows Server–based hosts that are in a disjointed namespace, where the host’s fully qualified domain name (FQDN) resolved from the domain name service (DNS) is not the same as name obtained from AD.
  • VMware ESX Server hosts located anywhere in your environment.

I’m not 100% sure on how VMM handles cross-forest trusts, but this is a question I’ve asked internally and I’m waiting on a response.  Either way, you’ve still got a fair amount of scope and flexibility when it comes to management across AD.

The article goes on to talk about Library Servers, Utilisation of Memory and Resources and more, so definitely worth a read if you can spare the time.

http://technet.microsoft.com/en-us/library/cc793146.aspx