I see where JAL supports reading the event log for the machine the software resides upon, but is there a way to specify reading the event log of other servers?

Thanks...

You can use 24x7 Remote Agents running on remote servers to access NT event logs, files and other staff on these computers from virtually anywhere.

: I see where JAL supports reading the event log for the machine the software
: resides upon, but is there a way to specify reading the event log of other
: servers?

: Thanks...

: You can use 24x7 Remote Agents running on remote servers to access NT event
: logs, files and other staff on these computers from virtually anywhere.

Are you saying I cannot have a single agent monitor remote servers, that I must have a copy of 24x7 running on every server where I want to monitor the event log?

24x7 built-in functions don't support "remote registry" access at this time.

Here are some alternatives to using 24x7 Remote Agents for reading remote registry:

1. Use VBScript jobs in 24x7 to access remote registry using third-party COM objects. Try searching on the Internet for "Read Registry COM"

2. Use some existing or create your own DLL as an extension to 24x7. You can call your DLL functions from JAL jobs. See CALL in the on-line help for more info.

You should also test the overhead caused by reading/monitoring remote registries over the network, to check if you can tolerate it in your environment.

: Are you saying I cannot have a single agent monitor remote servers, that I
: must have a copy of 24x7 running on every server where I want to monitor
: the event log?