Purpose of ALATOMAWUNOBE
------------------------

Reduce unwanted alerts sent by WUP. Here is a typical usage scenario :

Server-A is a DNS server and you have three active monitors on it :

Ping => Check that device is reachable
DNS => Check DNS is OK
Disks => Check that the Raid-array disk is OK

Of these three monitors, we can consider that Ping is a CRITICAL one. By 
critical I mean that, if Ping is down, DNS and Disks will be done -simply 
because Wup will not be able to actually check these monitors if Server-A is 
completely down !

So I want alerts to behave this way :

* If DNS goes down and the rest is OK, send me a mail.
* If Disks goes down and the rest is OK, send me a mail.
* If Ping goes down, definitely send me a mail, but please DON'T send me two 
additional mails (one for DNS and one for Disks), because I KNOW that 
Server-A is down !

Please note that my complete scripts also include the capability to send an 
Sms for alerting -in fact what I do is an SMS for critical monitors and an 
email for non-critical monitors. However I cannot give this SMS stuff 
because it relies on a licensed activex from microsoft.

How to use
----------


A/ Set up the environment (to be done only once)
------------------------------------------------

A.1/ Place the MD-Alerter.vbs script in some directory of the Wup server 
(avoid using directory names with spaces or longer than 8 chars, since I 
don't handle this very well).

A.2/ Edit the MD-Alerter.vbs script and correct the following constants :

A.2.a/ c_MailSrv => FQDN of your mail server
A.2.b/ c_MailFrom => Email address FROM which the alerts will be sent
A.2.c/ c_VbPath => Path to the Sms alert script -useless because I can't 
provide this script due to licensing issues


B/ Create your alarm definitions (as many as needed)
----------------------------------------------------

B.1/ In What's Up, define a VbScript action script policy (in this example I 
will call it AlaMail). Copy the code from "MD-AlertLauncher.vbs" and paste 
it into that monitor.

B.2/ Adapt the code to your needs and correct the following constants :

B.2.a/ c_MailTo is the email address(es) where the alert should be sent. You 
can use several recipients, separated by semicolons.
B.2.b/ c_CriticalMonitors is the list of critical monitors. You can use 
several of them, separated by semicolons. Note that the names to use are the 
active monitor names as they appear in Wup (for instance HTTP, Ping, 
SMTP...).
B.2.c/ c_VbPath is the full path to the MD-Alerter.vbs script. Correct this 
constant to match the path you defined in step 1/.

C/ Assign your alarms (as many as needed)
-----------------------------------------

The AlaMail script MUST be assigned to each and every active monitor defined 
on the device you want to manage. Using it as a global action DOES NOT WORK 
-because the global action in Wup does not expose to the script WHICH active 
monitor went down or up.