- This topic has 12 replies, 4 voices, and was last updated 14 years, 4 months ago by
.
- Posts
-
To clear a particular event log (application, system, security, etc)
Open command prompt:
wevtutil cl LOGNAME ; where LOGNAME is the name given to the log.
For example under Windows Logs in Event Log if you wish to clear the Application portion.
wevtutil cl Application
To find the given name of the event log right click on it and choose Properties. It is listed under full name. For example the Microsoft Office Diagnostics log under Application and Service logs is listed as ODiag so to clear it i would type
wevtutil cl ODiag
You can go through the logs manually and build a a batch file that clears the entire Event Logs or just particular ones you care about. I have a logon script that clears all the “Windows logs” on startup.
My script:
wevtutil cl application
wevtutil cl system
wevtutil cl security
wevtutil cl setup
wevtutil cl forwardedevents
wevtutil cl hardwareeventsSave as clearwindowslogs.bat
To clear a particular event log (application, system, security, etc)
Open command prompt:
wevtutil cl LOGNAME ; where LOGNAME is the name given to the log.
For example under Windows Logs in Event Log if you wish to clear the Application portion.
wevtutil cl Application
To find the given name of the event log right click on it and choose Properties. It is listed under full name. For example the Microsoft Office Diagnostics log under Application and Service logs is listed as ODiag so to clear it i would type
wevtutil cl ODiag
You can go through the logs manually and build a a batch file that clears the entire Event Logs or just particular ones you care about. I have a logon script that clears all the “Windows logs” on startup.
My script:
wevtutil cl application
wevtutil cl system
wevtutil cl security
wevtutil cl setup
wevtutil cl forwardedevents
wevtutil cl hardwareeventsSave as clearwindowslogs.bat
WTH halladayrules? Did you even read my post? I don’t know how makes it clearer I both know how to clear the event log, how to use wevtutil’s syntax as my script for clearing works… The thread is not about clearing the event log, it’s about HALTING event logging…
Your script doesn’t even work as there are over
Please!?
😕
WTH halladayrules? Did you even read my post? I don’t know how makes it clearer I both know how to clear the event log, how to use wevtutil’s syntax as my script for clearing works… The thread is not about clearing the event log, it’s about HALTING event logging…
Your script doesn’t even work as there are over
Please!?
😕
Sorry yesterday was a long day for me lol u know how that can be.
Your script works fine.
It disables all the logs that are able to be disabled.
The wevtutil sl log_name /e:false is the same as right-clicking on the log and choosing “Disable log”
As the same with wevutil sl log_name /e:true
GUI version:
If you notice when you try to right-click on any of the logs that fall under Windows Logs (i.e Application, System, etc) the Disable/Enable log option is not available which leads me to believe that it is not supported or not practical.
Disabling all the event logs or “halting” as you call it renders the Windows Event Log service useless. If you are intending to halt or disable event logging why not just disable the Windows Event Log service altogether. As long as you don’t depend on or use the Task Scheduler service or Windows Event Collector service you are better off just disabling the service.
Sorry yesterday was a long day for me lol u know how that can be.
Your script works fine.
It disables all the logs that are able to be disabled.
The wevtutil sl log_name /e:false is the same as right-clicking on the log and choosing “Disable log”
As the same with wevutil sl log_name /e:true
GUI version:
If you notice when you try to right-click on any of the logs that fall under Windows Logs (i.e Application, System, etc) the Disable/Enable log option is not available which leads me to believe that it is not supported or not practical.
Disabling all the event logs or “halting” as you call it renders the Windows Event Log service useless. If you are intending to halt or disable event logging why not just disable the Windows Event Log service altogether. As long as you don’t depend on or use the Task Scheduler service or Windows Event Collector service you are better off just disabling the service.
Yes, the NT 6.1 event system is somewhat FUBAR; ie. it doesn’t appear to behave at the kernel level the way Mark Russinovich describes. Disabling the Windows Event Log Service does not stop disk writes as the NT Kernel still attempts to write events, and though no event is stored, a disk write still takes place… I thought if the proper interface were used and logging were halted with /e:false in UNIX fashion this would stop, but this doesn’t appear to work either…
😐
Yes, the NT 6.1 event system is somewhat FUBAR; ie. it doesn’t appear to behave at the kernel level the way Mark Russinovich describes. Disabling the Windows Event Log Service does not stop disk writes as the NT Kernel still attempts to write events, and though no event is stored, a disk write still takes place… I thought if the proper interface were used and logging were halted with /e:false in UNIX fashion this would stop, but this doesn’t appear to work either…
😐
I did some disk monitoring on my Windows Server 2008 32-bit box to see how it behaves on my machine. I used the DiskMon sysinternals utility. I have the Windows Event Log service disabled in this scenario.
Here’s the results I got:
Total Reads + Writes
0-10 mins: 15,570
11-20 mins: 689
21-30 mins: 1,191
31-40 mins: 52
41-50 mins: 0
51-60 mins: 0Not a single disk write occurred for another 34 minutes when all of a sudden it went active for a second. Over 5,000 reads/writes occurred. I went into Resource Monitor (task manager) and I pinpointed that my antivirus was downloading a large signature update. During the first hour of up time on my machine 28,000,000 bytes were devoted to ESET Antivirus, the next closet was Eboostr with 300,000. The next closet was under 10,000.
Gotta love Server 2008.
I did some disk monitoring on my Windows Server 2008 32-bit box to see how it behaves on my machine. I used the DiskMon sysinternals utility. I have the Windows Event Log service disabled in this scenario.
Here’s the results I got:
Total Reads + Writes
0-10 mins: 15,570
11-20 mins: 689
21-30 mins: 1,191
31-40 mins: 52
41-50 mins: 0
51-60 mins: 0Not a single disk write occurred for another 34 minutes when all of a sudden it went active for a second. Over 5,000 reads/writes occurred. I went into Resource Monitor (task manager) and I pinpointed that my antivirus was downloading a large signature update. During the first hour of up time on my machine 28,000,000 bytes were devoted to ESET Antivirus, the next closet was Eboostr with 300,000. The next closet was under 10,000.
Gotta love Server 2008.
Interesting, and thank you for posting halladayrules! While I did see a sort of (pretty ragged really) gradual slow down for about the first 20 minutes with my minimal service complement, it stayed at about 50 w/m for two hours at which point I gave up; perhaps this is hardware/driver specific…
Regardless, I found an interesting solution for SSD users that want to minimize writes to disk in the 64-bit edition of the Windows 7 Embedded Demo in the form of the Enhanced Write Filter.
It was a bit of a trick to port and install on Server 2008 R2, but I did get it to work, and as it caches all writes to RAM, it even offers some performance (and security) enhancemnt on HD systems. Pretty nifty driver/feature Microsoft has made with this as it can be disabled live flusing any changes to disk, and then reset at boot.
:ugeek:
Interesting, and thank you for posting halladayrules! While I did see a sort of (pretty ragged really) gradual slow down for about the first 20 minutes with my minimal service complement, it stayed at about 50 w/m for two hours at which point I gave up; perhaps this is hardware/driver specific…
Regardless, I found an interesting solution for SSD users that want to minimize writes to disk in the 64-bit edition of the Windows 7 Embedded Demo in the form of the Enhanced Write Filter.
It was a bit of a trick to port and install on Server 2008 R2, but I did get it to work, and as it caches all writes to RAM, it even offers some performance (and security) enhancemnt on HD systems. Pretty nifty driver/feature Microsoft has made with this as it can be disabled live flusing any changes to disk, and then reset at boot.
:ugeek:
- You must be logged in to reply to this topic.
