FIX: VMM won’t start, error 1067

I’ve recently configured VMM in the restricted environment where you always need to ask IT staff to delegate rights for service and install accounts in order to make SQL Server and VMM Server working. The requirements for DKM container or SPN registration are described at many sites, blogs including official Microsoft docs, but I  faced with a new problem just after VMM installation.

I couldn’t start VMM service. Checked SQL Server services and communication from VMM Server, VMM database properties  and etc…and did not find any unusual or wrong in my configuration. I went then to the VMMLogs and reviewed the report generated after the VMM service start attempt and found interesting strings:

System.AggregateException: One or more errors occurred.—> Microsoft.VirtualManager.DB.CarmineSqlException: The SQL Server service account does not have permission to access Active Directory Domain Services (AD DS).
Ensure that the SQL Server service is running under a domain account or a computer account that has permission to access AD DS.

The following steps helped me to resolve the error:

  • Open Active Directory Users and Computers
  • Expand Builtin container and locate Windows Authorization Access Group
  • Add SQL Service account to the Windows Authorization Access Group
  • Start SCVMMService

or use PowerShell (RSAT-AD-Tools are required):

Add-ADGroupMember sqlsvc -Members “Windows Authorization Access”

Start-Service scvmmservice

 

Switching dynamic IP to static in VMM

Creating a VM from virtual disk or existing virtual machine is a basic task in every VMM infrastructure. What if you want to assign IP from static pool instead of dynamic which is just the one option by default for such deployments? Well,doing this in wizard, will end by receiving a warning:“You cannot customize IP settings for a stored virtual machine or a virtual hard disk. You can only customize IP settings if you use a VM template” and static IP pool will be grayed out.

vmm static ip pool greyed out

If you don’t want to create VM template for some reason, PowerShell will help you to fix this behavior. Just start VM creation wizard, edit hardware and other settings and leave Dynamic IP for network adapter. Then don’t run VM and execute the following PowerShell script:

#Get VM
$vm=Get-SCVirtualMachine -Name "rl-srv-01.demolab.com"

#Get static pool which you are going to use with that VM (here I'm filtering pool by address range)
$pool=Get-SCStaticIPAddressPool|? {$_.IPAddressRangeStart -eq "10.10.25.1"}

#Grant changes
Grant-SCIPAddress -GrantToObjectType "VirtualNetworkAdapter" -GrantToObjectID $vm.VirtualNetworkAdapters[0].ID -StaticIPAddressPool $pool

#Update network adapter settings
Set-SCVirtualNetworkAdapter -VirtualNetworkAdapter $vm.VirtualNetworkAdapters[0] -IPv4AddressType static

Go back to the VM settings and check changes that script has successfully made:

vmm dynamic to static ip pool result