Category Archives: Update Rollup

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.

SCOM and Deprecating SHA1 Certificates what you need to know!

With the recent deprivation of SHA1 certificates in favour of the more secure SHA2 it’s important to know that SCOM uses  SHA1 to manage workloads for cross platform monitoring (Unix / Linux).

Have no fear the MS SCOM team have released an article on how to replace your existsing SHA-1 certificates with the newer SHA256 certificates.

It is important to note that you will need to update your 2012 R2 environments to UR 12 and your 2016 environments to UR2 respectivly in order to use the new SHA256 certificates by default.

The article is available here

SCOM 2016: UR2 has been released!

Update rollup 2 for the remaining System Center products is out! Get it here or through the Windows Update.

As always test before deploying to your production environment!

New, Fixed and Improved

 

    • When you use the Unix Process Monitoring Template wizard (adding a new template) to monitor processes on UNIX servers, the monitored data is not inserted into the database because of the following failure:

      Log Name: Operations Manager
      Source: Health Service Modules
      Date:
      Event ID: 10801
      Task Category: None
      Level: Error
      Keywords: Classic
      User: N/A
      Computer:
      Description: Discovery data couldn’t be inserted to the database. This could have happened because of one of the following reasons:
      – Discovery data is stale. The discovery data is generated by an MP recently deleted.
      – Database connectivity problems or database running out of space.
      – Discovery data received is not valid.

      The following is the underlying exception that causes this issue:

Exception type: Microsoft.EnterpriseManagement.Common.DataItemDoesNotExistException Message: ManagedTypeId = ccf81b2f-4b92-bbaf-f53e-d42cd9591c1c InnerException: StackTrace (generated): SP IP Function 000000000EE4EF10 00007FF8789773D5 Microsoft_EnterpriseManagement_DataAccessLayer!Microsoft.EnterpriseManagement.DataAccessLayer.TypeSpaceData.IsDerivedFrom(System.Guid, System.Guid)+0x385

 

  • When a management server is removed from the All Management Servers Resource Pool, the monitoring host process does not update the TypeSpaceCache.
  • When alerts are closed from the Alerts view after you run a Search, the closed Alerts still appear in the View when the Search is cleared.
  • When you press Ctrl+C to copy an alert in Operations Manager Alert view and then press Ctrl+V to paste it to Notepad, the Created time is in UTC time, not local time.
  • Groups disappear from Group view after they are added to a Distributed Application.
  • IM notifications from Operating Manager to Skype fail when an incorrect exception causes NullReferenceException in the SipNotificationTransport.Send method.
  • When the maintenance mode option for the dependency monitor is set to “Ignore,” and the group (consisting of the server to which this dependency monitor is targeted) is put in Maintenance mode, the state of the monitor changes to critical and does not ignore maintenance mode.
  • Because of a rare scenario of incorrect computation of configuration and overrides, some managed entities may go into an unmonitored state. This behavior is accompanied by 1215 events that are written to the Operations Manager log.
  • Recovery tasks on “Computer Not Reachable” Operations Manager Monitor generate failed logons on SCOM Agents that are not part of the same domain as the management groups.
  • The ManagementGroupCollectionAlertsCountRule workflow fails and generates a “Power Shell Script failed to run” alert.
  • Get-SCOMGroup cmdlet fails when thousands of groups are created in Operations Manager.
  • Organizational unit properties for computers that are running Windows are not discovered or populated. This discovery is part of the System Center Internal Library MP. After this update, organizational unit properties will be discovered for all computers that are running Windows.
  • When the Operations Manager Health Service agent starts, and the agent is configured for AD integration, if the agent cannot contact Active Directory at all, it immediately goes dormant and stops trying to connect and obtain the policy from Active Directory.

Issues that are fixed in the UNIX and Linux management packs

  • SHA1 is deprecated, and SHA256 certificates are now supported on the management server that’s used to sign the Unix/Linux OMI certificate.
  • OMI does not work on Linux servers configured for FIPS compliance.
  • Avg. Physical disk sec/transfer performance counters are not displayed for Hewlett Packard computers.
  • OMI displays incorrect Memory information on Solaris 10 computers.
  • Network adapter performance is not displayed for SLES 12 x64 platform in the Operations Manager Console.
  • Cannot discover file systems on HPUX 11.31 IA-64 computers with more than 128 disks. Previously it supported only 128 VGs. Now support is extended to 256 VGs.
  • Deep monitoring cannot be started successfully on some JBoss applications because the discovery of the JBoss application server sets the Disk Path for the JBoss server incorrectly. Deep monitoring was not being started in JBoss stand-alone mode when a nondefault configuration was used.

SCOM 2012 R2: Update Rollup 12 Released

UR12 for SCOM 2012 R2 has been release as usual you can get it from the download catalog or through windows update.

Changes and fixes

    • 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.
( X ) Management Server Upgraded Check

The management server to which this component reports has not been upgraded.

    • 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:
      Log entry:

      Log Name:      Operations Manager
      Source:        Health Service Modules
      Date:
      Event ID:      10801
      Task Category: None
      Level:         Error
      Keywords:      Classic
      User:          N/A
      Computer:
      Description:    Discovery data couldn’t be inserted to the database. This could have happened because of one of the following reasons:
      – Discovery data is stale. The discovery data is generated by an MP recently deleted.
      – Database connectivity problems or database running out of space.
      – Discovery data received is not valid.

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

Exception:

Exception type:   Microsoft.EnterpriseManagement.Common.DataItemDoesNotExistException
Message:          ManagedTypeId = ccf81b2f-4b92-bbaf-f53e-d42cd9591c1c
InnerException:   <none>
StackTrace (generated):            SP               IP               Function            000000000EE4EF10 00007FF8789773D5 Microsoft_EnterpriseManagement_DataAccessLayer!Microsoft.EnterpriseManagement.DataAccessLayer.TypeSpaceData.IsDerivedFrom(System.Guid, System.Guid)+0x385

Changes and fixes for Unix and Linux

  • RHEL 7 on Power8 is now supported in System Center2012 R2 Operations Manager
  • 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.