Logo
programming4us
programming4us
programming4us
programming4us
Home
programming4us
XP
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server
programming4us
Windows Phone
 
Windows Server

Windows Server 2008 R2 : Configuring Operations Manager 2007 R2 (part 4) - Notifications and Subscriptions

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
3/18/2011 9:31:48 PM

Notifications and Subscriptions

When alerts are generated in the console, there is a wealth of information available about the nature of the problem and how to troubleshoot and resolve it. However, most administrators will not be watching the console at all times. Operations Manager has a sophisticated notification mechanism that allows alerts to be forwarded to email, SMS, IM, or even a command-line interface. The most common method of alert notification is email.

However, Operations Manager generates a lot of alerts. If each one of these alerts were forwarded, this would overwhelm the average administrator’s Inbox and prove totally useless. Operations Manager has two alert parameters to help categorize the alerts. Each alert has two parameters that help guide the notification process, severity and priority.

Alert Severity is the first and main parameter. There are three severity levels:

  • Critical (2)— These alerts indicate that there is a problem that needs to be fixed immediately and is directly actionable (that is, there is something that can be done).

  • Warning (1)— These alerts indicate that there is a problem, but that it might not be immediately impacting the environment or might not be directly actionable.

  • Information (0)— These alerts indicate that there is something that is good to know, but might not be a problem nor is actionable.

By the nature of things, there are a lot more warning alerts generated than critical alerts. In general, notifications should only be sent out for critical alerts. That is, there should never be an email sent for a warning or informational alert.

Alert Priority is the second parameter that qualifies the alert status. The priority allows management pack authors to make some alerts more important than others. There are three levels of priority as well:

  • High

  • Medium

  • Low

In general, a high-priority, critical severity alert is very important. This includes events like an agent down or a security breach. A medium-priority, critical severity alert is important. Both are generally actionable.

The best practice is to create two SMTP channels to deliver the alert notification emails, which are as follows:

  • SMTP (High Priority)— High-priority email to an SMTP gateway

  • SMTP (Regular Priority)— Regular email to an SMTP gateway

Then, create two notification subscriptions that use the Severity and the Priority to select the emails to be sent:

  • Notification for All Critical Severity High-Priority Alerts

  • Notification for All Critical Severity Medium-Priority Alerts

This provides a configuration that will deliver the very important alerts (high-priority critical severity alerts) via high-priority email and important alerts (medium-priority critical severity alerts) via regular email. All other alerts will be available in the console and no emails will be sent to notify of them.

The next sections will set up the notification infrastructure described previously.

The first step is to set up a channel, that is, how the emails will be sent. The steps are as follows:

1.
Launch the Operations Manager 2007 R2 console.

2.
Select the Administration space.

3.
Select the Channels node.

4.
Right-click the Channels node and select New Channel, E-Mail (SMTP).

5.
Enter SMTP Channel (High Priority) for the channel name and click Next.

6.
Click the Add button, enter the FQDN of the SMTP server, and click OK.

7.
Enter a return SMTP address and click Next.

8.
Change the Importance to High and click Finish. Click Close to close wizard.

9.
Right-click the Channels node and select New Channel, E-Mail (SMTP).

10.
Enter SMTP Channel (Normal Priority) for the channel name and click Next.

11.
Click the Add button, enter the FQDN of the SMTP server, and click OK.

12.
Enter a return SMTP address and click Next.

13.
Leave the Importance at Normal and click Finish. Click Close to close wizard.

The second step is to set up the subscriber, that is, to whom the emails will be sent. The steps are as follows:

1.
Launch the Operations Manager 2007 R2 console.

2.
Select the Administration space.

3.
Select the Subscribers node.

4.
Right-click the Subscribers node and select New Subscriber.

5.
Click the “...” button and select a user or distribution group. Click OK.

6.
Click Next.

7.
Click Next to always send notifications.

8.
Click the Add button.

9.
Type Email for the address name and click Next.

10.
Select the Channel Type as E-Mail (SMTP) and enter the delivery email address.

11.
Click Finish.

12.
Click Finish again to save the subscriber. Click Close to exit the wizard.

Note

It is a best practice to use distribution lists rather than user email addresses for subscribers.


The last step is to set up the subscriptions, that is, what to notify on. The steps are as follows:

1.
Launch the Operations Manager 2007 R2 console.

2.
Select the Administration space.

3.
Select the Subscriptions node.

4.
Right-click the Subscriptions node and select New Subscription.

5.
Enter Notification for All Critical Severity High Priority Alerts for the subscription name and click Next.

6.
Check the Of a Specific Severity and the Of a Specific Priority check boxes.

7.
In the Criteria Description pane, click the “Specific Severity” link, check the Critical check box, and click OK.

8.
In the Criteria Description pane, click the “Specific Priority” link, check the High check box, and click OK.

9.
Click Next.

10.
Click the Add button, click Search, select the subscriber, click the Add button, and click OK.

11.
Click Next.

12.
Click the Add button, click Search, select the SMTP Channel (High Priority) channel, click the Add button, and click OK.

13.
Click Next and then click Finish.

14.
Right-click the Subscriptions node and select New Subscription.

15.
Enter Notification for All Critical Severity Medium Priority Alerts for the subscription name and click Next.

16.
Check the Of a Specific Severity and the Of a Specific Priority check boxes.

17.
In the Criteria Description pane, click the “Specific Severity” link, check the Critical check box, and click OK.

18.
In the Criteria Description pane, click the “Specific Priority” link, check the Medium check box, and click OK.

19.
Click Next.

20.
Click the Add button, click Search, select the subscriber, click the Add button, and click OK.

21.
Click Next.

22.
Click the Add button, click Search, select the SMTP Channel (Normal Priority) channel, click the Add button, and click OK.

23.
Click Next and then click Finish.

Now, the subscribers will get email notifications for alerts based on the severity and priority. These severities and priorities are based on the judgments of the authors of the management packs, which might or might not be optimal for any given organization.

Other -----------------
- Windows Server 2008 R2 : Configuring Operations Manager 2007 R2 (part 1) - Agent Proxy Configuration & Active Directory Client Monitoring Configuration
- Windows Server 2003 : Understanding How Clients Obtain Configuration (part 4) - DHCP ACK & DHCP NACK
- Windows Server 2003 : Understanding How Clients Obtain Configuration (part 3) - DHCP Offer & DHCP Request
- Windows Server 2003 : Understanding How Clients Obtain Configuration (part 2) - Analyzing DHCP Messages & DHCP Discover
- Windows Server 2003 : Understanding How Clients Obtain Configuration (part 1) - Initial Lease Process & Lease Renewal Process
- Windows Server 2008 R2 : Installing Operations Manager 2007 R2 (part 3) - Deploying OpsMgr Agents
- Windows Server 2008 R2 : Installing Operations Manager 2007 R2 (part 2) - Importing Management Packs
- Windows Server 2008 R2 : Installing Operations Manager 2007 R2 (part 1) - Single-Server OpsMgr 2007 R2 Install
- Windows Server 2003 : Configuring DHCP Servers to Perform DNS Updates
- Integrating System Center Operations Manager 2007 R2 with Windows Server 2008 R2 : Securing OpsMgr
 
 
Top 10
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
 
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server