It appears you are trying to get the executable to run on the remote system. This would be like going to start -> run and running \\server\path\script\inetrestart.exe. No matter how hard you try, the exe will always run on the box you are on.
In order to have the exe run on the remote system, you will need to run a utility such as psexec (for Windows) or plink (for Unix) which will login to the remote system and run the exe on that system. You would then configure the External Process Action with the following parameters:
Executable Name: psexec.exe
Command Line Parameters: \\server -u [user] -p [pwd] [cmd]
Startup Directory: c:\path_to_psexec\
For more on psexec: http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
Hope this puts you in the right direction.
I did what you said but I'm a little confused because
I create a external process to trigger right after my intranet goes down
right now the "external process" in in warn state why is that it suppossed to be in green state is not right?
how it will know when to lunch I'm a little out of focus in this.
if you can tell me what is the different bewteen "external process" and "add action ==> external process"