Update Rollup 9 for System Center 2012 R2 Operations Manager

Introduction
This article describes the issues that are fixed in Update Rollup 9 for Microsoft System Center 2012 R2 Operations Manager. It also includes the installation instructions for the update rollup.

Issues that are fixed in this update rollup

  • SharePoint workflows fail with an access violation under APM

    A certain sequence of the events may trigger an access violation in APM code when it tries to read data from the cache during the Application Domain unload. This fix resolves this kind of behavior.

  • Application Pool worker process crashes under APM with heap corruption

    During the Application Domain unload two threads might try to dispose of the same memory block leading to DOUBLE FREE heap corruption. This fix makes sure that memory is disposed of only one time.

  • Some Application Pool worker processes become unresponsive if many applications are started under APM at the same time

    Microsoft Monitoring Agent APM service has a critical section around WMI queries it performs. If a WMI query takes a long time to complete, many worker processes are waiting for the active one to complete the call. Those application pools may become unresponsive, depending on the wait duration. This fix eliminates the need in WMI query and significantly improves the performance of this code path.

  • MOMAgent cannot validate RunAs Account if only RODC is available

    If there's a read-only domain controller (RODC), the MomAgent cannot validate the RunAs account. This fix resolves this issue.

  • Missing event monitor does not warn within the specified time range in SCOM 2012 R2 the first time after restart

    When you create a monitor for a missed event, the first alert takes twice the amount of time specified time in the monitor. This fix resolves the issue, and the alert is generated in the time specified.

  • SCOM cannot verify the User Account / Password expiration date if it is set by using Password Setting object

    Fine grained password policies are stored in a different container from the user object container in Active Directory. This fix resolves the problems in computing resultant set of policy (RSOP) from these containers for a user object.

  • SLO Detail report displays histogram incorrectly

    In some specific scenarios, the representation of the downtime graph is not displayed correctly. This fix resolves this kind of behavior.

  • APM support for IIS 10 and Windows Server 2016

    Support of IIS 10 on Windows Server 2016 is added for the APM feature in System Center 2012 R2 Operations Manager. An additional management pack Microsoft.SystemCenter.Apm.Web.IIS10.mp is required to enable this functionality. This management pack is located in %SystemDrive%\Program Files\System Center 2012 R2\Operations Manager\Server\Management Packs for Update Rollups alongside its dependencies after the installation of Update Rollup 9.

    Important Note One dependency is not included in Update Rollup 9 and should be downloaded separately:

    Microsoft.Windows.InternetInformationServices.2016.mp
  • APM Agent Modules workflow fails with Null Reference exception during workflow shutdown

    The APM Agent Modules workflow may fail, causing MonitoringHost.exe to crash during module shutdown. Additionally, you receive the following error message:

    STACK_TEXT:
    00000000`1b60f520 00007ff8`a5cc73d4
    microsoft_enterprisemanagement_modules_apm_agentmodules!Microsoft.EnterpriseManagement.Modules.Apm.AgentModules.RetryManager.Dispose+0xb400000000`1b60f5b0 00007ff8`a5cc717b microsoft_enterprisemanagement_modules_apm_agentmodules!Microsoft.EnterpriseManagement.Modules.Apm.AgentModules.RetryManager.Finalize+0x8b

    SYMBOL_NAME:
    microsoft_enterprisemanagement_modules_apm_agentmodules!Microsoft.EnterpriseManagement.Modules.Apm.AgentModules.RetryManager.Dispose+b4

    This fix resolves this issue.

  • AEM Data fills up SCOM Operational database and is never groomed out

    If you use SCOM’s Agentless Exception Monitoring to examine application crash data and report on it, the data never grooms out of the SCOM Operational database. The problem with this is that soon the SCOM environment will be overloaded with all the instances and relationships of the applications, error groups, and Windows-based computers, all which are hosted by the management servers. This fix resolves this issue. Additionally, the following management pack’s must be imported in the following order:

    • Microsoft.SystemCenter.ClientMonitoring.Library.mp
    • Microsoft.SystemCenter.DataWarehouse.Report.Library.mp
    • Microsoft.SystemCenter.ClientMonitoring.Views.Internal.mp
    • Microsoft.SystemCenter.ClientMonitoring.Internal.mp


  • The Downtime report from the Availability report does not handle the Business Hours settings

    In the Downtime report, the downtime table was not considering the business hours. This fix resolves this issue and business hours will be shown based on the specified business hour values.

    The updated RDL files are located in the following location:

    %SystemDrive%\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\Reporting

    To update the RDL file, follow these steps:

    1. Go to http://MachineName/Reports_INSTANCE1/Pages/Folder.aspxMachineName //Reporting Server.
    2. On this page, go to the folder to which you want to add the RDL file. In this case, click Microsoft.SystemCenter.DataWarehouse.Report.Library.
    3. Upload the new RDL files by clicking the upload button at the top. For more information, see https://msdn.microsoft.com/en-us/library/ms157332.aspx.

    Note As part of this fix, if you want to generate a Downtime report for a specific duration spanning more than one day, use the business hours option. To do this, set the business hours as 12:00AM & 11:59PM and set all the days as business days.

  • Adding a decimal sign in an SLT Collection Rule SLO in the ENU Console on a non-ENU OS does not work

    You run the System Center 2012 R2 Operations Manager Console in English on a computer that has the language settings configured to use a non-English (United States) language that uses a comma (,) as the decimal sign instead of a period (.). When you try to create Service Level Tracking, and you want to add a Collection Rule SLO, the value you enter as the threshold cannot be configured by using a decimal sign. This fix resolves the issue.

  • SCOM Agent issue while logging Operations Management Suite (OMS) communication failure

    An issue occurs when OMS communication failures are logged. This fix resolves this issue.

