SCOM 2007 R2 – Monitoring Windows Server 2012 machines in SCOM 2007 R2

Last week I got several questions on how and when Operations Manager will provide monitoring support for Windows Server 2012 so I wanted to clarify things in this blog.
There is also an official Microsoft blog post about this.

Management Group Version Management Server or Gateway Version OpsMgr Agent Version Agent OS Version Supported Configuration?
2007 R2 2007 R2 2007 R2 Windows Server 2012 No
2007 R2 2007 R2 2012 RTM Windows Server 2012 Yes
2007 R2 2007 R2 2012 SP1 Windows Server 2012 Yes
2012 RTM 2012 RTM 2012 RTM Windows Server 2012 Yes
2012 SP1 2012 SP1 2012 SP1 Windows Server 2012 Yes

 

As shown in the above table SCOM 2007 R2 doesn’t support monitoring of Windows 2012 in combination with the 2007 R2 agent.

But because the 2012 agent is backwards compatible installing the 2012 agent on an Windows 2012 machine, it properly reports to the SCOM 2007 R2 environment.

Expectations are that with the next CU Windows 2012 is supported.

SCCM 2012 – Reporting and DPM rights on SQL

Issue
At a customer of ours we have installed a SQL 2012 R2 server for all System Center Products including DPM 2012.
After installing the SCCM 2012 Reporting functionality on the SQL server the eventviewer flooded with:

Log Name: Application
Source: MSSQLSERVER
Event ID: 18456
Task Category: Logon
Level: Information
Description:
Login failed for user ‘NT AUTHORITY\SYSTEM’. Reason: Failed to open the explicitly specified database. [CLIENT: 1.1.1.1.1]

Cause
After some investigation we found that the SCCM 2012 reporting installation messed around with the security rights of the System Center SQL database.

The NT Authority\System account was removed from the SYSadmin role


Resolution

Add the NT\Authority\System account to the Sysadmin role