Cannot login to VMM \ Server Core edition with other accounts

Question

I recently built a VMM 2019 \ UR2 server on 2019 Core edition using SQL 2019. All works ok except i can only login to the console using the VMM service account.

If i try another account i added into the Administrator User Role group, i get

VMM is unable to perform this operation without a connection to a Virtual Machine Manager management server.

Use the Get-VMMServer cmdlet or the -VMMServer parameter to connect to a Virtual Machine Manager management server. For more information, type at the command prompt: Get-Help Get-VMMServer -detailed.

ID: 1615

I never had this issue before when i ran "desktop version" Server 2019, what am i missing from Core edition?

Firewall ports are controlled via GPO 8100 etc and the VM is under the same group but then again, it works perfectly fine under the service account credentials.

Anyone seen this before? Never installed VMM on core edition before, any tips?

Thanks

Answer 1

Hi,

There is a similar thread you can reference:

Error ID 1615 VMM is unable to perform this operation

Answer 2

Virtual Machine Manager setup creates a login for the VMM service account and adds it to db_owner role in the VMM database. MemberShip in the db_owner role is required for the service account of SCVMM. Removing that account from the db_owner role triggers Login FAilures . Assigning any combination of roles with less permissions and individual permissions instead of db_owner for the VMM service account will not work and its not supported.

Whenever user connect to SCVMM through the console or a command shell, the VMM service dynamically adds the user to the VMM database. When the user disconnects, the VMM service automatically removes the user from the VMM database.

As a connected user performs actions, the VMM service runs EXECUTE AS statements to run database stored procedures on the user's behalf. For it to work, the VMM service account must have the IMPERSONATE permission on the user. Non-dbo users don't have this permission.

You can't work around this limitation by explicitly granting the IMPERSONATE permission to a non-dbo service account because you can grant IMPERSONATE only on an existing principal. Because the VMM service dynamically adds and removes database users, you can't grant IMPERSONATE permissions on them ahead of time. The user must exist at the time you grant permissions.

The SQL Server language reference specifically documents the requirement that a principal must exist when the IMPERSONATE permission is granted to the principal. For more information, see Specifying a User or Login Name.

]2

For your information this is my SCVMM service account in your case that could be different. Please check SCVMM service account of “System Center Virtual Machine Manager” service, account, it could be different in your infra.

Make sure your db_owner is assigned correctly.

Thanks regards,
Nitesh Pal