This documentation is archived and is not being maintained.

Planning for the VMM Server

Updated: October 21, 2008

Applies To: Virtual Machine Manager 2008, Virtual Machine Manager 2008 R2, Virtual Machine Manager 2008 R2 SP1

The VMM server is the hub of a VMM implementation through which all other VMM components interact and communicate.

The VMM server communicates with the VMM database and with managed computers—virtual machine hosts and library servers.

Before installing the VMM server, you must join the computer to a domain in Active Directory Domain Services (AD DS).

Installing the VMM server on a cluster has not been tested and is not supported. To make the VMM server highly available, it is recommended that you install it on a highly available virtual machine.

If you install the VMM server on a virtual machine, do not migrate this virtual machine to another host from within the VMM Administrator Console. If the virtual machine is highly available, do not migrate this virtual machine to another node on the cluster from within the VMM Administrator Console. When the VMM server is running on a virtual machine, it is literally managing itself; therefore, any migration, including quick migration, will result in a service interruption.

Multiple VMM Servers

For most VMM deployments, a single VMM server is sufficient and will enable you to scale out your VMM deployment by adding more virtual machine hosts and library servers as your virtual environment grows. Having a single VMM server with a single database enables you to centrally manage your entire virtual environment.

In the following situations, you might find having more than one VMM server beneficial:

  • When your environment extends beyond a central data center to include branch offices or other remote sites where you want to create, run, and manage virtual machines. This topology is discussed in more detail later in this topic.

  • When you want to manage a development and test virtual environment separately from your production virtual environment.

  • When your virtual environment grows beyond the supported maximum number of hosts and virtual machines, which is 400 hosts and 8,000 virtual machines.

  • When you have a large number of self-service virtual machines—in the range of 1,000 to 4,000 virtual machines—dedicated for use by self-service users.

If your business needs dictate that you install more than one VMM server, keep the following points in mind:

  • Each VMM server must be installed on a separate computer and each VMM server must use a separate VMM database. Multiple VMM servers can use the same database instance but cannot use the same database.

  • Each host or library server can be managed by only one VMM server at a time.

  • Multiple VMM environments are not integrated and cannot share data.

  • VMM does not provide a method for replicating physical files in the VMM library or metadata for objects that are stored in the VMM database. Physical files must be replicated outside of VMM and metadata must be transferred by using scripts or other means. VMM does not support DFS Namespaces (DFSN), formerly known as Distributed File System (DFS), or DFS Replication (DFSR).

Branch Offices or Other Remote Sites

If your environment extends beyond a central data center to include branch offices or other remote sites where you want to create, run, and manage virtual machines, there are additional topology considerations. For more information, see Planning for Branch Offices or Remote Sites.

See Also