Hi,
To implement bulk monitoring of TCP ports 5985 and 5986 across multiple source and target systems using SCOM 2022, here’s an example:
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi, I have a bunch of PS code-based reports, ad-hoc scripts and custom GUI tools made in PS Studio relying on PowerShell remoting thus tcp/5985, 5986 ports being accessible (on all servers) from Windows Admin Center/Bastion Hosts. What would be the best way of monitoring whether these ports are accessible on all servers in the forest from Windows Admin Center/Bastion Hosts (as source systems)?
Windows Admin Center server:ANY --> all servers:5985 (tcp)
Windows Admin Center server:ANY --> all servers:5986 (tcp)
Bastion Host servers:ANY --> all servers:5985 (tcp)
Bastion Host servers:ANY --> all servers:5986 (tcp)
Hi,
To implement bulk monitoring of TCP ports 5985 and 5986 across multiple source and target systems using SCOM 2022, here’s an example:
I am aware of this but how to implement it in-bulk (multiple source systems, multiple target systems and two target ports)?
Hi,
To monitor the accessibility of TCP ports 5985 and 5986 on all servers from Windows Admin Center and Bastion Hosts using SCOM 2022, you can use the TCP Port template in SCOM. This template allows you to monitor the availability of applications accessible over TCP, including verifying that specific ports are reachable from defined watcher nodes.
Here's a step-by-step approach:
Define Watcher Nodes: Set up your Windows Admin Center and Bastion Hosts as watcher nodes in SCOM. Each watcher node will attempt to connect to the specified ports on the target servers.
Create TCP Port Monitors:
Configure Monitoring Intervals: Set the intervals at which the monitors will check the port accessibility. This can help you detect any intermittent connectivity issues.