There have been various questions on how and when Operations Manager will provide monitoring support for Windows Server 2012 so I wanted to clarify things in this blog.
The supported configurations for Operations Manager are detailed as per the below and these should be referred to as the official guidance:
OM 2012: http://technet.microsoft.com/en-us/library/hh205990.aspx
OM 2007 R2: http://technet.microsoft.com/en-us/library/bb309428.aspx
(OM 2012 SP1 will be added in the near future)
To summarize from the above and to fill some gaps as documentation is getting updated.
OM 2007 R2:
OM 2007 R2 agent is not supported on Windows Server 2012. Running OM 2007 R2 server components on Windows Server 2012 is also not supported.
You can monitor WS2012 using an OM2007 R2 Management Group, the SC2012 and above agent and the MPs that are tested and licensed for OM2007 R2. The Windows Server Base OS MP is supported in the configurations shown below.
WS2012 support matrix for OM2007 R2/SC2012:
Management Group Version
Management Server or Gateway Version
OpsMgr Agent Version
Agent OS Version
Windows Server 2012
OM 2012 will support monitoring Windows Server 2012(Except from APM monitoring of applications hosted on IIS8 which requires SP1). Running OM 2012 server components on Windows Server 2012 is not supported.
The OM 2012 console is not supported on Windows 8 client and running the OM 2012 agent on Windows 8 client is not supported.
OM 2012 SP1:
OM 2012 SP1 will provide full support for Windows Server 2012, both for monitoring and for running OM 2012 SP1 server components. This includes the console and agent on Windows 8 client.
Management packs for monitoring Windows Server 2012 roles which are typically made available 60 to 90 post RTM of the Windows Server Role will start to be made available from mid-September and we expect most roles to have shipped their English language MPs by the end of September. Localized MPs will start to be delivered from October for most roles. (Localized MPs will be delivered in the 8 Languages that is supported by OM2012 to begin with.)
There are no plans to ship a Management Pack for monitoring Windows 8 client machines. Update Sep 7 2012: We are reevaluating this and investigating building a Windows 8 client MP. Stay tuned!
- Daniel Savage, Principal Program Manager
Are you saying that OM 2007 R2 will never support monitoring of Windows Server 2012 ???
Yes, that is the plan.
That seems fair enough. hopefully it means that the MPs for 2012 components will use all the features in OM2012, and not be hampered by having to work on OM2007 as well. Plus of course means they can develop and test them faster.
Has the release date for OM 2012 SP1 been announced publicly? (I understand that there are various official roll-ups, CTP and unsupported workarounds).
More generally, is a date been announced for SP1? This blocks the Windows 2012 migrations ....
"There are no plans to ship a Management Pack for monitoring Windows 8 client machines."
I'm totally disappointed! Without a dedicated MP, there is no way to monitor Windows 8 clients out of the box!
Have you guys ever heard of Hyper V and TESTING!!!!!!!!!!!!!!!!!!!!!
@Sadda - Thanks for the feedback. We are reconsidering this decision now.
Please a rough date for SP1. Without the ability to monitor Server 2012 or bring a server 2012 into VMM, I will not be able to move to the server 2012 platform.
@Travis & SCOM Team,
Glad to hear that your team is reevaluating on Windows 8 MP!
They indirectly mentioned here ... by the end of this month! :)
"Management packs for monitoring Windows Server 2012 roles which are typically made available 60 to 90 post RTM of the Windows Server Role will start to be made available from mid-September and we expect most roles to have shipped their English language MPs by the end of September."
It will be good if Microsoft reconsiders support for monitoring Windows Server 2012 with SCOM 2007 R2.
As I remember Microsoft promised that every new mp that is released will be compatible with SCOM 2007 R2 and SCOM 2012. Mainstream support for SCOM 2007 R2 ends in 2014 so there are still customers who depends on 2007 R2.
SP1 beta is released - www.microsoft.com/.../details.aspx
Can you share any information on how this decision was reached? Since the SCOM 2012 agent can report back to a SCOM 2007 R2 management group, is this solely a management pack issue? Are there features in the management pack that require SCOM 2012 servers?
I agree with Stanislav, Microsoft should reconsider the decision not to support monitoring Windows Server 2012 machines from Ops Mgr 2007 R2. I can understand why installation of Ops Mgr 2007 R2 is not supported on Windows Server 2012 but at least a basic level of monitoring should be supported.
I think we will not be able to change their minds. For such big unpleasant surprise at least they could have warned us in a months earlier. Announcing such thing in the last minute just breaks the plans for many customers. I still want at least explanation why this was decided that way.
Can any one one from Microsoft at least responds?