Kevin Holman's System Center Blog

Posts in this blog are provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified in the Terms of UseAre you interested in having a dedicated engineer that will be your Mic

OpsMgr 2012: Configure notifications

OpsMgr 2012: Configure notifications

  • Comments 30
  • Likes

Setting up notifications for email, IM, or command channels is almost identical to how this was configured in OpsMgr 2007 R2.  This article will just serve as a walk through to the process, such as immediately after deploying OpsMgr 2012.  The key difference here is that Notifications are now managed by a Resource Pool, instead of just depending on the RMS.

 

Notifications in OpsMgr are made of of three primary components – the Channel, Subscriber, and the Subscription.  The Channel is the mechanism that we want to notify by, such as Email.  The subscriber is the person or distribution list we want to send to, and the subscription is a definition of criteria around what should be sent.

 

The SMTP Channel:

 

We will first need to create the channel:  Under Administration pane > Notifications > Channels.  Right click and choose New channel > Email (SMTP)

image

 

Give your channel a name.  We might have multiple email channels.  Once for emails to our primary work mailboxes.  Maybe another with different formatting for sending email to cell phones and pager devices.  Lets just call this one our “Default SMTP Channel”

image

 

Click Add, and type in the FQDN of your SMTP server(s).  This can be an actual SMTP enabled mail server, or a load balanced virtual name.

I am going to select “Windows Integrated” for my Authentication mechanism, since my mail server does not allow Anonymous connections.

image

 

For the Return Address – I have created an actual mail enabled user to send Email notifications through SCOM.  This might not be a requirement to be a real mail address – mostly that depends on your mail server security policies.

image

 

Next up is the email format.  We can customize this with very specific information that is relevant to how we want emails to look from SCOM.  I will just accept the defaults for now.  I can always come back and customize this one, or create additional channels with different formats later.

 

 

The Subscriber:

Next up – creating the subscriber.  Right Click “Subscribers” and choose “New Subscriber”

This will default to show your domain account.  You can change this to whatever you like:

image

Next – we need to choose when Kevin wants to receive email notifications.  This is especially important for things like on call pager devices, or when people work shifts and only want to see emails during certain times.

Next – we need to add an email address to the subscriber.  I will add my default work email:

image

Then select the Channel type, and the email address:

image

 

Additionally – you can configure a specific schedule for this specific address.  The previous schedule was for the subscriber itself, but a subscriber can have multiple addresses with different schedules if needed.  I will keep things simple and choose “Always send”.   Click Finish a couple times and your subscriber is set up.

 

The Subscription:

 

Now we create a new subscription – Right Click “Subscriptions” and choose New Subscription.

Give your subscription a descriptive name that describes what it is and who it is to.  Like – “Messaging team – all critical email alerts”  Here is mine:

image

 

On the criteria screen – we have some very granular capabilities to scope this subscription.  My goal for this simple one is just to send me any new critical alert that comes into my environment:

 

image

 

Next we add the subscribers to the subscription:

 

image

 

We also need to choose which Channel we want to use for this subscription:

 

image

 

On this same screen – there is an option for delay aging:

image

 

What that does – is allow for you to have multiple alert subscriptions – and using delay – create an escalation path if an alert is not modified in a way that takes it out of the notification path for these subscriptions.

Click “Finish” and we are all set.  Behind the scenes – what happened is that all this information was actually written to a special management pack – the Microsoft.SystemCenter.Notifications.Internal MP.

Let’s test our work.

 

I have a test rule that generates a critical alert whenever a specific event is written to the event log.  Since I subscribed to all critical alerts – this should trigger my subscription and deliver an email:

 

It worked!

image

 

 

Advanced configuration – setting up a Run As Account to authenticate to the SMTP server:

 

Note – there is a Run-As Profile that ships with SCOM called the “Notification Account”.  If this is not configured, SCOM will try to authenticate to the Exchange server using the Management Server Action Account.  If this is not allowed to authenticate, you might need to configure this Run-As profile with a Run As Account.

For instance – I disabled the ability for mail relay on my Exchange server.  When I do this – only mail enabled Exchange servers can connect to it.  Subsequent notifications fail to go through – and I will see two possible alerts in the console:

