|
I learned what _vbscript_ meant after I left
that job… but as I recall almost everything in Unicenter can be command
line driven. Why not set up a script to parse the services and create an agent
configuration file for each server based on what services should be started
(minus ones you don’t want to monitor like SNMP), on that server? Otherwise
can you set up groups of servers? I bet they’re not all one-offs, and
IIRC you can set up groups for agent configurations and send those
configurations out to those groups, at least you could in v 4.0. I think you could set up an event log rule
on the agents to watch for the phrase “service stopped” to send an
alert too… It can be tedious but if you put some work
into it you will be rewarded. It’s been a while but if you’re new
to CA email me offline if you want specific help, I’ll help with what I
can remember… Rich ----------------------------------------------------------------------- From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Harding, Devon The problem is that we have over 200
servers with different roles. I wish Unicenter had an agent that can look
at a server that is set to automatic and if its stopped, send an alert. I
know MOM does this. This seems link this is going to be a tedious job. - From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rich Milburn Hi When you are configuring
service monitoring, I would start out by getting a list of the services that
are running on each server, and then eliminating the ones that are,
what’s the word I’m looking for... redundant? For example, it’s
silly to monitor the SNMP service with an SNMP agent – if the SNMP
service goes down, you won’t get a report via SNMP. You should
(IMHO) start out monitoring a subset of your total services, and select the
ones that are specific to a server’s function. On each server, pick
out which services are running that, if stopped, will mean a loss of
service. For example, losing MSSQL service would be bad on a SQL
server. WW Web Publishing Service would be bad to lose on a Web
server. And so on. Pick a couple on each server, and monitor those
to start with. Other things to select for are dependencies – not
just in the service defs, but for example if SNMP service goes down,
you’ll have all the others go red and send events too. Otherwise,
if you’re not careful, you’ll end up with a red map all the time,
and it won’t mean anything. I wish I still had lists
for Win2K… but that was 2 years ago on a different continent. Rich ----------------------------------------------------------------------- From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of How can I get a list of the default
services that should be started on a Windows 2000/2003 server? I’m
trying to configure my Unicenter monitoring server Windows
Systems Engineer Southern
Wine & Spirits - BSG 954-602-2469 __________________________________ -------APPLEBEE'S
INTERNATIONAL, INC. CONFIDENTIALITY NOTICE-------
|
