Proper Hyper-V domain setup

I am new to Hyper-V setup. I have maintained several systems that were already setup. I am setting up a brand new office. They want a domain controller/file server and a RDS server. I am going to build it on a host machine and make the file server and RDS server two separate Vms on the host machine.
In reading the Microsoft manual, they suggest joining the host to the domain before I create the VMs. Since these will be the only servers on the network, should I make the host a domain controller or wait until I create the DC VM and join it then?
Thomas AnthonySecurity AdministratorAsked:
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.

Cliff GaliherCommented:
Never make the host a DC. You can run a physical DC, a DC as a guest, or keep the host as a workgroup. All options are acceptable and have trade-offs, but none involve making the host a DC. In fact, no other roles should run on the host. So don't be tempted to nake it a file server or other services either. Just Hyper-V itself.

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:
I would either:

1. Use a real, physical DC, and join the HyperV machine to the domain. This need not be a "server", an old i3 desktop should be enough. I would advise HDD mirroring. Usually I would set the physical DC up holding all FSMO roles, and add a VM DC as well, just for redundancy. DCs in small networks are really not heavily used.

2. Leave the HyperV box out of the domain, just as a stand alone, and use a virtual DC.
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
That sounds good.
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
Windows Server 2012

From novice to tech pro — start learning today.