Update Rollup 12 for System Center 2012 R2 Operations Manager

Introduction

This article describes the issues that are fixed in Update Rollup 12 for Microsoft System Center 2012 R2 Operations Manager. It also contains the installation instructions for this update.

Issues that are fixed in Operations Manager

  • When you try to upgrade System Center 2012 R2 Operations Manager Reporting Server to System Center 2016 Operations Manager reporting server, the upgrade fails for the following configuration:
    • Server A is configured as System Center 2012 R2 Operations Manager including Management Server.
    • Server B is configured as System Center 2012 R2 Operations Manager, including Operations Manager Database (OpsMgrDB), Operations Manager Data Warehouse (OpsMgrDW) and Operations Manager Reporting Server.
  • Recovery tasks on "Computer Not Reachable" messages in the System Center Operations Manager Monitor generate failed logons for System Center Operations Manager Agents that are not part of the same domain as the Management Groups.
  • When a Management Server is removed from the All Management Servers Resource Pool, the monitoring host process do not update the Type Space Cache.
  • SHA1 is deprecated for the System Center 2012 R2 Operations Manager Agent and SHA2 is now supported.
  • Because of incorrect computations of configuration and overrides, some managed entities go into an unmonitored state. This behavior is accompanied by event 1215 errors that are logged in the Operations Manager log.
  • IntelliTrace Profiling workflows fail on certain Windows operating system versions. The workflow cannot resolve Shell32 interface issues correctly.
  • There is a character limitation of 50 characters on the custom fields in the notification subscription criteria. This update increases the size of the limitation to 255 characters.
  • You cannot add Windows Client computers for Operational Insights (OMS) monitoring. This update fixes the OMS Managed Computers wizard in the System Center Operations Manager Administration pane to let you search or add Windows Client computers.
  • When you use the Unix Process Monitoring Template wizard to add a new template to the monitor processes on UNIX servers, the monitored data is not inserted into the database. This issue occurs until the Monitoring Host is restarted. Additionally, the following is logged in the Operations Manager log file:


  • Additionally, you may receive the following exception, which causes this issue to occur:

New Linux operating systems supported

  • RHEL 7 on Power8 is now supported in System Center2012 R2 Operations Manager

Issues that are fixed in the UNIX and Linux management packs

  • SHA1 is deprecated and SHA2 is now supported on the management server that's used to sign the UNIX/Linux Operations Manager i (OMi) certificate.
  • OMi start attempts fail on all FIPS-enabled UNIX/Linux systems. This fix updates the agents to support FIPS-enabled systems.
  • The Average Physical disk sec/transfer performance counters are not displayed for Hewlett Packard systems.
  • OMi displays incorrect memory information for Solaris 10 systems.
  • The Network Adapter Performance counter is not displayed for SLES 12 x64 platforms in the console.
  • You can't discover file systems on HPUX 11.31 IA-64 computers that have more than 128 disks. Previously, only 128 VGs were supported. This update extends support to 256 VGs.
  • Deep monitoring can't be started successfully for some Jboss applications because the discovery of the Jboss application server sets the DiskPath for the Jboss server incorrect. Deep monitoring is not started in JBoss stand-alone mode when a nondefault configuration is used. This update provides additional support for JBoss stand-alone mode.

How to obtain Update Rollup 12 for System Center 2012 R2 Operations Manager

Download information

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

Microsoft Update

To obtain and install an update package from Microsoft Update, follow these steps on a computer that has an Operations 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.

Manual download of the update packages

Go to the following website to manually download the update packages from the Microsoft Update Catalog:

