Should terminal services ideally be deployed as a single or dual Windows 2012 server solution?

Previously Small Business Server Premium was required in order to setup terminal services, with the second server then becoming the terminal server.

With SBS being discontinued, should terminal services ideally be setup as a single or dual Windows 2012 standard server solution and what are the pros / cons, if this can be setup either way?

There are approximately 20 users, with perhaps 5 terminal services sessions required at any one time, where users do not have their own desktop computer to connect to in the office.

There is also accounting software in place which uses SQL, with perhaps 5 users.
LVL 1
itcroydonAsked:
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.

Don ThomsonCommented:
SBS  starting with SBS 2003  do not support the Terminal Services option - With the SBS 2012 Premium - you have a separate license that allows you to run a Terminal server as a second box. You will need to purchase CALS for the number of simultaneous RDP users.
0
itcroydonAuthor Commented:
The question relates to setting up terminal services on Windows 2012 standard edition.
0
Cliff GaliherCommented:
You'll want *at least* two servers. Given your described setup, three or four (virtualized is fine) makes sense.

I never colocate roles on a DC. So a DC is one server.
I don't colocate other *server* roles on the session host server, so that's #2
And the supporting roles for RDS, like lice sing, RDCB...since I wouldn't colocate them, makes #3.

SQL may warrant its own server, or it may be okay to colocate it on #2 or #3, depending on usage, demand, etc. Hence three or four.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

VB ITSSpecialist ConsultantCommented:
Do you plan on deploying Terminal Services (now known as Remote Desktop Services) on new or existing hardware? Do you plan on using Hyper-V virtual machines for the RDS Session Hosts (aka Terminal Servers)?

If you are only planning on having one physical machine then you can follow these steps to install RDS on a Domain Controller, although I wouldn't recommend this: http://support.microsoft.com/kb/2833839

Can't really give more recommendations without knowing what hardware you have to work with.
0
itcroydonAuthor Commented:
This would probably be deployed on two new servers, with RAID 5 SAS drives, 16GB RAM and a Xeon processor.

Previously RDS was not supported on a DC, but in a real world scenario, I am not sure if a single DC & RDS server solution is viable. Microsoft also seem to be moving away from a single server, multi-role solution for small businesses with the discontinuation of SBS 2011.
0
VB ITSSpecialist ConsultantCommented:
I would personally spend a bit extra on the core components of the server (RAM and better CPU, depending on your choice) and utilize the Hyper-V role. A single Windows Server 2012 R2 Standard license will allow you to fire up two 2012 R2 Standard Hyper-V virtual machines, providing you do not use the host for anything else except managing the Hyper-V Virtual Machines. Please have a read of the 2012 R2 Licensing Brief for further clarification: http://download.microsoft.com/download/3/D/4/3D42BDC2-6725-4B29-B75A-A5B04179958B/WindowsServer2012VirtualTech_VLBrief.pdf

For your scenario I think two RD Session Hosts would be the way to go. Having two RD Session Hosts allows for redundancy should one of them go down or has a problem. It doesn't make sense in this day and age to have only one RD Session Host unless you are restricted by licenses.

What I would personally do, funds permitting, is have two physical hosts running 2012 R2 Standard with the Hyper-V role installed. I would then have a VM on each physical host which would be a Domain Controller, this way if one host goes down your users will still be able to still be able to log in. Configure one DC as your file and print server, the other as the SQL server for the accounting software.

You can then assign the last remaining 2012 R2 Standard license for your RD Session Hosts.

With the Accounting software, make sure you speak to the software provider and confirm that they support their software in a Terminal Services/Remote Desktop Services environment.
0

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
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
Remote Access

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.