![\"\"](\"https:\/\/ingmarverheij.com\/wp-content\/uploads\/2011\/05\/email1.jpg\")
Events generated by System Center Operations Manager (SCOM), like alerts and warnings, usually indicate (upcoming) problems. Notifiying you\u2019re system administrators enables you to troubleshoot te problem as quickly as possible.<\/p>\nEvents generated by System Center Operations Manager (SCOM), like alerts and warnings, usually indicate (upcoming) problems. Notifiying you\u2019re system administrators enables you to troubleshoot te problem as quickly as possible.<\/p>\n
For a customer I\u2019ve configured multiple distributed applications. Each distributed application defines a critical application that needs to be monitored. All distributed applications are displayed on a monitor showing the state of the distributed application.<\/p>\n
![\"\"](\"https:\/\/ingmarverheij.com\/wp-content\/uploads\/2011\/05\/Distributed-Apps1.png\")
<\/p>\n
<\/p>\n
When an event is triggered, for instance because the service is down, a notification needs to be sent. Not only to the system adminstrators, who administer the infrastructure, but also to the technical and functional application operator.<\/p>\n
Active Directory groups are used to make the membership of the managable, since role based access control (RBAC) is used.<\/p>\n
<\/p>\n
<\/p>\n
For each distributed application an Active Directory group is created, in my example \u201cSCOM Alerts \u2013 DistributedApp \u2013 CitrixXenAppPADesktop\u2019 is used . The group type is Security<\/strong>, not Distribution<\/em>. This is required in a later phase. Since we don\u2019t want the group to be displayed in the global address list, the group is hidden <\/strong>from the address list<\/strong>. We don\u2019t want any delivery reports<\/strong>, so these are disabled <\/strong>aswell. Finally members <\/strong>are added<\/strong>, this are the functional and technical application operators who manage the application.<\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n In the System Center Operations Manager open the tab \u2018Administration\u2019, select the node Notification\\Channels and add a new E-Mail Notification Channel<\/strong>. Give the channel a describing name, like the name of the channel and the mailsystem used. Then define the SMTP servers <\/strong>used to send the e-mails, specify the return address <\/strong>(you\u2019ll want to monitor delivery errors, if an operator isn\u2019t notified they won\u2019t solve the problem) and the retry interval. Finally you can customize the format <\/strong>of the message <\/strong>that is send. The default message is quite technical.<\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n Select the node Notifications\\Subscribers and add a new Notification Subscriber<\/strong>. Define the name of the subscriber, this is the name <\/strong>of the group <\/strong>you specified in the first step (this is why the group type should be security). Then configure when<\/strong> the group should receive notifications, this applies to this subscription, you can change the schedule <\/strong>per e-mail addresslater. Finally add the address <\/strong>where the notification is send to. This will open a seperate wizard.<\/p>\n Give the address a describing name<\/strong>, best practice is to keep the same name as the Active Director group. Specify the channel type E-Mail (SMTP)<\/strong> and specify the delivery address <\/strong>(the e-mail address). Finally you can specify when <\/strong>this e-mail address <\/strong>should receive notifications.<\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n Select the node Notifications\\Subscriptions and add a new Notification Subscription<\/strong>. Start by specifying a describing name <\/strong>of the subscribtion, this is where you specify which notifications are sent to what subscriber (one or more e-mail address). Then check the condition \u2018raised by any instance of a specific class\u2019 <\/strong>and specify the class, which is the distributed application you want to receive notifications from. In my example this is \u2018Citrix XenApp PA Desktop\u2019. Then add a subscriber<\/strong>, this is the subscriber you created in the previous step, which should receive the notification. Next step is to add the channel <\/strong>you created earlier. The notification will be send using this channel, which is E-Mail (SMTP)<\/strong>. If events are triggered to frequent, and resolve fast, you can delay <\/strong>the notification. If the condition remain unchanged for the specified interval<\/strong>, the notification will be send.<\/p>\n In the last step the summary<\/strong> is displayed, don\u2019t forget to enable<\/strong> the notification subscription!<\/p>\n![\"\"](\"https:\/\/ingmarverheij.com\/wp-content\/uploads\/2011\/05\/image1.png\")
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nNext step is configuring a notification channel<\/strong>, this enables us to send e-mail<\/strong> from SCOM.<\/h5>\n
<\/a><\/p>\n<\/a><\/a><\/p>\n<\/a><\/p>\nThen add a subscriber <\/strong>for each distributed application.<\/h5>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nThe last step is to\u00a0 create a subscription<\/strong>.<\/h5>\n
<\/a><\/p>\n