Download icon
 Download the Operations Manager update package now.

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:
    <machineKeyvalidationKey="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's 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. These are the commands that 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.

    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 the given order:

  1. Install the update rollup package on the following server infrastructure:
    • Management server or servers
    • Audit Collection Services
    • Gateway servers
    • Web console server role computers
    • Operations console role computers
    • Reporting
    • Agent
  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.

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 correspond 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. Run the flowing Datawarehouse SQL script on Datawarehouse Server against OperationsManagerDW database:

    UR_Datawarehouse.sql

    Note This script is can be found in the following location:

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

  4. Run 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 dependencies:
      • 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 dependencies:
      • Microsoft.SystemCenter.Apm.Infrastructure.mpb
      • Microsoft.SystemCenter.Apm.Library.mpb
      • Microsoft.SystemCenter.Apm.Library.Resources.(LANGUAGECODE_3LTR).mpb
      • Microsoft.Windows.InternetInformationServices.2016.mp (this MP has to be downloaded separately from the Microsoft Update Catalog) which has the following dependency:
        • Microsoft.Windows.Server.2016.Discovery.mp (this MP has to be downloaded separately from the Microsoft Update Catalog)
    • 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
    • Microsoft.SystemCenter.OperationsManager.AM.DR.2007.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 location:

%SystemDrive%\Program Files\System Center2012 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 12 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:

    
    Download icon
     System Center Management Pack for UNIX and Linux Operating Systems

  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 In this command, PatchCodeGuid is a placeholder that represents one of the following GUIDs.

PatchCodeGUID

Component

Architecture

Language

{68FD737C-9083-4CE6-B37C-C43654385D61}

Agent

amd64

en

{7B4BBE8B-E9A0-423D-B7BA-5C267E145C77}

ACS

amd64

en

{7984B87F-F323-4FF2-AF82-3D2E25B30144}

Console

amd64

en

{751D327D-0E07-46AD-8845-2FA6B6F9C099}

Reporting

amd64

en

{CCEBCC3B-B9CC-41F3-BE83-D43BBE7D4AE2}

WebConsole

amd64

en

{09A7C466-0868-4FA5-A114-CFCAAE580B3F}

Gateway

amd64

en

{75C7E47A-4651-4B13-B2A0-8793D30B920A}

Server

amd64

en

{F3C3C190-C610-4B5D-87F4-B72C428EDFEB}

Agent

x86

en

{A59DC285-D3A1-4973-B381-E92C3378C6A8}

Console

x86

en

{18586181-7EDA-4ED9-8652-803AE8EE8153}

ACS

amd64

cn

{29D1FDB8-93EB-4A5E-9191-21066B9BA6E7}

Console

amd64

cn

{A72C3214-FAC1-49DC-AEF1-9105F2912871}

Reporting

amd64

cn

{B6210642-7AAD-41B5-BDC0-512D182E9A39}

WebConsole

amd64

cn

{515C3C6C-71F7-44AB-81E9-700CC10C7905}

Console

x86

cn

{D3816BEB-E533-412B-8BAD-D16609D66278}

ACS

amd64

cs

{54E5D145-7A3C-4F10-8E87-CC7216D39F9E}

Console

amd64

cs

{17CA68A9-E11B-4D4A-9763-FDCEDE320ACE}

Reporting

amd64

cs

{A8D8C178-AB92-4779-A68A-B37252971E5B}

WebConsole

amd64

cs

{3E5954D3-0801-4D8D-A27B-558F192FBEC7}

Console

x86

cs

{0081C94D-BBEF-43ED-93AD-E5C9BD7F6BD5}

ACS

amd64

de

{7BF3CF8F-1CC4-4035-874E-EECDFD20CB9C}

Console

amd64

de

{539D9C5F-B70A-440F-8C99-3D9D8FA007C7}

Reporting

amd64

de

{C6729FDD-EF28-4ED8-ADB6-0C7A820F468C}

WebConsole

amd64

de

{55745602-99C9-4DDC-B0DF-3F0CB814345D}

Console

x86

de

{D770A2D6-F9E3-4FF7-997D-D02FED2FCF2D}

ACS

amd64

es

{73223C9D-53AD-46A8-BFCC-CB1CD921731F}

Console

amd64

es

{FD6E4936-A8F2-4487-8275-32B0FEA231D5}

Reporting

amd64

es

{0BAF906F-E0A5-4564-A2BD-28F412B99E4A}

WebConsole

amd64

es

{D9FDECBC-D032-4EED-BA46-C6143C39FC83}

