This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 32%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Hello!
I have started to install SCVMM, before assembling two nodes into a cluster I have a question about the database.
The instructions say:
Configure the database as follows:
1.Create a new database with settings: Name: VirtualManagerDB; Collation: Latin1_General_100_CI_AS, but aligned with the specific SQL Server instance collation.
2.Grant db_owner permissions for the database to the VMM service account.
3.In VMM setup, you'll select the option to use an existing database and specify the database details and VMM service account as the database user.
In step 2
you need to create a separate service account for SCVMM and make it the owner of the database?
Then when installing SCVMM create another service account or use one and the same with MS SQL server?
Please tell me how to do it correctly.
As I understood through this service account SCVMM will always access the database.
https://zcusa.951200.xyz/en-us/system-center/vmm/plan-install?view=sc-vmm-2022
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 92%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EXM%3C/text%3E%3C/svg%3E)
Hello!
You're on the right track with your SCVMM installation. Here’s a detailed breakdown to help you:
db_owner permissions to this SCVMM service account for the VirtualManagerDB database. This is crucial because SCVMM requires full control over the database to function correctly.This service account will continuously access the database, ensuring SCVMM can perform its operations seamlessly.
Hello!
Thank you for your help.
You helped me understand my next installation steps in more detail.
Please tell me I have configured the Allways On availability group in MS SQL Server.
Do the steps above need to be done on both nodes or only on the Primary?
When configuring SCVMM with an Always On availability group in SQL Server, you need to perform the steps on the primary node.
Create the VirtualManagerDB database on the primary node.
Grant db_owner permissions to the SCVMM service account on this database.
Add the VirtualManagerDB database to the Always On availability group. This will ensure that the database is replicated across all nodes in the availability group.
Use the same SCVMM service account for accessing the database on all nodes. This account will have the necessary permissions on the primary node, and these permissions will be replicated to the secondary nodes as part of the availability group configuration.
Dear XinGuo-MSFT ,
I apologize,
When installing VMM on the first host, I cannot connect to the database if I specify the MS SQL cluster name.
As indicated in paragraph number 8 of this instruction
https://zcusa.951200.xyz/en-us/system-center/vmm/ha-server?view=sc-vmm-2022
8.In Database configuration, specify the database to use for VMM. The database should be highly available and deployed in a separate failover cluster. This dialog appears if VMM isn't clustered or if it's clustered but not using Always On Availability Groups. Specify the cluster name.
But, if I simply specify the name of the first node instead of the cluster name (which is incorrect according to the instruction), this step of the installation is successful.
Please tell me what could be the cause of this error?
This is my first installation of SCVMM in a cluster)
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.