[OpsMgr 2012 R2] Changing Target Group in Process Monitoring is failing

Today, I've encountered an issue with a process monitoring.
The case has been detected because the targeted group that was enabling my process monitor has been deleted in SCOM... and the result is an error message when editing the Process Monitor

Clicking OK is opening the properties and we can see that targeted group field is empty...

 You are also allowed to clik on the [...] button to select a new group.

 

The bug is that any activities on the targeted group field is not seen as a change on the monitor configuration and the Apply button is always greyed !At this step, you cannot save the change and also your new targeted group cannot be saved.

A work-arround is to edit a field in an other pane, for example in the Running Processes pane and you will see that the Apply button has been activated.

 

 Applying the change at this step will save your new targeted group change.



You can easyly reproduce this with no group deletion - just try to change the targeted group by an other and you will see that the Apply Button is always in grey state meaning the the change is not 'seen' by SCOM and you will not be able to save the new conf.


By the way, Microsoft has been informed and a bug will be openned to the developper team... to be followed !

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007 R2][OpsMgr 2012][OpsMgr 2012 SP1][OpsMgr 2012 R2] Be careful upgrading Base Windows Server Operating System MP to version 6.0.7294.0

Here is a quick warning  to all the SCOM administrators that would keep there infrastructure up-to-date !
Before importing the latest OS MP you must know that Microsoft has pulled the version 6.0.7294.0 of the OS MP from the catalog and reverted to version 6.0.7292.0 a full explanation of the issue has been blogged by Kevin Holman >>> Here <<<.

The best right now should be to not upgrade to the latest MP, waiting Micorosoft to release a fixed version.

There is currently a bug in this version of the MP that causes logical disks to be discovered more than once and this causes a flood of performance data to hammer your DB. This issue was discovered by Daniele Grandini.


This release 6.0.7294.0 was just a minor update with some bug fixes (Fixed more performance collection workflows that were failing for mount points)


If you have already imported the latest release, you'll not be able to go back the the previous version (removing OS base MP is quite impossible because of the dependencies from the other MPs). You should also disable the performance collection rules temporarily, until a fixed MP is released by Microsoft.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2012] Is there a bug in the SCOM 2012 Web Availability Templates ?

Michael Humphrey has published on his blog an article that raises the existence of a bug in the Web Availability Templates.

He has set up an availability monitor to query msn, bing, premier.microsoft.com, and technet. He has intentionally put in a mistyped URL, www.msn.cop. Alert is well raised for this inaccessible URL. Then he fixed the typo replacing www.msn.cop by www.msn.com and it's seems that this update is not taken in account even if you force the monitor to an healthy state. Monitor return back to unhealthy with the old URL.

The workaround is make your changes, then export the MP, delete the MP and reimport it. But this action of deleting, then importing a large MP (that was monitoring 40 URL) caused the OpsDB and DW to fall behind for about 30 minutes...

Read the article here : http://www.opsmanfan.com/index.php/7-a-bug-in-the-scom-2012-web-availability-templates

This posting is provided "AS IS" with no warranties.