Export (0) Print
Expand All

Release Notes for Operations Manager in System Center 2012 R2

Updated: November 1, 2013

Applies To: System Center 2012 R2 Operations Manager

Before you install and use Operations Manager in System Center 2012 R2, read these release notes.

Advisor Monitoring Server group reserved for Advisor Connector use only

Description: The Microsoft System Center Advisor Monitoring Server group is reserved for the control of agents that are included into the Advisor Connector. This group should not be modified or added to the Advisor Managed list.

Workaround: This is by design.

.NET Framework required for enabling Advisor Connector on agents

Description: To enable the Advisor Connector on Operations Manager agent computers, Microsoft .NET Framework must first be installed.

Workaround: For agents running Windows Server 2008 R2 and earlier, install .Net Framework 3.5 SP1. For agents running Windows Server 2012 and newer, install .Net Framework 4.0 or higher.

ASP.NET Web API data producers not installed if Microsoft .NET Framework 4.x not installed first

Description: If you install an Operations Manager for System Center 2012 R2 agent on a computer that does not have Microsoft .NET Framework 4.x previously installed, some data producers for the ASP.NET Web API will not be installed. If you later install the Microsoft .NET Framework 4.x on the computer and try to monitor an application that uses the ASP.NET Web API with the application monitoring feature, the applicable data producers will still be missing, and monitoring for that application will not work.

Workaround: This is by design. To restore the missing data producers, the agent should be re-installed after Microsoft .NET Framework 4.x has been installed on the computer.

You must import management packs in order to use Application Performance Monitoring with Windows Server 2012 R2

Description: You must import the Windows Server 2012 R2 and IIS 8 management packs in order to use Application Performance Monitoring (APM) with Windows Server 2012 R2.

Workaround: System Center 2012 R2 Operations Manager includes APM support for Windows Server 2012 R2 and IIS8 (Internet Information Services 8). However, In order for this feature to work you must import the following set of monitoring packs:

  • Microsoft.Windows.Server.2012.R2.Discovery.mp

  • Microsoft.Windows.Server.Library version 6.0.6989.0 or newer

  • Microsoft.Windows.Server.2012.Discovery version 6.0.6989.0 or newer

  • Microsoft.Windows.InternetInformationServices.CommonLibrary version 7.0.8862.0 or newer

  • Microsoft.Windows.InternetInformationServices.2012 version 7.0.8862.0 or newer

    This is a new version of the IIS8 management pack. Do NOT use the Microsoft.Windows.InternetInformationServices.6.2 management pack, which was part of the "Windows 8 beta management pack release". Remove the Microsoft.Windows.InternetInformationServices.6.2 management pack if you had previously imported it.

  • Microsoft.SystemCenter.Apm.Web.IIS8

    This is in the /ManagementPacks folder of the System Center 2012 – Operations Manager media, and is the equivalent of the Microsoft.SystemCenter.Apm.Web.IIS7 management pack which was previously (and still is) used for IIS7.

WCFServerAsyncBeginProducer cannot be found on agent after upgrade

Description: During upgrade from System Center 2012 to System Center 2012 R2, a new System Center 2012 R2 agent which is configured for APM monitoring will still receive OLD configuration settings from a management group which has not yet been upgraded, and might log an 'information' event (ID 1295) in the event log with the following message:

Cannot find producer "Microsoft.EnterpriseManagement.OperationsManager.Apm.Instrumentation.InstrumentationClass.WCFServerAsyncBeginProducer of assembly Microsoft.EnterpriseManagement.OperationsManager.Apm.Instrumentation, Version=7.0.5000.0, Culture=Neutral, PublicKeyToken=9396306c2be7fcc4, processorArchitecture=MSIL" in assembly Microsoft.EnterpriseManagement.OperationsManager.Apm.Instrumentation, Version=7.0.5000.0, Culture=Neutral, PublicKeyToken=9396306c2be7fcc4, processorArchitecture=MSIL, producer is inaccessible due to access level or producer has an incorrect signature. Please see documentation for details.

Workaround: None. This event is by design. Everything else in APM works normally, and this event message can be safely ignored.

After upgrade the web console does not work due to IIS becoming corrupt

Description: While upgrading to System Center 2012 R2, Operations Manager, if the upgrade breaks the web console, you can encounter a Runtime Error: Server Error in ‘/OperationsManager’ Application. In the application log on the web console server, you will see an event with an exception message: Could not load type 'System.ServiceModel.Activation.HttpModule'.

For example, as part of the upgrade process you are prompted to add “HTTP Activation” to the role services of the Operating System. This leaves IIS in a semi-broken state, and requires a re-registration of ASP.NET in IIS to correct. This can occur anytime you add any IIS components after ASP.NET.

Workaround: Re-register ASP.NET in IIS.

  • On Windows Server 2008 R2 SP1, run the following in an elevated CMD:  C:\Windows\Microsoft.NET\Framework64\v4.0.30319>aspnet_regiis.exe -i -enable

  • On Windows Server 2012, run the following in an elevated CMD:  C:\Windows\Microsoft.NET\Framework64\v4.0.30319>aspnet_regiis.exe -r 

Using sudo elevation with Solaris operating systems requires a configuration change if sudo executable is not in an expected path

Description: If you want to use sudo elevation on a computer running Solaris, and the sudo executable is not in an expected path, you need to create a link to the correct path. Operations Manager will look for the sudo executable in the path /opt/sfw/bin, and then in the path /usr/bin. If sudo is not installed in one of these paths, a link is required.

Workaround: The UNIX and Linux agent installation script creates the symbolic link /etc/opt/microsoft/scx/conf/sudodir to the folder expected to contain sudo. The agent uses this symbolic link to access sudo. The installation script automatically creates the symbolic link, so no action is needed for standard UNIX and Linux configurations. However, if sudo is installed in a non-standard location, you should change the symbolic link to point to the folder where sudo is installed. If you change the symbolic link, its value is maintained for uninstall, re-install, and upgrade operations with the agent.

See Also

-----
For additional resources, see Information and Support for System Center 2012.

Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.
-----
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft