Description of Update Rollup 4 for System Center 2012 Operations Manager Service Pack 1

Issue 1

Windows PowerShell scripts or modules cannot be executed in an AllSigned environment.

Symptom

You receive the following error message:

Issue 2

Location points are not displayed in the GSM Map Dashboard because of a Microsoft SQL Server time-out.

Symptom

The following events may be logged in the SQL Server Operations Manager event log:

Issue 3

An incorrect warning is generated when security event 5140 is monitored.

Symptom

The warning contains incorrect information for Source Address, Source Port, and Share Name.

Issue 4

An empty target group is created when endpoints are enumerated.

Symptom

ETL tracing displays the following message:

[Microsoft.EnterpriseManagement.Modules.Apm.ServerDiscovery] [] [Verbose] :TemplateAgentDiscoveryProbeAction.ProcessDataItem{templateagentdiscoveryprobeaction_cs148}( 00000000038E0B6A )Application instances for the next application components were not found in the system:

Issue 5

Generic performance reports contain no object data after export.

Symptom

By default, performance reports have the object information (Servername, Disk Label, and so on) collapsed . When the report is exported, this information is missing.

Issue 6

When you open a network node dashboard on a Windows 7 Service Pack 1 x86-based computer, the console hangs.

Symptom:

CPU use will be near 99 percent, and the console will be unresponsive.

Issue 7

A user role that is created by using Windows PowerShell on a non-US locale system does not show the display name and description on the console.

Issue 8

Customer cannot add overrides or subgroups to groups by using cmdlets; query processor ran out of internal resources

Symptom

When you create an override on a group or adding to a group, you may receive the following message:

The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference lots of tables or partitions. Please simplify the query. If you believe that you have received this message in error, contact Customer Support Services for more information.

Issue 9

When you select objects in the dashboard, you receive a "The query processor ran out of internal resources" error.

Symptom

You receive the following error message:

Note This is a rare event and expected only for extremely complex queries or queries that reference lots of tables or partitions.

Issue 10

Successive discovery uses a different device key. This behavior causes duplicate devices to be discovered.

Symptom

When network discovery is run, duplicate entries for the same device may be added to the database.

Issue 11

vStateDailyFull returns empty when the time zone on the Data Warehouse server is UTC+0X:30.

Symptom

Availability reports may be displayed as blank.

Issue 12

Health State of Advisor monitored agent is always "Warning" in Advisor Health State.

Issue 13

APM monitor is not functional when you upgrade to a later version of Operations Manager

Issue 14

In the Internet Information Services 8.0 and Internet Information Services 7.0 modules, a website cannot be discovered or monitored if HTTP binding is missing from the configuration.

Issue 15

SQL broker conversations can lead to very large OperationsManager DB size and TempDB size

Issue 1

In rare cases, Management Server’s Monitoringhost.exe process may stop with an access violation when it is monitoring log files on UNIX and Linux computers.

Symptom

Intermittently, the Management Server Monitoringhost.exe process on a server that is managing UNIX and Linux will crash with a second-chance access violation 0xc0000005. When this occurs, the managed UNIX or Linux computers go into an "unmonitored" or "critical" state.

Issue 2

Linux computers that have multiple "release" files in /etc, may not be identified correctly during discovery. This includes an OS-release file.

Symptom

Whediscovery of a Linux-based computer fails with an error during SSH discovery. Or, the operating system name and version are determined incorrectly. This issue occurs can occur when multiple *-release files exist in /etc and one of the is named "os-release." The error message may resemble the following:

Issue 1

A Solaris computer that has lots of monitored resources (for example, file systems, physical disks, and network adapters) may run out of file descriptors and not monitor the resources. This occurs because the default user limit on Solaris is too low to allocate sufficient file descriptors. The updated agent now overrides the default user limit with a user limit for the agent process of 1024.

Symptom

On a Solaris computer, the Operations Manager agent’s log (/var/opt/microsoft/scx/log/scx.log) contains errors or warnings together with the following text:

Issue 2

A monitored Solaris zone that is configured for dynamic CPU allocation together with Dynamic Resource Pools may log errors in the agent logs and return incorrect values for processor performance counters.

Symptom

This issue applies to any monitored Solaris zones that are configured together with Dynamic Resource Pools and a "dedicated-cpu" configuration that involves a range of CPUs.

Issue 3

If Linux Container (cgroup) entries are in /etc/mtab, errors are logged when physical disk discovery is enabled, and some physical disks may not be discovered.

Symptom

If entries in /etc/mtab on a monitored Linux computer begin with the string "cgroup," errors that resemble the following may be logged in the agent’s log (/var/opt/microsoft/scx/log/scx.log):

Issue 4

Physical disk configurations that cannot be monitored or failures in physical disk monitoring for UNIX and Linux computers cause failures in file system monitoring.

Symptom

Logical Disk instances (file systems) are not discovered by Operations Manager for a monitored UNIX- or Linux-based computer.

Known issues with this update

• After you install the update rollup package on all roles on the server that is running System Center Operations Manager 2012 Service Pack 1 (except on the Agent and Gateway roles), the updates do not appear in the Add or Remove Programs item in Control Panel.

• After you apply Update Rollup 4, the Operations Manager console has to be reopened in order to apply the Alert Attachment Management Pack fix.

• After you install the update rollup package, the version number of the console is not changed.

• If the ACS update package is installed, uninstalled, then reinstalled, the database upgrade script that is included in this update will not run because the database version is changed during the first installation of the ACS update. This could result in a server crash if the user reuses a partition when the partition still present.
  
  The partition can be closed manually in SQL Server Studio. To do this, browse to the ACS database, and then run the following script in a Query Editor window:
  
  

  begin tran

  
  
  

  
  
  

  -- mark all active partitions for closing

  
  
  

  if (select count(*) from dtPartition where Status = 0) > 0

  
  
  

      update dtPartition set Status = 1 where Status = 0

  
  
  
  
  

  commit tran

  
  
  In order to create a new partition, stop AdtServer, run this script, and then restart AdtServer.

• After you install the update rollup package on a web console, you may receive the following error message when you access ASP.NET webpages that have ViewState enabled after you upgrade from ASP.NET 1.1 to ASP.NET 2.0:
  
  

  Server Error in '/OperationsManager' Application.
  To resolve this issue, close and then restart Internet Explorer.

Installation notes

• This update rollup package is available from Microsoft Update in the following languages:

  • Chinese Simplified (CHS)

  • Japanese (JPN)

  • French (FRA)

  • German (DEU)

  • Russian (RUS)

  • Italian (ITA)

  • Spanish (ESN)

  • Portuguese (Brazil) (PTB)

  • Chinese Traditional (CHT)

  • Korean (KOR)

  • Czech (CSY)

  • Dutch (NLD)

  • Polish (POL)

  • Portuguese (Portugal) (PTG)

  • Swedish (SWE)

  • Turkish (TUR)

  • Hungarian (HUN)

  • English (ENU)

  • Chinese Hong Kong (HK)

• Some components are multilanguage, and the updates for these components are not localized.

• You must run the update rollup as an administrator.

• If you do not want to restart the computer after you apply the console update, close the console before you apply the update for the console role.

• To start a new instance of Microsoft Silverlight, clear the browser cache in Silverlight, and then restart Silverlight.

• Do not install the update rollup package immediately after you install the System Center 2012 SP1 server. Otherwise, the Health Service state may not be initialized.

• If User Account Control is enabled, run the .msp update files from an elevated command prompt.

• You must have System Administrator rights on the database instances for the Operational Database and Data warehouse to apply updates to these databases.

• To enable the web console fixes, add the following line to the %windir%\Microsoft.NET\Framework64\v2.0.50727\CONFIG\web.config file:
  
  

  <machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>

Note Add the line under the <system.web> section, as described in the following article in the Microsoft Knowledge Base:

911722 You may receive an error message when you access ASP.NET webpages that have ViewState enabled after you upgrade from ASP.NET 1.1 to ASP.NET 2.0

Supported installation order

We recommend that you install the update rollup package in the following order:

1. Install the update rollup package on the following server infrastructure:

   • Management server or servers

   • Gateway servers

   • Reporting servers

   • Web console server role computers

   • Operations console role computers

2. Manually import the management packs.

3. Apply the agent update to manually installed agents, or push the installation from the Pending view in the Operations console.

Notes

• Install the update rollup package on agents either before or after you install the update rollup package on the server infrastructure.

• If the Connected MG/Tiering feature is enabled, first update the top tier of the Connected MG/Tiering feature.

Update Rollup 4 files have a version number of 9538.1084.

Installation information

To download the update rollup package and extract the files that are contained in the update rollup package, follow these steps:

1. Download the update packages that Microsoft Update provides for each computer. Microsoft Update provides the appropriate updates according to the components that are installed on each computer.

2. Apply the appropriate MSP files on each computer.
   
   Note MSP files are included in the update rollup package. Apply all MSP files that relate to a specific computer. For example, if the web console and console roles are installed on a management server, apply the MSP files on the management server. Apply one MSP file on a server for each specific role that the server holds.

3. Execute the UR_Datawarehouse.sql SQL script on Datawarehouse Server against the OperationsManagerDW database.
   
   Note This script is included in the server component update. After the installation is complete, you can fid the script in the following folder:

   %SystemDrive%\Program Files\System Center 2012 SP1\Operations Manager\Server \SQL Script for Update Rollups\

4. Import the following management packs:

   • Microsoft.SystemCenter.Apm.Infrastructure.mpb

   • Microsoft.SystemCenter.IntelliTraceCollectorInstallation.mpb

   • Microsoft.Windows.InternetInformationServices.CommonLibrary.mp

   • Microsoft.SystemCenter.Advisor.Internal.mpb

   • Microsoft.SystemCenter.AlertAttachment.mpb

   • Microsoft.SystemCenter.Apm.Infrastructure.Monitoring.mp

   • Microsoft.SystemCenter.Apm.Library.mpb

   • Microsoft.SystemCenter.DataWarehouse.Report.Library.mp

   • Microsoft.SystemCenter.DataWarehouse.Reports.mp

   • Microsoft.SystemCenter.DataWarehouse.ServiceLevel.Report.Library.mp

   • Microsoft.SystemCenter.Image.Library.mp

   • Microsoft.SystemCenter.IntelliTraceProfiling.mpb

   • Microsoft.SystemCenter.Visualization.Library.mpb

   Note Management packs are included in the server component updates in the following folder:
   

   %SystemDrive%\Program Files\System Center 2012 SP1\Operations Manager\Server\Management Packs for Update Rollups

Uninstall information

To uninstall an update, run the following command:

msiexec /uninstall PatchCodeGuid /package RTMProductCodeGuid

Note In this command, the placeholder RTMProductCodeGuid represents one of the following GUIDs.

Additionally, the placeholder PatchCodeGuid represents one of the following GUIDs.

File information

The following files are updated in Update Rollup 4 for System Center 2012 Service Pack 1.

How to install Operations Manager UNIX and Linux monitoring packs and agents

To install the updated monitoring packs and agents for UNIX and Linux operating systems, follow these steps:

1. Apply Update Rollup 4 to your System Center Operations Manager 2012 Service Pack 1 environment.

2. Download the updated management packs from the following Microsoft website:
   

   System Center Monitoring Pack for UNIX and Linux Operating Systems

3. Install the management pack update package to extract the management pack files.

4. Import the following updated management packs and management pack bundles:

   • Microsoft.Unix.Library management pack (from the \2012 SP1\ folder)

   • Microsoft.Unix.LogFile.Library management pack bundle

   • Microsoft.Unix.ShellCommand.Library management pack bundle

   • Microsoft.Unix.Process.Library management pack bundle

   • The library management packs that are relevant to the Linux or UNIX platforms that you are monitoring in your environment

   
   
   Note The Microsoft.Linux.Universal management packs are also in the \2012 SP1\ folder.

5. Import the updated management pack for each version of Linux or UNIX that you are monitoring in your environment.

6. Upgrade each agent to the latest version by using either the Update-SCXAgent Windows PowerShell cmdlet or the UNIX/Linux Agent Upgrade Wizard in the Administration pane of the Operations Console.