Adding hyper v host fails with "invalid credentials" or "spedified host is not a hyper v server"
Adding hyper v host fails with "invalid credentials" or "spedified host is not a hyper v server"
Best answer by Danyang007
Hello Guys,
I finally resolved the issue thanks to
The resolution is to install Microsoft KB 5034127 on the Veeam server. i restarted after the installation and everything went smoothly.
Got it fixed with the help of Veeam support.
In 2022 there was a MS update that hardened DCOM security. It started out as disabled by default, then it turned into being enabled by default with a reg key you could implement to bypass it. In March of 2023, an update enforced it. This DCOM hardening was preventing the non-domain-joined Veeam server from passing the target server’s local admin credentials through to join it to the backup infrastructure.
Further details: KB4376: Access to Hyper-V or Veeam B&R Components Fails After DCOM Hardening is Enabled
The resolution is to install Microsoft KB 5005102 on the Veeam server: Microsoft Update Catalog
This information was really hard to come by, so I hope this makes it easier for the next person to resolve their issue. This KB does not get applied through normal monthly updates, so simply patching the server will not help.
Thanks everyone for your input along the way!
Thank you guys, you were all amazing.
Comment
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.