tag:blogger.com,1999:blog-893729307599410422.post314696416923165593..comments2023-10-26T10:16:11.799+02:00Comments on Virtualization and some coffee: VM Monitoring with Hyper-V Clusters in Windows Server 2012Kristian Nesehttp://www.blogger.com/profile/11112639253922959602noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-893729307599410422.post-57457541252444399032012-09-21T23:10:07.020+02:002012-09-21T23:10:07.020+02:00Hey Kristian,
Thanks for the blog!
I agree, reb...Hey Kristian,<br /><br />Thanks for the blog! <br /><br />I agree, rebooting the VM on service failures is not always acceptable in enterprise scenarios and as you mentioned this could well trigger Ops Manager warnings. It's for this reason that we added a "Enable automatic recovery for application health monitoring" option under the VM properties settings tab. By unchecking this you can customize your recovery action or trigger a customized recovery action off event 1250 and Ops Manager.<br /><br />Best,<br /><br />Subhasish Bhattacharya (Microsoft) Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-893729307599410422.post-59859419652712421812012-09-21T23:02:49.394+02:002012-09-21T23:02:49.394+02:00Hey Kristian,
Thanks for the blog!
I agree, reb...Hey Kristian,<br /><br />Thanks for the blog! <br /><br />I agree, rebooting the VM on service failures is not always acceptable in enterprise scenarios and as you mentioned this could well trigger Ops Manager warnings. It's for this reason that we added a "Enable automatic recovery for application health monitoring" option under the VM properties settings tab. By unchecking this you can customize your recovery action or trigger a customized recovery action off event 1250 and Ops Manager.<br /><br />Best,<br /><br />Subhasish Bhattacharya (Microsoft) Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-893729307599410422.post-65455754613700304232012-09-21T23:02:36.797+02:002012-09-21T23:02:36.797+02:00Hey Kristian,
Thanks for the blog!
I agree, reb...Hey Kristian,<br /><br />Thanks for the blog! <br /><br />I agree, rebooting the VM on service failures is not always acceptable in enterprise scenarios and as you mentioned this could well trigger Ops Manager warnings. It's for this reason that we added a "Enable automatic recovery for application health monitoring" option under the VM properties settings tab. By unchecking this you can customize your recovery action or trigger a customized recovery action off event 1250 and Ops Manager.<br /><br />Best,<br /><br />Subhasish Bhattacharya (Microsoft) Subhasish Bhattacharya (MSFT)noreply@blogger.comtag:blogger.com,1999:blog-893729307599410422.post-86323233336941940872012-09-21T23:02:15.451+02:002012-09-21T23:02:15.451+02:00Hey Kristian,
Thanks for the blog!
I agree, reb...Hey Kristian,<br /><br />Thanks for the blog! <br /><br />I agree, rebooting the VM on service failures is not always acceptable in enterprise scenarios and as you mentioned this could well trigger Ops Manager warnings. It's for this reason that we added a "Enable automatic recovery for application health monitoring" option under the VM properties settings tab. By unchecking this you can customize your recovery action or trigger a customized recovery action off event 1250 and Ops Manager.<br /><br />Best,<br /><br />Subhasish Bhattacharya (Microsoft) Subhasish Bhattacharya (MSFT)noreply@blogger.comtag:blogger.com,1999:blog-893729307599410422.post-55279059723943200842012-09-21T23:01:44.557+02:002012-09-21T23:01:44.557+02:00Hey Kristian,
Thanks for the blog!
I agree, reb...Hey Kristian,<br /><br />Thanks for the blog! <br /><br />I agree, rebooting the VM on service failures is not always acceptable in enterprise scenarios and as you mentioned this could well trigger Ops Manager warnings. It's for this reason that we added a "Enable automatic recovery for application health monitoring" option under the VM properties settings tab. By unchecking this you can customize your recovery action or trigger a customized recovery action off event 1250 and Ops Manager.<br /><br />Best,<br /><br />Subhasish Bhattacharya (Microsoft)Subhasish Bhattacharya (MSFT)noreply@blogger.com