virtual machine not displayed in rdweb and no virtual template available in collection creation

I am attempting to setup RDS on a Server 2016 Standard server.  No virtualization on the server level, so it is the AD, DS, DHCP, and all the RDS.  I ran the rds setup in the Quickstart deployment, session-based and all looks ok.  The applications and physical computers appear when go to the rdweb.  I wanted to also have 1-2 virtual machines available on the rdweb.  I installed the hyper-v role on server and have setup 1 virtual machine - Windows 10 Pro evaluation.  I can get into that fine on the server through hyper-v manager.  When I try to add a virtual desktop collection in rds - edit deployment, I get to the step of selecting a desktop template and nothing will show up in that window.  I have joined the vm1 to the domain, made sure I did the sysprep tool.  I am wondering if it is possible to have this vm show up when log into rdweb along with the physical desktops?  Also, can I accomplish this when I have one server doing all of this?  There are 5-7 users in 2 different physical offices.

Thanks in advance for any advice.  I am new to virtualization.
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:
Yep.  Don't do that.

Hyper-V should only ever be Hyper-V.  No exceptions.  Full stop.

A domain controller should only be a domain controller.  Small exceptions, but RDS is definitely never one of them.

Either one of those really screws up the system in ways you can't predict.  Both is just plain bad.

What you need to do, if you are going to do this right.

Physical Server-HyperV (and the RDVH role because technically that just does Hyper-V stuff)

VM-Server #1 ADDS, maybe DHCP, maybe RDS support roles *maybe* ...I don't like public facing roles on a domain controller though, and RDWeb (IIS) and RDGateway are both public facing.  

VM-Server #2 should be your session host.  Better to stuff the other RD stuff here if you can't justify a 3rd server VM.

Client OS VMs as desired.  

You stuffed WWWAAAYYY too much on the physical box, and broke a couple of cardinal rules on top of it.  You will not get good results 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
natjohnAuthor Commented:
Would I help the situation if I removed the AD and DC and created a workgroup instead of a domain?  Then would it be more acceptable to place the rds services on the server?  And completely remove hyper-v.  If so, would an acceptable practice to be to remove these roles rather than completely wipe out all?  If I remove those roles, will my SSL certificates stay in place?
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.