Answered by:
Monitor Cookdown issue

Question
-
We implemented cookdown for a monitor. The strange thing is when multiple instances of the monitor script are initiated for the 1st run, then cookdown happens later. Is this normal? Btw, MP cookdown analysis shows no problem for cookdown monitor.
Thanks!
Wednesday, June 4, 2014 8:19 PM
Answers
-
Using On demand detection could break the cook down. Some information can be found here: http://www.systemcentercentral.com/opsmgr-mp-authoring-and-clarification-on-cook-down-and-ondemand-detection/
Markus Bölske, Lumagate. Blogg: www.opsmanager.se
- Marked as answer by Yan Li_ Tuesday, July 15, 2014 5:50 AM
Thursday, June 5, 2014 5:18 AM -
No, it's normal. To monitor cookdown, You can refer below links
http://www.systemcentercentral.com/data-source-monitoring-script-for-opsmgr-cookdown/
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer" Mai Ali | My blog: Technical | Twitter: Mai Ali
- Marked as answer by Yan Li_ Tuesday, July 15, 2014 5:50 AM
Sunday, June 8, 2014 10:48 AM
All replies
-
Using On demand detection could break the cook down. Some information can be found here: http://www.systemcentercentral.com/opsmgr-mp-authoring-and-clarification-on-cook-down-and-ondemand-detection/
Markus Bölske, Lumagate. Blogg: www.opsmanager.se
- Marked as answer by Yan Li_ Tuesday, July 15, 2014 5:50 AM
Thursday, June 5, 2014 5:18 AM -
No, it's normal. To monitor cookdown, You can refer below links
http://www.systemcentercentral.com/data-source-monitoring-script-for-opsmgr-cookdown/
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer" Mai Ali | My blog: Technical | Twitter: Mai Ali
- Marked as answer by Yan Li_ Tuesday, July 15, 2014 5:50 AM
Sunday, June 8, 2014 10:48 AM