Failed to send notification

Notification subsystem failed to send notification over 'Smtp' protocol to 'kevinhol@opsmgr.net'. Rule id: Subscription02e8b6be_528d_407c_8edf_5f29dddaae6b

Failed to send notification using server/device

Notification subsystem failed to send notification using device/server 'ex10mb1.opsmgr.net' over 'Smtp' protocol to 'kevinhol@opsmgr.net'. Microsoft.EnterpriseManagement.HealthService.Modules.Notification.SmtpNotificationException: Mailbox unavailable. The server response was: 5.7.1 Client does not have permissions to send as this sender. Smtp status code 'MailboxUnavailable'. Rule id: Subscription02e8b6be_528d_407c_8edf_5f29dddaae6b

In this case – I must configure the Run-As account with a credential that is able to authenticate properly with my Mail Server.  I already have a user account and mailbox set up:  OPSMGR\scomnotify

Under Administration > Run As Configuration > Accounts – create a Run As Account.

The account type will be “Windows” and give it a name that makes sense:

image

Input the user account credentials:

image

Choose “More Secure” and click Next, then Close.

 

So – we have created our Run As Account – next we need to choose where to distribute it.  Account credential distribution is part of the “More Secure” option – we need to choose which Health Services will be allowed to use this credential.  In this case – we want to distribute the account to the management server pool in SCOM 2012 that handles notifications.

Open the properties of our newly created action account, and select the Distribution tab:

image

 

Click “Add”, and in the Option field – change it to “Search by Resource Pool Name” and click Search:

image

 

Choose the Notifications Resource Pool, click Add, and OK:

 

image

 

Now we have created our Run As Account for notifications, and then distributed it to the Notifications Resource Pool (which contains all management servers dynamically)

Next – we need to configure the Run As Profile – which will associate this account credential with the actual Notification workflows.

Under Administration > Run As Configuration > Profiles, find the “Notification Account” profile.  Open the properties of this Profile.

Under Run As Accounts – click Add:

image

 

Select our Notification Run As Account, and click OK

image

Then Save it.  This will update the Microsoft.SystemCenter.SecureReferenceOverride MP with these credentials and configurations for notification workflows.

From this point forward – Whichever Management server in the Notifications Resource Pool that is currently responsible for handling notifications, will spawn a MonitoringHost.exe process under our credential that we configured:

image

 

This credential will be used to authenticate to the Exchange server to send SMTP notifications.  Now my email notifications are flowing smoothly once again!  If the current management server goes down, another management server in the Notifications Resource Pool will pick up this responsibility and spawn the process, and continue sending notifications. 

 

High availability out of the box.  One of the benefits of the improved SCOM 2012 architecture improvements.

