Some Notes on OpsMgr notification subscriptions
June 10, 2009
Today is “notfication day”
I have to (re-) create several notfication subscriptions in OpsMgr 2007 R2 and tumble over some issues, which i have almost forgotten:
Note 1: Adding Subscribers for a existing subscription
If you add a new subscriber to an existing subscription, i recommend to delete ALL existing subscribers and then re-add them including the new subscribers. If you do no delete the existing subscribers i found out, that it is almost certain, that the added subscriber will not get notified…
Note 2: If you use Notification Command Channels, it might be useful to increase the maximum number of asynchronous responses
Maybe you will get an Alert:
The process could not be created because the maximum number of asynchronous responses (5) has already been reached, and it will be dropped.
Then you should consider increasing the number of responses, which can be run on the RMS. You can increase the number via this registry setting:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Modules\Global\Command Executer]
“AsyncProcessLimit”=dword:0000000a
But before doing so, i recommend to read the blog post from Clive Eastwood carefully: http://blogs.technet.com/cliveeastwood/archive/2008/04/16/some-more-command-notification-tricks-and-tips.aspx
To be continued…
Entry Filed under: System Center Operations Manager. Tags: Notification, OpsMgr.
Trackback this post | Subscribe to the comments via RSS Feed