Skip to main content

Hi

good day

this is my first post on Veeam communities

please I need help with adding HyperV hosts to my Veeam infrastructure 

 

I did an upgrade to Veeam 12 about a month ago. I realized that my HyperV hosts were offline. Of four, two are running Windows Server 2022.

 

i saw some things about DCOM Hardening which I don’t want to accept (yet)

can anyone help me with measures to resolve this problem?

 

Like the message states did you check permissions and expired password?  You need to use a local Administrator account on the host to connect.

Also check the Veeam logs here - C:\ProgramData\Veeam -- see if there is any information there.

Also ensure Firewall ports are open and not blocking.


thanks for your response.

I am yet to analyse the logs. I will update once I do this.

However, the local admin account was used, and the firwall was disabled.

So no port limits.


@ZadokZeePriest - if this is a local account being used, you may need to enable remote UAC on the server to connect with a local account. I just discussed this issue with another poster having an issue connecting to a computer with a local account:

Can you try the resolution there and see if it works?


@ZadokZeePriest - if this is a local account being used, you may need to enable remote UAC on the server to connect with a local account. I just discussed this issue with another poster having an issue connecting to a computer with a local account:

Can you try the resolution there and see if it works?

Ah yes always forget about good old UAC.  Try what Shane suggested for sure. ☝🏻


I still do forget Chris 😆


Okay thanks

im offsite now and would try these things later.

i disabled UAC before now while I was troubleshooting earlier.

 

a quick one: should the fact that it’s a Windows 2022 server matter in this sense? 


What you disabled was the UAC within control panel probably. What I’m suggesting you disable is REMOTE UAC from within the Windows Registry. No...2022 doesn’t matter. This is a known “issue” (security enhancement) for Windows devices for a while now.


Keep us posted on the result when you’re able to test this out.


 

Hi

I have done everything here, and the error is still the same.

 

  • I checked the EnableLUA from the remote registry and set it to 0
  • I ensured the local admin credentials are correct.
  • I also ensure the UAC from the Control panel was disabled

Error is the same.

I have tried both Veeam 11 and 12.

Same error.

 

The Veeam 12 is an upgrade of the Veeam 11.

 

All not working.


Like the message states did you check permissions and expired password?  You need to use a local Administrator account on the host to connect.

Also check the Veeam logs here - C:\ProgramData\Veeam -- see if there is any information there.

Also ensure Firewall ports are open and not blocking.

 

So what logs exactly am I examining here?

 

 


Can you get to the Admin$ share on the hyper-V host? \\192.168.1.126\Admin$ Also can you ping the host?

I suspect the windows firewall is enabled and you’ll need to disable it 1st if you’ve not allowed the ports. Veeam will create the firewall rules allowing you to re-enable the firewall after readding it back in.


What’s the format of the local credentials you’re using? It should be in the format of HOSTNAME\user (not .\user), or for a domain account DOMAIN\user.


Like the message states did you check permissions and expired password?  You need to use a local Administrator account on the host to connect.

Also check the Veeam logs here - C:\ProgramData\Veeam -- see if there is any information there.

Also ensure Firewall ports are open and not blocking.

 

So what logs exactly am I examining here?

 

 

Check the Backup folder to see if there is anything of relevance and also ensure the credentials as per Shane’s post for the format.


 

I was able to access the admin shares and the c shares with the same credentials giving me errors here.

The first screenshot was included to show that the username format was HOST\User 

the password used was also checked dI can’t put that out here]

 

The windows firewall is also disabled:

disabled windows firewall to ensure there are no issues.

 


The irony of this is,

I tested another backup software [I will keep the name]

I was able to discover the hosts and the VMs.

Same procedure.

‘No tweaking or reconfiguration.

 

Honestly, are we sure this is not really about Veeam and HyperV hosts?


 

Hi

I have done everything here, and the error is still the same.

 

  • I checked the EnableLUA from the remote registry and set it to 0
  • I ensured the local admin credentials are correct.
  • I also ensure the UAC from the Control panel was disabled

Error is the same.

I have tried both Veeam 11 and 12.

Same error.

 

The Veeam 12 is an upgrade of the Veeam 11.

 

All not working.

@ZadokZeePriest - this is not the correct Registry Key. Look at my approved answer in the post, or follow this Microsoft link to see the procedure, which is also referenced by a Veeam KB. You need to add the LocalAccountTokenFilterPolicy registry key and set it to 1 to disable remote UAC restrictions.


Additionally, make sure you have File and Print Sharing service enabled, as noted by prerequisites noted in the Guide.


i found some logs in the Backup folder.

The highligted parts seemed very noteworthy:

 


 

Hi

I have done everything here, and the error is still the same.

 

  • I checked the EnableLUA from the remote registry and set it to 0
  • I ensured the local admin credentials are correct.
  • I also ensure the UAC from the Control panel was disabled

Error is the same.

I have tried both Veeam 11 and 12.

Same error.

 

The Veeam 12 is an upgrade of the Veeam 11.

 

All not working.

@ZadokZeePriest - this is not the correct Registry Key. Look at my approved answer in the post, or follow this Microsoft link to see the procedure, which is also referenced by a Veeam KB. You need to add the LocalAccountTokenFilterPolicy registry key and set it to 1 to disable remote UAC restrictions.

It is enabled.

Same thing.


When you said the firewall is disabled was that on the VBR server or the host?

Are you adding the hyper-V hosts standalone or as a cluster?


When you said the firewall is disabled was that on the VBR server or the host?

Are you adding the hyper-V hosts standalone or as a cluster?

  • On the host.
  • Standalone.

The logs show references to a cluster …. was the name / ip previously assigned to a hyper-v cluster?

 

If you do nslookup on the host IP does it just return a single host name? or nslookup on the Name even :)


Hi

I did an NSLOOKUP

And found another appliance sharing that IP address.

 

I changed the IP

Error was still persistent.

 

 


Are you adding it by ip or host name as DNS will need time to update


If you want to use DNS run - ipconfig /flushdns to refresh it then ping the hostname to see if it resolves the new IP or not.


Comment