Issues that are fixed in the UNIX and Linux management packs

  • Discovery of Linux computers may fail for some system locales
    Using the Discovery Wizard or Windows PowerShell cmdlets to discover Linux computers may fail during the final Agent Verification step for computers that have some system locales, such as zh_TW.UTF-8. The scxadmin command that is used to restart the agent during the discovery process did not correctly handle Unicode text in the standard out-of-the-service command.
  • The UNIX/Linux Agent intermittently closes connections during TLS handshaking

    Symptoms include the following:
    • Failed heartbeats for UNIX or Linux computers, especially when the SSLv3 protocol is disabled on the Management Servers.
    • Schannel errors in the System log that contain text that resembles the following:

      A fatal error occurred while creating an SSL client credentials. The internal error state is 10013.
    • WS-Management errors in the event log that contain text that resembles the following:

      WSManFault
      Message = The server certificate on the destination computer (<UNIX/LINUX-COMPUTER-NAME) has the following errors:
      Encountered an internal error in the SSL library.
      Error number: -2147012721 0x80072F8F
      A security error occurred

UNIX and Linux management pack update

To install the updated monitoring packs and agents for UNIX and Linux operating systems, follow these steps:
  1. Apply Update Rollup 9 to your System Center 2012 R2 Operations Manager environment.
  2. Download the updated management packs for System Center 2012 R2 from the following Microsoft website:
  3. Install the management pack update package to extract the management pack files.
  4. Import the updated management pack for each version of Linux or UNIX that you are monitoring in your environment.
  5. 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.

How to obtain and install Update Rollup 9 for System Center 2012 R2 Operations Manager

Download information

Update packages for Operations Manager are available from Windows Update or by manual download from the Microsoft Update Catalog.

Windows Update
To obtain and install an update package from Windows Update, follow these steps on a computer that has an Operational Manager component installed:

  1. Click Start, and then click Control Panel.
  2. In Control Panel, double-click Windows Update.
  3. In the Windows Update window, click Check Online for updates from Microsoft Update.
  4. Click Important updates are available.
  5. Select the update rollup package, and then click OK.
  6. Click Install updates to install the update package.
Microsoft Update Catalog
This update package is available for manual download and installation from the Microsoft Update Catalog:

