>If there's an answer other than the ones outlined in that link, I'd like to know it, too.
>
>Actually, that's just one example of spurious Event Log messages being generated. If you're analyzing logs it would be nice to have some way to ignore them during analysis, if they can't be stopped from polluting the logs themselves.

Yes, this is why I built this advanced real time event viewer at the Web site level. It pulls out all the logs from all servers for our environments and summarizes it in full list and by importance (Critical, Error) by TimeCreated, RecordID as well as offering a global view of the entire network so to know exactly what happens at the exact time.

For that printer issue, we had a procedure that each of us did when we moved to VM to make sure the printer settings are not broadcasted. However, today, a system engineer logged into the servers, and of course this procedure was not applied on the related client RDP connection, so it created a bunch of errors.

However, with this event viewer I have now, I can apply filters and conditions to fit it in exactly the way I want. So, I can decide to have those being ignored so they will never be logged, for example, or be logged and be moved away to archive immediately as they are created.