WMI based monitors Windows 2003 Server
Hi,
I'm trying to monitor a few Windows 2003 Server boxes, but when I e.g. add a CPU monitor and run a test, it fails with:
Possible reasons
1. The device might be down.
2. The username and password provided for this device might be wrong.
3. The domain password for this device was not provided
4. The domain password for this device might be wrong
The credentials /are/ correct!
When I run the scripts in conf/application/scripts on the command line from the box running OpManager they seem to work fine (e.g memory.vbs, cpu.vbs).
Also, I can't get OpManager to run scripts based on raised alarms. I'm trying to run a batch script (via Notification Profile - run Program), but no joy. The script is not called. Where can I start to debug? Log files?
A few suggestions to improve an already excellent product:
* Custom monitoring. Allow the user to run monitoring scripts and raise alarms based on return value: retvalue != 0 -> alarm.
* Custom monitoring 2. Poll TCP port on given host on definable intervals and raise alarm based on return value (Integer + "\r\n"). retvalue != 0 -> alarm.
* JMX / MBeans: incorporate JMX - a killer that would wipe out all competition. Something like MC4J Management Console with triggers and alarms. Really useful for Java application developers and system managers.
Regards,
--
Thomas
Also, I few suggestions (IMHO) to improve an already excellent product:
1. Custom monitoring scripts
I'm trying to monitor a few Windows 2003 Server boxes, but when I e.g. add a CPU monitor and run a test, it fails with:
Possible reasons
1. The device might be down.
2. The username and password provided for this device might be wrong.
3. The domain password for this device was not provided
4. The domain password for this device might be wrong
The credentials /are/ correct!
When I run the scripts in conf/application/scripts on the command line from the box running OpManager they seem to work fine (e.g memory.vbs, cpu.vbs).
Also, I can't get OpManager to run scripts based on raised alarms. I'm trying to run a batch script (via Notification Profile - run Program), but no joy. The script is not called. Where can I start to debug? Log files?
A few suggestions to improve an already excellent product:
* Custom monitoring. Allow the user to run monitoring scripts and raise alarms based on return value: retvalue != 0 -> alarm.
* Custom monitoring 2. Poll TCP port on given host on definable intervals and raise alarm based on return value (Integer + "\r\n"). retvalue != 0 -> alarm.
* JMX / MBeans: incorporate JMX - a killer that would wipe out all competition. Something like MC4J Management Console with triggers and alarms. Really useful for Java application developers and system managers.
Regards,
--
Thomas
Also, I few suggestions (IMHO) to improve an already excellent product:
1. Custom monitoring scripts