Skip to main content
  • EN

Hey Team, 

We use strictly hyper v server core hosts to house vms in the environment.

 

I observed a few things?

  1. Veeam successfully creates repos both azure and lcoal
  2. Veeam successfully added all the hyperv host servers showing all vms under each
  3. Error code - 32774 - Performing a Hyper V Backup Type for a vm under any host to a local repo FAILS - i observe a “logon as a service” error then i am directed by veeam support to read - https://learn.microsoft.com/en-us/troubleshoot/windows-server/virtualization/starting-or-live-migrating-hyper-v-vms-fails
  4. Performing a Windows Agent type backup type where i manually added the same vm and others (housed under the hyperv core server) with domain firewall off completes successfully, beautifully even.
  5. Performing a backup from the vm under the hyperv host server to azure/object type storage works perfectly
  6. Performing a Hyper V VM restore from Azure back to Hyper VM FAILS - logon as a service error / logon failure
  7. Performing a hyper V VM restore from local repo to another hyper v host FAILS - logon as a service error / logon failure

Article below does NOTHING for me as the NT Virtual Machine\Virtual Machines is NOT listed in my DC when I try to add to the GPO - logon as a service option. I am also not allowed to move the hyper v host to a new OU, rules of the bosses.

 https://learn.microsoft.com/en-us/troubleshoot/windows-server/virtualization/starting-or-live-migrating-hyper-v-vms-fails

 

When i navigate to secpol.msc and try to add or even remove entries from the local policies->user rights assn ->logon as a service i get this notification(Clearly managed by AD/DC), i get the below message:

 

Instant VM Recovery headache:

 

I normally fix these issues quickly. I could remove/disable the GPO: User rights assignment/Log on as a Service from the DC, followed by a GPUpdate / Force on the Hyper-V machine, but I cant do that here.

Support has provided some response, but idk. I am here feeling a bit drained now.

 

 

Good day,

I asked for permission to perform below change and it was granted. Backups are now moving fast and efficient. I have not tried restore jobs yet. I will update.

 

Method 1

Place the computer account for the Hyper-V Host in an Organizational Unit (OU) that doesn't have any policies applied, that manage user rights, and then run gpupdate /force command or reboot the computer. It should remove the user rights applied by policy and allow user rights defined in the local security policy to take effect.

This means that ALL my hyper v hosts will have this “logon as a service” disabled.

Comment


Terms & Conditions