Do I need a third party tool for this?
feedback
|
|
Microsoft purposely prevents you from doing this. The whole concept of the Event Viewer is to present to you certain events that may require your attention. If one could go in and delete any old random event, then the system could in a sense be compromised without you knowing, therefor making it unsafe. If you are having an event logged that is and error....find out what is causing the problem and fix it. You don't want to patch a hole in a dam by sticking a wad gum in the hole. If something is logging informational or caution events too much, then many times the event log source (either Microsoft or a third-party) has some setting that indicates how often or to what level of logging to configure for an application. And that is where you go to minimize the logging, not by doing surgery on the event log. | ||||
|
feedback
|
|
The only thing you can do in Windows is clear the whole log. I only found one third party app that claims to do this -Winzapper, however I have never used it and it states it is for NT and 2000 so I do not know if it will work for server 2003/2008. Be aware that there is potential for corruption of the Event log when using these, so tread carfeully. | |||
|
feedback
|
|
The OP's post if valid. The number one problem with logging, error reporting, and alerting is white noise. When too many "errors" are reported and most of them are low priority or of no concern at all, administrators tend to ignore ALL errors. Good or bad, this is just a fact of life. One of the errors he is talking about is (I think) event ID 1111. It simply means that you have a printer mapped with a driver that is not available on the server to which you are connected. It is an error of no concern in most cases ... there is nothing to "fix" as it is not a problem. If you want to find actual problems and you have specific event ID's that you don't care to weed through, create a custom view with the following steps ...
Now when you wish to look at your event log, use your custom view and only the information you are truly concerned with will be displayed. I know that this is a late post to a dead thread but hopefully it helps someone else who is Googling this more than posts of "[Working as intended, n00b!]" ;-) | |||
feedback
|
|
What might solve your problem is to change the audit policies in group policy. Without knowing what specifically you want to not show up, I'm not sure if there's a setting for it, but here's an example. In GPMC, drill down through Computer Configuration - Windows Settings - Security Settings - Local Policies - Audit Policy. There's not a TON of granularity here, but maybe you can get rid of what's filling up your logs. (My DCs aren't 2008, so this is what I've got from a 2003 AD perspective, hopefully it's not completely different) | |||
|
feedback
|