Re: TS running Office or .NET applications
- From: Peter <Peter@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 26 Feb 2009 13:00:08 -0800
Thanks for the response guys, good stuff and lots to work on.
TP - your definition of Terminal Services as
"Think of a TS as a workstation PC, only with multiple users using it
concurrently" has brought more clarity to my mind than sifting through
several web sites and 2 white papers.
Thankyou very much.
--
Regards - Peter
"TP" wrote:
Answers inline....
Peter wrote:
I work as an app developer/asst network administrator for a small
firm (50 users), we currently run SBS Server 2003.
I have been informed that later this year we will be moving to
Terminal Services and I am a TS ignorant.
We have a number of applications based variously on Office programs
or .Net that some users need to access, but not all. In fact it would
be undesirable to allow all users to access all applications.
Recommend you use .NET 3.5 SP1 to get the best memory use.
Consider using ngen with shared libraries in the GAC, and set unique
DLL base address for each. I say consider because depending
on your apps, the number of instances, power of your server, etc.
the additional optimization may not accomplish much.
On a TS with large app(s) and many users the memory savings
can be very substantial.
The Performance Benefits of NGen.
http://msdn.microsoft.com/en-us/magazine/cc163610.aspx
However I was of the notion that Terminal Services was a bit of a one
size fits all approach. I have read lots about TS and Office with
regards to licencing, but there seems to be very little written about
TS and Office based applications.
So my first question is, using TS (it will probably be 2008), can we
customise user's access to applications?
Yes, if you mean allowing only some users to run certain applications.
Secondly, some of these apps now run from the server, but some have
local executable files on the workstation, how is that situation
managed under TS?
Think of a TS as a workstation PC, only with multiple users using
it concurrently. Whether you run the executable from the local TS
drive or not depends on your needs and the application.
Lastly, some of these apps can get very CPU hungry and I imagine with
TS that the server will be doing the grunt work instead of the
workstation, so if I have 4 or 5 users running heavy CPU workloads
simultaneously, is it likely that the server will be slowed
appreciably? (the server computer will be new but I have no idea of
the spec yet)
Slow response is possible, just like it is on a workstation PC. It is
critical that you test in order to get a sense of how much RAM, CPU,
and disk I/O needed. A typical new TS will have an x64 OS, dual
quad-core, 16G or 32G RAM, with multiple 15K SAS drives running
RAID 5 or preferably RAID 10. The number of drives depends on
you IOPS requirements.
Office is 32-bit and will run fine under an x64 OS. Testing your
specific configuration as well as your applications is needed to
make sure everything works.
Dual quad-cores will likely handle your scenario of 4-5 users with
heavy CPU workload simultaneously. Again setting up a test box
is critical.
I apologise for the lameness of my questions but as I mentioned, I am
a complete ignorant to Terminal Services.
Thanks.
-TP
- References:
- TS running Office or .NET applications
- From: Peter
- Re: TS running Office or .NET applications
- From: TP
- TS running Office or .NET applications
- Prev by Date: Re: how to get info about ts sessions over wmi/powershell?
- Next by Date: Re: Terminal Services connection problem
- Previous by thread: Re: TS running Office or .NET applications
- Next by thread: Same APP on WS2008 slower than WS2003 - often.
- Index(es):
Relevant Pages
|
Loading
