none
Newly Installed SCOM Agent showing Not Monitored State RRS feed

  • Question

  • Hi Folks,

    Have installed the agent through console, I could see the agent in console but in not monitored state.

    Have done clear cache, resintalled the agent manually but still showing up in not monitored state.

    Your help is highly appreciated on this.

    Regards

    SK

    Friday, November 22, 2019 11:48 AM

Answers

All replies

  • Hi,

    What version and build of SCOM are you using?

    What operating system is the agent running on?

    Start by checking the Operations Manager event log for any errors.

    Also make sure you have the required firewall port 5723 (TCP) open:
    Configuring a Firewall for Operations Manager

    You can also refer to the troubleshooting guide here:
    Troubleshooting gray agent states in System Center Operations Manager

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:


    • Edited by Leon Laude Friday, November 22, 2019 12:04 PM
    Friday, November 22, 2019 12:03 PM
  • Hey,

    the first thing to do in such cases is to examine the Event Log (Operations Manager) on the affected Agent. Please do the following:

    - Restart the Service once
    - Note the events that are logged after the start of the service (Warning and Erros)
    - Post them here, so that we can check them out and help you. Please make sure you hide (mask) senstive informatio like server names, IP adresses, ect..

    The other question is: have you waited enough? Depending on the number of workflows the agets needs to execute it could last up to 30 Min to get the Status turned to green (monitored).

    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

    Friday, November 22, 2019 12:04 PM
    Moderator
  • Hi, 

    Restarted the services, flushed, reinstalled but still same error. Please find the error logs. Port 52723 is open from agent to MS. I'm, unable to post the image here.

    Event : 20070:

    The OpsMgr Connector connected to MSxxxx but the connection was closed immediately after authentication occurred.  The most likely cause of this error is that the agent is not authorized to communicate with the server, or the server has not received configuration.  Check the event log on the server for the presence of 20000 events, indicating that agents which are not approved are attempting to connect.

    21025
    7023
    7025
    7024
    7028

    These events are keep repeating.

    Friday, November 22, 2019 12:46 PM
  • Was the agent pushed from SCOM console or installed manually?
    Friday, November 22, 2019 12:56 PM
  • If the agent was installed manually, it will show up under Administration > Pending Management. 

    But note that for the agent to show up under Pending Management, it requires you to configure the manual agent installation settings as per below:


    Blog: https://thesystemcenterblog.com LinkedIn:

    Friday, November 22, 2019 1:11 PM
  • Hi,

    That is something for a start. Please make sure the port is really open first:

    Test-NetConnection -ComputerName <mgmtserver.domain.com> -Port 5723

    - Please ensure you can resolve the agents name from the management server and the otehr way around.

    - Please check if your Management Serevrs respectively Management Group is Healthy (Monitoring ->Operations Manager -> Management Group Health, Managment Server, etc.)
    - Please post also the description of those events, we need the information to be able to tell what is going on.

    Thanks and 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


    Friday, November 22, 2019 1:12 PM
    Moderator
  • In the Operations log in Event Viewer, is it full of 1102 Event IDs? If so, check the Hslockdown status: 

    https://scomandothergeekystuff.com/tag/hslockdown/

    Friday, November 22, 2019 1:19 PM
  • Hi,

    Ron has a point here, especially if the server is a domain controller :)

    Deploying SCOM 2016 Agents to Domain controllers – some assembly required

    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

    Friday, November 22, 2019 1:48 PM
    Moderator
  • Hi,

    Just to confirm with you, one or some specific agents have such issue or all the agents are showing not monitored? Have we download the corresponding management packs and imported them?

    As Stoyan said, is the agent a domain controller?

    Microsoft Management Packs
    http://social.technet.microsoft.com/wiki/contents/articles/16174.microsoft-management-packs.aspx
       
    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.
    Monday, November 25, 2019 8:11 AM
  • Hi All,

    Thanks for your inputs.

    This is not a Domain Controller server and dont see any events of 1102.

    Its not about pending management issue, as the agents are in agent managed tab as not monitored state.

    All the required Management Pack are available.

    Regards

    SK

    Monday, November 25, 2019 8:39 AM
  • Is this a domain-joined agent or a workgroup/DMZ agent?

    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, November 25, 2019 8:41 AM
  • If you run the Get-SCOMParentManagementServer powershell cmdlet for that agent, what is the primary MS there? Is the agent trying to communicate with this one or with another one?
    Monday, November 25, 2019 8:54 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, December 3, 2019 5:02 AM
  • check the DNS configuration for the computer, both FQDN and DNS suffix.
    An agent can also show as not monitored because the new agent has the same NetBIOS name as a previously installed agent. When the agent is deleted from Operations Manager, the grooming of the deleted agent is occurs after two days. Therefore, the agent is not immediately groomed out of the database completely. To work around this limitation, wait three days after deleting the agent to install the new agent.

    roger

    Tuesday, December 3, 2019 6:38 AM
  • Hi All,

    There was a issue with MS, not accepting any agents. This has been sorted out.

    Wednesday, December 11, 2019 6:48 AM
  • Hi All,

    There was a issue with MS, not accepting any agents. This has been sorted out.

    Hi,

    can you please share some more details what exactly was wrong? This way we will help others, who experience the same problem. It would also great if you mark all the answers, which helped you on the way to the solution.

    Thank you in avdance for that!

    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

    Wednesday, December 11, 2019 9:26 AM
    Moderator