Since I wanted to be sure that I got it right I contacted Microsoft HQ directly with this question. This is one of the huge benefits being a MVP . Soon I got my much needed answers which I couldn’t post earlier since I was a ‘bit’ busy.
But here it is with a big thanks to Daniel Savage and Travis Wright from Microsoft.
|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 you can see SCOM R2 does NOT support the monitoring of Windows Server 2012 when a SCOM R2 Agent is being used.
However, when you’re properly licensed for running System Center 2012 but haven’t upgraded to OpsMgr 2012 yet, you can install OpsMgr 2012 Agents on those Windows 2012 Server systems and let them report to your SCOM R2 environment.
This is a valid scenario since an OpsMgr 2012 Agent is backwards compatible, thus capable communicating with a SCOM R2 Management Group.
I know, the support statement for SCOM R2 tells us main stream support ends on July the 8th 2014. However, it doesn’t mean all new products which come out before that date are supported by SCOM R2 as well.