Introduction

This article describes the issues that are fixed in Update Rollup 7 for Microsoft System Center 2012 R2 Operations Manager. Additionally, this article contains the installation instructions for Update Rollup 7 for System Center 2012 R2 Operations Manager.

Issues that are fixed in this update rollup

Operations Manager

  • The home page link in the Web Console Noscript.aspx file is vulnerable to cross-site scripting (XSS)

    A security vulnerability exists in the Web Console for System Center 2012 R2 Operations Manager that could allow elevation of privilege if a user goes to an affected website by using a specially crafted URL. This fix resolves that vulnerability. For more information, see Microsoft Security Bulletin MS15-086.

  • "Agents by Health State" report shows duplicate entries and inconsistent data

    Sometimes a single agent has multiple entries displayed in the "Agents by Health State" report. The fix for this issue makes sure the most recent state of the agent is displayed in the report.

  • Dependent tables are not groomed (Event.EventParameter_GUID table)

    The following issues are fixed:

    • In a database, the grooming of certain MT$X$Y tables were missed because of the filtering logic. Therefore, the tables were never groomed. There were scenarios in which lots of unwanted data was stored in these tables. This issue is now fixed, and data is groomed data from these table. This results in performance gains because there is less data from which to query.

    • In Data Warehouse, the grooming of certain tables was missed occasionally because current logic expects the rows to be returned in a certain order. This issue is now fixed, and the grooming of these tables will not be missed. In some scenarios, millions of rows were stored in these tables. This issue is now fixed. Data is now groomed from these tables. This results in performance gains because there is less data from which to query.



  • Management Packs do not synchronize between management servers

    In a SQL AlwaysOn setup, the SQL in the times of failover does not acknowledge the notifications that are registered by SCOM. This leads to inconsistent data in the environment, and the changes in management pack are not reflected in the whole environment. This update resolves this issue.

  • Leaked transaction causes over 100 SPIDs in SCOM database to be permanently blocked by the "p_DataPurging" stored procedure 

    Sometimes, because of a leaked transaction in the p_DataPurging stored procedure, the SPID becomes stuck. This causes other SPIDs to be blocked, and SCOM is brought to a standstill. This issue is fixed in this update. The fix prevents other SPIDs from being blocked.

  • Operations Manager SDK crashes because of SQL errors when QueryResultsReader.Dispose is called

    The Operations Manager SDK could potentially crash when it disposes of a database connection in some scenarios. Additionally, you receive an error message that resembles the following:

    Exception object: 00000004058197a0
    Exception type: System.Data.SqlClient.SqlException
    Message: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
    InnerException: System.ComponentModel.Win32Exception, Use !PrintException 0000000405819050 to see more.


    This update handles these scenarios gracefully.

  • You can't view dashboard performance counters that are created by using the TCP Port Monitoring template

    When you use the TCP Port Monitoring template to monitor network connectivity and the availability of local and remote assets, the template is missing a write action to the data warehouse. With the update, you can present this information on dashboards.

  • Dynamic inclusion rule is added to a group definition unexpectedly if an explicit member instance of the group disappears

    If all the explicit member instances of the group disappear, a dynamic rule is added to the group unexpectedly. With the update, no dynamic rule is generated in these situations.

  • You can't create group by using the SQL Server 20XX Installation Seed

    On the Dynamic Members tab of the Group Creation wizard, if you have a host class of your desired class, and if you try to select the inherited property of the host class, group creation fails. For example, if you select the Display Name(Object) property of Host=Windows Computer of the Management Server class on the Dynamic Members tab, group creation fails, and you receive the following exception:

    Processing the template failed. See inner exception for details.
    Verification failed with 1 errors:
    -------------------------------------------------------
    Error 1:
    Found error in 1|StressCollectPerformancecounterMP|1.0.0.0|UINameSpaceb2240e1340254758bc3a0f1bd0082f4d.Group.DiscoveryRule/GroupPopulationDataSource|| with message:
    The configuration specified for Module GroupPopulationDataSource is not valid.
    : Cannot find specified MPSubElement DisplayName, on MPElement= Windows!Microsoft.Windows.Computer, in expression: $MPElement[Name="Windows!Microsoft.Windows.Computer"]/DisplayName$


    This update resolves this issue.

  • Add MPB support to the SCOM online catalog

    The Management Pack catalog supports only those management packs that have the .mp extension and not the .mpb file-name extension. When this feature is implemented, the Management Pack catalog now supports MPB files.

    This update helps include management packs such as Azure Management Pack and SQL Management Pack on the Management Pack catalog that were not featured because of the .mpb file-name extension.

  • Active Directory Integration in Perimeter Network fails when there is only an RODC present

    When Active Directory Integration is enabled, the SCOM agent cannot talk to an RODC to obtain SCP information and instead looks for a RW domain controller. With this update, the Agent obtains SCP information from the RODC if information is available.

  • System Center Operations Manager subscriptions that use the filter to search for specific text in the description (of the message) do not work

    When you create a message subscription by using a criterion that contains specific text in the message description, no alerts were received through notifications. With this update, you receive notifications when the message description has specific text.

  • CLR load order change

    The current behavior for agents is to choose a CLR version based on the operating system version. For Windows Server 2012 and newer, the .NET Framework 4.0 is loaded. For operating systems older than Windows Server 2012, the .NET Framework 2.0 family is loaded. On management servers, the .NET Framework 2.0 family is loaded. This essentially maps the .NET Framework version used to the version available out-of-box on the server. The problem with the current behavior is that even if the Management Pack author knows that .NET Framework 4.0 is present on the system, it cannot be used.

    In the new behavior, the agent loads the .NET Framework 4.0 if it is available else it falls back to the .NET Framework 2.0.

  • Problems in obtaining monitoring objects by using "managementGroup.EntityObjects.GetObjectReader"

    In large System Center Operations Manager installations, when entity objects under a management group are retrieved by the object reader by using buffered mode, the object reader sometimes encounters System.Collections.Generic.KeyNotFoundException messages. With this update, the object reader ignores the invalid objects if they are not available.

  • The "Threshold Comparison" setting in the consecutive-samples-over-threshold monitor cannot be configured

    Although you configured the Threshold Comparison setting in the consecutive-samples-over-threshold monitor, the conversion of the Threshold float value from the management pack was incorrect for the German locale and caused monitor configuration failures. This issue is now fixed in this update for every supported locale.

  • Agentless Exception Monitoring (AEM) causes the Health Service to crash because the maximum path length of 248 character is exceeded

    When AEM client monitoring is turned on, sometimes the Windows error reporting file is created in a large file hierarchy. In scenarios in which the path is longer than 248 characters, AEM monitoring was causing the Health Service to crash. This issue is fixed.

  • After you update management packs, the newly added default (visible) columns to view are not visible automatically

    The first time that a view is opened on the console, registry keys are written in the HKEY_Current_User hive. The customization settings for the user are written in the registry. If the default view changes, the customization settings in the registry are not updated to reflect the new defaults. This update adds the newly added default column in the view.

  • Branding update

    Updates the "Operational Insights" name to "Operations Management Suite" in the System Center Operations Management console.

