| that actually isn't an unreasonable suggestion but it does limit you to actually setting it up on each specific box and if you ever want to change anything you have to do it everywhere manually.
I figured out how to make it work in .NET today after a lot of searching and trying and asking on forums. Essentially you don't need to do the impersonation option and you need to set the options.enablepermissions to true. From what I can gather (and I may be wrong) when you open a wmi connection and use impersonate it attempts to run on the remote machine with the user credentials you launched your process with on whatever machine you physically at. It really doesn't seem to like that.
If you just skip specifying the options.impersonate property it works fine as long as you then specify appropriate credentials through the options property. So far I have it working so that I can connect to any computer on the network I specify and can backup and clear the log. With a little bit of work I hope to make it so that I can even specify a UNC path to backup to.
If I manage to make that work I can now launch one process at the server and go out and get every machines security log on the network instead of walking around to 30+ stations that have between 1 and 9 computers each.
If you are interested I'll share it once I have it working like I want.
__________________  |