Installation instructions

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 this 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 this update rollup package immediately after you install the System Center 2012 R2 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 Web pages that have ViewState enabled after you upgrade from ASP.NET 1.1 to ASP.NET 2.0
  • The fix for the data warehouse BULK insert commands time out issue that is described in Update Rollup 1 for System Center 2012 R2 Operations Manager adds a registry key. This key can be used to set the time-out value (in seconds) for the data warehouse BULK insert commands. The following commands insert new data into the data warehouse.

    Note This key must be manually added on any management server on which you want to override the default BULK insert command time out.

    Registry location:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Data Warehouse

    DWORD name: Bulk Insert Command Time Out Seconds
    DWORD Value: 40

    Note Set this value in seconds. For example, for a 40-second time-out, set this value to 40.

Supported installation order
We recommend that you install this update rollup package by following these steps in this particular order:

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

    • Management server or servers
    • Gateway servers
    • Web console server role computers
    • Operations console role computers


  2. Apply SQL scripts (see installation information).
  3. Manually import the management packs.
  4. Apply the agent update to manually installed agents, or push the installation from the Pending view in the Operations console.


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

Operations Manager Update
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. Or download from the Microsoft Download Catalog.
  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 flowing Datawarehouse SQL script on Datawarehouse Server against OperationsManagerDW database:

    UR_Datawarehouse.sql


    Note This script is located in the following path:

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

  4. Execute the following Database sql script on the Database server against the OperationsManagerDB database:

    Update_rollup_mom_db.sql

  5. Import the following management packs:
    • Microsoft.SystemCenter.TFSWISynchronization.mpb, which has the following dependency:
      • Microsoft.SystemCenter.AlertAttachment.mpb, which should be installed from the System Center Operations Manager 2012 R2 media.
      • Microsoft.SystemCenter.Visualization.Library.mpb
    • Microsoft.SystemCenter.Visualization.Component.Library.mpb
    • Microsoft.SystemCenter.Visualization.Library.mpb
    • Microsoft.SystemCenter.Advisor.mpb
    • Microsoft.SystemCenter.Advisor.Internal.mpb
    • Microsoft.SystemCenter.2007.mp
    • Microsoft.SystemCenter.Advisor.Resources.LANGUAGECODE_3LTR.mpb
    • Microsoft.SystemCenter.SyntheticTransactions.Library.mp
    • Microsoft.SystemCenter.OperationsManager.Library.mp
    • Microsoft.SystemCenter.OperationsManager.Internal.mp
    • Microsoft.SystemCenter.Apm.Web.IIS10.mp which has the following dependency:
    • Microsoft.SystemCenter.ClientMonitoring.Internal.mp which has the following dependency:
      • Microsoft.SystemCenter.ClientMonitoring.Library.mp
      • Microsoft.SystemCenter.DataWarehouse.Report.Library.mp
      • Microsoft.SystemCenter.ClientMonitoring.Views.Internal.mp

For information about how to import a management pack from a disk, see the How to Import an Operations Manager Management Pack topic on the Microsoft TechNet website.

Note Management packs are included in the Server component updates in the following path:

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


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

  1. Apply Update Rollup 7 to your System Center 2012 R2 Operations Manager environment.
  2. Download the updated management packs for System Center 2012 R2 from the following Microsoft website:


  3. Install the management pack update package to extract the management pack files.
  4. Import the updated management pack for each version of Linux or UNIX that you are monitoring in your environment.
  5. 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.

Uninstall information

To uninstall an update, run the following command:

msiexec /uninstall PatchCodeGuid /package RTMProductCodeGuid


Note The PatchCodeGuid placeholder represents one of the following GUIDs.