UNIX and Linux Management Pack

  • In some cases, Unix and Linux agents report incorrect CPU Percent Processor Time

    The Unix and Linux agents use Percent IO Wait Time when they calculate Percent Processor Time for a CPU object. The agents no longer include IO Wait Time in the calculation when they return Percent Processor Time.

  • A Logical Disk Health alert is not generated for a UNIX or Linux Logical Disk (file system) that is unmounted if the mount point exists after the file system is unmounted

    When a file system is mounted as a subdirectory, the mount point can still exist if the file system is unmounted. The UNIX and Linux Logical Disk Health monitor now inspects a more robust set of data before it returns data about online and offline status.


Updates that are included in this update rollup

The following files are updated to support the following manageable operating systems.

Operating system

Management pack

Debian 8 (x64)

Microsoft.Linux.UniversalD.1.mpb

Debian 8 (x86)

Microsoft.Linux.UniversalD.1.mpb


How to obtain and install Update Rollup 7 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 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.

Manual download of the update packages

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

Download Download the Operations Manager update package now.

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 described in Update Rollup 1 for System Center 2012 R2 Operations Manager adds a registry key that 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.

    Registry location:HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Data Warehouse
    DWORD name: Bulk Insert Command Timeout 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 orderWe 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

    • 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 updateTo 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. Run 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\Microsoft System Center 2012 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. This management pack has the following dependency:

      • Microsoft.SystemCenter.AlertAttachment.mpb. This 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


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\Microsoft System Center 2012 R2\Operations Manager\Server\Management Packs for Update Rollups

