<div>
I know that this is not related with your problem, but since it can be and probably is a print spooler issue, please try the following.<br />
<a href="http://www.wincert.net/tips/windows-server/2176-print-spooler-keeps-refreshing-spoolsvexe-causing-high-cpu-usage" rel="ugc">http://www.wincert.net/tips/windows-server/2176-print-spooler-keeps-refreshing-spoolsvexe-causing-high-cpu-usage</a>
</div>


I know that this is not related with your problem, but since it can be and probably is a print spooler issue, please try the following.
http://www.wincert.net/tips/windows-server/2176-print-spooler-keeps-refreshing-spoolsvexe-causing-high-cpu-usage [http://www.wincert.net/tips/windows-server/2176-print-spooler-keeps-refreshing-spoolsvexe-causing-high-cpu-usage]

<div>
We resolved the problem on our own and did not receive any advise on the posting that helped solve the issue.
</div>


We resolved the problem on our own and did not receive any advise on the posting that helped solve the issue.

<div>
<div class="content wysiwyg-content">
We are having a problem with our Windows 2003 Terminal Server.<br />
We have several applications, MS Office, Navision, Adobe and others available on this server.<br />
Users are having to wait a long time for the Print Dialog box to show up on the screen after they click the Print button inside these applications.<br />
It can range from 15-90 seconds. Mostly in the 60+ seconds.<br />
Print Preview is snappy as expected.<br />
<br />
All of the printers on the Terminal Server are IP Network Server printers.<br />
We do not have any third party printing utilities.<br />
From a processor utilization perspective, a 1 minute average is about 25% utilization during the times when users are printing and complaining.<br />
Some of the printers are on the same network. Some are on the far side of a WAN connection. But the issue is the same for both local and WAN.<br />
<br />
Any thoughts on how to troubleshoot or resolve would be helpful
</div>
</div>


We are having a problem with our Windows 2003 Terminal Server.
We have several applications, MS Office, Navision, Adobe and others available on this server.
Users are having to wait a long time for the Print Dialog box to show up on the screen after they click the Print button inside these applications.
It can range from 15-90 seconds. Mostly in the 60+ seconds.
Print Preview is snappy as expected.

All of the printers on the Terminal Server are IP Network Server printers.
We do not have any third party printing utilities.
From a processor utilization perspective, a 1 minute average is about 25% utilization during the times when users are printing and complaining.
Some of the printers are on the same network. Some are on the far side of a WAN connection. But the issue is the same for both local and WAN.

Any thoughts on how to troubleshoot or resolve would be helpful

Terminal Server Printing

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).