Category Archives: Update Rollup

SCOM 2019: UR1 has been released!

The much anticipated release of UR1 for SCOM 2019 is here and you can get it from the update catalog.

There’s quite a bit to unpack here so lets have a look

The big changes are of course support for gMSA which I for one have been looking forward to for a while. The security benefits are obvious and I can say while it does work well be aware that it is complex to implement so read those instructions thoroughly.

The one click upgrade experience is also a step in the right direction making things much simpler for the SCOM admin, just note it only includes the server update so you will still need to upgrade your console, reporting etc manually.

See below for a complete list of all the changes

Improvements and issues that are fixed


Web Console Fixes/Changes:

  • State widget now supports sorting by health and age. 
  • Alert widgets can now be searched on Date Time and sorted based upon age and severity.
  • The alert link in email notification when browsed throws an error, “Your session with the Web Console server expired” even though the user was not logged in web console . You will now see the login page post this fix.
  • Alert summary view in SCOM Web console was fixed in size.  This can be expanded as required now.
  • When Alert state is changed to some custom state, then these alerts are not displayed in web console. Alerts with custom resolution states will be displayed now.
  • Few additional scrollbars appear when a customer widget is created in web console or browser window size is reduced.
  • Improvement: SCOM views will load/save much faster than before. 

Unix/Linux/Network Monitoring Fixes/Changes:

  • SCX by default does Info level logging which causes SCX logs to be filled up soon. With 2019 UR1, Warnings and Errors will be logged by default not Info.
  • In the network device monitoring, if the node property is changed to null/empty, it displays the old value of the property not the null value. The actual value will be displayed now which includes null.
  • In a scenario where multiple (~500) virtual network interfaces are running on agent, SCOM sometimes received heartbeat failure alerts for such agents. SCOM will monitor only physical interfaces hosted on these machines. For monitoring virtual interfaces, you need to set “enumvif” to true. 
  • SNMP GET or SNMP WALK resulted monitoring host to crash when the network object ID is equal to ULONG Max. There is an error with event ID 4000 due to this crash.
  • For linux distros servers, when the kernel version >= 4.18, then file system related performance data is shown as 0 in SCOM. This is fixed in FS provider to make it kernel version agnostic and collect file system stat info.
  • Use of Async Windows Management Infrastructure (MI) APIs is default functionality from SCOM 2019 UR1 for scalability improvements.More details here

 Admin Console Fixes:

  • When admin created “one-time maintenance mode schedule” for non-English locales, SCOM console displays an error “The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection”. Admin would be able to create one-time maintenance schedule now.
  • When SCOM agent is multihomed, then SCOM 2019 MS always displays logon type as “Interactive” for this agent. The correct logon type will be displayed now.
  • Unit monitor to check correct logon type for Run as Account had incorrect name and Operational State.
  • “Operations Manager Products” view in Admin console did not update the “Version” column for the installed component version. This column will now reflect the updated version of all the components listed.