Comments
  • Hi Kevin,

    A thing about the Notification Channel format. Printing Priority and Severity does not necessarily translate into the user friendly string format. I expected like 'Low' or 'High'  to be printed for Priority or severity being 'Warning' or 'Error'. Instead when I add the following text into my channel format for Severity: $Data[Default='Not Present']/Context/DataItem/Severity$, I get 2 for error, 1 for Warning and 0 for Information. Same issue with Priority as well.

    I want to know if this is by design or can we somehow translate the numbers into user friendly string format. It helps for our support engineers to prioritize their work.

    Thank you,

    Shahin

  • Hi Kevin, great post as always, I do have a question though and it is probably a stupid one. We have everything set up and working for notifications internally and we have 2 remote domains that send notifications in via Gateway servers. The internal notifications are fine but the external ones have the date set in American format. I did some reading and it was suggested that I should log on to the management server using the notification account but this would seem silly since the internal ones work fine.

    The question is, do I have to set up a new notification account from each of the external domains and add them as a user in Exchange or can I use the internal notification account and distribute the credentials to the external Gateway servers? I'm just a bit unclear on the authentication across external domains.

  • @DH -

    The notification account is only used on a single management server that is part of the notifications resource pool... whichever MS happens to own the notification role.  It is the only management server that connect to exchange.  You do not distribute the notification account to gateways... their alerts flow into a management server queue, then they are inserted into the database, then a notification workflow runs on a set frequency and looks for alerts matching notification criteria, and sends notifications.  If there is something different or unique about alerts coming from agents behind gateways - that is based on the configuration of those servers.

  • Hi Kevin

    My customer has configured the Authentication method for SMTP as Anonymous in Channel.

    Also not created Domain User account, Run As Account & Run As Profile.

    The current configuration is without Run As Account & Run As Profile & running fine, received notification mails.

    It means if Authentication method for SMTP is Anonymous then in that case no need to have Domain User account & no need to create Run As Account & then Run As Profile.

    The Run As Account & Run As Profile need to create when selected Windows Integrated as Authentication method.

    kindly reply

    Regards,

    SandeepK

  • Are there some restrictions who can or cannot view the hyperlinks with in the emails?

    How are these configured, I have setup the Read-Only Operators, within the User Roles, however my users are still getting 403 errors?  My SCOM Admins open up the links without any problems at all.

    blogs.technet.com/.../5722.image_5F00_2F3F0AD3.png

  • Hello Kevin,

    I'm trying to configure the notifications alerts from SCOM 2012, but i keep getting the error "Client not authenticated".

    I'm not using Exchange, i'm using an third part software smtp server just to relay to Office365 smtp server. I've configured everything right (RunAsAccount, RunAsProfile, Channels, Subscribers and Subscriptions).

    Could you please help me on this one?

  • Kevin, I wonder why there is no option to subscribe for alerts associated with particular agent (path). Instead we need to create a group for bunch of objects for which we need subscriptions. This ends up in multiple group creation for multiple customers and finally a big mess. I'm currently using a powershell to notify based on path parameter but I like to have it as inbuilt feature. Please let me know if it makes sense...

  • Hi Kevin, I tell him that I have a setup like this on the way to spend it publishes. Retail Version 2012 Version 7.0.8560.0. The mail server is Lotus Notes. Perform all the checks are correct, for example Talnet port 25. But do not send emails. I can tell you can configure a cone event generation? thank you very much

  • También utilice : http://sourceforge.net/projects/smtpclient/files/ y desde este equipo recibo mail sin problemas son de la herramienta de notificación de SCOM 2012 - Responder : jecavallin@hotmail.com

  • Also use: http://sourceforge.net/projects/smtpclient/files/ and receive mail from this computer without problems are the notification tool SCOM 2012

  • Saludos, Kevin Holman

    He realizado todos los pasos que indicas en tu tutorial y me sigue saliendo este error.

    Notification subsystem failed to send notification using device/server 'outlook.latam.telefonica.corp' over 'Smtp' protocol to 'consolasccm.fija.pe@telefonica.com'. Microsoft.EnterpriseManagement.HealthService.Modules.Notification.SmtpNotificationException: Failure sending mail. --> Unable to connect to the remote server --> No connection could be made because the target machine actively refused it 10.167.205.10:25. Smtp status code 'GeneralFailure'. Rule id: Subscription6cd8df94_a9c8_4721_9f13_ee48c23ae340


    Otro error que muestra también es:

    Notification subsystem failed to send notification over 'Smtp' protocol to 'consolasccm.fija.pe@telefonica.com'. Rule id: Subscription6cd8df94_a9c8_4721_9f13_ee48c23ae340

    Le solicito si me puede apoyar a resolver este caso, para ello brindo los siguientes datos que he realizado,

    Al utilizar el comando PING al "outlook.latam.telefonica.corp" me muestra que no hay respuesta o tiempo de espera agotado para esta solicitud.

    Agradecere a interpretar es error que me muestra esos dos mensajes y así poder buscar una solución, cuyo objetivo es que me permita enviar notificaciones de alertas a mi Correo.

    Gracias

  • Hi Kevin.

    I want to send notifications using SCOM 365 office, configure the relay and configure notifications following your blog, but notifications do not work.

    The error is: Notification subsystem failed to send notification over 'Smtp' protocol to 'user@domain.com'
    Notification subsystem failed to send notification using device / server 'smtp.office365.com' over 'Smtp' protocol to 'user@domain.com'.

    help me!
    Thank you

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Search Blogs