When trying to add a Hyper-V host to VBR 13 from either the web console or GUI, we receive the error ‘Samba failed with error: NT_STATUS_ACCESS_DENIED - Can’t load /etc/samba/smb.conf. The same error occurs when trying to add MS Server 2022 and 2025. The MS server has it’s firewall disabled.
Anyone else experienced this issue?
Dave
Best answer by Dave Bartlett
The Veeam Console ‘Create Windows Deployment Kit’ option isn’t functioning and throws the error below.
If done through the web GUI you’ll get a zip file which after extracting on the HV host will give you the following folder structure.
Running SetUp.bat deploys the installer service and OpenSSL and then imports the certificate. Once done, in the Veeam Console or web UI a server can be added as long as the method is ‘Connect using certificate-based authentication’ as shown below.
+21I have seen this before. Let me dig through my notes to see what fixed it. I had to mount the ISO file on the host and install a few packages.
+21Actually did you try adding the server via the Veeam Backup Console install? Not the WebUI as that is limited.
Hi Chris, same result either from the console or web GUI. I’ll take a look at the ISO to see what’s available for the HV host.
Dave
+21Hi Chris, same result either from the console or web GUI. I’ll take a look at the ISO to see what’s available for the HV host.
Dave
I actually looked at the ISO but did not see anything. Will keep looking.
Ok, I’ve got things working using the deployment kit and installing on the HV host.
Thanks for your input Chris!
Dave
+21Ok, I’ve got things working using the deployment kit and installing on the HV host.
Thanks for your input Chris!
Dave
Not a problem Dave. What was the fix just out of curiosity as I found some notes from someone at Veeam. LOL
The Veeam Console ‘Create Windows Deployment Kit’ option isn’t functioning and throws the error below.
If done through the web GUI you’ll get a zip file which after extracting on the HV host will give you the following folder structure.
Running SetUp.bat deploys the installer service and OpenSSL and then imports the certificate. Once done, in the Veeam Console or web UI a server can be added as long as the method is ‘Connect using certificate-based authentication’ as shown below.
+21Ah yes that was the fix and in my notes. Using the WebUI not console. Great and glad you got it fixed.
Hello!
I have just installed the Veeam Software Appliance (Backup Server, v13.0.0.4967) as I am working on comparing Veeam to Rubric as our Rubric renewal is coming soon. I used the ISO image and the installation went smoothly. I then installed a Hardened Repository using the Veeam Infrastructure Appliance. Added it to the Veeam Backup Server and that went well.
I have also installed a new Windows 2025 Datacenter standalone Hyper-V server. I downloaded the Veeam Deployment Kit from the Web UI, by clicking on the link that is found in the Managed Servers tab. The resulting zip file downloaded the windows deployment kit, which I copied over to the new Windows Hyper-V server and installed successfully.
When I go to add the Hyper-V server as a manager server I performed the following:
Has anyone else experienced this. These three installs were all new and I am not sure what else to try.
Thanks, Vince.
Hello!
I have just installed the Veeam Software Appliance (Backup Server, v13.0.0.4967) as I am working on comparing Veeam to Rubric as our Rubric renewal is coming soon. I used the ISO image and the installation went smoothly. I then installed a Hardened Repository using the Veeam Infrastructure Appliance. Added it to the Veeam Backup Server and that went well.
I have also installed a new Windows 2025 Datacenter standalone Hyper-V server. I downloaded the Veeam Deployment Kit from the Web UI, by clicking on the link that is found in the Managed Servers tab. The resulting zip file downloaded the windows deployment kit, which I copied over to the new Windows Hyper-V server and installed successfully.
When I go to add the Hyper-V server as a manager server I performed the following:
Has anyone else experienced this. These three installs were all new and I am not sure what else to try.
Thanks, Vince.
Be sure to disable NETBIOS resolution on any NIC you’re not using for backup. You can run “nbtstat -n” and if your NETBIOS name resolves to multiple IPs, that’s your issue. Just disable it where not needed, should only be enabled on the IP used for backup.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
