rprise Edition) for VMM to be installed against. It is assumed that you have installed SQL Server 2012 SP1 on both of your cluster nodes, but have not created the AlwaysOn Availability Group and the associated Listener. Now, you need to perform the following steps: On the first SQL node, for this example DEMO-SQL01, open the SQL Server Configuration Manager application, right-click on the SQL Server Service instance under SQL Server Services and click on Properties. On the AlwaysOn High Availability tab, check the Enable AlwaysOn Availability Groups checkbox. Then, restart the SQL Server service after enabling this checkbox. SQL Server (MSSQLSERVER) Properties Log On Service FILESTREAM AlwaysOn High Availability Startup Parameters Advanced Windows failover cluster name: DEMO-SQLCLUS Enable AlwaysOn Availability Groups Allow this instance of SQL Server to use availability groups for high availability and disaster recovery. 2. Perform the same task on the second SQL Server node. On the first SQL node, open SQL Server Management Studio and create a database called TmpVMMDB. A database is required to create the AlwaysOn Availability Group against. Once VMM has been installed, the database can be removed. New Database Select a page Script General Options Filegroups Database name: TmpVMMDB Owner: <default> Use full-text indexing Database files: Logical Name File Type Filegroup Initial Size (MB) Autogrowth / Maxsize TmpVMMDB PRIMARY By 1 MB, Unlimited TmpVMMDB Not Applicable By 10 percent, Unlimited Installing Virtual Machine Manager Ensure the Recovery Model dropdown of the database is set to Full. Perform a full backup of the TmpVMMDB database. If you do not do this, you will not be able to create the Availability Group. Database Properties - TmpVMMDB Select a page Script General Files Filegroups Collation: atin1_General_CI_AS Options Recovery model: Change Tracking Permissions Compatibility level: SQL Server 2012 (110) Extended Properties Containment type: Mirroring Transaction Log Shipping Other options: On the firs