Monitoring processes
Next step was to install on a 2003 server and monitor 2 PC’s, setting these up no problems. After configuring these devices to check for a running process, if process not running start the process – again simple enough but what is happening is if the process is not running on either of the PC’s process starts on the SERVER not on the PC’s – this is weird HELP.
I started doing some testing to see whether IT Service View would continually poll for said running process, if process was found not to be running Service View started said process (on the server) – this was great, but discovered if I stopped said process Service View would not restart it. Any help would be greatly appreciated.
Check these things
You've seen that IT Service View has Responses, and then you choose what you want the Response to do.
OK, there are two responses that do different things, but sound similar. 'Run Local Programs' and 'Launch a Windows Process'.
'Run Local Programs' does just that. It runs a program on the same machine as ITSV. It is intended for people that have set up admin scripts and programs that are always run from an admin machine centrally.
'Launch a Windows Process' however launches a process on the monitored, remote machine provided you are using WMI.
If you are using this, make sure that the Command Line field includes the path of the .exe you want to run.
As it says in the Help, if the process you are launching has a User Interface you won't be able to see it - but it will be there. WMI launches programs like these into Session 0 where you can't see the UI.
Let me know if this fixes your problem.