Console

x86

es

{317370E9-04C8-4F01-B063-749CECC0FE37}

ACS

amd64

fr

{0D46EEEB-7770-4A4B-B139-7C936C13D439}

Console

amd64

fr

{470E4BAE-1AC1-46DD-9E6F-1790F3A38798}

Reporting

amd64

fr

{5C9D550D-98DA-414C-91A4-CDE146D0FB93}

WebConsole

amd64

fr

{113C5AB3-49CF-4775-A497-1F12629EFACD}

Console

x86

fr

{C540F929-0B7E-41ED-B7AD-D61850910C2A}

ACS

amd64

hu

{584C8163-EA4F-4B67-9595-9E30596F2806}

Console

amd64

hu

{43E233F1-8B2F-467F-9BC0-AE167A189CD6}

Reporting

amd64

hu

{0ED5853C-22E6-44FC-B37C-71B0227D4252}

WebConsole

amd64

hu

{9715E245-239A-499B-9EA9-D04776593E97}

Console

x86

hu

{29D84599-AC51-45C5-8E9E-3DEEB8EB2EF6}

ACS

amd64

it

{0D3A7D8B-9EFF-4B5F-AEE2-1141FEF0B9AF}

Console

amd64

it

{5BC763FA-5690-426D-BE01-8216DD166054}

Reporting

amd64

it

{5EBE2BFC-6656-489C-9BDD-931DB26A8EDD}

WebConsole

amd64

it

{B2D871F2-2622-4871-BFF3-7B204E16B668}

Console

x86

it

{B6544774-2151-4B6A-8ADD-72B66FD8FB96}

ACS

amd64

ja

{EFE8C131-EBD1-4342-9C8E-87A168550FA6}

Console

amd64

ja

{00ADFEFA-DE92-4F33-AAF2-3FFBA1399097}

Reporting

amd64

ja

{9632DEC0-3DC5-4204-B4AD-C3CB65C9BE7C}

WebConsole

amd64

ja

{BA480341-7B9C-4578-9EA1-D51938D42876}

Console

x86

ja

{430FE765-B713-494C-9963-74F8264CEC41}

ACS

amd64

ko

{3E8EF83D-6779-45AA-95E1-1520A3EAC4AA}

Console

amd64

ko

{AA8BDB89-628D-44CC-91A8-1F8C60E9FF65}

Reporting

amd64

ko

{D1BC210A-0906-445B-8E01-06D106B03B0F}

WebConsole

amd64

ko

{09201284-11D3-4FA7-9F00-0634CA2B588B}

Console

x86

ko

{592F903F-C69E-4893-A7FB-834DFD75A55D}

ACS

amd64

nl

{CC08529F-7F4A-4CFB-8A4D-CD550FFFBFBF}

Console

amd64

nl

{83C45A71-C6FE-4522-89F8-753C73EC7275}

Reporting

amd64

nl

{71B4B658-02BB-48DD-B1B6-DDB7F71B2E8F}

WebConsole

amd64

nl

{CC39B2F9-2252-405A-868B-655E122894B1}

Console

x86

nl

{82A37AC6-08DF-402A-B38D-886C8FED8D97}

ACS

amd64

pl

{4E21BD1D-BB95-40BC-967A-8B49839715E6}

Console

amd64

pl

{505FA3E5-1194-40B4-9948-E552EADFCCB9}

Reporting

amd64

pl

{D5770B11-8A4E-4FED-84FC-22922506B260}

WebConsole

amd64

pl

{6AA3402D-DB3A-474D-BF98-10B899329E71}

Console

x86

pl

{7438B35E-4382-4721-8F16-3804607BB4CF}

ACS

amd64

pt-br

{9F3AF6DA-6350-414C-A086-A0AB64B231F7}

Console

amd64

pt-br

{28BC3546-A61D-410E-B0F6-8743BBD64BAF}

Reporting

amd64

pt-br

{DAD727C6-6543-4951-8006-CB8FD1898E9C}

WebConsole

amd64

pt-br

