Terminal Services Hardware Req

[Xsorovan]

My company has been presented with an opportunity to get some new software and the company suggests we run it as a served application via Terminal Services. Last time I played with application serving in terminal services was when Windows 2000 was new, so I'm a little rusty.

My first question though is, what kind of hardware requirements do you think a terminal server that is supplying around 10 concurrent users to a database program would need? I mean I am all for not worrying about how much it needs and buying a nice big fat server so it won't be a problem... but we are a non-profit and thus getting anything technology wise is, well, hard. So I'll need some help with what you all think of what the minimum specs for something like that would be.

(Or at very least point me to some resources that might help. I've been Googling this morning and I can find all sorts of whitepapers on all sorts of topics on TS, and I have gotten distracted, but I just need some solid numbers right now. (EX: 5 users per cpu/core is the most you want to push, with a gig of ram per user, etc... that kind of stuff))

Thanks!

 

[Bashbelly]

I looked at doing this a while back (still havent really implemented anything). But if I remember right memory usage = 50mb for the sesssion itself + total app used ram. So if you use excel and your average file opened = 350 mb ram then you will need 400mb ram per users.

 

[RebateMonger]

Before you get too involved in TS, you should at least take a look at Windows Server 2008's Application Publishing capabilities. It's very cool stuff and solves some problems like using dual monitors in TS mode.

 

[Goosemaster]

Originally posted by: RebateMonger
Before you get too involved in TS, you should at least take a look at Windows Server 2008's Application Publishing capabilities. It's very cool stuff and solves some problems like using dual monitors in TS mode.

Much more efficient for single apps than 2003:thumbsup:

 

[drebo]

Sounds to me like they just want you to buy more licensing from them. Terminal services licenses aren't cheap.

If you're not using thin clients already and all servers are local, there's no reason to use terminal services, at least in my opinion.

 

[Xsorovan]

Originally posted by: RebateMonger
Before you get too involved in TS, you should at least take a look at Windows Server 2008's Application Publishing capabilities. It's very cool stuff and solves some problems like using dual monitors in TS mode.

Than s for the tip... correct me if I'm wrong though: it looks like the application server is more like Adobe Air, or Google Gears for Windows Applications and that the apps need to be built on dot net for that to work at all.

As we aren't building a custom app I don't think that would be of much use. (and I know the DB app we are looking at isn't created in dot net)

Or possibly did I miss something?