We help IT Professionals succeed at work.

Remote Desktop Hardware planning

I'm looking into implementing a Remote Desktop services on Windows Server 2008 R2. I'm trying to get an idea of what kind of hardware I need with an eye toward the future. I'd like to support around 500 users. I have found some links from Microsoft talking about best practices and a list of where bottlenecks may occur but I would really love numbers. How many core per 10 users, how much ram, What type of Raid.

Thanks,
Comment
Watch Question

DarinTCHSenior CyberSecurity Engineer
CERTIFIED EXPERT

Commented:
so your going to run RDS (old Terminal Server) for 500 concurrent connections?
what's your budget
how many servers?
are these all physical or virtual
are we talking dell/HP or other

Author

Commented:
yes 500 concurrent. And well those are the questions i am trying to answer. I need to know what it's going to take with regards to hardware to get all of the users on terminal. I can figure out HDD space. I'm really just trying to get a sense of the RAM and CPU usage of users in RDS.
David Johnson, CDSimple Geek from the '70s
CERTIFIED EXPERT
Distinguished Expert 2019
Commented:
The hardware demands vary hugely.. are the users running photoshop or rendering video's or running notepad.  There are way too many variables to consider, I can see networking being a potential bottleneck.

A potential starting base would be 500 G of ram, 500 MB/S disk io, 500 Ghz of processing power
nappy_dThere are a 1000 ways to skin the technology cat.
CERTIFIED EXPERT
Commented:
If you haven't already done so, take a look at this URL.  While it is a few years old, the concepts still apply.

http://technet.microsoft.com/en-us/library/bb608286.aspx


BTW DO NOT, run video rendering or Photoshop in RDP sessions.  These would not be a wise use of resources.
CERTIFIED EXPERT

Commented:
The biggest pitfall of RDP is in the clients printers and, if you are not careful, that server will wind up seriously bogged down with all of the drivers necessary to support printing.You will have to install drivers for almost every allowed printer or the user won't be able to print.  GDI and All-In-Ones tend to be massive resource hogs;  Postscript and PCL printers the opposite.  Additionally; in mixed environments (x64 and x86) those driver versions have to match perfectly or you get flakey printing.
Beyond that, as other posters have said, avoid intensive apps and RDP works quite well on relatively lightweight hardware.
There are a 1000 ways to skin the technology cat.
CERTIFIED EXPERT
Commented:
One of the nice features of Windows 2008R2 is universal printing.  Windows Terminal server now uses this feature for I would think 90% of the printers out there so this reduces your need to add 100's of other printer drivers compared to Windows 2003 Terminal server.

Author

Commented:
Thanks all

Explore More ContentExplore courses, solutions, and other research materials related to this topic.