SystemCenter

All about System Center Articles and Tutorials

SCOM Agent Port Requirements

Posted by on Nov 30, 2016 in SCOM, SCOM 2012, SCOM 2016

SCOM Agent Port Requirements

Many a times whenever SCOM Administration team gets any new requirement to monitor the Servers / Devices through SCOM they ask the requester to get the required ports open.

I have seen the scenarios wherein the agent push is not successful through SCOM Console as the required ports are not open.

So, I thought it will be good if we make a note of the Firewall ports that are required by Operations Manager Agent Push Process.

Following table lists the Operations Manager Agent Push requirements for the Firewall Ports:

Windows Servers

Action Services Ports Required
Agent Push Installation Microsoft Monitoring Agent 5723 TCP
File and Print Sharing 137 UDP, 138 UDP, 139 TCP, 445/TCP
Remote Administration 135 TCP, 445 TCP
RPC/DCOM High Ports 49152-65535 TCP/UDP
Agent Pending Repair Microsoft Monitoring Agent 5723 TCP
File and Print Sharing  137 UDP, 138 UDP, 139 TCP, 445/TCP
Remote Administration 135 TCP, 445 TCP
RPC/DCOM High Ports 49152-65535 TCP/UDP
Agent Pending Upgrade Microsoft Monitoring Agent 5723/TCP
File and Print Sharing 137 UDP, 138 UDP, 139 TCP, 445/TCP
Remote Administration 135 TCP, 445 TCP
RPC/DCOM High Ports 49152-65535 TCP/UDP

UNIX/Linux Servers

Action Services Ports Required
Agent Push Installation scxadmin 1270 TCP/UDP
SSH 22 TCP/UDP

Network Device

Action Services Ports Required
Discovery SNMP 161, 162 UDP

If you are doing manual Agent installation of MOMAgent.msi, you will need to open 5723/TCP only, the direction will be from Agent Server to Management Server. Rest all ports can be opened bidirectionally.

Please refer below link to know more about the Port requirements for System Center Operations Manager:

Supported Firewall Scenarios

This post is applicable for both Operations Manager 2012 and 2016.

Hope this helps.

Submit a Comment

Your email address will not be published. Required fields are marked *