UNIX/Linux Management Pack updateTo 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:

    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.



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

{F9554174-E3FC-49D3-BC09-9E2BD67069D2}

Agent

amd64

en

{31D2B7A7-FE84-4FBE-8EEE-08A47852FA85}

Console

amd64

en

{62C40871-6D59-4DEC-BD4C-44E099A7A973}

WebConsole

amd64

en

{3CE80539-6CF2-4F21-9B6C-ABFEED70C13E}

Gateway

amd64

en

{C61BC742-A505-4DE9-96C9-21E4218C8B0A}

Server

amd64

en

{31D824CC-B427-4388-BFC8-1D3CF6AECD9C}

Agent

x86

en

{597CE9CA-2329-4D1D-A596-355A1B994B90}

Console

x86

en

{5CB5B2AD-E938-44F2-8F3B-CD015BD16C23}

Console

amd64

cn

{98E38BFC-5466-4A62-B33C-D57B72F74340}

WebConsole

amd64

cn

{6F2CDB1D-6C6E-43C8-A298-3111F2083121}

Console

x86

cn

{9FDAA1C2-B318-446B-A91E-DFCFB5A755C7}

Console

amd64

cs

{FAC3C24C-7824-4B08-BC15-6FBC1AA7824F}

WebConsole

amd64

cs

{BE4265AC-6535-4FF2-8EE0-B8EBA4E8F40E}

Console

x86

cs

{D8F8E96B-CEDE-418F-88F4-49293EB1474D}

Console

amd64

de

{3F7C9FB1-CCCC-459A-9DC1-BF38986A688C}

WebConsole

amd64

de

{9E587FD9-BB98-4A7D-8852-406A8F7D6EDC}

Console

x86

de

{4887C640-A8CB-41AD-96E4-F2145031E885}

Console

amd64

es

{190C89CA-9C8C-42DA-81E2-CA19EDAE0734}

WebConsole

amd64

es

{33A1518A-F72F-44BA-AE7B-D94058B5568B}

Console

x86

es

{2784DF35-4FFB-4DCD-8393-476242B1E997}

Console

amd64

fr

{8E483F31-A26D-40FF-A9B7-FD4D6238516A}

WebConsole

amd64

fr

{70A98D76-6759-435F-B1B7-B7C87DE258F5}

Console

x86

fr

{526CD533-F08F-471E-88A4-586E1819E855}

Console

amd64

hu

{C0FF27B1-BFC9-4885-95C2-D4330A190E8A}

WebConsole

amd64

hu

{8C817892-B064-485E-AE7C-AACA49BDC605}

Console

x86

hu

{48717DD1-922E-43C0-B7DE-3C637E383078}

Console

amd64

it

{D23132D5-1115-42A9-B714-C4F7833E6AE4}

WebConsole

amd64

it

{7991AE88-CEC0-40B0-ADFD-2F3352EF3FB6}

Console

x86

it

{1FFB9900-95B0-46B6-A4E6-EF978B084ABC}

Console

amd64

ja

{2275AB19-F9B5-4E26-81FA-5B06A5D54797}

