Compartilhar via

Fixing troubled agents

  • Artigo

<!--[if lt IE 9]>

<![endif]-->

Comments

  • Anonymous
    January 01, 2003
    We really try hard to come up with ways to solve the problem without resrting to editing a SQL table directly.... doing so is really unsupported and should only be done under the direct guidance (or should I say order) of PSS in a case with Microsoft.  There are a few circumstances, where that seems to be the only recourse... but we should exhaust all other options first.

  • Anonymous
    January 01, 2003
    Useful information Kevin, I'm also into a situation where 1-2 agents are not healthy. While checking i found config.xml file is not updated though i cleared the cached and even allowed the system to recreate Health Service State folder but that failed too in updating the xml file. I've also noticed Temp folders are not getting created on these agents. I've reinstalled the agent as well. Agent gets into gryed state after a while even if i restart the service. In the event log i see lot of logs generated   Rule/Monitor "Microsoft.SystemCenter.LearningModule.FailedInitialization.Alert"  cannot be initialized and will not be loaded" and many more similar to this. Any help is appreciated.

  • Anonymous
    October 02, 2009
    The comment has been removed

  • Anonymous
    June 30, 2010
    Thanks Kevin, very good blog.  Can you provide any additional advice or reasons why an agent health turns grey, we get this a lot ?  the agents are multi-homed, could this be impacting ?

  • Anonymous
    September 24, 2010
    This Blog is very useful.  As to other potential issues with grey agents, check out this kb  support.microsoft.com/.../2288515.

  • Anonymous
    April 04, 2011
    Simply Log on to DC and run the following commands

  1. hslockdown /L you will see NT Authoritysystem is in denied state Then run the command to bring it in allowed state hslockdown /A "NT AUTHORITYSystem" Cheers Saad

  • Anonymous
    April 07, 2011
    hi Kevin, Great article.  I have used this advice a few times to help with agetns issues.  However I have come across with an issue I am having a hard time with.  I have an agent deployed and teh agent is showing healthy in the Agent State view.  This particular  agent is on a Windows 208 R2 server.  For some reason the disovery of this windows 2008 server is not working.  I have other windows 2008 servers that are working fine.  The agent knows enough that it is on a windows server, but all of the OS specifc monitors are not active.  The logs show nothing.  I am at a loss here.  I have cleared the cache, repaired the agent.  Any help is apprecieated.  thanks.

  • Anonymous
    December 20, 2011
    Kevin, My problem lies on the Root Management Server. Absolutely everything is running with no issues but for some reason, the Server is greyed out I can restart the service and it is okay for a few minutes, then goes right back into the greyed out status... Operationally and all functions correctly but it just never looks good to see the RMS greyed out... Any ideas?

  • Anonymous
    January 12, 2012
    Jayson, your issue may be related to SPNs. We just wrestled with it and finally got it right. www2.wolzak.com/.../15-the-opsmgr-connector-could-not-connect-to-msomhsvcrms01local mymomexperience.blogspot.com/.../ops-manager-2007-agent-not-connecting.html

  • Anonymous
    January 15, 2012
    After upgrading System Center Essentials 2007 with the latest OS Management Pack, the owner’s agent of the Hyper-V cluster became grayed out. If I change the cluster current host server to other server, it becomes grayed out and the previous one (which was the current host server before) becomes healthy again.

  • Anonymous
    April 13, 2012
    The comment has been removed

  • Anonymous
    June 03, 2014
    It will also apply/reapply any agent related hotfixes in the management server’s Program FilesSystem Center Operations Manager 2007AgentManagement directories.

  • Anonymous
    June 03, 2014
    It will also apply/reapply any agent related hotfixes in the management server’s Program FilesSystem Center Operations Manager 2007AgentManagement directories.

  • Anonymous
    August 01, 2014
    "The problem might be that they are not showing up in the console at all!"....any suggestions for diagnosing this problem? This particular agent also has no "OperationsManager". A few of the other logs are there, but many that I typically see in a client are missing. This was a manual installation of the ccm client.

  • Anonymous
    August 06, 2014
    The comment has been removed

  • Anonymous
    October 03, 2014
    Hello Kevin,

    Excellent article for the machine, but do you have something similar for Virtual Machine working through collectors and not reporting...

    Thanks,
    Dom

  • Anonymous
    May 31, 2016
    helpful tips . i have an issue . i have scom 2012 sp1 . when i am checking windows server computer group it showing me windows 7 computers as well . when i am creating new group for servers it also showing me windows 7 computers mix with windows servers.

  • Anonymous
    June 08, 2016
    Hi Kevin,You have been an inspiration since I started working on SCOM. Your blog has helped me a lot. Thanks a ton!I have been encountering an issue in my environment. We have a domain say 'A' on which we have our MS and we have a gateway server on our another domain B which has trust relationship with domain 'A'. We have an agent in domain 'C' which has two way trust with domain 'B'.When I tried to install agent on the server in domain 'C' and make it communicate to the gateway in domain 'B'. Agent is not communicating with the gateway, we could see event 20002 on the gateway and event 20070 on the agent machine.It is not able to be authenticated and getting rejected.Could you please help me on this issue ?

    • Anonymous
      June 08, 2016
      Just because you have a trust between B and C, does not mean Kerberos is supported. If agent in C is rejected by GW in B, it most likely means you need to use certificates between C and B.

  • Anonymous
    October 28, 2016
    The comment has been removed

    • Anonymous
      October 28, 2016
      You should send me an email. This is WAY too complex and I barely understand what you are asking. kevin dot holman at microsoft dot com
      • Anonymous
        October 28, 2016
        Morning, understood, thank you for taking the time to respond! email forthcoming.T.S.

  • Anonymous
    November 28, 2017
    The comment has been removed

  • Anonymous
    November 30, 2017
    I have a very stubborn agent that is stuck and can no longer be reinstalled. I've uninstalled, cleaned registry, and file system but if I try to manually install (2016 UR4 MG) it never shows up in pending management (I've set my GMS Settings to review), and when I try to push the discovery fails with "there were no computers disvovered...". I've deleted the agent, ran remove-scomdisabledclassinstance, and did state and object cleanup in the SQL, but when I use the search in the console I still get all the objects that are associated with this agent. Get-SCOMPendingManagement yields no results, and I can't reinstall this agent into my SCOM 2016 environment, please help.

  • Anonymous
    December 06, 2017
    Hi Kevin Sir

  • Anonymous
    December 06, 2017
    Hello Sir

  • Anonymous
    July 10, 2018
    Hi Kevin,We are having an issue with one of the SCOM monitored servers, where sometimes the SCOM Agent goes under Not Monitored state, other days we find the Windows Operating System State goes under Not Monitored state but the SCOM Agent remains healthy. So we tired to Flush the health service state, repaired the SCOM Agent at that time the Windows OS state and Agent State comes back to healthy but after a couple of days the issue reoccures. Could you please advice on this issue.

  • Anonymous
    October 25, 2018
    The comment has been removed

    • Anonymous
      October 25, 2018
      I'd look in SQL in the AgentPendingActions table - and see if they are present there as "ghosts".https://blogs.technet.microsoft.com/kevinholman/2008/09/29/agent-pending-actions-can-get-out-of-synch-between-the-console-and-the-database/Do these show up in "Agent Managed"? Have you tried deleting them, and let them come back in?
      • Anonymous
        October 27, 2018
        Actually the agents are auto approved in our environment. They don't go to Pending management. Yes, they are showing up in Agent managed as Not Monitored. I tried deleting them in Agent managed and they are coming back in.
        • Anonymous
          October 27, 2018
          That means they are working - but cannot get config. This usually means something is broken with their parent path (GW and/or MS) where the parents need their cache flushed, OR - you are having problems generating/calculating new config (snapshot/delta failing) or you have management servers where the config service isnt running. Lastly - you can see this happen where is something orphaned in the SCOM database breaking config, or just config for that specific agent.
          • Anonymous
            October 31, 2018
            I have verified and removed couple of orphaned entries for other agents in the Opsmgr DB. But still thet doesn't turnup green in the agent managed view for the problematic agents.

  • Anonymous
    December 19, 2018
    (The content was deleted per user request)