Auditing Printer Additions/Deletions, Driver and Port Changes
| The Print Server MP covers most aspects of printer queue health and error states (The Print Server State Script gets all the way down to low paper, open drawers, etc), but we wanted a way to track certain other changes to the print server that may adversely impact functionality...a small measure of configuration mgmt and to provide some forensic data of sorts when printers suddenly stop working due to fundamental changes in configuration Specifically, the following items were of interest: 1. Queue create/delete 2. Driver change 3. Print Port change (to a new port) The easy road on this is to check for events generated when each action is performed. We can take the following aspects of these three events and use them as criteria in Event Rules to raise Warning events to create an easily visible trail to mark the changes not being captured through default rule. Ran through a quick exercise in the lab, and here are the events we can use to flag these print server-related changes NOTE: On the downside, you'll notice the user shows up as SYSTEM....so much for catching our perpetrator :( Here are the events. Criteria for your Event Rule are in RED 1. Successful Printer Creation Event Type: Information 1b Printer Deletion Event Type: Warning
Event Type: Warning 3. Port Change (will also generate an event on adds) Event Type: Information |










Comments on "Auditing Printer Additions/Deletions, Driver and Port Changes"
-
marcus said ... (6:33 AM) :
post a comment links to this postgood stuff, pete. keep up the great work. i'm curious on the events - they all seem to be from source Print and have different event ids. in that case, is it necessary to description filters?