Why is Windows Services Monitoring important?
Many software applications that run on Windows NT, 2000 or
above run as windows services, running as background processes
with no direct user interface and no logged-on user (e.g.
as a server). They are typically started automatically and
therefore are expected to stay running. If any of these important
services should fail, many users and external services are
immediately affected and so ensuring that these services are
running continuously is a key requirement for most system
administrators.
OpManager's Windows Services Monitoring Features
|
OpManager allows you to monitor windows services either locally
or across multiple servers on the network. OpManager uses
WMI to monitor Windows services and does not require an agent
to be installed on each remote machine.
|
|
When a monitored service fails, OpManager can perform one
of the following actions automatically
- Restart the failed service
- Reboot the machine
- Alert the System Administrator through email or SMS.
|
Important windows services monitored out-of-the-box
In additon to monitoring system level services like HTTP,
LDAP, SMTP etc, OpManager supports monitoring of the following
Windows Services by default.
OpManager monitors availability and response-time for the
following services
Alerter |
FTP |
Net Logon |
DHCP Server |
IAS |
Print Spooler |
DNS Server |
IIS |
RPC |
Disk Manager |
Messenger |
Telephony |
Event Log |
MySQL |
Telnet |
Need Features? Tell Us
If you want to see additional Windows Services monitoring
features implemented in OpManager, we would love to hear.
Click here to continue