sullend
asked on
School solution?? Remote Desktop Service scalability/requirements
I am investigating the option of setting up a Remote Desktop Service for 300-500 concurrent student users. (but up to 3000 actual users)
I work at a public school and we have (5) 100 Mb connections to our colo (which has 500mb) to meet the traffic requests for each site.
I would like to start converting old PC's /laptops into "Dumb Terminals" and allow remote sessions to the client desktop on the server.(the server does not exist yet)
My questions are:
How scalable is this solution,(assume I am running Windows 2012R2 DataCenter/Hyper V)
How much Horsepower will I need to take care of my users? memory/processor needs per user?
(most if not all end user requests will be for web pages with minimal Office applications sprinkled in. no Video editing or large end user apps)
What connections speeds do I need between my Server,(cluster/farm) and my SAN for this to work?
How much bandwidth is required between the client and the Remote Desktop Server/(per user)?
(the most intense data transfer I can think of the user would need is for watching youtube videos)
In regards to storage is the remote desktop the end user sees duplicated for each actual user or is it shared in both common disk space and common memory?
(for example if everyone needs the office suite installed are they all going to have to have there own unique memory and disk space for each office session or are these common files shared?)
I already have a SAN with 6 Terabytes, my users will be saving little if any documents to there desktops,(we use google drive for our document storage)
Some of you out that have already done this I am sure, just trying to evaluate the process without "reinventing the wheel".
I do not have the funds for a Citrix environment due to licensing cost, however I figured a lot of Citrix Admin started on the same road I am on before switching to Citrix..What pitfalls will I see that may push me to upgrade to Citrix at a later point?
I work at a public school and we have (5) 100 Mb connections to our colo (which has 500mb) to meet the traffic requests for each site.
I would like to start converting old PC's /laptops into "Dumb Terminals" and allow remote sessions to the client desktop on the server.(the server does not exist yet)
My questions are:
How scalable is this solution,(assume I am running Windows 2012R2 DataCenter/Hyper V)
How much Horsepower will I need to take care of my users? memory/processor needs per user?
(most if not all end user requests will be for web pages with minimal Office applications sprinkled in. no Video editing or large end user apps)
What connections speeds do I need between my Server,(cluster/farm) and my SAN for this to work?
How much bandwidth is required between the client and the Remote Desktop Server/(per user)?
(the most intense data transfer I can think of the user would need is for watching youtube videos)
In regards to storage is the remote desktop the end user sees duplicated for each actual user or is it shared in both common disk space and common memory?
(for example if everyone needs the office suite installed are they all going to have to have there own unique memory and disk space for each office session or are these common files shared?)
I already have a SAN with 6 Terabytes, my users will be saving little if any documents to there desktops,(we use google drive for our document storage)
Some of you out that have already done this I am sure, just trying to evaluate the process without "reinventing the wheel".
I do not have the funds for a Citrix environment due to licensing cost, however I figured a lot of Citrix Admin started on the same road I am on before switching to Citrix..What pitfalls will I see that may push me to upgrade to Citrix at a later point?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
what is good baseline for a session host (processor count etc?)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER