No so long ago I’ve wrote and article SCVMM Maintenance mode for host does not put the computer object in maintenance mode in SCOM reported as fixed in SC 2012 SP1 and later verified that the same issue is not fixed in SP1 in article SCVMM and SCOM Maintenance Mode Integration Not Fixed in SC 2012 SP1 UR1. After reporting this bug for second time yesterday I’ve received e-mail from MSFT that there is development on the reported bug. The bug report is passed to a feature owner as a Design Change Request (DCR). It will be fantastic if this feature can be fixed in a future Update Rollup. To me it is not so hard bug to fix but developer perspective it can quite different so if we do not receive this fix in Update Rollup let’s hope it will be fixed in future service pack or in vNext. The bug report is still active and you can still vote on it here.
Not so long ago I’ve wrote an article titled SCVMM Maintenance mode for host does not put the computer object in maintenance mode in SCOM reported as fixed in SC 2012 SP1. I’ve reported the bug described in the article and that report was closed on Microsoft Connect site as fixed before the official release of SC 2012 SP1. As I do not trust blindly and always verify any information I’ve tested if this bug is fixed after the release of SC 2012 SP1 UR1. After I’ve made the test in my home lab I was experiencing the same bug again. My test was verified also by Steve Beaumont so the issue is not in my TV screen only. To me in 99% of the cases when you put Hyper-V host in maintenance mode in VMM you will probably want to restart that host and not to receive SCOM alerts about it. I think it is highly unprofessional someone to report to you an bug and you to close that report as fixed without actually fixing it. But as stubborn guys I’ve logged this bug again. If you want to join you can vote for fixing this bug here. I suggest to hurry with your vote before someone closing that report as fixed again .
Last week I’ve submitted a bug on a feature of SCVMM that I’ve spotted a long time ago. Due to various reasons I’ve somehow always forgot to submit it. The bug is that when you integrate SCOM 2012 and SCVMM 2012 you can put the Hyper-V host in maintenance mode in VMM and this will automatically put the Hyper-V host in maintenance mode in SCOM. This is true but to some extent. Actually only the objects in SCOM related to SCVMM are put in maintenance mode. What this means if you put the Hyper-V host in maintenance mode trough SCVMM and you restart that host you will still receive alerts like health service failure or failed to connect from SCOM about that host. The reason for that is if only objects related to VMM are put in maintenance mode other objects like the computer object, the health service and the agent watcher are still in active monitoring. A few days after submitting that bug in Microsoft Connect site I’ve received e-mail that this bug is closed as fixed:
As this issue is still present in System Center Virtual Machine Manager 2012 SP1 beta this leads me to believe that there are probably post beta releases for TAP customers which are not publically available. In a matter of fact there are some rumors over Internet that System Center 2012 SP1 has passed RTM and could be available early in January. I really hope so these rumors are true so we can have final release of Service Pack 1 for System Center 2012 as soon as possible. When RTM is available I will try to test if this bug is really fixed.
Microsoft Operations Manager beta program is open on Microsoft Connect site. If you sign up you can download Managing and Operating a Microsoft Private Cloud—How to Apply the Microsoft Operations Framework (MOF) guide and provide feedback before the final release. Sign up and get the beta guide from here.