> -----Original Message----- > From: Ziots, Edward [mailto:[EMAIL PROTECTED] > Subject: RE: Question on Printer creation Auditing > > Himm which event ID David, I don't see it in my audit logs. I want to > track down which tech is blowing up my print server so I can drop the > hammer once and for all.
Mine shows as 2, 9 and 20. 20 shows the driver being loaded by SYSTEM, 9 shows the printer as "set" by the user who installed the printer and 2 shows printer as "created" by the installing user . Source is Print for all three events. This is on my Citrix 4.5 lab running Server 2003 R2. Webster > -----Original Message----- > From: David Lum [mailto:[EMAIL PROTECTED] > Subject: RE: Question on Printer creation Auditing > > Event logs will tell you who created what and when... > > > > > -----Original Message----- > From: Ziots, Edward [mailto:[EMAIL PROTECTED] > Subject: Question on Printer creation Auditing > Importance: High > > Since it seems I cant get it through to some folks about bad print > drivers, and causing print servers to crash. I am in the midst of > rebuilding 2 print servers, and I would like to lay down auditing on > the > printers to who created what and when. > > Would it be as easy as auditing for certain group the printers key in > the registry, or is there more to it, to make sure I track down who > updates drivers, or makes a change to a printer on the print servers. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