Others:

  • When system proxy is configured on the Reporting Server; proxy overrides are ignored by the “Report Console Watcher Monitor” and “Web Console Watcher Monitor” and as a result HTTP/HTTPS access fails.  With UR1 fix, “Set proxy Direct” parameter of the mentioned monitors can be set to true and URLs will be accessed.
  • SCOM did not discover Windows Cluster which are deployed on servers with IPV6 network only enabled. IPV6 network will be supported for cluster monitoring now.
  • When the Domain controller is moved to a different AD site, then SCOM does not display the correct site name. Any dynamic group which are created for SiteName will also fail

 In addition to these, all the issues fixed in SCOM 2016 UR8 and prior UR for SCOM 2016 are also fixed in SCOM 2019 UR1. Details of the fixes are below.

  • In a scenario where SCOM monitors 100s of virtual machines hosted on a single Hyper-v server; every hour the healthservice.exe of each Virtual machine write into the VM page file simultaneously. Due to this concurrent paging, every hour disk I/O increases and database becomes unresponsive. HealthService.exe now have Memory Trimming enabled by default on an hourly schedule. A registry key is provided to disable the memory trimming and control the duration.

          Registry key is: “HKLM\Software\Microsoft\Microsoft Operations Manager\3.0\Setup\MemoryTrimming”

         Enable – 0 (Trimming is disabled); 1 (trimming is enabled)

         DelayInSeconds – Time period agent waits to start trimming (default is 120s)

         PeriodInSeconds – Recurring period at which the working set should be trimmed (default is 3600s)

  • Historical data do not appear, if input reporting end time is before group creation time. With this fix, historic data for a group (if data is available for objects in the group) would be displayed irrespective of group creation time.
  • Maintenance mode state changes which are recorded in MaintenanceModeStage table requires grooming when table grows. If the table is large, grooming takes longer and the operation times out with SQLTimeOut exception.
  • If a group is renamed in a Management pack, then console shows the new value but Powershell command Get-SCOMGroup returns the old name of group. Database Updates functionality was inconsistent for SCOM group renaming through MP and SCOM Console.
  • CPU Spike issues because of workflows running on all agents at the same time is addressed through script optimization and removing the sync time. 
  • Improvement: Sometimes SQL stored procedure “p_SelectForNewTypeCache” takes long time to complete, and SDK service fails to start. This is fixed and above SQL stored procedure will complete faster now.
  • Improved the performance of SCOM console in listing the groups.
  • Users of a scoped group are not able to use the Console.
  • SCOM console crashes while trying to connect to Azure Log Analytics and Azure Monitor.
  • SCOM Network Device Re-Discovery now probes for SNMP V3 devices too.
  • Agents by Health State report shows duplicate agent names.
  • Fixed an issue that prevented addition of a group in the Storage Spaces Direct 2016 management pack dashboard.
  • Linux agent is not able to get the correct version and port details for JBoss EAP 7.1.
  • An issue that lead to creation of multiple empty temp files in the /tmp directory of Linux servers has been fixed.
  • Fixed the formatting issue with the output for the task ‘Top10 CPU Processes’ when using Windows Management Infrastructure (MI) APIs.
  • Fixed an issue that caused the corruption of /etc/login.cfg file on AIX 7 machines during install/upgrade of the agent.
  • AIX Agent is now transitioned to 64-bit package to accommodate more stack and heap space if needed to avoid any stack/heap overflow which occasionally leads to heartbeat failure.
  • Free memory calculation accommodated appropriately on RHEL-7 platform.

SCOM: News from Ignite

This year at Ignite SCOM had it’s own dedicated session which is great to see. Here is a summary of the new upcoming features in UR1.

Version Agnostic Management Packs
Storage Spaces Direct (S2D) MP
RHEL 8 Support
One click patching experience
Support for gMSA
Relability and Performance Improvemennts for Linux Agent
Common Management Pack for Linux
Resource Group monitoring in Azure MP
Azure MP Web Console Dashboards

The ones I’m most looking forward to are of course the support for gMSA, with security being so critical in today’s IT real-estate this features adds an additional layer of peace of mind to your SCOM monitoring.

The one click patching experience is also a nice quality of life improvement, I had the privilege to see this in action and I like the direction this is going.

More agnostic management packs are also on the way which will simplify administration of products the same way we’ve seen them improve the SQL monitoring experience.

What do you think of this update? Leave a comment or if you have an idea head over to the SCOM Uservoice https://systemcenterom.uservoice.com/forums/293064-general-operations-manager-feedback and let the product group know.

SCOM 2016: UR 8 is now available!

Update Rollup 8 for SCOM 2016 is now available, as usual you can get it through windows update or via the download catalogue here

Improvements and fixes


  • Fixed: In a scenario where SCOM monitors 100s of virtual machines hosted on a single Hyper-v server; every hour the healthservice.exe of each Virtual machine write into the VM page file simultaneously. Due to this concurrent paging, every hour disk I/O increases and database becomes unresponsive. HealthService.exe now have Memory Trimming enabled by default on an hourly schedule. A registry key is provided to disable the memory trimming and control the duration.

          Registry key is: “HKLM\Software\Microsoft\Microsoft Operations Manager\3.0\Setup\MemoryTrimming”

         Enable – 0 (Trimming is disabled); 1 (trimming is enabled)

         DelayInSeconds – Time period agent waits to start trimming (default is 120s)

         PeriodInSeconds – Recurring period at which the working set should be  trimmed (default is 3600s)

  • Fixed: Historical data do not appear, if input reporting end time is before group creation time. With this fix, historic data for a group (if data is available for objects in the group) would be displayed irrespective of group creation time.
  • Fixed: Maintenance mode state changes which are recorded in MaintenanceModeStage table requires grooming when table grows. If the table is large, grooming takes longer and the operation times out with SQLTimeOut exception.
  • Fixed: If a group is renamed in a Management pack, then console shows the new value but Powershell command Get-SCOMGroup returns the old name of group. Database Updates functionality was inconsistent for SCOM group renaming through MP and SCOM Console.
  • Fixed: CPU Spike issues because of workflows running on all agents at the same time is addressed through script optimization and removing the sync time.
  • Fixed: If the registry key under “Computer\HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup\UseMIApi” is set and a Unix/Linux Script task without a parameter is executed then this task fails. 
  • Improvement: Sometimes SQL stored procedure “p_SelectForNewTypeCache” takes long time to complete, and SDK service fails to start. This is fixed and above SQL stored procedure will complete faster now.

