I came across a great article on TechNet which is essentially a compilation of useful SCOM information, it includes everything from the basics and key concepts, to deployment guidelines and information on how to configure and use different features.
With the release of SCOM 2012 R2 Microsoft has official amended the supported SQL collation settings. In the past you had to use SQL_Latin1_General_CP1_CI_AS, this was due to the data warehouse being installed with this setting by default regardless of the SQL server collation setting. This was a nice addition which has been due for a long time, having collation mismatches between your OpsDB and DW can cause a whole host of issues which are well documented.
Of course the new settings only apply to fresh installations, when upgrading the previous collation settings will still be used.
Click here for the complete supported configuration.
Veeam has recently announced version 7 of their Veeam Management Pack for System Center. The most exciting new feature is the inclusion of support for Microsoft Hyper-V which has been a long awaited addition.
It is currently in public beta which does not include the support for VMware and requires Microsoft System Center 2012 and later and Microsoft Hyper-V 2012 and later.
Click here for more information and to sign up for the beta.
Press release available here.
“New in version 7:
Support for Microsoft Hyper-V — now you get the same deep visibility with monitoring, reporting and capacity planning that you’d expect from Veeam for both Hyper-V and vSphere infrastructures.
Unique dashboards for vSphere and Hyper-V — see what’s happening in your environment in real time. Get in-context views with heatmaps for visualizing multiple metrics.
Visibility of Hyper-V backups in System Center — monitoring, reporting and capacity planning for Veeam Backup & Replication for Hyper-V.”
Here is an article from the OpsMgr Engineering Blog detailing an issue with SCOM discovering Ckuster Resources
“If a Cluster has orphaned object entries in ClusterHive registry key, the System Center Operations Manager agent may not discover some or all Cluster resources. This can occur with System Center Operations Manager 2007 (OpsMgr 2007) or System Center 2012 Operations Manager (OpsMgr 2012).”
The article details a fix which envolves locating and then removing the orphaned objects:
“First, use the Failover Cluster PowerShell commands Get-ClusterResource and Get-ClusterGroup to get the list of Resources and Groups. Then, using the output, check for Resources/Groups that appear as Offline and verify if these can be seen in the Failover Cluster Console. Verify with the Cluster administrator whether these are still valid, then assuming they are not and you’ve identified which ones that are orphaned, delete them using these commands from an elevated CMD Prompt (Run As Administrator):
For orphaned resources: Cluster RES “<RESOURCE_NAME>” /DELETE
For orphaned groups: Cluster GROUP “<GROUP_NAME>” /DELETE
Once this is done the missing cluster resources should now be discovered.”
One of the additional features of the recent Update Rollup 2 for SCOM 2012 R2 is new widgets, these are made availible by completing the import of the new manegements packs portion of the Update Rollup process, which includes Microsoft.SystemCenter.Visualization.Library.mpb.
This article contains a list of the new widgets as well as a brief description of each. There are some welcome additions which should enable a much richer dashboard experience.
Microsoft has released version 18.104.22.168 of the SQL MP which enables the discovery and monitoring of SQL Server 2014 Database Engines, Databases, SQL Server Agents and other related components. This Management Pack is designed to run by Operations Manager 2007 R2 (except dashboards), Operations Manager 2012 or Operations Manager 2012 R2.
For more information, including a list of new features and improvements go here.