 a new library share Share name: Share location: Select... Share description: Use an existing library share Share name: Share location: Share description: For highly available VMM management server installations, library shares must be created manually after Setup in the Library workspace in the VMM console. We recommend that you use highly available file server shares. Installing Virtual Machine Manager 5. After the installation is complete, the VMMMS role can be seen in Failover Cluster Manager, as shown in the following screenshot: Failover Cluster Manager Action Failover Cluster Manager Roles (1) DEMO-VMMCLUS.ad.demo Search Queries Roles Nodes Status Owner Node Priority Storage VMMMS Running Other DEMO-VMM01 Medium Networks Cluster Events If you examine the VMMMS role, you can see that only one node can possibly own the role at the moment. VMM Service VMMMS Properties General Dependencies Policies Advanced Policies Registry Replication Clear the check box if you do not want a node to host this resource or this clustered instance. Possible Owners: DEMO-VMM01 DEMO-VMM02 SQL Server tasks Once the first VMM installation is complete, there are a number of SQL Server tasks that need to be performed: 1. Add the SVC_VMMSrvc SQL Login to the other SQL Server node. Alter the recovery model of the VirtualManagerDB database to Full. 3. Create a full backup of VirtualManagerDB. Add VirtualManagerDB to the AlwaysOn High Availability Group. 5. Remove TmpVMMDB from the AlwaysOn High Availability Group. Chapter 1 Adding SVC_VMMSrvc SQL Login to the other SQL Server node The SQL Server Logins that have been created by the VMM installation process must be created in every other node of the SQL Server AlwaysOn High Availability Group. Failure to complete this will result in VMM inability to access the database should it failover. This is because unlike Failover Clustering, which protects the entire SQL Server instance, SQL Server AlwaysOn High Availability Groups only protect databases. As shown in the following screenshot, the 