Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I asked this question in SuperUser without much luck and so I am posting it here to see if anyone can assist.

We have a central syslog server and we want it to capture event log events from Windows hosts. We are specifically interested in logging service start/stop events. We installed "Eventlog to Syslog" on these windows hosts and all works well with XP hosts (Events come from Service Control Manager). However, we are having issues with Win2k hosts. For some reason, service start/stop events do not get logged in the Event Log for Win2k hosts. I got another friend from another company to test on a Win2k host and he does get start/stop events on them. I have searched around for local audit policies i need to enable but with not much luck. Anyone have any ideas?

Thanks in advance.

share|improve this question

Try with syslogAgent ( which doesn't need any special configuration (I haven't try eventlog so i don't know).

If it fails again, then your audit deamon is propably deactivated. Otherwise, the problem is eventlog's configurations. (Maybe it will help you )

share|improve this answer

My initial suspicion would be that something like the COM+ or SENS services are disabled or broken on your W2K servers. I'm not certain that either of these would cause your problem but they would be a good place to start. If you are still getting logon\logoff events on the affected systems then this isn't likely to be the cause as those will be disabled if something is wrong with either of these services. It might be worth working through the list of "standard" Windows 2000 services here to see if there is anything significant that is either disabled or failing to start.

You can use SysInternals Process Monitor to try and zero in on anything that is failing when you Start\Stop some services. It may not be able to help in this case but there's a good chance that if there is an error or an access rights issue preventing the events being logged then Process Monitor should report that every time you start\stop services.

Another approach that might work, even if you can't figure out how to get the stop\start events themselves to generate events, is to enable auditing on the services. If you are using actual service accounts for the services themselves then you should be able to trap the account logon\logoff events associated with starting\stopping the associated services. This Technet link should get you started if you want to try this.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.