PatchGuidsComponentArchitectureLanguage
DE2A13BC-9276-4FF2-B4B5-B5018749960CAgentamd64en
D59CFD85-015D-44EE-8B63-C6291ACD91ADConsoleamd64en
F494E851-24E1-406C-A195-C8E6CB68CD75Webconsoleamd64en
470A897B-E3F5-4FF2-812D-DD4A2DFF194CGatewayamd64en
995F7810-86E7-4F27-A943-3EB7468DA48AServeramd64en
AE18A9A8-B4F1-4791-9219-ADBDB27C4562Agentx86en
F5670042-EA03-4C11-9967-47733C5E148BConsolex86en
{48142C15-D71E-4B30-95D1-6BA396D3D0ED}Consoleamd64cn
{9E5100EB-858B-4826-89B2-4EDC5119AED7}Webconsoleamd64cn
{A2BDEC38-4DCD-41C8-8F2C-6AE3595B57B0}Consolex86cn
{22EFBA98-C5F4-4F0F-8761-E33A58C53B75}Consoleamd64cs
{93FED2F7-A713-4946-A23B-55C99E0B2FD7}Webconsoleamd64cs
{8D72BCC5-8292-43E6-BA40-B64FD01FD88F}Consolex86cs
{9C15FBC2-B642-451A-931F-FA45C473536D}Consoleamd64de
{69CD2B38-11FC-4A04-ACAA-DD050D2C5C48}Webconsoleamd64de
{DAA5F79F-679B-48B0-B914-30938836878A}Consolex86de
{31CBEB5B-B09B-4E49-AA96-98690B57F2AA}Consoleamd64es
{A6E95931-CB79-4826-BF99-3C031415DB93}Webconsoleamd64es
{B0B67664-BFB5-4F28-9089-466EFA80C950}Consolex86es
{55BA0F87-C436-4320-878E-2AC2F89190C9}Consoleamd64fr
{E6A1CCEC-C531-455F-83B0-615AD72B39B1}Webconsoleamd64fr
{0853D0ED-4318-415C-BFB1-EBF196C4730C}Consolex86fr
{C543A962-6868-4E61-B5B7-0A4FEE26F3BA}Consoleamd64hu
{B6A3FB85-A81E-496C-9365-04513DF94DD6}Webconsoleamd64hu
{8873A139-7A0E-4620-916F-4A0F8EBBD3E5}Consolex86hu
{86A02228-4788-4F09-B5AB-D0D8ED9C88AC}Consoleamd64it
{3165FD51-F9F1-4507-9349-C856E5A54C4D}Webconsoleamd64it
{1167DBF9-59E3-4354-930C-2C6742B6E23E}Consolex86it
{4FB10F73-8506-42BB-83BA-62DAD071717E}Consoleamd64ja
{949970F2-A886-4F4C-A746-4BCD73B9E6A0}Webconsoleamd64ja
{E46A2CB9-60F4-4126-B832-3E7DE1B070BB}Consolex86ja
{7BA70AE3-8460-4895-B609-A43103B9506E}Consoleamd64ko
{EADCD58E-720A-4D6E-9DDD-790A3EED0986}Webconsoleamd64ko
{BF69C0C0-3D60-4FEC-980D-DDE58C8CA65A}Consolex86ko
{CC0F3871-90A9-4F13-A624-5E85158CF60E}Consoleamd64nl
{B5EA340D-8B33-4CF9-BB7B-CB3FEF95A803}Webconsoleamd64nl
{9EFED365-ED5A-4F58-AE78-D9FC09E3FD98}Consolex86nl
{46367369-977B-4726-A454-5A0B85376B4E}Consoleamd64pl
{F3DF6838-64E5-462A-9F52-BA5661F3D70A}Webconsoleamd64pl
{CC7676B8-E538-4487-A058-CA23290C0487}Consolex86pl
{93FA2B7C-2A70-4F09-A2CA-CE279F18BFF6}Consoleamd64pt-br
{3883A60C-1677-4F7C-BE20-798480A23CE5}Webconsoleamd64pt-br
{B096DFAC-D6D2-4C26-B7CC-11B75B75A32C}Consolex86pt-br
{FAEA0565-61C6-481F-93A6-A400F0C6BD18}Consoleamd64pt-pt
{F24F8B9B-3055-4A1F-BB15-EE2BBE02FAFC}Webconsoleamd64pt-pt
{3DD40F66-7BE3-464C-B710-E140BE6D29C2}Consolex86pt-pt
{28405BCF-8D4E-46A2-9614-567C3E6A94EE}Consoleamd64ru
{409C007F-8480-4502-8CF7-72539C7F0926}Webconsoleamd64ru
{EDBF0866-B378-4FBB-AE63-6B3C4BA42CCC}Consolex86ru
{837515BA-275A-425C-8047-B09D96ABEB3C}Consoleamd64sv
{7DDBA84C-0653-4A0A-B1EB-F1DA3BC317D0}Webconsoleamd64sv
{E5E5DA27-978D-402E-88D4-69AA50102EB7}Consolex86sv
{B81E6F83-8E89-42DB-8850-238595AE09BF}Consoleamd64tr
{4D1C7853-ED9C-417A-87F8-E14DDD19CBB9}Webconsoleamd64tr
{6E6BC4E1-8C2E-44AC-9AC7-A59AFEBFBCCC}Consolex86tr
{4FC204CE-4E73-4DAF-A131-9BC4CFC2AD47}Consoleamd64tw
{45EBE016-0E6B-40D0-8D46-18D3E972D124}Webconsoleamd64tw
{7D8F2380-F009-450C-8DA2-C6E25F209E01}Consolex86tw
{4FC204CE-4E73-4DAF-A131-9BC4CFC2AD47}Consoleamd64tw
{45EBE016-0E6B-40D0-8D46-18D3E972D124}Webconsoleamd64tw
{7D8F2380-F009-450C-8DA2-C6E25F209E01}Consolex86tw
{3DEA0831-63C4-4A91-9C56-6D4D14D8E499}Consoleamd64zh-hk
{E63052B7-EF60-411F-ACE9-13160495655A}Webconsoleamd64zh-hk
{1AE2B0B4-0AAC-4776-A5C5-95C1F9FDCBD4}Consolex86zh-hk


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

