Symptoms

Issues that Update Rollup 4 fixes are as follows.

Operations Manager (KB2880799)

Issue 1

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

Symptom

You receive the following error message:

The PowerShell script failed with below exception

System.Management.Automation.CmdletInvocationException: AuthorizationManager check failed.

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:

Microsoft.EnterpriseManagement.Presentation.DataAccess.DataAccessDataNotFoundException: Exception reading objects ---> Microsoft.EnterpriseManagement.Common.UnknownDatabaseException: The query processor ran out of internal resources and could not produce a query plan.


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



Xplat Update

Operations Manager - UNIX and Linux Monitoring

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:

Failed during SSH discovery. Exit code: 2
Standard Output:
Standard Error: line 1: syntax error near unexpected token `('


Operations Manager - UNIX and Linux Monitoring (Management Pack Update)

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:

errno = 24 (Too many open files)


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):

Warning [scx.core.common.pal.system.disk.diskdepend:418:29352:139684846989056] Did not find key 'cgroup' in proc_disk_stats map, device name was 'cgroup'.


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.

New support in this update

  • Debian GNU/Linux 7

  • JEE App servers:

    • IBM WebSphere 8.0

    • IBM Websphere 8.5

    • Oracle Weblogic 12c

Note The JEE App server additions are a separate Management Pack release. However, they depend on updates to the UNIX/Linux agent.

Resolution

Installation instructions for Operations Manager

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.

Component

RTMProductCodeGuid

Server

{8070C91C-7D7C-4DAD-88B1-0966EEA9A8FE}

Console (AMD64)

{5142AB0B-73E3-4AD3-9D0F-65B3D9026769}

Console (x86)

{358C8AF0-25BB-425A-A4E6-7ADE54ED4736}

Reporting

{A2D27C0E-181D-4955-B95D-D3FB651E6AF7}

WebConsole (AMD64)

{5ED945BA-2BDD-4567-804E-8D3D2DB5CC9B}

ACS

{3E7464F7-A468-44E1-9A95-58349E022EAE}

Agent (AMD64)

{8B21425D-02F3-4B80-88CE-8F79B320D330}

Agent (x86)

{387306D9-78CE-4E0E-B952-28A50CC8B3EE}

Agent (IA-64)

{F3DDB021-89BC-464F-9107-69E2547D08FD}

Gateway

{80C2A57A-4193-4800-AA27-CD79553FE9DF}

SCX-ACS (AMD64)

{B30F4F71-2AF3-4542-855B-E1C7A31AC9A5}

SCX-ACS (x86)

{B30F4F71-2AF3-4542-855B-E1C7A31AC9A5}


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

PatchCode

Component

CPU

Locale

{034104B1-6F4C-4FCA-91C8-60F322F9E84F}

Console

AMD64

CN

{6A8A2680-D5D9-4864-BCC1-8D236FC61AF0}

WebConsole

AMD64

CN

{32817D23-A568-4152-93EF-A5EB41E026E2}

ACS

AMD64

CN

{477432D3-C16D-46E6-BBFA-2F8635D16157}

Console

x86

CN

{0086237E-A8E1-4CC9-99B9-9DE9E4DA7012}

WebConsole

AMD64

CS

{CD0BB32D-6696-4F3F-AB24-0CB092CA3576}

Console

AMD64

CS

{21944E70-98C3-4750-B421-119845FC4D87}

ACS

AMD64

CS

{8D080B73-46A0-4347-BD90-3A85161F2149}

Console

x86

CS

{6D82B7AE-D695-4306-AF61-2FFAC18B9DB3}

Console

AMD64

DE

{CCB1EC00-08B4-4C8C-8EBD-A8806C98466E}

WebConsole

AMD64

DE

{36488258-BC00-4386-AF72-B51C36D51EF1}

ACS

AMD64

DE

{1C5BDCD7-42B4-4220-AFA8-AA022E405C4A}

Console

x86

DE

{754ECA21-DEFB-4263-9742-F26511844D61}

Agent

AMD64

EN

{C985A2D3-43F1-4D43-8D52-776D0A57C8F4}

Server

AMD64

EN

{A942A1C3-CA7F-4FA0-8A9A-955C45D4FA39}

Gateway

AMD64

EN

{2A33D7B6-B84B-4938-BB84-3C39998CDD6C}

WebConsole

AMD64

EN

{7E136E85-340E-4246-90E5-D511FE1D5E00}

Console

AMD64

EN

{2DB5680B-4CEC-4858-B2E5-47AC0609E888}

ACS

AMD64

EN

{22E3B260-7634-4E0E-9C3E-867C833F4958}

Agent

IA-64

EN

{C29540CB-99D9-4420-A786-5FFE1B2437A9}

Agent

x86

EN

{C0718D35-0C6F-4BA4-8058-73DBC18C8982}

Console

x86

EN

{FD0869E4-4456-45AA-B818-6493AAA8C60A}

Console

AMD64

ES

{A36F8BBC-C6C7-43A0-84DC-AEDE30211D8F}

WebConsole

AMD64

ES

{8CB2B542-C54A-4EBB-89EF-EC43CBB126B5}

ACS

AMD64

ES

{5334A969-2545-4A68-AE81-A34149457574}

Console

x86

ES

{72853588-ED64-469C-BE3E-15501411307C}

Console

AMD64

FR

{AE924254-3F55-4BEA-B3FB-816EB66D25B2}

WebConsole

AMD64

FR

{ED1E4C82-C783-4719-A229-8795C160CB8B}

ACS

AMD64

FR

{0243380F-4E96-4BCD-BFA0-59B494AD5094}

Console

x86

FR

{FE813D41-3E8C-4504-AEFF-34F37421F1C4}

Console

AMD64

HU

{D7C1D332-53FF-4BAD-91B6-E228763A6EC5}

WebConsole

AMD64

HU

{892D9FED-7721-4D32-9D54-0037B0DFA584}

ACS

AMD64

HU

{F8FC53C6-C11F-4D4B-A50C-B7EC816FFCE0}

Console

x86

HU

{E2B1F861-0FFA-4F0B-B65A-E0A2A9D909F4}

Console

AMD64

IT

{1FC6251D-6B20-4257-B309-B75B9C22A864}

WebConsole

AMD64

IT

{B8E7A45B-4A75-4855-8E3C-F4770DC0F802}

ACS

AMD64

IT

{40D08E18-1EAA-4843-83E0-E80205D9FCA4}

Console

x86

IT

{E2B1F861-0FFA-4F0B-B65A-E0A2A9D909F4}

Console

AMD64

JA

{1FC6251D-6B20-4257-B309-B75B9C22A864}

WebConsole

AMD64

JA

{B8E7A45B-4A75-4855-8E3C-F4770DC0F802}

ACS

AMD64

JA

{40D08E18-1EAA-4843-83E0-E80205D9FCA4}

Console

x86

JA

{0B8E3BFE-96B7-4F6C-8E98-A8DC096025D2}

Console

AMD64

KO

{60EDCAB0-DD12-4C67-9619-0F270856EF81}

WebConsole

AMD64

KO

{3A43E1DE-D7E7-4B35-A222-6B0002BD70A7}

ACS

AMD64

KO

{027397E8-7CC9-4E9F-B5C6-E318DD27F1EA}

Console

x86

KO

{4537494D-6BE3-4EE1-8A4B-6100066E548B}

Console

AMD64

NL

{394F384C-B779-4807-BEB2-AAF49D7B8F36}

WebConsole

AMD64

NL

{99A889F5-2688-4647-B151-EC0B648F12AB}

ACS

AMD64

NL

{8FA80DCD-2158-4CC3-AB46-DF435B32F01E}

Console

x86

NL

{F556EFB2-98B2-451C-ACE1-A5E5998461CF}

Console

AMD64

PL

{2465880F-EAFF-41C6-AC37-8BC93AAA3827}

WebConsole

AMD64

PL

{99837B33-23C7-45BA-9870-CA75BFB4536C}

ACS

AMD64

PL

{A7803664-B1EC-4770-BC1F-D7FFB7D361E1}

Console

x86

PL

{E47642A9-DC0A-4840-9EAD-8B4602E80629}

Console

AMD64

PT-BR

{2B3B2BEB-282A-4F70-9180-7CB533BD4FD8}

WebConsole

AMD64

PT-BR

{CDC3A048-519B-435D-A95D-8387A32BA1F6}

ACS

AMD64

PT-BR

{A5DC8E58-1E8C-4B18-9A42-24842A9A1316}

Console

x86

PT-BR

{AC75A42E-FDB8-44AB-AA80-12DF2778A561}

Console

AMD64

PT-PT

{4C4BF401-C8EE-4462-A3F7-C6C6757B06BE}

WebConsole

AMD64

PT-PT

{1655217C-0F03-4393-8D83-0AC33BC018F0}

ACS

AMD64

PT-PT

{FA7650B8-34F6-4F60-99D5-FF9ABD1B5CBA}

Console

x86

PT-PT

{B7597EE8-A50D-40AC-B576-52198F891C65}

ACS

AMD64

RU

{ACC0CBC1-8AF5-413A-979E-23279696AFED}

Console

AMD64

RU

{CB1B15A5-608A-4C85-95D0-0D68AE70FF17}

WebConsole

AMD64

RU

{F1447444-434E-4B96-91BB-608C3C19B9EF}

Console

x86

RU

{A531456A-89A2-44D7-BD61-D8720DC18CA8}

ACS

AMD64

SV

{6C4B4125-FE01-415C-B048-126992171F5C}

Console

AMD64

SV

{91009F7F-D113-475E-98B6-0C9C0DAAE92A}

WebConsole

AMD64

SV

{561E553A-3ACE-4C18-8EA2-39E4EFB7FCF5}

Console

x86

SV

{29088EE4-7009-407E-8D6E-7B85EC61C9A6}

Console

AMD64

TR

{72B34BB4-A9B8-4D5C-BC69-D95D4CD85FE3}

WebConsole

AMD64

TR

{9FB57BBE-C9A6-4063-A8A9-C3616CCF0854}

ACS

AMD64

TR

{9E319A80-398B-48CC-B1DF-620F1CED9920}

Console

x86

TR

{5A6274BF-5520-4833-AA19-4962EFC6A306}

Console

AMD64

TW

{07E7A281-2EC3-4310-921D-A7E7ECAFC382}

WebConsole

AMD64

TW

{3A3652DA-D8A1-4280-8815-AF6B769CB704}

ACS

AMD64

TW

{DE888A70-8C38-4D5C-9A73-12E040DF4D01}

Console

x86

TW

{0F4EBAD6-8AC9-403B-9FFD-E1E5FD4A2335}

Console

AMD64

ZH-HK

{87F65387-6617-4878-9550-B65FF18A6921}

WebConsole

AMD64

ZH-HK

{5489231A-D862-4143-B88A-A08B08BB197E}

ACS

AMD64

ZH-HK

{5A94AEC9-D41E-4EB4-945A-FC137A9B50EA}

Console

x86

ZH-HK

File information



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

Operations Manager Update (KB2880799)

Files that are changed

File Size

Version

AdtPerf.dll

78,552 bytes

7.0.9538.1084

AdtServer.exe

101,080 bytes

7.0.9538.1084

AdtSrvDll.dll

477,912 bytes

7.0.9538.1084

AdvisorConnector.dll

334,848 bytes

7.0.9538.1084

Aggregation.dll

300,760 bytes

7.0.9538.1084

AggregationCommon.dll

64,216 bytes

7.0.9538.1084

AntiXssLibrary.dll

134,872 bytes

7.0.9538.1084

ARCore.dll

708,824 bytes

7.0.9538.1084

ClientEventHandlerV56.dll

202,456 bytes

7.0.9538.1084

ClientShared.dll

206,336 bytes

7.0.9538.1084

CLRXMonitorHandlerV4.dll

372,952 bytes

7.0.9538.1084

CLRXMonitorHandlerV51.dll

136,408 bytes

7.0.9538.1084

ConnectorBridge_x64.dll

78,552 bytes

7.0.9538.1084

CSMAMonitorHandlerV5.6.dll

156,376 bytes

7.0.9538.1084

CSMPMonitorHandlerV5.6.dll

267,992 bytes

7.0.9538.1084

CSMXMonitorHandlerV5.dll

221,912 bytes

7.0.9538.1084

EventCommon.dll

363,224 bytes

7.0.9538.1084

HandlerBase.dll

293,592 bytes

7.0.9538.1084

HandlerBaseV5.dll

39,640 bytes

7.0.9538.1084

HealthServiceRuntime.dll

319,192 bytes

7.0.9538.1084

IDatabaseInfoProvider.dll

37,080 bytes

7.0.9538.1084

Interop.Shell32.dll

56,024 bytes

7.0.9538.1084

ISEManager.dll

10,968 bytes

7.0.9538.1084

ISEMHandler.dll

14,552 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.Management.DataProviders.dll

591,064 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.Modules.Apm.AgentModules.dll

91,352 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.Modules.Apm.AlertAttachment.Modules.dll

74,456 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.Modules.Apm.AlertAttachment.ServerModules.dll

32,472 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.Modules.Apm.ApplicationCompatibilityCheck.dll

48,344 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.Modules.Apm.IntelliTraceConvertor.Modules.dll

39,128 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.Modules.Apm.IntelliTraceProfiling.Modules.dll

29,912 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.Modules.Apm.LibraryConfigManager.dll

241,880 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.Modules.Apm.ServerDiscovery.dll

248,536 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.Modules.Apm.ServerModules.DataTransfer.dll

30,936 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.Modules.Apm.ServerModules.DataTransferInterfaces.dll

21,208 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.Modules.Apm.ServerModules.dll

55,512 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.Modules.PowerShell.dll

88,792 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.Monitoring.Components.dll

1,135,832 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.Monitoring.Console.exe

4,666,584 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.Monitoring.DataProviders.dll

415,960 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.OperationsManager.Apm.Common.dll

330,968 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.OperationsManager.Apm.DataClasses.dll

158,424 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.OperationsManager.dll

1,026,776 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.OperationsManager.MonitoringViews.dll

1,810,136 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.Presentation.Controls.dll

1,772,760 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.Presentation.Core.dll

496,856 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.Presentation.DataProviders.Library.dll

108,248 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.Presentation.WebConsole.dll

98,520 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.RuntimeService.dll

395,992 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.UI.Administration.dll

4,467,416 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.UI.Authoring.dll

9,906,904 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.UI.ConsoleFramework.dll

2,809,560 bytes

7.0.9538.1084

Microsoft.ManagementServices.AppDiagnostics.IntelliTraceConvertor.dll

70,360 bytes

7.0.9538.1084

Microsoft.EnterpriseManagement.DataAccessLayer.dll

7.5.2905.145

Microsoft.Mom.Modules.ClientMonitoring.dll

457,432 bytes

7.0.9538.1084

Microsoft.Mom.ServiceCommon.dll

27,864 bytes

7.0.9538.1084

Microsoft.MOM.UI.Components.dll

6,142,680 bytes

7.0.9538.1084

Microsoft.SystemCenter.Advisor.Internal.dll

65,240 bytes

7.0.9538.1084

Microsoft.SystemCenter.Advisor.Internal.mpb

143,360 bytes

Not Applicable

Microsoft.SystemCenter.AlertAttachment.mpb

114,688 bytes

Not Applicable

Microsoft.SystemCenter.Apm.Infrastructure.Monitoring.mp

60,120 bytes

Not Applicable

Microsoft.SystemCenter.Apm.Infrastructure.mpb

933,888 bytes

Not Applicable

Microsoft.SystemCenter.Apm.Library.mpb

831,488 bytes

Not Applicable

Microsoft.SystemCenter.DataWarehouse.Report.Library.mp

723,672 bytes

Not Applicable

Microsoft.SystemCenter.DataWarehouse.Reports.mp

56,024 bytes

Not Applicable

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

211,672 bytes

Not Applicable

Microsoft.SystemCenter.Image.Library.mp

1,125,080 bytes

Not Applicable

Microsoft.SystemCenter.IntelliTraceProfiling.mpb

131,072 bytes

Not Applicable

Microsoft.SystemCenter.OperationsManagerV10.Commands.dll

647,384 bytes

7.0.9538.1084

Microsoft.SystemCenter.Visualization.Library.mpb

126,976 bytes

Not Applicable

MOMAdvisorMsgs.dll

31,448 bytes

7.0.9538.1084

MOMAgentInstaller.exe

365,272 bytes

7.0.9538.1084

MOMAgentInstallerPS.dll

52,952 bytes

7.0.9538.1084

MomIISModules.dll

571,096 bytes

7.0.9538.1084

MOMModules.dll

2,610,904 bytes

7.0.9538.1084

MOMModules2.dll

248,536 bytes

7.0.9538.1084

MOMPerfSnapshotHelper.exe

50,392 bytes

7.0.9538.1084

MOMPerfSnapshotHelperProxy.dll

18,648 bytes

7.0.9538.1084

OMVersion.dll

8,920 bytes

7.0.9538.1084

PCounterHandlerV3.5.dll

50,392 bytes

7.0.9538.1084

PMonitorHandlerV4.dll

252,632 bytes

7.0.9538.1084

PMonitorHandlerV51.dll

146,136 bytes

7.0.9538.1084

SEMHandlerManager.dll

28,888 bytes

7.0.9538.1084

silverlightclientconfiguration.exe

3,598,552 bytes

7.0.9538.1084

TraceFmtSM.exe

447,192 bytes

7.0.9538.1084

TraceLogSM.exe

107,224 bytes

7.0.9538.1084

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.

Files that are changed

File size

Version

GetOSVersion.sh

11 KB

Not applicable

MOMSCXLogModules.dll

286KB

7.4.4317.0

Microsoft.AIX.5.3.mpb

16709KB

7.4.4334.0

Microsoft.AIX.6.1.mpb

16709KB

7.4.4334.0

Microsoft.AIX.7.mpb

15919KB

7.4.4334.0

Microsoft.AIX.Library.mp

31KB

7.4.4334.0

Microsoft.HPUX.11iv2.mpb

39310KB

7.4.4334.0

Microsoft.HPUX.11iv3.mpb

39374KB

7.4.4334.0

Microsoft.HPUX.Library.mp

31KB

7.4.4334.0

Microsoft.Linux.Library.mp

31KB

7.4.4334.0

Microsoft.Linux.RedHat.Library.mp

15KB

7.4.4334.0

Microsoft.Linux.RHEL.4.mpb

35334KB

7.4.4334.0

Microsoft.Linux.RHEL.5.mpb

34862KB

7.4.4334.0

Microsoft.Linux.RHEL.6.mpb

33057KB

7.4.4334.0

Microsoft.Linux.Universal.Library.mp

16KB

7.4.4334.0

Microsoft.Linux.Universal.Monitoring.mp

83KB

7.4.4334.0

Microsoft.Linux.UniversalD.1.mpb

64736KB

7.4.4334.0

Microsoft.Linux.UniversalR.1.mpb

67680KB

7.4.4334.0

Microsoft.SLES.10.mpb

33692KB

7.4.4334.0

Microsoft.SLES.11.mpb

22977KB

7.4.4334.0

Microsoft.SLES.9.mpb

16346KB

7.4.4334.0

Microsoft.SUSE.Library.mp

15KB

7.4.4334.0

Microsoft.Solaris.10.mpb

16189KB

7.4.4334.0

Microsoft.Solaris.11.mpb

17225KB

7.4.4334.0

Microsoft.Solaris.9.mpb

8516KB

7.4.4334.0

Microsoft.Solaris.Library.mp

22KB

7.4.4334.0

Microsoft.Unix.ConsoleLibrary.mpb

23KB

7.4.4334.0

Microsoft.Unix.Library.mp

83KB

7.4.4334.0

Microsoft.Unix.LogFile.Library.mpb

86KB

7.4.4334.0

Microsoft.Unix.Process.Library.mpb

98KB

7.4.4334.0

Microsoft.Unix.ShellCommand.Library.mpb

68KB

7.4.4334.0

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×