|
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 Harding, Devon 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 __________________________________
|
- RE: [ActiveDir] Default Ser... Rich Milburn
- Re: [ActiveDir] Defaul... Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
- RE: [ActiveDir] Defaul... neil.ruston
- RE: [ActiveDir] Defaul... Harding, Devon
- RE: [ActiveDir] Defaul... Rich Milburn
- Re: [ActiveDir] De... Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
- RE: [ActiveDir] Defaul... Rich Milburn
