Agents reporting to Gateway Management servers grayed out.

py 206 Reputation points
2021-04-05T11:24:17.197+00:00

Hello All,

Good day :)

Here's the situation .

I have 2 domains.
Domain A has 4 MS and Domain B has 2 GW servers

We pushed around 5000 agents using a deployment tool. However, during deployment we can use only one MS and hence all servers were pushed to MS's in phases. In the end there were high number of servers reporting to one server and i ran a load balancing script to distribute the agents between the servers.

The issue is all the servers of domain B reporting to GW servers are grayed out.

Used the below article to set the Failover

https://kevinholman.com/2018/08/06/assigning-gateways-and-agents-to-management-servers-using-powershell/

PS C:\> $Gateway = Get-SCOMManagementServer | where {$.Name -eq "GW1.B.com"}
PS C:\> $Gateway.GetPrimaryManagementServer().DisplayName
MS1.A.com
PS C:\> $Gateway.GetFailoverManagementServers().DisplayName
MS3.A.com
MS2.A.com
MS4.A.com
PS C:\> $Gateway = Get-SCOMManagementServer | where {$
.Name -eq "GW2.B.com"}
PS C:\> $Gateway.GetPrimaryManagementServer().DisplayName
MS4.A.com
PS C:\> $Gateway.GetFailoverManagementServers().DisplayName
MS3.A.com
MS2.A.com
MS1.A.com

Any advise on how i can get my agents reporting to GW healthy ?

System Center Operations Manager
System Center Operations Manager
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
1,610 questions
0 comments No comments
{count} votes

Accepted answer
  1. Crystal-MSFT 53,991 Reputation points Microsoft External Staff
    2021-04-06T02:05:41.483+00:00

    @py , From your description, I know the agents connect to GW2 are all greyed out. And the GW2 server is still healthy. If there's any misunderstanding, please let us know.

    For our issue, we can go to the affected agent side and check HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Agent Management Groups\<SCOM management group>\Parent Health Services\, Make sure Authentication name and network name are the FQDN of GW2 server.

    Our issue is resolved. Here is a summary for it:

    Cause:

    =========

    The servers in GW2 domain have been assigned a Management server rather than the GW server when the AD assignment is switched in a script

    Resolution:

    ============

    Uncheck the AD assignment and change the Management server to Gateway name.

    Hope it can help.


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


4 additional answers

Sort by: Most helpful
  1. CyrAz 5,181 Reputation points
    2021-04-05T13:59:46.94+00:00

    You should start by having a look at their Operations Manager log and check what specific issue they are facing.
    And of course double check the usual suspects : certificates, dns resolution, firewall port opened...


  2. System Center guy 691 Reputation points
    2021-04-09T06:23:21.217+00:00

    >All agents report to GW2 in grey state and GW2 is in health state.

    Troubleshoot steps

    1. select one of the agents reporting to GW2
    2. restart microsoft monitoring agent service
    3. review event log for error
    4. telnet GW2 with port 5723
    5. using following powershell to check agent primary management server
      $agent=get-scomagent |where-object{$_.displayname -eq 'XXX.B.com'}
      get-scomparentmanagementserver -agent $agent

    The result should be GW2.B.COM

    Roger


  3. System Center guy 691 Reputation points
    2021-04-14T02:35:01.127+00:00

    Moreover, restart Microsoft Monitoring Agent Service such that the agent uses new setting to connect management server.

    Roger

    0 comments No comments

  4. py 206 Reputation points
    2021-04-21T11:42:37.15+00:00

    I seem to have gotten to the root of the issue. Thanks much for your assistance @System Center guy @Crystal-MSFT @CyrilAzoulay

    When i ran the scripts to load balance the server, it interestingly has switched on the the AD assignment and the servers in the GW 2 domain have been assigned a MS rather than the GW server. Now i'm in the process of unchecking the AD assignment and change the MS name in MM proprieties in control panel


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.