Release Notes for Operations Manager in System Center 2012 SP1
Updated: May 13, 2016
Applies To: System Center 2012 SP1 - Operations Manager
Before you install and use System Center 2012 Service Pack 1 (SP1), read these release notes about Operations Manager.
Critical and non-critical connectivity exceptions are both shown as “non-critical” for MVC applications
Description: When monitoring an ASP.NET MVC application with Application Performance Monitoring (.NET application performance monitoring), if the setting to monitor "All Exceptions" is selected (as opposed to only "Critical Exceptions"), all connectivity exceptions will report as "critical".
Workaround: Select only the "Critical Exception" option for monitoring for MVC applications, as opposed to "All Exceptions".
.NET Application Performance Monitoring will not work correctly when Operations Manager agents and management servers are on different Operations Manager release versions
Description: Discovery of WCF endpoints, monitoring of Windows Services and other Application Performance Monitoring (.NET application performance monitoring) related functionality is not supported across Operations Manager versions. For example, a 2012 SP1 agent reporting to a System Center 2012 – Operations Manager server (or vice versa, an System Center 2012 – Operations Manager agent reporting to a 2012 SP1 management group) will not work correctly.
Workaround: Install both agents and management servers with the same Operations Manager release.
No parameters are collected for RecordError when monitoring an ASP.NET MVC application
Description: When monitoring an ASP.NET MVC application with Application Performance Monitoring (.NET application performance monitoring), exception events do not have parameters collected.
Workaround: None. We are working on this to issue to be resolved in a future release.
You must import Windows 8 management packs in order to use Application Performance Monitoring with Windows Server 2012
Description: You must import the Windows Server 2012 and IIS 8 management packs in order to use APM (.NET application performance monitoring) with Windows Server 2012.
Workaround: System Center 2012 Service Pack 1 (SP1), Operations Manager includes APM support for Windows Server 2012 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.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.
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 some changes made to the agent for Beta, we removed a class from the code.Result: During upgrade, a new SP1 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.
Web Recorder functionality does not work with IE10 on Windows 8
Description: Web Recorder functionality does not work with Internet Explorer 10 on Windows 8.
The Network Summary Dashboard cannot load data on the OM12SP1 UI when connecting to an OM12 Management Group
Description: When using the Network Summary Dashboard in System Center 2012 Service Pack 1 (SP1), Operations Manager, customers cannot load data when connecting to a System Center 2012 – Operations Manager management group.
Workaround: Use the System Center 2012 – Operations Manager User Interface to connect to a System Center 2012 – Operations Manager management group, or upgrade the management group to SP1.
On upgrade from a licensed install customers will see an Evaluation EULA even though product is licensed
Description: During upgrade from a licensed installation of Operations Manager, customers will see an Evaluation EULA even though product is licensed.
Workaround: Run Get-ScomLicense in PowerShell to see the actual license agreement.
File names for the Data Warehouse database and log are .mdf and .ldf
Description: The file name for the Operations Manager Data Warehouse SQL Database is always ".mdf", and the log file name ".ldf" instead of the database name.
Workaround: Use the SQL process to rename the files to match the database name. See How to consolidate physical files and rename the logical file name in SQL Server 2000 and in SQL Server 2005.
The Microsoft System Center Application Monitoring 360 SLA Management Pack is not imported by default during setup
Description: The applications dashboard under Monitoring\Application Monitoring in the Monitoring section of the Operations Manager console contains a section for Service Level Agreements (SLAs). By default, this section is empty for any application. There is a management pack containing default SLAs for these applications on the SP1 CD that you can import, that will make the SLAs appear. You can also create and modify your own SLAs for the applications.
Workaround: There are two processes to populate SLAs in the applications dashboard:
Create your own SLAs for the applications. For more information, see How to Configure 360 .NET Application Monitoring Dashboards in System Center 2012 SP1.
Import the "Microsoft System Center Application Monitoring 360 SLA" management pack, Microsoft.SystemCenter.ApplicationMonitoring.360.SLA.XML, from the SP1 media, which contains default SLAs.
Do not install a System Center 2012 SP1, Operations Manager Management Group pointing to a System Center 2012 Data Warehouse
Description: Do not install a System Center 2012 Service Pack 1 (SP1), Operations Manager versioned management group pointing to a System Center 2012 – Operations Manager versioned data warehouse. The data warehouse will not function.
Workaround: None. Ensure both the management group and the data warehouse pointed to are running the SP1 version of System Center 2012 – Operations Manager.
After upgrade to SP1 the web console does not work due to IIS becoming corrupt
Description: While upgrading to System Center 2012 Service Pack 1 (SP1), 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.