Slowly Terminal Server response

All,
We have a Terminal Services server (w2k, 2gb RAM) running in application
mode. Recently, the server (the users response) has been running extremely
slow. We have about 20 users connecting to this server via a VPN connection
to our main server (SBS 2k3 R2) and then they connect to our Terminal Server
with the TS client software or Remote Desktop Connection (should they all be
using the TS Client software and could this be the problem).

The application that the users are using is an MS Access applications.
Pretty simple: data entry forms, query listings, reports. Very low
transactional
application.
I went into the Task Manager and noticed that the spoolsv.exe is taking
up a large amount of memory. I quess my question is what should I be looking
for to
find out why the server is running so slowly?

Is there a good article on TS regarding system requirements for x amount
of users connecting?

Any help or guidance would be appreciated.

Follow-up info:

the CPU will peg at 100% sometimes for 10 - 20 seconds at a clip. The
culprits seem to be the Access applications (sessions).
This particular Terminal Server has 2 CPU chips (Dell P1400, SP4). Not sure
why the application would grab 100% of the CPU.
This is becoming a major problem for some of our users. Not sure where I
should be looking.
Is there a parameter that I can tweak to tell the CPU to only allocate a
certain amount of CPU time (cycle) per user at any given time?
Memory wise, each Access session seems to be taken up about 22,000k to
32,000k of Mem Usage.

Again, if there is a good white-paper on this issues or subject I'd be
glad to read it.

Sorry for double posting this issue. The last time I sent this in was over a
month
ago and I, yes I, never followed up on the response.

Thank you,
Thomas Kroljic


.

Relevant Pages

  • RE: Windows Server 2003 Servicing Multiple AD Domains
    ... > Is there any performance or access issues having users connecting across ... > Domains via transitive trusts to a common shared Windows 2003 File & Print ... > Storage Server for Home Directories and other shares? ...
    (microsoft.public.windows.server.active_directory)
  • 2008R2 Standard remote access
    ... Standard edition? ... What kind of protection do I need on the server that they ... edition limited to the number of users connecting. ... (I normally purchase licensing by ...
    (microsoft.public.windows.server.setup)
  • Office XP on Terminal Server 2003
    ... I hae a Windows Server 2003 box set up for Terminal ... It is working just fine for the users connecting ... to work with a shared accounting program and Adobe ... The user can start Excel on it's own just fine however ...
    (microsoft.public.windows.server.general)
  • Re: Changing to terminal server
    ... everything is running under one server: 10 users connecting ... squl, exchange server, office apps, internet. ... >>> are SqL database, quickbooks, microsoft office, internet, etc. ...
    (microsoft.public.windows.server.sbs)
  • Performance Problems.. Server hardware smoked by $500 box?
    ... webserver with a separate db/file server sitting behind it. ... Now granted the development machine has the most Mhz, ... CPU: Intel Pentium III Origin = ... Ubench CPU: 25713 ...
    (freebsd-performance)