Solved

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

Posted on 2014-10-20
6
226 Views
Last Modified: 2014-11-10
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.
0
Comment
Question by:itcroydon
6 Comments
 
LVL 14

Expert Comment

by:Don Thomson
ID: 40392044
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
 
LVL 1

Author Comment

by:itcroydon
ID: 40392193
The question relates to setting up terminal services on Windows 2012 standard edition.
0
 
LVL 57

Assisted Solution

by:Cliff Galiher
Cliff Galiher earned 250 total points
ID: 40392241
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
Connect further...control easier

With the ATEN CE624, you can now enjoy a high-quality visual experience powered by HDBaseT technology and the convenience of a single Cat6 cable to transmit uncompressed video with zero latency and multi-streaming for dual-view applications where remote access is required.

 
LVL 24

Expert Comment

by:VB ITS
ID: 40392271
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
 
LVL 1

Author Comment

by:itcroydon
ID: 40421055
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
 
LVL 24

Accepted Solution

by:
VB ITS earned 250 total points
ID: 40421365
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

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I'm a big fan of Windows' offline folder caching and have used it on my laptops for over a decade.  One thing I don't like about it, however, is how difficult Microsoft has made it for the cache to be moved out of the Windows folder.  Here's how to …
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…

830 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question