Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Possible Duplicate:
What tool do you use to monitor your servers?

I manage two Windows development servers which are part of a much bigger network. I would like to monitor these two servers, but I want to avoid any situation which could probe or map the entire network. Most other workstations and servers are managed by a dedicated team and mapping out the network would probably set off alarm bells. Not to mention, I'm only interested in these two servers.

As an example: Spiceworks wants to do a network scan on first run. I want to avoid that and just configure in the specific servers I need to monitor. What would be a good server monitoring package for this situation?

share|improve this question

marked as duplicate by Shane Madden, Ward, EEAA, Sven, MDMarra Nov 29 '11 at 15:03

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

can you let us know what you would like to monitor. It would help us think of a better tool. but as @BoBo said for just PING Response and network link PRTG is the way to go. – t1nt1n Nov 29 '11 at 8:25

Nagios is pretty popular

You might also want to check out a fork of Nagios

share|improve this answer

You don't mention what you want to monitor but PRTG (Paessler) will give you 10 sensors for free which might be enough to get you going. You only need to know the name and have credentials for accessing them.

Have you spoken to the monitoing group and see if they can do it for you? They might prefer to have it within the larger system.

share|improve this answer
+1 PRTG is awesome for a small Windows environment. – Nic Nov 29 '11 at 7:14

Not the answer you're looking for? Browse other questions tagged or ask your own question.