Printer Spooler on Terminal Server

[Snoopy]

Dear All,

I have Windows 2003 Ent terminal server, there are about 100 terminal
sessions on this terminal, all my client computers have the option enabled to
map that local pritner into a terminal server so they can print to they local
printers.

Recetly I have noticed that my Printer Spooler service on my terminal server
is eating my CPU cycles up to 60% of processor time, some times even heier.
My CPU is an AMD Opteron 2.51Ghz, which should be more than enouth to hendle
my sessions. There is only one application that run on my terminal and that
taking a very small amount of CPU cycles almost nothing compared to printer
spooler.

Are there any best practices that i can folow for my problem?

Thank you

 

[TP]

Re: Printer Spooler on Terminal Server

Hi,

You have one or more printer drivers loaded on your server
that are not compatible with terminal services. Either update
them to TS compatible drivers or map them to a driver that
shipped with 2003 by following these instructions:

Windows 2000 Terminal Services server logs events 1111, 1105, and 1106

http://support.microsoft.com/kb/239088

Another alternative is to purchase a third-party universal
printer driver solution. In this case you would disable printer
mapping and remove all of the drivers you have installed
now. The only driver you would have installed would be
the UPD solution and it would handle printer autocreation.

-TP

Snoopy wrote:
> Dear All,
>
> I have Windows 2003 Ent terminal server, there are about 100 terminal
> sessions on this terminal, all my client computers have the option
> enabled to map that local pritner into a terminal server so they can
> print to they local printers.
>
> Recetly I have noticed that my Printer Spooler service on my terminal
> server is eating my CPU cycles up to 60% of processor time, some
> times even heier. My CPU is an AMD Opteron 2.51Ghz, which should be
> more than enouth to hendle my sessions. There is only one application
> that run on my terminal and that taking a very small amount of CPU
> cycles almost nothing compared to printer spooler.
>
> Are there any best practices that i can folow for my problem?
>
> Thank you