ComponentRTMProductCodeGuid
Server{C92727BE-BD12-4140-96A6-276BA4F60AC1}
Console (AMD64){041C3416-87CE-4B02-918E-6FDC95F241D3}
Console (x86){175B7A24-E94B-46E5-A0FD-06B78AC82D17}
WebConsole (AMD64){B9853D74-E2A7-446C-851D-5B5374671D0B}
Gateway{1D02271D-B7F5-48E8-9050-7F28D2B254BB}
SCX-ACS (AMD64){46B40E96-9631-11E2-8D42-2CE76188709B}
SCX-ACS (x86){46B40E96-9631-11E2-8D42-2CE76188709B}
Agent (AMD64){786970C5-E6F6-4A41-B238-AE25D4B91EEA}
Agent (x86){B4A63055-7BB1-439E-862C-6844CB4897DA}

Files updated in this update rollup

The following is a list of files that have changed in this Update Rollup. If you do not have all previous update rollups installed, files other than those listed here may also be updated. For a complete list of files that are updated, refer to the "Files Updated in this Update Rollup" section of all update rollups that were released after your current update rollup.

Files that are updatedVersionSize
PerfMon.dll7.1.10268.01.94 MB
PerfMon64.dll7.1.10268.03.18 MB
Microsoft.EnterpriseManagement.DataAccessService.OperationsManager.dll7.1.10226.1118571 KB
PerfCounterMonitor.dll7.1.10268.01.14 MB
HealthService.dll7.1.10268.03.16 MB
Microsoft.EnterpriseManagement.UI.Authoring.dll7.1.10226.11779.45 MB
MOMModules.dll7.1.10268.02.50 MB
Microsoft.SystemCenter.Apm.Infrastructure.mpb7.1.10226.1177980 KB
Microsoft.SystemCenter.Apm.Library.mpb7.1.10226.1177780 KB
Microsoft.SystemCenter.Apm.Library.Resources.(LANGUAGECODE_3LTR).mpb7.1.10226.1139156 KB
Microsoft.SystemCenter.ClientMonitoring.Library.mp7.1.10226.117797 KB
Microsoft.SystemCenter.DataWarehouse.Report.Library.mp7.1.10226.1177713 KB
Microsoft.SystemCenter.ClientMonitoring.Views.Internal.mp7.1.10226.1177149 KB
Microsoft.SystemCenter.ClientMonitoring.Internal.mp7.1.10226.117753 KB
UR_Datawarehouse.sql7.1.10226.1177147 KB
Microsoft.SystemCenter.DataWarehouse.Report.Downtime.rdl7.1.10226.1177128 KB
Microsoft.SystemCenter.DataWarehouse.Report.Availability.rdl7.1.10226.1177193 KB
Microsoft.SystemCenter.DataWarehouse.Report.AvailabilityMonitor.rdl7.1.10226.1177290 KB
Microsoft.SystemCenter.DataWarehouse.Report.AvailabilityTime.rdl7.1.10226.1177150 KB
OpsMgrTraceTMF.cab7.1.10226.11772.69 MB
Microsoft.EnterpriseManagement.OperationsManager.Apm.Instrumentation.dll7.1.10268.0373 KB

