RE: How to disable logging of failed printer installation
The problem is not so much the display as the fact that the sheer volume of
failed printer installation events pushes other events off the end of the
log. I know I could make the log size larger before cycling, but in the case
of this server, I just opted to override RDP client printer settings with
server-side RDP settings to deny client printer connections. Anyone that
prints from this server would use a network printer that is installed on the
server anyway. I was just hoping that, like the print job logging, there
would be a registry entry to deny printer installation event logging.
Thank you.
"Vera Noest [MVP]" wrote:
> Yes, I'm afraid that I made the same mistake, to think that those
> settings would also apply to redirected printer creation events.
> But I guess they don't.
> I'm not sure if it is possible at all to get rid of these events.
> Maybe the best you can achieve is to filter out them in
> EventViewer.
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?QnJpYW4=?= <Brian@discussions.microsoft.com> wrote on 02
> okt 2008 in microsoft.public.windows.terminal_services:
>
> > All items there are already unticked. They are all related to
> > print jobs, not printer installations.
> >
> > "Richard Kelly" wrote:
> >
> >> You can disable print eventing on the terminal server using the
> >> Printer and Fax applet in control panel. Open up the applet,
> >> slect file, then server properties an then select advanced
> >> remove the ticks for the event types you no longer want. I can
> >> never remember the actual reg values for these, if you are
> >> desperate for them update the thread and I'll see if i can dig
> >> them out for you...please note that this will disable all print
> >> eventing for the seleted types on the servers.
> >>
> >> "Brian" wrote:
> >>
> >> > Thanks, Vera.
> >> >
> >> > That site has good information on managing printers, but in
> >> > this specific case, it is a TS that is rarely, if ever, used
> >> > for printing. I am not very concerned with the ability of the
> >> > client to connect its printers; I just want to disable the
> >> > logging of the printer connection-related events and guess
> >> > that there must be a registry entry somewhere (like the one
> >> > that I used to disable print job logging).
> >> >
> >> > "Vera Noest [MVP]" wrote:
> >> >
> >> > > This should help:
> >> > >
> >> > > How can I turn off printer notifications for all users?
> >> > > http://ts.veranoest.net/ts_faq_printing.htm#PrinterNotificat
> >> > > ions
> >> > >
> >> > > _________________________________________________________
> >> > > Vera Noest
> >> > > MCSE, CCEA, Microsoft MVP - Terminal Server
> >> > > TS troubleshooting: http://ts.veranoest.net
> >> > > ___ please respond in newsgroup, NOT by private email ___
> >> > >
> >> > > =?Utf-8?B?QnJpYW4=?= <Brian@discussions.microsoft.com>
> >> > > wrote on 30 sep 2008 in
> >> > > microsoft.public.windows.terminal_services:
> >> > >
> >> > > > Just one clarification: I still want clients to be able
> >> > > > to print if they want and if the printer maps correctly
> >> > > > (all the important ones work correctly), so I don't want
> >> > > > to disable printer mapping at the server - I just don't
> >> > > > want the printer-related entries filling up the event
> >> > > > log.
> >> > > >
> >> > > > "Brian" wrote:
> >> > > >
> >> > > >> Various client stations of my terminal servers have
> >> > > >> virtual printers (CutePDFWriter, etc.) that do not exist
> >> > > >> on the TS. I would actually prefer that clients disable
> >> > > >> printer connections, but that does not always get done,
> >> > > >> and so it fills up the TS event log with pairs of
> >> > > >> 1106/1111 errors. (printer could not be installed /
> >> > > >> Driver... is unknown)
> >> > > >>
> >> > > >> What is the registry entry for disabling logging of
> >> > > >> printer installation-related events on the TS?
>