{98E643CF-226E-4FE5-A82A-3263F4BAA3A3}

Console

x86

pt-br

{E1340BC1-274E-402B-B4C8-D4DC29E0B303}

ACS

amd64

pt-pt

{BA013848-5A16-41DE-8119-9603722ECB91}

Console

amd64

pt-pt

{D2B94906-3C5F-48AE-A927-F1E5FA7BCD54}

Reporting

amd64

pt-pt

{12DA3935-33C1-4B28-9045-C2326BADCA2F}

WebConsole

amd64

pt-pt

{D1A8A91C-F92D-4D23-9807-0A76C6DDFC8C}

Console

x86

pt-pt

{FCDBF70C-EFF9-4A2A-A14E-9C787723108E}

ACS

amd64

ru

{9C8E375F-329B-4CB4-9E16-D7C6B2ADEB9D}

Console

amd64

ru

{B3997AFB-9D12-479F-91E2-AE94F12A980E}

Reporting

amd64

ru

{78539738-7326-4A19-AB21-B2864F20578D}

WebConsole

amd64

ru

{12B3C409-CAC4-4428-993C-1E803FD381FB}

Console

x86

ru

{86550C05-54B1-4451-82B8-6936F54B81DE}

ACS

amd64

sv

{9EED3088-8FC5-418B-9283-5DDDEEC0C560}

Console

amd64

sv

{8C21044A-8292-42DF-A24C-0EE5A8EB8582}

Reporting

amd64

sv

{BB88FE3C-C622-4C84-8F95-765CD9D72CD2}

WebConsole

amd64

sv

{72F72E07-7871-4905-AC80-E67EF83C4E9F}

Console

x86

sv

{EDFB5A0F-D577-4511-AB8D-40DFF8179F6B}

ACS

amd64

tr

{DAB67967-52C2-42CD-AE87-F1070DFA8B19}

Console

amd64

tr

{13912066-D2E4-4332-89A4-BAE2A3A2A371}

Reporting

amd64

tr

{0B89D9F6-9D92-43F1-BE5B-9BA889413704}

WebConsole

amd64

tr

{FD169D02-700D-43DB-8D7B-D9D6C26BFE41}

Console

x86

tr

{3738A4C7-05BA-45F4-A18D-287BCF2CDE19}

ACS

amd64

tw

{6519EE80-E9C5-4538-9EFB-BBCB7B4B1DE3}

Console

amd64

tw

{E2E57F99-A1F5-429B-A55B-1C793D2F7AB6}

Reporting

amd64

tw

{D4B143D8-B922-4504-9D22-E7852868C721}

WebConsole

amd64

tw

{8C935C2D-5199-4D3F-936D-D37EC205F4D6}

Console

x86

tw

{62F10210-F447-422D-8009-6643BD0D28BC}

ACS

amd64

zh-hk

{E9717F03-4092-4EC5-9B74-8806EDB6973B}

Console

amd64

zh-hk

{3D0D92CF-52F6-4B6D-BEDF-81454C1B1963}

Reporting

amd64

zh-hk

{666F5D05-8C74-4A47-AC05-A19416B68552}

WebConsole

amd64

zh-hk

{A1433F38-5C63-4402-9947-F4D98209C0FF}

Console

x86

zh-hk

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

Component

RTMProductCodeGuid

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}

ACS

{8574A035-1191-4EBA-BA6C-1F4D37171CE2}

Agent (AMD64)

{786970C5-E6F6-4A41-B238-AE25D4B91EEA}

Agent (x86)

{B4A63055-7BB1-439E-862C-6844CB4897DA}

Reporting{D6E655E7-6318-4C50-B184-55E70DB179C1}

Files updated in this update rollup

The following is a list of files that have changed in this update rollup. If you don't 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, see the "Files Updated in this Update Rollup" section of all update rollups that were released after your current update rollup.

Files that are updated

Version

Size

scxcertlib.dll

7.5.1067.0

75KB

scxcertmodules.dll

7.5.1067.0

186KB

scxcertconfig.exe

7.5.1067.0

31KB

