| Event Id | 51 |
| Source | |
| Description | PrintQueue <queue> could not be pruned. Error: <error code>. |
| Event Information | According to Microsoft: CAUSE: Printer Pruner detects that a given PrintQueue object is orphaned by contacting the print server and comparing the printer object to the Active Directory PrintQueue object. If the printer on the print server restricts access to Printer Pruner, Printer Pruner cannot perform the comparison and cannot delete the PrintQueue object. For proper Printer Pruner operation, a printer must grant access to the Everyone group and/or the Domain Controllers group. By default, when a printer is created, the Everyone group is granted Print access. If this permission is removed and the printer is published, Print access must be granted for the Domain Controllers group on the printer. Otherwise, Printer Pruner cannot do its job and Active Directory will contain stale PrintQueue objects. RESOLUTION: Make sure that the Everyone group or the Domain Controllers group has access to all printers that are published in Active Directory. |
| Reference Links | Printer Pruner May Not Remove Printer Queue Objects from Active Directory |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.