locked
Root SCOM 2007 R2 server is in an unmonitored state RRS feed

  • Question


  • We noticed that our SCOM 2007 R2 management server was not producing any alerts or emailed alerts.   So we placed the management server in maintenance mode, but never return to an monitored state.    Event logs we are only getting a Event ID 20058 about the root connector.

     

    Does anyone have any recommendations on how to get the management server back online?   

    Monday, January 24, 2011 7:20 PM

Answers

All replies

  • Hi

    You should never set the Root Management Server to Maintenance mode:

    http://blogs.technet.com/b/smsandmom/archive/2007/12/06/opsmgr-2007-object-still-shows-to-be-in-maintenance-mode-after-the-window-has-expired.aspx

    http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/d4200b02-ceda-4540-85b1-b2835cf35a0d

    The only solution I have found when someone has done this is to stop maintenance mode on the RMS and keep rebooting until it comes out of mainteance mode.

    Cheers

    Graham


    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
    Monday, January 24, 2011 7:34 PM
  • Those URLs did not produce any results.    Do you have any other suggestions?

     

    At this time maintenance mode is stopped but the server is listed in a "not monitored" state.

    Tuesday, January 25, 2011 12:05 AM
  • sabo_e

    stop the maintanance mode.and right click on the rms server and again confure the enabling montiroting and then restart the pc

    Tuesday, January 25, 2011 7:17 AM
  • Hi

    Can you try this (taken from a Kevin Holman post):

    - Stop the RMS Health service (system center management) and then rename the \Health Service State folder to \Health Service State.OLD


    - Start Health service on RMS. This will force RMS to generate new config. Look in the new \Health Service State\Connector Configuration Cache\<MGNAME>\ directory for the config XML file. A new one should be generated within a few minutes. (longer on very large management
    groups)

    - If the file does not get created - you have an issue with your RMS not generating new config.

    - If the file does get created - then go back to the event log on the RMS, after the HS restart, and filter on all warning, critical, and error events. You should see a clue as to whats going on.

    Cheers

    Graham

     


    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
    Tuesday, January 25, 2011 7:19 AM
  • Thanks for the feedback.     Did those steps, seemed to produced the desire results, in terms of the event log - no errors, very few warnings seems pretty clean but still the server is saying "not monitored", we have a support call opened at this point.
    • Marked as answer by Nicholas Li Monday, January 31, 2011 7:14 AM
    Tuesday, January 25, 2011 12:24 PM
  •  

    Hi,

     

    Regarding this issue, I would like to share the following with you for your reference:

     

    OpsMgr 2007: The Health of the Root Management Server is in a Gray “Not Monitored” State

    http://blogs.technet.com/b/smsandmom/archive/2008/08/28/opsmgr-2007-the-health-of-the-root-management-server-is-in-a-gray-not-monitored-state.aspx

     

    Getting headaches trying to figure out why you are seeing the 'Not Monitored' state for Management Servers or Agents?

    http://blogs.technet.com/b/momteam/archive/2008/03/10/getting-headaches-trying-to-figure-out-why-you-are-seeing-the-not-monitored-state-for-management-servers-or-agents.aspx

     

    If the issue persists, please also check the Event Log of the server and let us know the details if there are any related errors.

     

    Thanks.


    Nicholas Li - MSFT
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Nicholas Li Monday, January 31, 2011 7:14 AM
    Wednesday, January 26, 2011 10:04 AM
  • Hi All,

    I know I am late to ask this question :) I am wondering if anyone is still there to answer my question.

    We had put our RMS in maintenance mode several times, however it did not impacted our RMS and monitoring.

    Everything was ok after the maintenance period expired and all servers are monitored correctly. There is no errors like grey RMS or Agents in our Env.

    All monitors are also ok and in green mostly.

     

    So I find no impact of this in our env.

    Are these steps recommended only if there is an issue with RMS after we put it in maintenance mode?


    • Edited by abs_dear Wednesday, December 14, 2011 1:16 PM
    Wednesday, December 14, 2011 1:12 PM
  • Hi All,

    I know I am late to ask this question :) I am wondering if anyone is still there to answer my question.

    We had put our RMS in maintenance mode several times, however it did not impacted our RMS and monitoring.

    Everything was ok after the maintenance period expired and all servers are monitored correctly. There is no errors like grey RMS or Agents in our Env.

    All monitors are also ok and in green mostly.

     

    So I find no impact of this in our env.

    Are these steps recommended only if there is an issue with RMS after we put it in maintenance mode?



    Tuesday, December 27, 2011 12:02 PM
  • So I find no impact of this in our env.

    Are these steps recommended only if there is an issue with RMS after we put it in maintenance mode?

    Luckily ofr you, you have no problems.

    Only if you have problems with your RMS, i.e. it's grey in the console, should you follow the troubleshooting steps above. Other than that, I suggest you never ever again put your RMS in maintenance mode.

    Thursday, January 12, 2012 2:00 AM