Files that are updated in the UNIX and Linux management packs update

The following is a list of files that have changed in this update rollup. If you do not have all previous update rollups installed, files other than those listed here may also be updated. For a complete list of files that are updated, refer to the "Files updated in this update rollup" section of all update rollups that were released after your current update rollup.
Files that are changedFile sizeVersion
Microsoft.ACS.Linux.RHEL.7.mp20 KB7.5.1050.0
Microsoft.AIX.5.3.mpb15,869KB7.5.1050.0
Microsoft.AIX.6.1.mpb15,876KB7.5.1050.0
Microsoft.AIX.7.mpb14,872KB7.5.1050.0
Microsoft.AIX.Library.mp31KB7.5.1050.0
Microsoft.HPUX.11iv2.mpb19,998KB7.5.1050.0
Microsoft.HPUX.11iv3.mpb19,908KB7.5.1050.0
Microsoft.HPUX.Library.mp31KB7.5.1050.0
Microsoft.Linux.Library.mp31KB7.5.1050.0
Microsoft.Linux.RedHat.Library.mp15KB7.5.1050.0
Microsoft.Linux.RHEL.4.mpb7,905KB7.5.1050.0
Microsoft.Linux.RHEL.5.mpb7,819KB7.5.1050.0
Microsoft.Linux.RHEL.6.mpb7,394KB7.5.1050.0
Microsoft.Linux.RHEL.7.mpb2,333KB7.5.1050.0
Microsoft.Linux.SLES.10.mpb7,178KB7.5.1050.0
Microsoft.Linux.SLES.11.mpb4,713KB7.5.1050.0
Microsoft.Linux.SLES.12.mpb1,845KB7.5.1050.0
Microsoft.Linux.SLES.9.mpb3,801KB7.5.1050.0
Microsoft.Linux.SUSE.Library.mp15KB7.5.1050.0
Microsoft.Linux.Universal.Library.mp15KB7.5.1050.0
Microsoft.Linux.Universal.Monitoring.mp83KB7.5.1050.0
Microsoft.Linux.UniversalD.1.mpb14,127KB7.5.1050.0
Microsoft.Linux.UniversalR.1.mpb12,654KB7.5.1050.0
Microsoft.Solaris.10.mpb26,957KB7.5.1050.0
Microsoft.Solaris.11.mpb26,631KB7.5.1050.0
Microsoft.Solaris.9.mpb13,746KB7.5.1050.0
Microsoft.Solaris.Library.mp22KB7.5.1050.0
Microsoft.Unix.Library.mp83KB7.5.1050.0
Microsoft.Unix.LogFile.Library.mpb87KB7.5.1050.0
Microsoft.Unix.Process.Library.mpb98KB7.5.1050.0
Microsoft.Unix.ShellCommand.Library.mpb68KB7.5.1050.0
Properties

Article ID: 3129774 - Last Review: 02/29/2016 15:25:00 - Revision: 5.0

Microsoft System Center 2012 R2 Operations Manager, Microsoft System Center 2012 R2

  • kbqfe kbsurveynew kbfix kbexpertiseinter atdownload KB3129774
Feedback