Discussions specific to the Microsoft Hyper-V hypervisor
Post Reply
Posts: 1
Liked: never
Joined: Jul 20, 2020 1:41 pm
Full Name: Geoff

New Hyper-V Server Wizard - Invalid Namespace

Post by dvg »


Case #04288000

I have a bare metal Server 2016 Std with one Server 2016 Std Hyper-V instances running.

Base Server - B&R installed on this physical machine, not on Domain.
Hyper-V Instance - AD DC, DNS Server.

Is it best practices to have B&R installed on the bare metal server, outside of the VM?

I'm getting an error when using the New Hyper-V Server wizard when using the correct admin credentials for the VM that says 'Invalid namespace'. Support says it is a DNS issue so am I not using best practices?

I question the validity of the DNS issue, because if I use incorrect credentials, the wizard gives me an "Access denied" error says I need to have local admin privileges.

I have tried using the VM IP, netbios and FQDN - all return exact same errors.

Thanks for your feedback.

Egor Yakovlev
Veeam Software
Posts: 1701
Liked: 383 times
Joined: Jun 14, 2013 9:30 am
Full Name: Egor Yakovlev

Re: New Hyper-V Server Wizard - Invalid Namespace

Post by Egor Yakovlev »

Hi Geoff,
- yes, it is a good idea to keep VBR Server aside of production infrastructure, however it has nothing to do with "Proper DNS resolution should be in place" requirement. It should work both sides, so Veeam must be able to resolve names of production servers in question(Hyper-V host in this case) and back. How it is done - it is your choice, via shared DNS server or local hosts file edit. Please confirm Veeam Server can be resolved into IPv4 address from Hyper-V host machine, and if Hyper-V host server name resolves into IPv4 address from Veeam server.
- make sure credentials are in domain\username format. That is quite common mistake using "Administrator" as a user will lead nowhere, it must be either ".\Administrator" or "HV-Host-Name\Administrator" for local admin on Hyper-V host or "YourDomain\Administrator" for a domain authentication.
- make sure required firewall rules are set on said Hyper-V host, as in most cases by default, Microsoft will block 99% communication between Domain and Workgroup computers.
- also worth checking "LocalAccountTokenFilterPolicy" registry key, as it is commonly works out all Domain-Workstation authentication problems.

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 9 guests