SCOM 2016: UR7 is Live

Update rollup 7 for SCOM is now available as usual you can get it through windows update or here

How to guide – here note the known issues and slight change to getting started.

A decent update with quite a few fixes listed below:

Improvements and issues that are fixed


  • Fixed: Cannot use SQLOleDB.dll to probe databases like Oracle/MySQL.
  • Improved the performance of SCOM console in listing the groups.
  • Operations Manager grooms out the alert history only on an alert closure.
  • Agents by Health State report shows duplicate agent names.
  • Users of a scoped group are not able to use the Console.
  • Fixed an issue that prevented addition of a group in the Storage Spaces Direct 2016 management pack dashboard.
  • SCOM Network Device Re-Discovery now probes for SNMP V3 devices too.
  • Fixed re-registering for SNMP Traps in the Proxy Management Server.
  • Windows Computer Property “NetbiosDomainName” is not discovered properly.
  • SCOM console crashes while trying to connect to Azure Log Analytics and Azure Monitor.
  • Linux agent is not able to get the correct version and port details for JBoss EAP 7.1.
  • An issue that lead to creation of multiple empty temp files in the /tmp directory of Linux servers has been fixed.
  • Fixed the formatting issue with the output for the task ‘Top10 CPU Processes’ when using Windows Management Infrastructure (MI) APIs.
  • XPlat agent now supports monitoring of SUSE-11 SP4 platform with Security Module installed on it for TLS 1.2 compliance.
  • Fixed an issue that caused the corruption of /etc/login.cfg file on AIX 7 machines during install/upgrade of the agent.
  • AIX Agent is now transitioned to 64-bit package to accommodate more stack and heap space if needed to avoid any stack/heap overflow which occasionally leads to heartbeat failure.
  • Free memory calculation accommodated appropriately on RHEL-7 platform.

SCOM 2016: Update Rollup 6 released

A brief overview of the recently released UR6 for SCOM 2016 – get it here

Updates and Fixes

  • Application pool crashes and SharePoint application crashes because of APM agent and the profiler are now fixed. These occurred because the profiler was always on. This issue is fixed by disabling the profiler by default and enabling it only when APM is configured.Note If you’re using APM, restart IIS after you deploy the patches.
  • Improved logging to display error messages and suggest that you check performance counters when PdhExpandWildCardPath fails.
  • Fixed: Session Events tab in Application Diagnostics web console doesn’t display any data.
  • Fixed: Scheduled Maintenance Mode doesn’t work in an availability group that uses SQL Always-On configuration. In case of a failover to a secondary node, the Maintenance Mode Schedules that are created on the primary node don’t run. This has now been fixed. For details, see the “Enabling Schedule Maintenance Mode with SQL Always ON” section.
  • Updated fix: The Get-SCOMGroup cmdlet is slow to query large (more than 2,000) groups. A previous fix has been improved for faster querying of any number of groups.
  • Fixed: Users could not edit the Maintenance Schedule in the SCOM console if all the objects were removed. The schedule can now be edited. However, it cannot be saved unless it contains at least one object.
  • Fixed: SCX cannot connect with Linux machine if the KEX algorithms are configured as any of the following: ecdh-sha2-nistp256diffie-hellman-group-exchange-sha256, or diffie-hellman-group14-sha256.
  • Fixed: Using MI APIs causes MonitoringHost.exe to crash. This event is logged in the Application log, but no crash events are reported in the Operations Manager event log. After this fix, MonitoringHost doesn’t crash even if the useMIAPI registry key is enabled.
  • OMS (now Azure Log Analytics) connection onboarding wizard isupdated to communicate with the new APIs. This is because the OMS services were moved to the Azure Portal (link), and also because of the planned retirement of the OMS portal. This change will not affect any existing connection to OMS. However, for new connections or to reconfigure existing connections, the relevant management packs that are bundled together with this update rollup must be imported.
  • This update rollup creates a new “omi” user (system account).
  • XPlat support matrix changes:
    • SLES 10 is not supported.
    • CentOS 5 is not supported.
    • AIX 6.x is not supported.