WebConsole

amd64

ja

{695E2111-4BD4-42EC-8804-0EC557086E39}

Console

x86

ja

{D1902E10-7A29-4BDC-843E-35AC204D8B89}

Console

amd64

ko

{D111C81F-8861-47CB-888D-71E8FF1CA5A6}

WebConsole

amd64

ko

{D30876A6-17A5-4CCE-B02D-B7BCB408EDE9}

Console

x86

ko

{01C165EE-01B9-4C9E-A357-DC53E3F2FBC1}

Console

amd64

nl

{B647B41C-50B1-44C3-8530-A6299237A26A}

WebConsole

amd64

nl

{BE80CD82-24EF-4071-8CA6-B8E1E3DB37D5}

Console

x86

nl

{A7E01F7E-7E8C-45BA-BE2C-38ED0EF07470}

Console

amd64

pl

{2582171A-ABE0-4732-9383-EC473F6CD884}

WebConsole

amd64

pl

{6ED6FF3B-9824-464C-9FE4-DD44F4E3E040}

Console

x86

pl

{88819B94-AC6B-4061-9897-84F4D47FC66E}

Console

amd64

pt-br

{65839F41-CEDE-4E49-8392-3D5E2AD96DA7}

WebConsole

amd64

pt-br

{37BD9FE9-14C1-4D67-BA81-787E98AEB10E}

Console

x86

pt-br

{BF0FCD95-AEA8-4DAD-AE9D-4515D9A142DD}

Console

amd64

pt-pt

{C0955FC5-9C22-4582-B0CA-FD4A97FF7CDA}

WebConsole

amd64

pt-pt

{E214F8B0-2150-4137-AD8A-7EF7AA8F01D1}

Console

x86

pt-pt

{A63A8B0A-3D2D-4F67-AB24-C7B1995A9592}

Console

amd64

ru

{B8745D73-E707-4175-98DE-CF3694722258}

WebConsole

amd64

ru

{2568F8F2-D954-4E13-9DFB-9C17AE671DD9}

Console

x86

ru

{0340D0A3-54BD-45DA-8E42-BEF42259F34D}

Console

amd64

sv

{D20EB907-0D05-4BB9-B8BC-4998FADEEECA}

WebConsole

amd64

sv

{862FB5ED-FDD7-48B3-A0AF-1ABDC2F028B3}

Console

x86

sv

{52B218EA-CCF1-4459-926D-2A2DB04D5BED}

Console

amd64

tr

{6E4F738E-0B4C-4415-B14A-0BC972826392}

WebConsole

amd64

tr

{B4979932-1681-4EEB-93B7-52421BA945D1}

Console

x86

tr

{D74F2981-B91C-4C54-A0B1-20BF20BA402D}

Console

amd64

tw

{DCEBBB63-C559-4016-A392-887A8862F232}

WebConsole

amd64

tw

{EC1A7013-7B1D-4F40-8654-6B821DA3D68B}

Console

x86

tw

{BAD29A2A-F00C-4C9D-8403-9D639E71F2D8}

Console

amd64

zh-hk

{7870E4E7-91F1-433B-9A3B-804CCCB1496E}

WebConsole

amd64

zh-hk

{D056D3E7-AB94-47A1-A597-BC58B11CC320}

Console

x86

zh-hk



Additionally, RTMProductCodeGuid is a placeholder that 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}

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}



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 updated for Operations Manager

Files that are updated

Version

Size

Microsoft.EnterpriseManagement.Monitoring.Console.exe

7.1.10226.1090

4.25 MB

HealthService.dll

7.1.10229.0

3.16 MB

HealthServiceRuntime.dll

7.1.10229.0

312 KB

MOMConnector.dll

7.1.10229.0

686 KB

Microsoft.EnterpriseManagement.UI.Authoring.dll

7.1.10226.1090

9.44 MB

Microsoft.Mom.UI.Components.dll

7.1.10226.1090

5.87 MB

