 no special SQL collation requirements for VMM. When installing SQL Server, it will determine the appropriate collation according to the language of the operating system. Chapter 1 During the installation, the SVC_VMMSQLAgnt account was assigned to run the SQL Agent Service and the SVC_VMMSQLEng account was assigned to run the SQL Server Service, as shown in the following screenshot: Service Accounts Collation Microsoft recommends that you use a separate account for each SQL Server service. Service Account Name Password Startup Type SQL Server Agent DEMO\SVC_VMMSQLAgnt Manual SQL Server Database Engine DEMO\SVC_VMMSQLEng Automatic SQL Server Browser NT AUTHORITYALOCAL SERV... Disabled Once SQL Server has been installed, then VMM can be installed. VMM installation Ensure the Install_VMM and SVC_VMMSrvc accounts have been granted administrative rights to the server where VMM will be installed. Additionally, the Install_VMM account requires the following permissions in the SQL instance: The ALTER ANY LOGIN permission on the server or membership in the securityadmin fixed server role The CREATE DATABASE, CREATE ANY DATABASE, or ALTER ANY DATABASE permissions Alternatively, the VirtualManagerDB database can be precreated in the SQL instance, in which case the Install_VMM account would only require the ALTER ANY LOGIN permission on the server or membership in the securityadmin fixed server role. The VMM Service Account (SVC_VMMSrvc) and the Install_VMM accounts require SQL logins to be created and have the db_owner rights assigned to VirtualManagerDB. New Database Select a page Script General Options Filegroups Database name: VirtualManagerDB Owner: DEMO\SVC_VMMSrvc Use full-text indexing Database files: Logical Name File Type Filegroup Initial Size (MB) Autogrowth / Maxsize VirtualMana PRIMARY By 1 MB, Unlimited VirtualMana. Not Applicable By 10 percent, Unlimited Installing Virtual Machine Manager The SVC_VMMSrvc only has the public Server role, as shown in the following screenshot: Login Properties - DEMO\SVC_VMMSrv