Microsoft.Mom.DatabaseWriteModules.dll

7.1.10226.1304

100KB

Microsoft.EnterpriseManagement.UI.Administration.dll

7.1.10226.1304

4332kb

HealthService.exe

7.1.10292.0

34KB

HealthService.dll

7.1.10292.0

3251KB

csengine.dll

7.1.10226.1304

282KB

Microsoft.EnterpriseManagement.OperationsManager.dll

7.1.10226.0 

1.03 mb

Microsoft.SystemCenter.Advisor.Common.dll

7.1.10226.1304

154KB

SCMsgs.dll

7.5.3079.688

122KB

Microsoft.SystemCenter.Advisor.Resources.(LANGUAGECODE_3LTR).mpb

7.1.10226.1304

80 KB

Microsoft.SystemCenter.Advisor.mpb

7.1.10226.1304

368KB

Microsoft.SystemCenter.OperationsManager.AM.DR.2007.mp

7.1.10226.1304

148

Microsoft.SystemCenter.Advisor.Internal.mpb

7.1.10226.1304

148KB

Microsoft.SystemCenter.AlertAttachment.mpb

7.1.10226.1304

 124KB

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, see the "Files updated in this update rollup" section of all update rollups that were released after your current update rollup.

Files that are changed

File size

Version

Microsoft.ACS.Linux.RHEL.7.mp

20 KB

7.5.1068.0

Microsoft.AIX.5.3.mpb

15900 KB

7.5.1068.0

Microsoft.AIX.6.1.mpb

15905KB

7.5.1068.0

Microsoft.AIX.7.mpb

14903KB

7.5.1068.0

Microsoft.AIX.Library.mp

31 KB

7.5.1068.0

Microsoft.HPUX.11iv2.mpb

20.963 MB

7.5.1068.0

Microsoft.HPUX.11iv3.mpb

19.937 MB

7.5.1068.0

Microsoft.HPUX.Library.mp

31 KB

7.5.1068.0

Microsoft.Linux.Library.mp

31 KB

7.5.1068.0

Microsoft.Linux.RedHat.Library.mp

15 KB

7.5.1068.0

Microsoft.Linux.RHEL.4.mpb

8011KB

7.5.1068.0

Microsoft.Linux.RHEL.5.mpb

7958KB

7.5.1068.0

Microsoft.Linux.RHEL.6.mpb

7483 MB

7.5.1068.0

Microsoft.Linux.RHEL.7.mpb

4734 KB

7.5.1068.0

Microsoft.Linux.SLES.10.mpb

7317 KB

7.5.1068.0

Microsoft.Linux.SLES.11.mpb

4767KB

7.5.1068.0

Microsoft.Linux.SLES.12.mpb

1862 KB

7.5.1068.0

Microsoft.Linux.SLES.9.mpb

3655 KB

7.5.1068.0

Microsoft.Linux.SUSE.Library.mp

15 KB

7.5.1068.0

Microsoft.Linux.Universal.Library.mp

15 KB

7.5.1068.0

Microsoft.Linux.Universal.Monitoring.mp

83 KB

7.5.1068.0

Microsoft.Linux.UniversalD.1.mpb

14315 KB

7.5.1068.0

Microsoft.Linux.UniversalR.1.mpb

12919 KB

7.5.1068.0

Microsoft.Solaris.10.mpb

26858 KB

7.5.1068.0

Microsoft.Solaris.11.mpb

26898 KB

7.5.1068.0

Microsoft.Solaris.9.mpb

13875 KB

7.5.1068.0

Microsoft.Solaris.Library.mp

22 KB

7.5.1068.0

Microsoft.Unix.Library.mp

83 KB

7.5.1068.0

Microsoft.Unix.LogFile.Library.mpb

86 KB

7.5.1068.0

Microsoft.Unix.Process.Library.mpb

99 KB

7.5.1068.0

Microsoft.Unix.ShellCommand.Library.mpb

68 KB

7.5.1068.0

Properties

Article ID: 3209587 - Last Review: Jan 26, 2017 - Revision: 47

Feedback