pguerrero

Right on!

etg is using the native Windows Events subscription. You can set up a Windows server to act as the event collector for other Windows machines. Windows Event Collector (Windows)

Well, mine started working by trial and error. I deleted the config file and restarted the service, re-created alerts refining as much as I could and now I'm getting events in teh server. Glad that is working but not happy not knowing why it was failing.

How are the queries on the other logs different than the ones on system/application? I have the same error regardless of what log I test to.

The issue seems to be on sending; I think a better troubleshooting tool is the Kiwi Syslog Generator to verify the server can receive and the agent can send via syslog. The problem is with the query in Event Log Forwarder but I can't find what's wrong and neither the setup instructions nor the online help yield any…

Turns out this is the reason: When you are trying to use a 32 bit application and that application is trying to execute an action that calls a feature from System32 (on a 64bit system) you have to use a specific path. (from: http://eddiejackson.net/wp/?p=8929) Mind you, the above is from a 2016 post. Am I the only person…

I'm not sure I fully understand the environment but certain things like file explorer, control panel, etc. cannot run in a different user context. You'd see a similar situation if you try right-click then run as on a program that's in a network drive mapped under the current user's credentials. The solution is to map…