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 www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
Printer <printer name> was created.
|English: Request a translation of the event description in plain English.|
Bobby De La Rosa
In my case it appears that this event followed by Event (Event ID:2 printer was created), (Event ID:3 printer was deleted), (Event ID:4 printer is pending deletion), (Event ID:8 printer was purged) and (Event ID:9 printer was set) are created whenever a remote user logs onto my terminal server. They computer has a printer configured on it. The terminal server creates a printer session for each known printer driver it has for the new user. These events happens on a daily basis for my server.
This message will also be generated, when a local printer is mapped into a terminal server session.
Message generated when a new printer is configured.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (1) - More links...|
Send comments or solutions
- Notify me when updated