Memory/CPU requirements for application publishing in Windows Server 2008 TS

We are planning to deploy a single application to our employees through Windows 2008 TS. Right now I am trying to find out if there is a "rule of thumb" when it comes to per user CPU/memory requirements. The application is build on .Net Framework, database driven and somewhat printer intensive (in bursts of ~15 pages several times a day). Currently we have about 100 users.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

For 100 users I would definitely recommend you have a few powerful servers (2xQuad core processors with plenty of ram) setup with load balancing. As for the exact specs its hard to tell. One way would be to start off with at least a pair of servers (for redundancy) and see how it holds up, if it is not running as fast as you would like you could easily add more servers.
I hope this helps. Good luck.
I tend to work to Citrix's recommendations - the technology is similar.

No more than 30 concurrent users per server, on average.
Approx 128Mb RAM per concurrent users + OS overhead

If the terminal services server will be spooling all the print jobs (rather than another print server doing the job) you should look at moving the print servers spool folder (start, control panel, printers, file, server properties) to a disk other than where the application and other than where the operating system and page file is stored (i.e. dedicated disks if possible) and this should be a RAID 1 or RAID 0+1 set of disks.

CPU well... for 30 concurrent users using a database-itensive application I should think at least quad core and at least 2.5Ghz clock speed, but if you can afford an 8-way server at 2.8 or 3Ghz I should think the rule of "aim high as possible" applies.

Just out of interest if the application is .net why not deliver it through a web browser?
csbankAuthor Commented:

Can you point me to a Citrix or Microsoft article/white paper?

To your question about web deployment: It is a third party application, I do not know about a way to deliver it through a web browser.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.