Server 2008 Terminal Server spoolsv.exe High CPU Usage
Hi Experts,
We have a Server 2008 Terminal Server cluster and are having issue with spoolsv.exe. Clients are all running XP SP3.
The problem is that because of a limitation in TS Easy Print (have a case open with MS to fix the issue), I can not use Easy Print. Because there is no Easy Print, and some of the drivers that are loaded, and the amount of print jobs we go through, the CPU usage on these Terminal Servers regularly hits 100% (up to 90% of it is caused by spoolsv.exe).
My question is:
Does anyone know of a way to "throttle" spoolsv.exe? I would like to keep it so it can't use more that 25% of the processor. Or, if you have a better idea on how to limit it, I would be open to that as well.
NOTE: We have tried Windows System Resource Manager, but spoolsv.exe is on its permanent, non changeable exclusion list, and WSRM actually constantly uses approx. 20% of the processor in my testing, so not a good option even if it could throttle spoolsv.exe.
Thanks, let me know if I need to provide further detail!
We have a Server 2008 Terminal Server cluster and are having issue with spoolsv.exe. Clients are all running XP SP3.
The problem is that because of a limitation in TS Easy Print (have a case open with MS to fix the issue), I can not use Easy Print. Because there is no Easy Print, and some of the drivers that are loaded, and the amount of print jobs we go through, the CPU usage on these Terminal Servers regularly hits 100% (up to 90% of it is caused by spoolsv.exe).
My question is:
Does anyone know of a way to "throttle" spoolsv.exe? I would like to keep it so it can't use more that 25% of the processor. Or, if you have a better idea on how to limit it, I would be open to that as well.
NOTE: We have tried Windows System Resource Manager, but spoolsv.exe is on its permanent, non changeable exclusion list, and WSRM actually constantly uses approx. 20% of the processor in my testing, so not a good option even if it could throttle spoolsv.exe.
Thanks, let me know if I need to provide further detail!
ASKER
hi jhalliday,
sorry, should have mentioned that it was x86, not 64.
worth a shot, thanks
sorry, should have mentioned that it was x86, not 64.
worth a shot, thanks
No problem :)
What sort of printer drivers are you using ? Are they all the same manufacturer ? Oh one thing you could check is to see if any of them are using Java and the spooler service when it calls the driver is then spawning a java process. If thats the case you could have errant Java processes that are taxing your system via Spooler. Its a long shot.
What sort of printer drivers are you using ? Are they all the same manufacturer ? Oh one thing you could check is to see if any of them are using Java and the spooler service when it calls the driver is then spawning a java process. If thats the case you could have errant Java processes that are taxing your system via Spooler. Its a long shot.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Might be nothing but worth a look