locked
All Agents Show 'Not Monitored' RRS feed

  • Question

  • Hi

    I have a SCOM 2012 R2 installation. All my 440 agents (except 4) have changed status to 'Not Monitored'.  I have tried uninstalling the agents as well as flushing the 'Health Service State and Cache' on several with no improvements. 

    Also the 'Management Server State' console also reports the Health Service Watch view as both management servers listed as 'Healthy' but the 'Management Server State' shows 'Not monitored'.

    Where do you advise I start looking to remediate?



    • Edited by 10890lrl Wednesday, September 9, 2015 4:05 PM
    Wednesday, September 9, 2015 3:39 PM

Answers

  • Hi

    I'd suggest a support call so that someone can find a resolution quickly as monitoring is completely down. Forums are great for providing ideas to solve problems but if you need a quick response \ recovery then support is really the best bet.

    If you want to do this through the forums then I'd suggest:

    1. Check the OperationsManager event logs on the management servers for any errors \ warnings.

    2. Although nothing appears to be in maintenance mode, I'd run this:

    Get-SCOMMaintenanceMode

    3. This is at your own risk but have you Flushed the Health Service State Cache on the Management Servers?

    Cheers

    Graham


    http://blogs.technet.com/b/manageabilityguys/

    • Proposed as answer by Elton_Ji Tuesday, September 29, 2015 4:40 PM
    • Marked as answer by Elton_Ji Wednesday, October 7, 2015 9:07 AM
    Wednesday, September 9, 2015 4:52 PM
  • Recommend troubleshoot steps
    1) check event log
    2) flush 'Health Service State and Cache'  for both Management server and agent
    3)  restarting the System Center Management Health service
    4) check the DNS configuration for the computer, both FQDN and DNS suffix
    5) check whether the appropriate management pack for monitoring the object is imported
    6) Ensure that the appropriate monitors are enabled
    7) try placing the object in maintenance mode for several minutes
    Roger
    • Proposed as answer by Elton_Ji Tuesday, September 29, 2015 4:40 PM
    • Marked as answer by Elton_Ji Wednesday, October 7, 2015 9:07 AM
    Thursday, September 10, 2015 2:46 AM

All replies

  • Hi

    I'd suggest a support call so that someone can find a resolution quickly as monitoring is completely down. Forums are great for providing ideas to solve problems but if you need a quick response \ recovery then support is really the best bet.

    If you want to do this through the forums then I'd suggest:

    1. Check the OperationsManager event logs on the management servers for any errors \ warnings.

    2. Although nothing appears to be in maintenance mode, I'd run this:

    Get-SCOMMaintenanceMode

    3. This is at your own risk but have you Flushed the Health Service State Cache on the Management Servers?

    Cheers

    Graham


    http://blogs.technet.com/b/manageabilityguys/

    • Proposed as answer by Elton_Ji Tuesday, September 29, 2015 4:40 PM
    • Marked as answer by Elton_Ji Wednesday, October 7, 2015 9:07 AM
    Wednesday, September 9, 2015 4:52 PM
  • Recommend troubleshoot steps
    1) check event log
    2) flush 'Health Service State and Cache'  for both Management server and agent
    3)  restarting the System Center Management Health service
    4) check the DNS configuration for the computer, both FQDN and DNS suffix
    5) check whether the appropriate management pack for monitoring the object is imported
    6) Ensure that the appropriate monitors are enabled
    7) try placing the object in maintenance mode for several minutes
    Roger
    • Proposed as answer by Elton_Ji Tuesday, September 29, 2015 4:40 PM
    • Marked as answer by Elton_Ji Wednesday, October 7, 2015 9:07 AM
    Thursday, September 10, 2015 2:46 AM
  • By any chance, did you put the MS in maintenance mode?

    Faizan

    Thursday, September 10, 2015 7:12 PM
  • We found the problem. One of our team (name omitted for obvious reasons) decided to see what would happen if he created an override for the Health Service.

    After 4 weeks of pulling my hair out, Microsoft tech support spotted the problem and fixed it.

    Thanks to all for your advice.

    Wednesday, October 21, 2015 9:38 PM