There's more...
At the VMM management server installation, on the Configure service account and distributed key management page, you will be required to provide an account for the VMM service account. The account could be either the local system or a domain account (recommended):
- The domain account that you create specifically to be used for this purpose, as per best practice, must be a member of the local Administrators group on the computer.
- You are required to use a domain account for the VMM service if you want to use shared ISO images with Hyper-V VMs.
- You are required to use a domain account if you want to use a disjointed namespace.
- You are required to use a domain account if you want to install a highly available VMM management server.
- Changing the account identity of the VMM service after the VMM installation is completed, is not supported. If you need to change it, you must uninstall VMM and then select the Retain data option to keep the SQL Server database and the data, and then reinstall VMM by using the new service account.
If you get the following warning at the end of the installation:
The Service Principal Name (SPN) could not be registered in Active Directory Domain Services (AD DS) for the VMM management server.
Take the following steps in order to register the Service Principal Name (SPN) and Service Connection Point (SCP), or else no computers will be able to connect to the VMM management server, including the VMM console:
- Open a command prompt with administrative rights (Run As).
- Create the SPN for the VMM management server by running the following command:
setspn.exe -S SCVMM/vmm-mgmt01.rllab.com rllab\vmm-svc setspn.exe -S SCVMM/vmm-mgmt01 rllab\vmm-svc
Check if the VMM Service has the registered SPNs now:
setspn.exe -l rllab\vmm-svc
It should return something like this:
Registered ServicePrincipalNames for CN=VMM Service Account,OU=Service Accounts,DC=rllab,DC=com:
SCVMM/vmm-mgmt01
SCVMM/vmm-mgmt01.rllab.com
- Add the SPN values (REG_SZ) to the Registry key:
Software\Microsoft\Microsoft System Center Virtual Machine Manager Server\Setup\VmmServicePrincipalNames
You can use PowerShell to complete this registry task:
Set-ItemProperty -Path 'HKLM:\Software\Microsoft\Microsoft
System Center Virtual Machine Manager Server\Setup\' -Name
VmmServicePrincipalNames -Value "SCVMM/vmm-mgmt01,SCVMM/vmm-
mgmt01.rllab.com"

- Configure the SCP by running the following command:
C:\Program Files\Microsoft System Center 2016\Virtual Machine Manager\setup\ConfigureSCPTool.exe -install
To verify VMM SCP, you can check the following object: CN=MSVMM,CN=<VMM hostname>,CN=Computers,DC=rllab,DC=com using ADSI Edit (adsiedit.msc) connected to the Default Naming Context as shown in the following screenshot:
