Microsoft Remote Desktop Server for multiple users (30-40)

[saurabhwahile]

Hi!

 

So I'm looking to setup a windows server machine(a rack server), for remote desktop usage, what should be the recommended configuration, for 30-40 users accessing concurrently?

Also any tips and best practices around this will appreciated!

 

Thanks!

 

[Electronics Wizardy]

what are the users doing? Budget?

 

What os do they need?

 

 

 

 

[Sir Asvald]

1 hour ago, saurabhwahile said:

Hi!

 

So I'm looking to setup a windows server machine(a rack server), for remote desktop usage, what should be the recommended configuration, for 30-40 users accessing concurrently?

Also any tips and best practices around this will appreciated!

 

Thanks!

 

Here is a link. You need to do it on the server itself.

 

https://www.serverwatch.com/server-tutorials/multiple-remote-desktop-connections-on-windows-server-2016-and-windows-server-2012.html

[Jarsky]

Best practice is to configure the RDSH (Remote Desktop Session Hosts) role. Theres plenty of tutorials on setting this up. 

We have dozens of terminal servers, depending on what apps they're using - ive found for just a host where they might use a browser, putty, rdp to other servers, about 4 cores and 16-24gb of ram is normally enough for around 30 users.

 

Depending on the availability, you might want to consider setting the server up with ESXi and having 2 terminal servers as VM's so that when you're patching users can continue to use the other one if needed. Or if you have an application issue on one, users can use the other while you troubleshoot/reboot it. It also means you can do snapshots before patching as well....Since these would be user facing they should always be up to date with security and critical patches. 

 

[Mikensan]

On 11/23/2018 at 3:10 AM, saurabhwahile said:

Hi!

 

So I'm looking to setup a windows server machine(a rack server), for remote desktop usage, what should be the recommended configuration, for 30-40 users accessing concurrently?

Also any tips and best practices around this will appreciated!

 

Thanks!

 

So you could do a sinlge server farm, but if 30-40 users will "depend" on it then let management know it is a single point of failure.

 

You'll have to adjust for the applications you expect your users to be using, but for MS Office + Chrome I'd look at 3gb per user. If you expect 40 concurrent users I'd get no less than 128gb but would shoot for more to anticpate growth. Processor, it really depends on your budget and needs but again for Office + Chrome I would aim for as many cores as your budget allows. Count > speed for multi-user low-level operations.

 

That said I'd buy 3x whatever you chose, cluster them, and enable HA. I would buy 3 slightly older servers (R*20s for example) than 1 brand new server for that many users.

[Blake]

On 11/23/2018 at 7:55 PM, Jarsky said:

Best practice is to configure the RDSH (Remote Desktop Session Hosts) role.

 

Not quite.

 

Best Practice is purely dependant on the use case and business case. In this instance, if they are just looking for to replace a Windows Client OS as the 2 concurrent session limit and nothing else you'd be right. As they are requesting 30-40 users, it'd need more scale then that.

 

Looks to me that you'd setup RD gateway+RD Web Access (maybe), and a connection broker, then throw a few RD host (depending on scale required), assuming you need full remote desktops. If your looking at giving an app to 30-40 people, look into remoteapp.