SCOM 1807: What you need to know and yes it’s available!

The first update for System Center Operations Manager has just been released, what do you need to know about SCOM 1807?

Updates work the same way as the Update Rollups you are used to you can use windows update or get the packages manually here

First what’s fixed?

Issues that are fixed and improvements that are included


  • Fixes an issue that sometimes cause the Performance widget in the web console to throw an ArgumentExceptionmessage.
  • Fixes an issue that prevented the Alert view URL in the notification channel from to pointing to the new drill-down Alert page.
  • Fixes an issue that causes the web console to throw an ArgumentException message when the state widget is added to a dashboard or scoped to a specific group.
  • Improvement to the web console so that is now supports nondefault ports.
  • Fixes an issue that causes the pseudo file system to be enumerated.
  • Fixes an issue that caused the DNS 2016 Management Pack to throw false alerts for “DNS unused Zone Detected.”
  • Fixes an issue that caused the MySQL version to be listed as “for,” “on,” or NULL in Detail view for some platforms.
  • Improvement that enables Monitoring Solaris 10 Agents (x86) to provide heartbeat alerts and configuration errors about the SSL certificate.
  • Fixes an issue that prevented the Operations Manager console, the Service Manager console and PowerShell modules to coexist on the same server.Note Both Operations Manager and Service Manager must be upgraded to version 1807 to resolve this issue.
  • Fixes an issue in which Active Directory Integration rules were not visible or editable in an upgraded 2016 Management Group. This issue prevented the ongoing management of Active Directory integration assignment in the upgraded Management Group.
  • Fixes an issue that caused the system and MonitoredBy information to be displayed incorrectly in the Unix/Linux Computers view when the UNIX host name on the server is lowercase.
  • Fixes an issue that caused Active Directory integrated agents not to display correct failover server information.
  • Fixes an issue in Performance views in the web console that caused the selection of counters not to persist after a web console restart or refresh.
  • Fixes an issue in which the PowerShell cmdlet Get-SCXAgent fails and returns a “This cmdlet requires PowerShell version 3.0 or greater” error.
  • Fixes an issue in which a group name is changed through the operations console, the Get-SCOMGroup cmdlet does not retrieve the group data that includes the changed group name.
  • Fixes an issue that causes error HTTP 500 to occur when you access Diagram view through the web console.
  • Improvement in which the SQLCommand Timeout property is exposed so that it can be dynamically adjusted by users to manage random and expected influx of data scenarios.
  • Fixes an issue that caused the MonitoringHost process to crash and throw the exception “System.OverflowException: Value was either too large or too small for an Int32.”
  • Fixes an issue when company knowledge is edited by using the Japanese version of Microsoft Office through the Operations Manager console, you receive the following error (translated into English): “Failed to launch Microsoft Word. Please make sure Microsoft Word is installed. Here is the error message: Item with specified name does not exist.”
  • Fixes an issue that causes Microsoft.SystemCenter.ManagementPack.Recommendations to log errors on instances of Microsoft SQL Server that have case-sensitive collations.

And then what’s new?

  • Improvements to the HTML5 webconeole experience including:
    • Addition of a Powershell widget
    • Create HTML5 dashboards in MyWorkspace.
    • View HTML5 Network Node and Network Interface dashboards.
    • Create maintenance schedules from the HTML5 web console.
  • You can now enable or disable APM when pushing the agent from the console.
  • The Linux agent now supports Log rotation monitoring
  • Support for SQL 2017, there is a catch however you will need to update your existing SCOM to 1807 before you can upgrade your SQL to 2017

SCOM 2016: UR5 Released

Update Rollup 5 for SCOM 2016 has been released.

