none
All Servers with Agents pushed is landing into grayed out state. RRS feed

  • Question

  • Hi All,

    I have a client environment for SCOM 2012 where there are two Sites (TX and CA) within the same domain. Both these Sites are in different subnets. The Operational Manager Database and the Operation Data Warehouse are on the CA Site and there is only one Management Server on the TX Site. This architecture is working fine and all the required agents are getting monitored.

    I had to migrate this SCOM 2012 environment to SCOM 2016. So I have the similar Architecture with two different Subnets (TX and CA) and the Operational Manager Database is in the form of SQL failover Cluster with both the primary and secondary nodes on the Same subnet (CA). The Agents are being installed successfully from the CA site but when it comes to Agent installation from the TX Site, The agent is getting installed but the Servers land into Grayed out State.

    I am unable to find any reason as to why this is happening because this same architecture is working fine in the existing client environment.

    Please suggest some reasons for this issue.

    Thanks in advance.

    Thursday, October 3, 2019 11:20 AM

Answers

  • It seems that the architecture that was developed was in a Microsoft unsupported version as the Management Servers and the Database were not in the same subnet that was causing Latency.

    Thanks

    • Marked as answer by garima4496 Wednesday, October 16, 2019 4:46 AM
    Wednesday, October 16, 2019 4:46 AM

All replies

  • Hello,

    Start by looking in the Operations Manager event log on both agent computers that are grayed out and the SCOM management server for any clues, the event log should indicate if there are any abnormalities.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, October 3, 2019 11:34 AM
  • Hi,

    in addition to what Leon suggested you can check the Heatlh State chnage in the Health Explorere on one of the agents and the "Context" in particular to see what information it holds. 

    What I would do next is to make sure all your agents can reach your management server on port 5723 (Test-NetConnection). 

    Regards,


    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov

    Thursday, October 3, 2019 11:47 AM
    Moderator
  • Hi,

    Since the existing client environment is working, this could be a network issue. As Stoyan suggested, besides the logs, we may check the network setting (ports allowed).

    It is suggested to check the allowed ports configuration between the existing one and the new one. For example, make sure tcp port 5723 and dynamic ports (49152-65535) are allowed in both management server and managed computers.

    For testing purpose, we may also turn off the firewall temporarily to narrow down the problem.

    Hope the above information helps.

    Regards,

    Alex Zhu
    -----------------------------------------------
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, October 4, 2019 2:41 AM
  • Hi,

    It seems there is no update for a couple of days. May we know the current status of the problem? Is there any other assistance we can provide?

    Regards,

    Alex Zhu
    -----------------------------------------------
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    Tuesday, October 15, 2019 7:26 AM
  • It seems that the architecture that was developed was in a Microsoft unsupported version as the Management Servers and the Database were not in the same subnet that was causing Latency.

    Thanks

    • Marked as answer by garima4496 Wednesday, October 16, 2019 4:46 AM
    Wednesday, October 16, 2019 4:46 AM
  • It seems that the architecture that was developed was in a Microsoft unsupported version as the Management Servers and the Database were not in the same subnet that was causing Latency.

    Thanks

    Hi,

    thanks for updating us. Wish you a nice day!

    Regards,


    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov

    Thursday, October 17, 2019 8:11 AM
    Moderator