Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 513 Source: PrintService

Group Policy was unable to add per computer connection \\<server>\<printername>. Error code 0x2. This can occur if the name of the printer connection is incorrect or if the print spooler cannot contact the print server.
According to TD380098, the administrator should try these suggestions:
- Confirm that the Universal Naming Convention (UNC) name of the printer connection is correct and available from the affected computer or user.
- Use Group Policy Results to confirm that the appropriate Group Policy object (GPO) is applied to the affected computer or user.
Error code 0xbc4 - From support forum:
I may have found my solution. It appears the printer in question was added using a printui.dll command, and not through Group Policy as stated in the event log. I verified this by running the following command:

rundll32 printui.dll, PrintUIEntry /ge

I got rid of it with the following:

rundll32 printui.dll, PrintUIEntry /gd /n\\printserver\printername

I managed to find this by searching for the printer name in the registry, and finally stumbling on the key at hkey_local_machine\software\microsoft\windows nt\currentversion\print\connections. That "connections" key seems to relate to computer-level printer additions via printui.dll commands.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.