As usual you can get it from the catalog here or through windows update.

all in all this looks like a good update and solves a few persistent issues form previous versions.

Updates and Fixes


  • SCOM console and Service Manager console for PowerShell modules can now coexist on the same server.Note Both SCOM Update Rollup 5 (this update) and Service Manager Update Rollup 5 (update KB 4093685) must be installed to resolve this issue.
  • Active Directory Integration rules are not visible or editable in an upgraded 2016 Management Group. This prevents the ongoing management of Active Directory integration assignment in the upgraded Management Group.
  • When the UNIX host name on the server is in lowercase, the OS and MonitoredBy information is displayed incorrectly in the Unix/Linux Computers view.
  • Active Directory integrated agents do not display correct failover server information.
  • Performance views in the web console do not persist the selection of counters after web console restart or refresh.
  • The PowerShell cmdlet Get-SCXAgent fails with error “This cmdlet requires PowerShell version 3.0 or greater.”
  • During the upgrade from SCOM 2016 to SCOM 1801, if the reporting server is installed on a server other than the management server, the upgrade fails. Additionally, you receive the error message, “The management server to which this component reports has not been upgraded.”
  • If a group name has been changed through the operations console, the Get-SCOMGroup cmdlet does not retrieve the group data that includes the changed group name.
  • Error HTTP 500 occurs when you access Diagram view through the web console.
  • When you download a Linux management pack after you upgrade to SCOM 2016, the error “OpsMgr Management Configuration Service failed to process configuration request (Xml configuration file or management pack request)” occurs.
  • The SQLCommand Timeout property is exposed so that it can be dynamically adjusted by users to manage random and expected influx of data scenarios.
  • The MonitoringHost process crashes and returns the exception “System.OverflowException: Value was either too large or too small for an Int32.”
  • When company knowledge is edited by using the Japanese version of Microsoft Office through the SCOM console, the error (translated in English) “Failed to launch Microsoft Word. Please make sure Microsoft Word is installed. Here is the error message: Item with specified name does not exist” occurs.
  • Accessing Silverlight dashboards displays the “Web Console Configuration Required” message because of a certificate issue.
  • Microsoft.SystemCenter.ManagementPack.Recommendations causes errors to be logged on instances of Microsoft SQL Server that have case-sensitive collations.
  • Deep monitoring displays error “Discovery_Not_Found” if the installation of JBoss application server is customized.
  • Adds support for the Lancer driver on IBM Power 8 Servers that use AIX.
  • The ComputerOptInCompatibleMonitor monitor is disabled in the Microsoft.SystemCenter.Advisor.Internal management pack. This monitor is no longer valid.

SCOM 2016: Update Rollup 4 released!

UR4 for SCOM 2016 is out you can get it here or through windows update.

As usual test before implementing in your production environment and take special note of the known issues.

 

Issues that are fixed and improvements

  • When a log file is being monitored by SCOM, Monagent locks the file and won’t allow it to be renamed.
  • Adds support for TLS 1.2. For more information about how to set up, configure, and run your environment with TLS 1.2, see the following article in the Microsoft Knowledge Base:
    4051111 TLS 1.2 Protocol Support Deployment Guide for System Center 2016
  • Addresses an issue in which the APM AppDiagnostics console fails to create a Problem Management rule due to a FormatException. The appropriate string is now used for formatting, and the Problem Management wizard is able to run without issues.
  • This update resolves an issue that causes a crash of IIS application pools that are running under CLR 2.0 when the APM feature is installed on the server as part of SCOM Agent. The code now uses appropriate memory instructions, based on the CLR version.
  • Failure of GetOpsMgrDBWatcherDiscovery.ps1 script causes the Monitoring Host to crash.
  • WMI Health monitor doesn’t work if WINRM is configured to use https only.
  • SCOMpercentageCPUTimeCounter.ps1 script generates WMI errors that are caused by Service Principle Name (SPN) configuration issues.
  • WMI Health monitor doesn’t work if SPN http://servername is set to a user account.
  • Product knowledge of “Windows Cluster Service Discovery” includes an incorrect reference to “Windows NT.”
  • After a network outage, the management server does not reconnect to the gateway server if the gateway server was installed with the /ManagementServerInitiatesConnection=True option.
  • A configuration change to the network device triggers a rediscover of the device, and this process changes the SNMP agent address.
  • The UseMIAPI registry subkey prevents collection of custom performance rules data for all Linux servers.

