Message Management

The Tools

Tool  Description
autoack.zip Updated Feb 28, 2011! This .NET application will automatically acknowledge messages longer than the specified time span.  This application replaces autoack.vbs, which would cause deadlocks on certain configurations.   You must install the .NET framework 1.1 from Microsoft.  This tool only runs on the management server.

Updated 2/28/11 with a correction so AutoAck and AutoAckWindow works with Version 8.16 and 9.0 correctly.

Updated 7/29/05 with a new tool, AutoAckWindow.exe to handle "windows" of events (older than one hour, but newer than 3 hours)

Updated 5/27/05 with new handling to disown owned messages then acknowlege them (see readme for instructions how to disable this new default behavior)

Updated 4/30/04 to avoid deadlocks with large message volumes (implemented as an async client now)

Updated 4/16/04 to add extended WQL queries to autoack.

The Scripts

Use these individual scripts to perform programmatic message management on OpenView Operations for Windows servers.    These scripts must be run on the Operations server, and require (in most cases) a single input parameter - the Message ID you wish to act on.

These scripts MUST be run with cscript.exe to display properly.   To make cscript.exe your default script engine, run cscript.exe /h:cscript.

Download the scripts here:  msgscripts.zip

Script Name (<mandatory parameters> [optional parameters]) Description
ovowack.vbs <messageID> Acknowledge an active message.
ovowown.vbs <messageID> Own an active message.
ovowunack.vbs <messageID> Unacknowledge an acknowledged message.
ovowdisown.vbs <messageID> Disown an active message.
ovowanno.vbs <messageID> <"annotation text to add"> Annotate a message.  This adds a new annotation to an existing message.   
ovowlistmsgs.vbs [file] List all active messages (optionally, write them to a file).  This might be handy for a report generated daily of active messages.
ovowgetmsg.vbs <messageID> Get message details on a single message in the message database.
ovowsev.vbs <messageId> <Severity> Change an existing message severity.  This will notify all of the consoles of the state change, on the fly.   The second parameter is the SEVERITY - which must be one of these values:
1  Unknown
2  Normal
4  Warning
8  Minor
16 Major
32 Critical
ovowtext.vbs <messageId> <"new text"> Change the text of an existing message.  The first parameter is the ID of the message, the second parameter is the new text to put on the message.  The old text is saved as an annotation.
ovownodemessages.vbs <primarynodename> [optional file] Dump all of the messages for a given node to standard output.  Optionally, write it to a file that's in a suitable CSV format for use in Excel.
ovowgetanno.vbs <messageId> Get the annotations of a message.   Useful for getting message histories, etc.



    

    

These scripts utilize the WMI OV_Message Object to perform various methods on OpenView messages.