The_Dark1
asked on
Setting up Multiple Terminal Servers (Clustered or not?)
Hi Everyone,
I need some advise on how best to achieve the following:
I am currently involved in a test project that will require Terminal Server's (we would look at Citrix but the costs are fairly high - but it might be the way to go - so i thought I would post a Q here to see some feedback)
At the moment we are going to be publishing an application for a large amount of users through TS. However we know the current limitations (based on hardware and the application) we could house around 20-30 concurrent users on a singular terminal server. However we are expecting over 100 concurrent users to be using this application.
So my question is, what would be the easiest way to house this many EU's.
We are thinking of having multiple TS's in the environment, but we want each user to have the same Desktop on any TS. I know we can limit the total amount of users per terminal server, but how do we get the other users to connect to the second or third server and still see the same desktop?
IE - If we have 90 EU's in the environment, and we limit the maximum amount of EU's to 30 per server, then if TS1 reaches 30, how do we tell the environment to get user 31 to connect to TS2 and still show the same desktop and settings?
- Would clustering be the way to go (if so, how do I cluster - I am not experienced in clustering)?
- Roaming profiles on the environment (does this method even apply in Terminal Servers)?
- Scalabilty is another thing I need to factor in as well, so that if the environment grows to 200 EU's, then what would be the simplest way for us to add in another TS etc...
I guess the next part of this question is locking down the TS completely so these users have very limited functionality on the TS itself. I know I have the abiliy to lock the TS down locally, but when doing this through GPO's in the AD, the policies are limited in what I can apply to the user... any thoughts?
If you admins have come across this before, or can share any thoughts on this solution it would be greatly appericated.
Many thanks
I need some advise on how best to achieve the following:
I am currently involved in a test project that will require Terminal Server's (we would look at Citrix but the costs are fairly high - but it might be the way to go - so i thought I would post a Q here to see some feedback)
At the moment we are going to be publishing an application for a large amount of users through TS. However we know the current limitations (based on hardware and the application) we could house around 20-30 concurrent users on a singular terminal server. However we are expecting over 100 concurrent users to be using this application.
So my question is, what would be the easiest way to house this many EU's.
We are thinking of having multiple TS's in the environment, but we want each user to have the same Desktop on any TS. I know we can limit the total amount of users per terminal server, but how do we get the other users to connect to the second or third server and still see the same desktop?
IE - If we have 90 EU's in the environment, and we limit the maximum amount of EU's to 30 per server, then if TS1 reaches 30, how do we tell the environment to get user 31 to connect to TS2 and still show the same desktop and settings?
- Would clustering be the way to go (if so, how do I cluster - I am not experienced in clustering)?
- Roaming profiles on the environment (does this method even apply in Terminal Servers)?
- Scalabilty is another thing I need to factor in as well, so that if the environment grows to 200 EU's, then what would be the simplest way for us to add in another TS etc...
I guess the next part of this question is locking down the TS completely so these users have very limited functionality on the TS itself. I know I have the abiliy to lock the TS down locally, but when doing this through GPO's in the AD, the policies are limited in what I can apply to the user... any thoughts?
If you admins have come across this before, or can share any thoughts on this solution it would be greatly appericated.
Many thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I am thnking along the lines of this type of config:
1 Domain Controller
1 Exchange Server for the environment
and 2-3 TS Servers
So with this, what would you think?