Web Applications Maintenance Mode
I noticed that if I put a Web Application in Maintenance when it is failing, the Application will go to a healthy state when coming out of maintenance and then go to a critical state at the next polling cycle. Is this by design? We would prefer it just stay in critical state?
November 23rd, 2010 3:42pm

Yes - this is by design. The objects go into "Not Monitored" state when in maintenance mode and then health is recalculated when they come out of maintenance mode. Cheers GrahamView OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
November 23rd, 2010 3:51pm

Graham, If it is recalculated, then why would it show healthy before going critical? thanks, Bob
November 23rd, 2010 3:57pm

because it didn't perform a check yet (aka it's healthy). So it will go unhealthy on the first polling cycle.Rob Korving http://jama00.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
November 23rd, 2010 5:44pm

Hi Bob As Rob says - it is just being "reinitialised". If you take a look at the Health Explorer for your web application - select the object that is now critical and on the right side of the screen click on the "State Change Events" tab, you should see the following: Not Monitored - while it is maintenance mode Healthy - when it comes out of maintenance mode Critical - when the check takes place and there is a problem If you click on Healthy and State Change Events tab, you'll see it says "The monitor has been initialised for the first time or has exited maintenance mode" Cheers Graham View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
November 24th, 2010 4:19am

Graham, Thank you for the explanation - We were under the assumption that if a monitor comes out of maintenance the monitor alert would create a repeate count if monitor was triggered prior to maintenance mode and would reopen a monitor alert if it was closed. bob
Free Windows Admin Tool Kit Click here and download it now
November 24th, 2010 11:03am

Hi, this is likely happening "By Design" (legacy from first release of Reset Health feature of OM) due to the web application unit monitors defininga On Demand discovery workflow for the healthy (green) state that always turn the monitor to green. When you come out of MM it will probably reload the workflows and it would make the monitor show first green until the next run actually happens. (the same happens if you net stop/start the healthservice on the watcher node). HTH, Alex.This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
December 1st, 2010 5:53pm

Hi Bob Hopefully these answer your question so I'll close the thread for the moment. Please feel free to reopen if you have further questions and we'll continue to assist. Cheers GrahamView OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
December 2nd, 2010 5:32am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics