OS/System

Specification

Requirement

Microsoft System Center Operations Manager

2012, 2012 SP1, 2012 R2, or 2016

Hardware

HD Space: 2GB  Memory: What is required to run OpsMgr.  Processor: x64

OS

Windows 2012 or later

Additional Software

Microsoft .NET Framework 4.5.1 or later

Firewall Ports

From

To

Protocol

Ports

Notes

Machine with ENS for SCOM

OpsMgr SDK Service

TCP

445, 5723, 5724

Required to access SCOM SDK Services

Machine with ENS for SCOM

SMTP Delivery Server

TCP

25, 465

Required for communications between the Enhanced Email Notification Service and the SMTP delivery point. This is needed to deliver the email.

Permissions

When installing Enhanced Notification Service for SCOM, you should take into account the following security considerations.


Create a Windows Domain User Account to use as a Service Account


The service account should be a domain account and a Local Administrator on the machine where the service is installed. Our service uses Winsocks to open the SMTP listening port so local administrator rights are needed on the machine where it is being installed.


You can (re)use the System Center Operations Manager Action account if you like. To find your SCOM Action account, from the Operations Manager Shell run:


Get-SCOMRMSEmulator | ft ActionAccountIdentity


The Operations Manager Action account is already a member of the needed OpsMgr User role below.  (but you might have to add it to the Local Administrators group)


Add the Service Account to the Operations Manager Administrator User Role


The service account used must also be a Operations Manager Administrator inside System Center Operations Manager due to the fact the service pulls Operations Manager variables such as console web url and needs management pack access.


In the OpsMgr console, goto Administration -> Security -> Users Roles and add the Service account to Operations Manager Administrators group.