Server 2012 Terminal Server. What roles are needed?

I have been using terminal Server 2003 for long time and now I am upgrading to 2013.
Again Microsoft are so nice to change all the names of the roles and I have not been able to find a clear overview what I actually need to install to get it to work in the same way as in TS 2003

All I need is that teachers can sit at the school or home and login to their remote desktop. Thats all.
Nothing with apps and stuff like that.
Be aware that my Terminal Server is on the same server as DC. Aware that its not well seen to do it like that but only 5 teachers using it all the time and no real need for a 2nd server

When installing Remote Desktop Service there are thing like:
RD Web Access
RD Gateway
RD Lisencing
RD Connection Broker
RD Session Host
RD Virtualization Host

Very confusing for me

Is it not right that ALL i need to install is
RD Licensing
RD Session Host

I am asking as I have tried so many different combination but can not get it to work, so it helps knowing what I do need so I can work on narrowing down my problems

Kind REgards
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.

Cliff GaliherCommented:
So this is very easy *if* you are willing to do things the "right" way. You'll save yourself a ton of pain and will actually be faster.

First, don't run RDS on a DC. Just don't. Don't try to justify it. Don't try to force things to work. It is painful at best, and a security incident begging to happen at worst. And, with standard's 1+2 virtualization licensing, there is no cost or legitimate reason not to do things the right way.

Run a DC as a VM.

Install windows 2012 on your second VM and join it to the domain.

Run the add roles and features wizard on the new machine from server manager.

On the installation type screen, choose the remote desktop scenario type.

Choose the quick start deployment type.

Complete the wizard.

That will install *and* configure all the basic roles you need. Once done, you can add RDS licenses.

Yes, it adds the trivial complexity of a VM. But setup and ongoing management is *so* much easier. You'll not be banging your bead "experimenting" with finding the right combination.

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
morten444Author Commented:
Thanks for your reply
Yes this was what I did the whole time but no joy
later found out that clients are running an older client software and I therefore has to disable
 Network Level Authentication (NLA). for them to work. After disable it works fine
Thanks for your input on dedicated servers.
The trouth is that I have run it like this for 10years and running perfect untill the upgrade now.
I did have 2 servers enviroment but always got stuck in trouble shooting if the fault was DC or TS

I will consider this for next install after christmas. I have some VMware experiences so should go quite easy

Thanks again
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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.