Installing a Highly Available VMM Management Server
Updated: June 22, 2015
Applies To: System Center 2012 R2 Virtual Machine Manager
The procedures in this section describe how to do the following in Virtual Machine Manager (VMM):
Before you begin the installation of a highly available VMM management server, ensure the following:
All computers on which you are installing the highly available VMM management server meet the minimum hardware requirements and that all prerequisite software is installed on all computers, as described in the following topics:
For System Center 2012 and System Center 2012 SP1: System Requirements: VMM 2012 and VMM 2012 SP1
For System Center 2012 R2: System Requirements for System Center 2012 R2 and Preparing your environment for System Center 2012 R2 Virtual Machine Manager
You have created a domain account that will be used by the Virtual Machine Manager service. You must use a domain account for a highly available VMM management server. For more information about using a domain account, see Specifying a Service Account for VMM.
You have installed and configured the failover cluster on which you will install the highly available VMM management server. For more information about installing and configuring a failover cluster, see Overview of Failover Clusters, or Failover Clustering Overview.
You are prepared to use distributed key management to store encryption keys in Active Directory Domain Services (AD DS). You must use distributed key management for a highly available VMM management server. For more information about distributed key management, see Configuring Distributed Key Management in VMM.
You have a computer with a supported version of Microsoft SQL Server installed and running before you start the installation of VMM. For information about supported versions of SQL Server for the VMM database, see the following:
The following are some recommendations to consider for installing highly available VMM management servers in VMM:
We recommend that you use a highly available installation of SQL Server.
We recommend that the highly available installation of SQL Server is installed on a separate failover cluster from the failover cluster on which you are installing the highly available VMM management server.
We also recommend that you use a highly available file server for hosting your library shares.
The following are some additional considerations about highly available VMM management servers in VMM:
You can only have one implementation of a highly available VMM management server on a given failover cluster.
You can have VMM management servers installed on as many as sixteen nodes on a failover cluster, but there can only be one node active at any time.
You cannot perform a planned failover (for example, to install a security update or to do maintenance on a node of the cluster) by using the VMM console. To perform a planned failover, use Failover Cluster Manager.
During a planned failover, ensure that there are no tasks actively running on the VMM management server. Any running tasks will fail during a failover. Any failed jobs will not start automatically after a failover.
Any connections to a highly available VMM management server from the VMM console or the VMM Self-Service Portal will be lost during a failover. The VMM console will be able to reconnect automatically to the highly available VMM management server after a failover.
As of System Center 2012 Service Pack 1 (SP1), the VMM Self-Service Portal has been removed.