F
F
fuzzZy232017-01-05 00:22:23
Windows Server
fuzzZy23, 2017-01-05 00:22:23

What do they eat with Windows Server 2008?

Greetings to all who responded. Happy New Year!
The task is as follows: It is
necessary to organize a network, which should be headed by a Server with the ability to connect via RDP to 50 simultaneously connected users.
Given:
2 x Windows Server 2008 R2 EE 1-8cpu 25clt (two licenses)
Question:
1. "25clt" - 25 user licenses?
2. On Windows Server 2008, is it possible to purchase additional user licenses or 25 maximum?
3. If I have "Given" 2 x Windows Server 2008 R2 EE 1-8cpu 25clt - should I organize two servers to support 50 users? :D

Answer the question

In order to leave comments, you need to log in

3 answer(s)
S
Sergey, 2017-01-05
@edinorog

You can expand the standard license indefinitely!
buy 2008 while live 2016 ... will only be crazy!
licenses are purchased separately for RDP and separately for connection to the server. on the toaster was repeatedly discussed!

Y
Yumado, 2017-01-05
@Yumado

In your case there are two servers. To not change anything.
It is desirable to plan the server configuration from the number of users.
We calculate the number of processor cores according to the following algorithm.
One logical core for 2 users.
Those. 8*2=16 logical cores. 16*2 = 32 users.
Very weak configuration.
For 50 users, two 8-10 core processors are more suitable.
Two 8-core is equal to 32 logical. Two users per core. We get 64 users.
With minimal power.
Licenses are calculated later.
Taking into account the needs in processors, we plan to purchase licenses.

R
res2001, 2017-01-05
@res2001

In general, it is better to take at least Windows Server 2012 R2. In 2008, the microsoft in RDP eliminated some goodies, for example remote shadow - a very good thing if you know how to cook it. In the next versions, RDP (Windows Server) was returned back, apparently indignant admins managed to get through to them :)
1. 25 clt is 25 client licenses for connecting to Windows Server (Windows CAL). But you additionally need the Windows RDP CAL. Licensing can be both by the number of users and by physical processors (you need to figure out which will be more profitable). Terminal Server requires both types of licenses.
2. There is a possibility to purchase additional licenses, without problems, of both types.
3. 50 users is not a lot. You need to figure out what users will work with in the terminal and what kind of load. Typically, the load created by the average user is not large, so the amount of memory will play a greater role, and not the number of cores in the process. The best option, IMHO, is to raise the terminal on a virtual machine, give it more RAM and enjoy life.
If you raise 2 terminals, then in Windows it is possible to make a load balancer between terminal servers, so there will be one entrance to the terminal for users, and the balancer will choose which particular server the user will go to.
I would raise one terminal server for a start, and start launching users on it gradually, monitoring the load in the process. If it suddenly turns out that users are eating all the CPUs, then it's time to deploy a second terminal with a balancer. If rests against the memory - to finish off the memory.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question