Microsoft.EnterpriseManagement.Presentation.WebConsole.dll

7.1.10226.1090

105 KB

Microsoft.EnterpriseManagement.UI.Administration.dll

7.1.10226.1090

4.26 MB

Microsoft.EnterpriseManagement.UI.Administration.resources.dll

7.1.10226.1090

2.41 MB

Microsoft.EnterpriseManagement.Core.dll

7.5.3079.426

3.89 MB

Microsoft.Mom.Modules.ClientMonitoring.dll

7.1.10226.1090

446 KB

Microsoft.EnterpriseManagement.DataAccessLayer.dll

7.5.3079.454

2.4 MB

Microsoft.EnterpriseManagement.DataAccessService.Core.dll

7.5.3079.454

694 KB

Microsoft.Mom.Common.dll

7.1.10226.1090

242 KB

Microsoft.SystemCenter.SyntheticTransactions.Library.mp

7.1.10226.1090

47 KB

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

7.1.10226.1083

72 KB

Microsoft.SystemCenter.Advisor.mpb

7.1.10226.1090

348 KB

Microsoft.SystemCenter.Visualization.Component.Library.mpb

7.1.10226.1090

288 KB

update_rollup_mom_db.sql

7.1.10226.1090

142 KB

UR_DataWarehouse.sql

7.1.10226.1090

137 KB


Files that are updated for the UNIX and Linux Management Pack

Files that are changed

File size

Version

Microsoft.AIX.5.3.mpb

15,757KB

7.5.1045.0

Microsoft.AIX.6.1.mpb

15,769KB

7.5.1045.0

Microsoft.AIX.7.mpb

14,764KB

7.5.1045.0

Microsoft.AIX.Library.mp

31KB

7.5.1045.0

Microsoft.HPUX.11iv2.mpb

19,995KB

7.5.1045.0

Microsoft.HPUX.11iv3.mpb

19,903KB

7.5.1045.0

Microsoft.HPUX.Library.mp

31KB

7.5.1045.0

Microsoft.Linux.Library.mp

31KB

7.5.1045.0

Microsoft.Linux.RedHat.Library.mp

15KB

7.5.1045.0

Microsoft.Linux.RHEL.4.mpb

7,899KB

7.5.1045.0

Microsoft.Linux.RHEL.5.mpb

7,818KB

7.5.1045.0

Microsoft.Linux.RHEL.6.mpb

7,385KB

7.5.1045.0

Microsoft.Linux.RHEL.7.mpb

2,333KB

7.5.1045.0

Microsoft.Linux.SLES.9.mpb

3,799KB

7.5.1045.0

Microsoft.Linux.SLES.10.mpb

7,171KB

7.5.1045.0

Microsoft.Linux.SLES.11.mpb

4,711KB

7.5.1045.0

Microsoft.Linux.SLES.12.mpb

1,843KB

7.5.1045.0

Microsoft.Linux.SUSE.Library.mp

15KB

7.5.1045.0

Microsoft.Linux.Universal.Library.mp

15KB

7.5.1045.0

Microsoft.Linux.Universal.Monitoring.mp

83KB

7.5.1045.0

Microsoft.Linux.UniversalD.1.mpb

14,119KB

7.5.1045.0

Microsoft.Linux.UniversalR.1.mpb

12,608KB

7.5.1045.0

Microsoft.Solaris.9.mpb

13,780KB

7.5.1045.0

Microsoft.Solaris.10.mpb

26,963KB

7.5.1045.0

Microsoft.Solaris.11.mpb

26,621KB

7.5.1045.0

Microsoft.Solaris.Library.mp

22KB

7.5.1045.0

Microsoft.Unix.Library.mp

83KB

7.5.1045.0

Microsoft.Unix.LogFile.Library.mpb

86KB

7.5.1045.0

Microsoft.Unix.Process.Library.mpb

98KB

7.5.1045.0

Microsoft.Unix.ShellCommand.Library.mpb

69KB

7.5.1045.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!

×