Jump to content

Recommended Posts

Posted

Godo mornign all,

 

Since running an in-place upgrade frm Server 2016 to Server 2019 on our VMM server, SC-VMM service failed to restart. I've had to remove and re-install the VMM Console and servce on this machine, linking it to the same database that was used previously.

 

I'm not getting host not responding on all of the VM's in this cluster with an access denied error 20406 on the job log.

 

I've tried changing the accounts the service run under (even going so far as setting a domain admin account to test with, and still no luck.

 

I've tried updating the Run-as account in the cluster properties, yet after saving the updated cluster settings, if I go back in it has reverted to the previous settings.

 

I'm at a loss where to look next.

 

This is our smaller cluster we use for tesitng and an extra DC, however we need to run the same process on our main cluster and I'm concerned if things go wrong on that one, then it's going to be a much bigger issue

 

Can anyone help?

 

Cheers

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...