Gerald's space

Script that utilizes SNMPUtil to query a device and log that information into MOM as a performance Counter. Must provide OID in a text file file that you specify. I did it this way some that I query multiple OIDs from one device with one rule. Details of how to set this up are in the top of the script. The example I give in the script is for querying a Blackberry server for stats.

 

I created these scripts that can be used to setup a task in the MOM console that will allow any user to schedule an agent for maintenance mode.  Details on the scripts and setup procedure are in the readme.rtf

 

 

 

I use these scripts to monitor MSMQ on some of our application servers. I find it much easier than just using perfmon. I have links to two versions here.

 

And then an updated version. Same functions except it uses a varset to keep up with the messages on a queue so an event can be created once a queue drops below its threshold.

 

 

This script can be used to resend a notification for all alerts in a specifed rule group if the alerts go unacknowledged for a given period of time. Script requires the GUID of the rule group that contain the alert rules and a time threshold for the age of the alert.

 

 

This script can be used to resend a notification for a single alert if it goes unacknowledged for a given period of time. Script requires the GUID of the rule and a time threshold for the age of the alert.

 

This script sends alerts to different notification groups based of computer groups in MOM. Works well for Heartbeat notifications.

Script should be used as alert response and should be set to run on the management server.

I will give the setup for the script as it is currently. You may want modify the groups names based on your environment.

Before deploying the script you need to do the following in MOM.
1. Setup 3 Computer groups named Region1 Servers, Region2 Servers and Region3 Servers. Add servers to these groups.
2. Setup 4 Notification Groups named Region1 Notification Group, Region2 Notification Group, Region3 Notification Group and Central Notification Group. Add Operators to these groups.

 

Now setup the script as an alert response. Create 4 Parameters for the script. Region1, Region2, Region3 and Central. These parameters should be set to true or false based off if you want to notify a group or not for this alert.

That’s all. When the alert is created, this script will run. If the server is in Region1 then the notification will be sent to the region1 notification group. If the server is not in Region1, 2 or 3, then the notification is sent to the Central group.

 

2 Scripts here. 1 for checking version compliance for SQL Reporting Services and the second for checking the version of SQL 2000. The complinace script in SQL management pack only reads the version in the registry. This could actually be incorrect since depending on your patch level. I have changed the compliance script to run "SELECT SERVERPROPERTY('productversion')" on each SQL instance in order to get the correct version.

 

This is a SQL Space Monitoring that uses a stored procedure to get DB and log used space rather than relying on SQL DMO. Drawback is that you have to place the stored procedure in the master DB for each instance of SQL. But this does seems to be much more accurate than the current SQL space monitoring script. If fact, once we put it in, we got alerts for DBs being past thresholds that we thought we OK.

Currently only tested on SQL 2000.

Zip file contains the script and the stored procedure.

I have to credit the DBAs who helped me with the stored procedure. Without them I would have never got this done.

Also, orginal script was the one comes with the MS SQL Management Pack.

Regards,
Gerald