"every action" ???
That is not really what syslog is for. Syslog records the messages sent by systems when triggered by events. It records events for diagnostics, not every action. Overall using a syslog server is wise, but trying to log every action is probably not wise: for one thing you will fill up disks very rapidly.
Not saying you cannot do that, just that you probably should not and that syslog may not be the right tool for that job.
Now if you only want to echo the event log to a syslog server, check out this link for some ideas.
After you consider that, check out http://aplawrence.com/Reviews/NTSyslog.html
for another solution.
See the problem here is that MS (in their infinite wisdom) chooses to NOT use anyone else's standard solutions until the market forces the issue. (Remember how long it took them to decide it was OK for Windows to do native TCP/IP? I do.) Up to Win2k at least (I stopped checking after that) no windows product nativly spoke syslog. You have to run something that can YANK the log entries out, or add software to windows to make it play well in polite society.
Best of luck!