Known issues

  • During Audit Collection Services (ACS) update or removal, the Audit Collection Services Collector Setup wizard is incorrectly titled “System Center Operations Manager 2012 Audit Collection Server.”
  • When you access Silverlight dashboards, a “Web Console Configuration Required” message is displayed.

    To work around this issue, follow these steps:

    1. Click Configure in the dialog box.
    2. When you are prompted to run or save the SilverlightClientConfiguration.exe file, click Save.
    3. Run the SilverlightClientConfiguration.exe file.
    4. Right-click the .exe file, click Properties, and then select the Digital Signatures tab.
    5. Select the certificate that has Digest Algorithm as SHA256, and then click Details.
    6. In the Digital Signature Details dialog box, click View Certificate.
    7. In the dialog box that appears, click Install Certificate.
    8. In the Certificate Import Wizard, change the store location to Local Machine, and then click Next.
    9. Select the Place all certificates in the following store option and then select Trusted Publishers.
    10. Click Next and then click Finish.
    11. Refresh your browser window.

SCOM 2016: Update Rollup 3 Released

UR 3 for SCOM 2016 is out  you can get it through windows update or in the Catalogue here.

As always test in your labs before deploying to production systems.

Fixes in this update:

  • When you run System Center 2016 Operations Manager in an all-French locale (FRA) environment, the Date column in the Custom Event report appears blank.
  • The Enable deep monitoring using HTTP task in the System Center Operations Manager console doesn’t enable WebSphere deep monitoring on Linux systems.
  • When overriding multiple properties on rules that are created by the Azure Management Pack, duplicate override names are created. This causes overrides to be lost.
  • When the heartbeat failure monitor is triggered, a “Computer Not Reachable” message is displayed even when the computer is not down.
  • The Get-SCOMOverrideResult PowerShell cmdlet doesn’t return the correct list of effective overrides.
  • When creating a management pack (MP) on a client that contains a Service Level (SLA) dashboard and Service Level Objects (SLO), the localized names of objects aren’t displayed properly if the client’s CurrentCulture settings don’t match the CurrentUICulture settings. In cases where the localized settings are English English, ENG, or Australian English, ENA, there’s an issue when the objects are renamed.
  • The Event ID: 26373 error, which may cause high memory consumption and affect server performance, has been changed from a “Critical” message to an “Informational” message.
  • The Application Performance Monitoring (APM) feature in System Center 2016 Operations Manager Agent causes a crash for the IIS Application Pool that’s running under the .NET Framework 2.0 runtime. Microsoft Monitoring Agent should be updated on all servers that use .NET 2.0 application pools for APM binaries update to take effect. Restart of the server might be required if APM libraries were being used at the time of the update.
  • The UseMIAPI registry subkey prevents collection of processor performance data for RedHat Linux system. Also, custom performance collection rules are also impacted by the UseMIAPI setting.
  • Organizational Unit (OU) properties for Active Directory systems are not being discovered or populated.
  • The Microsoft.SystemCenter.Agent.RestartHealthService.HealthServicePerfCounterThreshold recovery task fails to restart the agent, and you receive the following error message:
    LaunchRestartHealthService.ps1 cannot be loaded because the execution of scripts is disabled on this system.

    This issue has been resolved to make the recovery task work whenever the agent is consuming too much resources. 

  • The DiscoverAgentPatches.ps1 script in Microsoft.SystemCenter.Internal.xml fails and you experience the following exception:
    Exception:
    Method invocation failed because [System.Object[]] does not contain a method named ‘op_Subtraction’.
    At C:\bin\scripts\patch.ps1:37 char:35
    +                   for($count = 0; ($productList.Count-1); $count++)
    +                                   ~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (op_Subtraction:String) [], RuntimeException
    + FullyQualifiedErrorId : MethodNotFound 

  • An execution policy has been added as unrestricted to PowerShell scripts in Inbox management packs.
  • SQL Agent jobs for maintenance schedule use the default database. If the database name is not the default, the job fails.
  • This update adds support for OpenSSL1.0.x on AIX computers. With this change, System Center Operations Manager uses OpenSSL 1.0.x as the default minimum version supported on AIX, and OpenSSL 0.9.x is no longer supported.