https://community.splunk.com/t5/Knowledge-Management/Windows-TerminalServices-Printers/m-p/19803#M7003 <P>I will check that out.....Thank you</P> Fri, 27 Jul 2012 17:46:16 GMT JohnFLi 2012-07-27T17:46:16Z https://community.splunk.com/t5/Knowledge-Management/Windows-TerminalServices-Printers/m-p/19801#M7001 <P>We have deployed the splunk client to all of our windows servers (a lot of them) One thing we see constantly is "SourceName=Microsoft-Windows-TerminalServices-Printers". (Its a none issue error)<BR /> Is it possible to get splunk to ignore those and not report on them?</P> Fri, 27 Jul 2012 16:49:59 GMT https://community.splunk.com/t5/Knowledge-Management/Windows-TerminalServices-Printers/m-p/19801#M7001 JohnFLi 2012-07-27T16:49:59Z https://community.splunk.com/t5/Knowledge-Management/Windows-TerminalServices-Printers/m-p/19802#M7002 <P>You can send those events to the null queue so they won't be in Splunk. Good example in the docs and included a link to a previous answer on splunkbase for this topic.</P> <P><A href="http://docs.splunk.com/Documentation/Splunk/4.3.3/Deploy/Routeandfilterdatad#Filter_event_data_and_send_to_queues">http://docs.splunk.com/Documentation/Splunk/4.3.3/Deploy/Routeandfilterdatad#Filter_event_data_and_send_to_queues</A></P> <P><A href="http://splunk-base.splunk.com/answers/11617/route-unwanted-logs-to-a-null-queue">http://splunk-base.splunk.com/answers/11617/route-unwanted-logs-to-a-null-queue</A></P> Fri, 27 Jul 2012 17:08:11 GMT https://community.splunk.com/t5/Knowledge-Management/Windows-TerminalServices-Printers/m-p/19802#M7002 sdaniels 2012-07-27T17:08:11Z https://community.splunk.com/t5/Knowledge-Management/Windows-TerminalServices-Printers/m-p/19803#M7003 <P>I will check that out.....Thank you</P> Fri, 27 Jul 2012 17:46:16 GMT https://community.splunk.com/t5/Knowledge-Management/Windows-TerminalServices-Printers/m-p/19803#M7003 JohnFLi 2012-07-27T17:46:16Z