rdweb, terminalserver, domain for multiple customers

Hi, i will setup a terminalserver/rdweb enviroment for multiple customers. Is this a ok way to do it?


rd web access and rd gateway server


Domain: domain.local
name: RDDC1.domain.local
Role: Active directory, DNS

name: RDCB1.domain.local
Role: RD Connection Broker

name: RDLS1.domain.local
Role: RD Licensing server

Child domain: cust1
name: RDDC2.cust1.domain.local
Role: Active directory, DNS

name: RDSH2.cust1.domain.local
Role: RD Session Host Server

Child domain: cust2
name: RDDC3.cust2.domain.local
Role: Active Directory, DNS

name: RDSH3.cust2.domain.local
Role: RD Session Host Server

This way each customer could have there own domain controller/server and there own terminalserver/rdweb server. And all users could use the same address to get to there terminalserver, https://rdweb.domain.local/rdweb
I need each customer to have there own domain controller/server since thay have some program that need that, they also need there own terminalserver.

Should i use child domain or tree domain? Is it possible to do it with tree domain and get one rd web access, rd gateway and connection broker server to function for all users/customers?
Who is Participating?
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.

Manjunath SulladTechnical ConsultantCommented:
First thing you need to analyze the capacity, Like How many external customers will be connecting to servers, All customers will connect at a time or What will be load on server.

Based on the capacity review, You can plan for architecture.

Seems to above architecture is fine,

But I am suspecting no need to configure all these servers, You can add these roles on same server, Instead of configuring another DNS, AD server.

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
per-wAuthor Commented:
The customers need there own AD server, the program cant be installed for more customers on same server, so thats why. I dont know if i need to have DNS on each child domian, but it was setup by the AD setup so i didnt choose it. This servers will be VMs. I know that Active Directory (server1) and Connection Broker and Licensing server could be on same server.
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.