SVC_VMMSrvc Login is not present on the second SQL Server node in the AlwaysOn High Availability Group, DEMO-SQL02: Object Explorer Object Explorer Connect Connect DEMO-SQL01 (SQL Server 11.0.3000 DEMO\ADMI DEMO-SQL01 (SQL Server 11.0.3000 DEMO\ADMINU Databases DEMO-SQL02 (SQL Server 11.0.3000 DEMO\ADMINU Security Databases Logins Security ##MS_PolicyEventProcessingLogin## Logins ##MS_PolicyTsqlExecutionLogin## Login missing from ##MS_PolicyEventProcessingLogin## DEMO\AdminUser DEMO-SQL02 ##MS_PolicyTsqlExecutionLogin## DEMO\DomainAdmins DEMO\adminuser DEMO\SVC_VMMSQLEng DEMO\Domain / Admins DEMO\SVC_VMMSrvc DEMO\SVC_VMMSQLEng DEMO\VMMInstallAccount DEMO\VMMInstallAccount NT AUTHORITY\SYSTEM NT AUTHORITYSYSTEM NT SERVICE\MSSQLSERVER NT SERVICE\MSSQLSERVER NT SERVICE\SOLSERVERAGENT NT SERVICE\SOLSERVERAGENT NT SERVICE\SQLWriter NT SERVICE\SQLWriter NT SERVICE\Winmgmt NT SERVICE\Winmgmt 2. Add the SQL Login for the SVC_VMMSrvc account by executing the following T-SQL in SQL Server Management Studio: CREATE LOGIN [DEMO\SVC_VMMSrvc] FROM WINDOWS Altering the recovery model of the VirtualManagerDB database to Full All databases that are to be included in a SQL Server AlwaysOn High Availability Group must use the Full recovery model. To alter the recovery model, open the first SQL Server node in SQL Server Management Studio, right-click on the database, and click on Properties. In the Select a page section, click on Options and change the Recovery model to Full, as shown in the following screenshot: Database Properties - VirtualManagerDB Select a page Script General Files Filegroups Collation: Latin1_General_100_CI_AS Options Change Tracking Recovery model: Permissions Compatibility level: SQL Server 2012 (110) Extended Properties Containment type: Mirroring Transaction Log Shipping Other options: Installing Virtual Machine Manager Creating a full backup of VirtualManagerDB In SQL Server Management Studio, perform a full backup of the VirtualManagerDB database. Adding VirtualManagerDB to AlwaysOn High Availability Grou