Hi @Shiva Ravichandran ,
this is a pretty common problem. Here is what you need to check:
- The first thing to check is whether the servers, which are having the problem, are in another domain, compared to the management server or Gateway they are configured to report to.
If the servers and their assigned management or gateway servers are in different domains and the domains do not have an Active Directory trust, which allows Kerberos authentication, then you need to do some certificate installation and management. Here are a couple of links, which depict the topic in more details (some of those are written for SCOM 2012 R2, but the steps are the same, nothing has changed):
Install a gateway server
https://learn.microsoft.com/en-us/system-center/scom/deploy-install-gateway-server?view=sc-om-2022
Step-by-step walkthrough: Installing an Operations Manager 2012 Gateway
SCOM 2012 – Connecting a gateway server using certificates
- The second important thing is the network connectivity. Each agent needs to be able to connect to port 5723 (TCP) on the assigned Gateway/management server. This would be the server, that the agent has in it connfiguration -> Control Panel -> Microsoft Monitoring Agent, tab "Operations Manager" You can easily check the connectivity, by running this on the troubled agents: Test-NetConnection -ComputerName <name_of_the_gateway.domain.local> -Port 5723
- Last, but not least - you ned to check whether the dual homing configuration has been successfully applied on the agent side. You neeed to connect to an affected system and check the Control Panel -> Microsoft Monitoring Agent, tab "Operations Manager", there you should have 2x entries for each SCOM MG.
I hope I could help you out with that.
(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
Regards
Stoyan Chalakov