Dear All, On friday i have put my 40 server in maintenace mode for 200min due to network activity but when i came back on monday they are still in maintenance mode so i have stop the maintenance mode but my all the 40 server goes on unmonitored state and they are still not coming out from unmonitored state. I have also restarted the server and services of scom2007 r2 but still is not working even i have check the logs also but still no hope. So anybody can tell me what has happen to my scom 2007 r2. Regards, Syed Tauseef

Hi Syed Can you check the operations manager event viewer on RMS? If any warnings or errors that will help to troubleshoot the issue. Donald D'souza (http://donald-scom.blogspot.com/)

Hi Syed Did you put your RMS into maintenance mode as well? It sounds like this is the issue. With the RMS in maintenance mode, it can't take any servers (or itself) out of maintenance mode. If the RMS is in maintenance mode, reboot it until it comes out .. then you should be able to take the other agents out of maintenance mode. Cheers GrahamRegards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

The RMS server is not in maintenance mode and it is in healthy state and i have stop the maintenance mode of the remining agents so they can get back in monitoring state but still they are not in monitoring state.

The RMS server is not in maintenance mode and it is in healthy state and i have stop the maintenance mode of the remining agents so they can get back in monitoring state but still they are not in monitoring state. and their are no alerts or warning on event viewer of op

1) Could you then check the OperationsManager event log on the RMS and also the OperationsManager event log on one of the agents that is not coming out of maintenance mode to see what the errors are. 2) You might want to choose an agent to flush the health service on to see if this resolves it ... it would help to do it on one server if you can just to see if it kicks starts everything - see below: - Stop the System Center Management Service on the RMS. - Go to c:\Program Files\System CenterOperations Manager 2007\Health Service State and rename the health service state folder. - Start the System Center Management Service. This will force a new configuration. 3) Any kerberos or authentication errors in the windows system event log on the RMS? http://blogs.technet.com/b/kevinholman/archive/2007/12/13/system-center-operations-manager-sdk-service-failed-to-register-an-spn.aspxRegards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

1) Could you then check the OperationsManager event log on the RMS and also the OperationsManager event log on one of the agents that is not coming out of maintenance mode to see what the errors are. 2) You might want to choose an agent to flush the health service on to see if this resolves it ... it would help to do it on one server if you can just to see if it kicks starts everything - see below: - Stop the System Center Management Service on the RMS. - Go to c:\Program Files\System CenterOperations Manager 2007\Health Service State and rename the health service state folder. - Start the System Center Management Service. This will force a new configuration. 3) Any kerberos or authentication errors in the windows system event log on the RMS? http://blogs.technet.com/b/kevinholman/archive/2007/12/13/system-center-operations-manager-sdk-service-failed-to-register-an-spn.aspxRegards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/