• A User is logged in to session 0 (Not RDP) and that user’s user name starts with “svc”)
• A Z: Drive is mapped and that it’s remote path starts with “\\Server\remote path”

Unlike other security software products, secRMM is designed as a light-weight security software product. What this means is that when secRMM does not need to be running, it enters into a quiescent state. The secRMM software will run only when a Removable Media device is plugged into the computer. This means that your end-users will not feel a performance impact from the secRMM software in their normal day-to-day computer work activities.

secRMM logs events into the Windows security event log. secRMM comes with a free Microsoft Operations Manager (OpsMgr) Mangement Pack that will create OpsMgr alerts from the secRMM events.

For details and download, please visit http://www.squadratechnologies.com

• Scripts are composed in a shared data sources to support ‘cookdown’
• New classes for better targeting and granularity
• Most of the collection rules have a short knowledge articles
• Added the Unit Monitor that checks for friendly names config file existence and generates an alert (including a knowledge base article)
• Minor scripts improvements. New scripts a little bit more stable and should not fail if you do not have an optional components (like a data replication groups) on your EVA
• New views
• Collection Rules for Windows PerfMon Counters are added (this rules are disabled by default)
•  Diagnostic task for Disk Group - Average Write Latency Monitor shows a TOP 5 virtual disks for Write Latency (not for activity, we're found that top 5 active (in+out MB\s) disks don’t help us to  troubleshoot, just because our biggest virtual disks are always on top, not the slowest disks which are the 'latency generators')
• New reports (defined in the dedicated management pack)

 (ver. 3.0.0.222):

• Fixed typo in diagnostic scripts
• Changed the Event Source for the event that diagnostic task create

Example MP for extending the SharePoint Monitoring.
- Monitoring of different SP Service
- Monitoring of Site Collection Sizes
- Monitoring of Content DBs
- Monitoring of SP SQL Instances

There will be warning events created if size limits are reached.

feel free to edit and use.

The SCOMGUY Opalis 6 Management Pack includes discoveries, service monitors, alerts, and views to assist Operators in detecting issues with Opalis Integration Server 6 servers.

·         Discovers Opalis 6 server components
·         Monitors Opalis 6 NT services
·         Agent Tasks to remedy service failures
·         Alerting Rules for Opalis 6 exceptions in the text logs
·         Opalis server state views for Role, Components and Services

Designed for use with Opalis 6.3 and SCOM R2

Download the package from the source by clicking the Download button.  

Click the Download button to read the technical details and download from the source.

This simple management pack augments Essentials 2010 functionality by adding one-click magic packet delivery using a custom task. The pack includes a custom view and custom task each targeting the 'Network Adapter (Client)' class. 

Requirements

• Requires the free Depicus wake-on-LAN command line utility (wolcmd.exe) extracted to c:\tools.
• Also requires that wake-on-LAN functionality is available and enabled in your managed client computers. 

For example, Dell makes a utility you can use to enable wake-on-LAN on your Dell desktop and laptop computers through a msi package created with the Dell Client Configuration Utility (DCCU).

• Instructions available at http://www.delltechcenter.com/page/Enable+Wake+On+Lan+with+DCCU.
• Download DCCU HERE.

Known Issues

Due to the way the IP addresses are stored on the Network Adapter class, this task will only work for client network adapters with a single IPv4 address. This means IPv6 should be disabled on the client network adapters in your environment. This should be doable for DHCP clients in most environments today.

UPDATE: 6.0.0.1 version added to resolve issues with alert closing for alerts older than an hour or older than a day.

Filename	Description
System.Uptime.Monitoring.xml	System Up Time Monitoring (unsealed)
Or
System.Uptime.Monitoring.mp	System Up Time Monitoring (sealed)
OM2007_MP_SystemUpTime.doc	This management pack guide.

Group	Contents
Computers Rebooted Daily	This group can be populated either explicitly or by using dynamic rules to contain systems that have planned scheduled daily reboots. (86400 seconds or 1 day)
Computers Rebooted Weekly	This group can be populated either explicitly or by using dynamic rules to contain systems that have planned scheduled weekly reboots. (604800 seconds or 7 days)
Computers Rebooted Monthly	This group can be populated either explicitly or by using dynamic rules to contain systems that have planned scheduled Monthly reboots. (2592000 seconds or 30 days)
Computers Rebooted Quarterly	This group can be populated either explicitly or by using dynamic rules to contain systems that have planned scheduled Quarterly reboots. (7776000 seconds or 90 days)

Name	Enabled	Type	Description
System Uptime Daily Reboot Monitor	False	Performance	This monitor checks the status of the System Up Time based on the Windows performance counter System: System Up Time. By default, this monitor is disabled. This monitor is configured with a threshold of 1 Day (86400 seconds) and is targeted towards computers in the ‘Computers Rebooted Daily’ group.
System Uptime Weekly Reboot Monitor	False	Performance	This monitor checks the status of the System Up Time based on the Windows performance counter System: System Up Time. By default, this monitor is disabled. This monitor is configured with a threshold of 7 Days (604800 seconds) and is targeted towards computers in the ‘Computers Rebooted Weekly’ group.
System Uptime Monthly Reboot Monitor	False	Performance	This monitor checks the status of the System Up Time based on the Windows performance counter System: System Up Time. By default, this monitor is disabled. This monitor is configured with a threshold of 1 month (30 Days or 2592000 seconds) and is targeted towards computers in the ‘Computers Rebooted Monthly’ group.
System Uptime Quarterly Reboot Monitor	False	Performance	This monitor checks the status of the System Up Time based on the Windows performance counter System: System Up Time. By default, this monitor is disabled. This monitor is configured with a threshold of 1 Quarter (90 days or 7776000 seconds) and is targeted towards computers in the ‘Computers Rebooted Quarterly’ group.

Name	Enabled	Type	Description
System Uptime Collection Rule	True	Performance	This rule collects the 'System Up Time' performance counter. By default it is configured to collect hourly.

Name	Description
System Up Time Report	A general system up time report, chosen by computer group, containing computer name and system up time in descending order by longest up time. Best viewed as an excel spreadsheet.

Name	Description
System Up Time Compliance Report	Chosen by computer group like ‘All Windows Computers’, this report shows computers that have a system up time greater than desired. Best viewed as an excel spreadsheet.

Name	Type	Description
System Up Time Alerts	Alert	All alerts generated from the System Up Time Monitoring Management Pack

Name	Type	Description
System Up Time Performance	Performance	All System Up Time performance counters on all Windows Computers
Just a standard performance view.

Please first read the documentation otherwise the MP will fail…..as you already know as SCOM Experts ;-)

If you have Feedback or addons to the MP please feel free to send them in!

The SQL Server DB Mirroring Management Pack discovers database mirroring components and provides probe based monitors to verify that database mirrors are operational. Optionally it verifies the roles and operating modes of mirrored databases against a Desired Configuration setting.

• Monitoring the availability state of mirrored databases and witnesses.
• Monitoring if the mirrors are operating in line with a Desired Configuration definition.
• View mirrored DBs as a service components and use them for Distributed Application designs.
• Report on SQL database mirroring configuration.
• Use the objects and groups discovered to add SQL database mirroring specific rules, monitors or overrides.

The Management Pack download contains a comprehensive guide that carefully lists all prerequisites. As a supplement it also contains an override MP that works in conjunction with the Extended Microsoft SQL Server MP hosted on OpsManJam. It shows how to use the discovered objects of the SQL Server DB Mirroring MP to parameterise existing or new MPs to support DB mirrors.

Download the SQL Server DB Mirroring Management Pack by clicking on the Download button in the upper right corner (bust be logged in - registration is free).

Change History