MS7 - Monitor Solution 7 - How to create a Uptime and Availability Monitor Policy using Server Management Suite

Useful  job! Could you create also a avaibility report based on data collected??

thank you

An Availability Report is already included out of the box.  You could also create your own Availability Report as the data is kept in the CMDB in SQL.

Hi Zarba. If you are going to be using the ICMP Availabiltiy Detail report I would first suggest updating your environment to SP4 HF1. You will find some benefits to the underlying reporting mechanism.

Hi all, the server avaibilty report included in Altiris Monitor Solution is based on System Healt and Tuning Policy.

I like to create a similar report based on one o more custom metric.
Also i like to know how work agentless monitoring. Where are saved data by metric collect agentless?
What are requirements to use Agentless monitoring?

I have not understand for example how to create a agentless  HTTP metric collect  that check url  "http://mytesturl"  .
After create metric collect and rule , how policy should be created?? suppose that http://mytesturl is a network device and not a computer

thank you

I have SP4 HF1 :)

Does anyone have an Uptime or Availability ICMP Report that will work with Link or ESX?

Joseph,

Can you show us how to create a report based on this monitor policy?

I created a monitor policy based on this video and it works wonderfully but I need to be able to report on it.

Thank you,

Logan

ICMP can often only show that the NIC is working and responding to pings, but the OS could still be down.

What would be a better metric to monitor if an agentless machine's OS is up or not ?

Is this report meant to return any results out the box?

Mine allways shows zero results. I have the Health and Tuning policies enabled on a number of servers and those are working fine.

I'd really be interested in getting some info out of this report...

Here is my summary with regards to  Network Discovery requirements and “Agent-Less” monitoring:

A Network Discovery task run is required as it will bind the machines specified in the IP Range (IP Range defined in Network Discovery Task)  to the Connection Profile used in that Network Discovery task. This is how the association between resource and connection profile to be used is made. This “resource to connection profile association” is needed for a resource that will be AgentLessly monitored using any of the follow AgentLess Metric sources:

1. HTTP
2. SNMP
3. WMI
4. WS-MAN 

So to summarize; During a Network Discovery Task run, any resource discovered is then associated with the Connection Profile used with the Network Discovery task. (Connection Profile selection is part of the Network Discovery task setup)  In order for our RMS Agent to connect to a resource using a specific protocol, we must have the connection profile binding to that resource.   However, for ICMP protocol, there is not passing of credentials so a Network Discovery need not be done if you are looking to monitor JUST for availability status (up\down) of a resource.  For all other protocols, we would need that “resource to connection profile” binding.