Should the Hyper-V manager be a domain controller for a different domain to its guest VMs?

I have a Windows 2016 Hyper-V manager with two guest VMs. One guest VM is a Domain Controller and the other is a SQL DB server which is a member of the domain.
The Hyper-v server is in a Workgroup. Should I make the Hyper-V server a Domain Controller for a separate domain and then make resources such as a NAS, members of that domain?
I'd like to access the NAS from the Hyper-V manager for VM builds and Disaster Recovery and I'd also like to access the NAS from the Guest VMs for software images.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

IvanSystem EngineerCommented:

I would like to point to one thing, regarding your setup and licensing. By default, you can use 1 Windows 2016 standard license to build 2 VM, but that would require that you do not install anything on Hyper-V host.

Since you have 2 VM, does this means that you have 1 Windows license? And if so, then that would mean that you will need 1 more license if you want to deploy DC role on Hyper-V server.

PS: I dont see why would you create new domain, just for NAS access. You can always use non AD auth, like basic or such, and access NAS from Hyper-V that way.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Mal OsborneAlpha GeekCommented:
Having multiple AD domains would be an odd way to go.

It is pretty common to have HyperV machines left as stand alone servers in a workgroup, particularly when one is running the only DC. Whiel it is possible the add the HyperV machine to the domain controlled by the DC running on it, that can cause a few complications, and gets messy.

I tend to recommend a stand alone machine as a DC, holding all FSMO roles, and configured to boot a few mins before anything else. That tends to eliminate a heap of problems and make troubleshooting and DR easier. A second DC on the HyperV machine is fine.

DCs don't typically do much, and are not heavily loaded. Unless you have thousands of users, even and old desktop PC can easily handle the load.  If you have a second DC on the HyperV machine, it is simple to recreate another DC should the need arise, so the stand alone DC need not be incredibly reliable. On the other hand,  there are a heap of "baby" servers made by most venders, a "real" server with duel PSUs, hardware mirroring and the usual monitoring hardware, redundant fans ect is possibly worthwhile.
ClintonKAuthor Commented:
Thanks both.
Forgot about the licencing issue. I only have a licence for Hyper-V and two x Guest VMs so a DC on the Hyper-V would blow the budget.
It was just a moment of musing when I considered the possibility or making the manager a DC.
I'll leave as-is.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.