Hi Erik D--
What version of Ip Monitor are you running?
I'm runnin 9.0.6.
EDIT: running 10 now :)
Great that you've upgraded, but that was what I was going to suggest doing to fix the problem. Let me check with the product manager and I'll get back to you.
Is it possible to pass user/pass from the monitor to the action (psexec.exe's -u & -p)?
It is not possible to pass the account and password out of ipMonitor in clear text. I'm sure if you could, administrators would freak out! ;)
My advice is to skip the "-u" and "-p" option. Instead, have ipMonitor impersonate an account capable of starting the remote process (by specifying a windows credential).
1) Create identical accounts on both computers (same pw & username).
2) Verify you can log the account on both boxes.
3) Try running psExec from the ipMonitor box, and verify it works.
4) Next, give the windows credential to ipMonitor within the alert.
5) Test the Alert.
If there is a trust relationship, skip the part where you create identical accounts on both computers.
Give it a try, let me know how it goes.
Guess u have a point there ;)
Hmm, setting the credential within the action works but isn't it possible to pass the credential used on the failing monitor? The default 'restart service'-action seem to be able to get the credential from monitor (it dont haven have its own credentials...).
I guess its not possible in current release but could it be made possible in the next? I see no reason why one should define the credential on the action on some actions where the other actions can "take" it from the failing monitor.