Getting ready
Before you start the installation of the VMM management server, ensure that your SQL server is up and running.
From the VMM server, run the following at Command Prompt:
Telnet SQL-Server 1433
If you get a black screen after typing the above and hitting Enter, the communication is established. If you receive the message Could not open connection to the host, the connection has failed and you need to look at the SQL services or the firewall rules of your SQL Server and proceed with the VMM installation. You can also use the Test-NetConnection SQL-Server -Port 1433 PowerShell command to check the communication between VMM and SQL. If TcpTestSucceeded has the value TRUE, VMM can reach SQL Service. Otherwise, the following message will be shown: WARNING: TCP connect to SQL-Server:1433 failed.
Telnet SQL-Server 1433
If you get a black screen after typing the above and hitting Enter, the communication is established. If you receive the message Could not open connection to the host, the connection has failed and you need to look at the SQL services or the firewall rules of your SQL Server and proceed with the VMM installation. You can also use the Test-NetConnection SQL-Server -Port 1433 PowerShell command to check the communication between VMM and SQL. If TcpTestSucceeded has the value TRUE, VMM can reach SQL Service. Otherwise, the following message will be shown: WARNING: TCP connect to SQL-Server:1433 failed.
Get your computer updated by running a Windows update and restart if requested, before continuing with the VMM installation.
Ensure that the following is true:
- The server meets the minimum system requirements.
- You have created the domain account that will be used by the VMM Service (for example, rllab\vmm-svc). Do not log in with this account. The VMM service account will be used in the VMMDKM wizard page.
- The installation account (for example, rllab\vmm-admin) is a member of the local Administrators group. The account you are going to use for VMM is required to be a member of the local Administrators group on the computer you are installing VMM in. Add RLLAB\vmm-svc as well, which is the account we created previously to be the SCVMM service account.
- You have closed any open applications and that there is no pending restart on
the server. - The computer is a member of the domain. In our case, we are using RLLAB.COM as the domain.
- You have created a DKM container in AD DS before installing VMM. Otherwise, if the user account running setup (RLLAB\vmm-admin) has the right to create the VMMDKM container in AD DS, you don't need to have created it previously.
If the setup does not complete successfully, check the logs in the %SYSTEMDRIVE%\ProgramData\VMMLogs folder.