———————————————————————————————————————————————————–
Update
Here is the WS2012 support matrix for OM2007 R2/SC2012 taken directly from SCOM Team blog:
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 |
- To use the SC2012 agent you have to be licensed for SC2012.
- The SC2012 RTM agent requires .NET3.5 be installed on WS2012. (SC2012 SP1 agent does not have this requirement)
———————————————————————————————————————————————————–
Microsoft release an clarification on Windows Server 2012 monitoring with SCOM 2007 R2. What Microsoft is saying in order to monitor Windows Server 2012 you have to install SCOM 2012 agent on such servers and as these agents can report back to SCOM 2007 R2 server we can actually monitor Server 2012 with such scenario. The only thing that is left to be clarified is if the Windows Server 2012 Management packs will be supported in SCOM 2007 R2 server. Full announcement is here.
Update:
Microsoft released 3 new management packs and one updated one:
So SCOM 2007 R2 will be able to monitor Windows Server 2012 if you implement certain scenario with the exception of some roles.
Update: Kevin Holman also confirms that SCOM 2007 R2 can monitor Windows Server 2012 in specific scenario. Read here.