Notifications with product knowledge from the management pack in System Center Operations Manager.
Yup. Html emails for SCOM.
It doesn’t get released until it works.
Working with you.
A powerful service that gets the Product Knowledge for an alert, attaches it to an email, and sends it on its way.
Create beautiful sexy email notifications based on 54 variables, in any html format you want.
Build your subject lines of your email out of 54 different variables, in any order you want.
Attach the Product Knowledge directly from the management pack AND your Company Knowledge to the alert.
Lighting Fast Direct API access via Microsoft’s System Center Operations Manager SDK.
Proven to handle thousands of alerts per hour with minimal memory and cpu usage.
Insert the notification channel that send the alert.
1) Alert is generated, the SCOM notification pool delivers the notification to the Enhanced Email Notification Service for SCOM.
2) The Enhanced Email Notification Service for SCOM, through the power of the Microsoft System Center Operations Manager SDK, talks to the RMS through direct API calls retrieving the Product Knowledge and Company Knowledge for the alert (if any).
3) The Enhanced Email Notification Service for SCOM then leverages the custom email template you build and delivers the email to the SMTP server of your choice. This allows the environment to leverage any rules or criteria for the notification channels you ALREADY have, to produce better notifications with the Product Knowledge the users need.
The Enhanced Notification Service for SCOM currently supports:
Yup. You can. But you will lose notifications. You will not have product knowledge, you will have plain text emails.
SCOM protects itself from spawning too many processes via the command channels. The default for running multiple scripts via command channels is 5. This is one of the reasons we created this service. Going over the process limit produces the famous:
The Process could not load because the maximum number of asynchronous has already been reached...
And the entry in OpsMgr Event Log
Log Name: Operations Manager Source: Health Service Module Event ID: 21410
As well as an Alert in the Operations Manager Console:
Alert Name: Operations Manager failed to start a process due to lack of resources Alert Resolution State: New Alert Description: The process could not be created because the maximum number of asynchronous responses (5) has already been reached, and it will be dropped. Command executed:
This won’t help if there are 20 new alerts and there are 10-20 console users managing alerts all at once. SCOM checks for new alerts every 60 seconds. New alerts (the ones that match) are batched up, then pushed down the notification channels for delivery. The command notification channel then processes these alerts asynchronously… or all the alerts at once.
If the alert count is over the AsyncProcessLimit, the first 5, using defaults, are processed, and the rest are dropped.
So lets say for a second, that you increase the AsyncProcessLimit to… say 100. Depending on the process that you are running (powershell + operations manager snapins) that could eat up 100-300Mb of memory per process. 100 processes x 200Mb. You better have Gigs of RAM in that notification server, it is going to need it.
If you are using this method, open up the Operations Manager Shell, run a get-scomalert, then check your task manager to see how much RAM powershell.exe is using.
First, we use the SMTP protocol to receive alerts from the SCOM environment. SMTP inherently addresses the retries and disconnects that may happen from time to time. SMTP notification channels are queued. The alerts will stream out the SMTP notification channel as the receiving SMTP server can handle them.
Second, we leverage System Center Operations Manager SDK. We talk directly to the API. Our service on average runs below 100Mb even while processing hundreds of messages.
Third, we queue our outbound SMTP email to your mail server. Your server not there? No worries, we queue it until it comes back online. You can customize the retry time and limits for your environment.
The Enhanced Notification Service for SCOM is a yearly subscription-based licensing model. We make it simple to start — or stop — your subscription at any time.
YES WE SAID FREE! The free version allows notifications for up to 10 (ten) agents in your Operations Manager Environment.
The Enterprise Edition of the Enhanced Notification Service for SCOM is licensed per Agent count in your Operations Manager Environment. You need to purchase the amount of agents you expect to have over the year.
To find out how many agents are in your environment, load the Operations Manager Shell, and run:
get-scomagent | measure-object
Yup, Contact us and we will be happy to discuss your options.
We'd really love to hear from you so why not drop us an email and we'll get back to you as soon as we can.