When this occurs, Printer Pruner writes a System event for each PrintQueue object that is detected as an orphan. This can accumulate rapidly for sites with large numbers of published print queues. If there are many published printers on the site, the System event log may become filled with Printer Pruner events.
NOTE: An incorrect Domain Name Server (DNS) or router configuration may also cause a DC to be unable to find print servers and exhibit this behavior.
- Before removing a DC from the network for an interval longer than the Directory Pruning Interval and Directory Pruning Retry periods, set the Directory Pruning Interval value to Never. These policies are located in Group Policy Editor under Computer Configuration\Administrative Templates\Printers.
- Stop the Spooler service on the DC.
You should use the Check Published State policy only if network outages are common, because the widespread use of this policy on many computers in the domain (that are constantly checking the publication status of their PrintQueue objects in Active Directory) can adversely affect network performance. Microsoft recommends that you set this policy only on the main production print servers.
For infrequent outages involving DCs that last over 24 hours and leave the computer powered on for the duration of the outage, Microsoft recommends stopping the Spooler service on the DCs.
Номер статьи: 246906 — последний просмотр: 1 марта 2007 г. — редакция: 1