Microsoft hat ein neues Update Rollup für System Center 2016 veröffentlicht.

Hier die Links auf die einzelnen Komponenten:

  • Data Protection Manager (SCDPM) -> KB4534063
  • Operations Manager (SCOM) -> KB4546986
  • Operations Manager – UNIX und Linux Monitoring -> kein Update
  • Orchestrator -> kein Update
  • Service Manager (SCSM) -> KB4546987
  • Service Management Automation -> kein Update
  • Service Provider Foundation -> kein Update
  • Virtual Machine Manager (SCVMM) -> KB4549434

Eine Übersicht dieses Updates ist hier verfügbar.

Kevin Holmann beschreibt hier, wie das Rollup eingespielt werden sollte.

Die Verbesserung für den Operationsmanager sind:

  • Fixed: On Windows Computer View of SCOM Console, Queries are optimized for better performance.
  • Fixed: We have updated SPROC to handle Alert Source Path Names which are greater than 512 in length. It was a mismatch where the table which was populating the DB was allowing larger strings while the table which was populated in this view took only 512. This caused data truncation and subsequently console crash.
  • Fixed: Made changes to the IP address parameter to support both IPv4 and IPv6 windows cluster.
  • Fixed: Fixed the issue with conversion of data smaller than 0.01 which was generated by Rule or Monitor. The data was transformed to a wrong (big) value on systems with OS locale language which has comma (“,”) instead of dot (“.”) as decimal format.
  • Fixed: Downtime duration will be calculated correctly for non-US time format in Downtime Report.
  • Fixed: fn_MPVersionDependentId creates an ID for each installed MP. The ID is a SHA1 hash of string “MPName, Version, Schema”. When the “Schema” part is omitted, it generates different hash which doesn’t match with the expected value. In the fix, “Schema=2” part is re-added in fn_MPVersionDependentId.
  • Fixed: We have made sure that correct end date for Availability, Health and Performance Details are shown in reports.
  • Enabled support for MSOLEDBSQL driver so that users may move from SQL Server Native Client. It is recommended to install Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL) to enable support for OLE DB Driver. This is most important to understand for TLS 1.2 enforced environments. Since SQL Native Client is deprecated and not supported for SQL 2016 and later, MSOLEDBSQL is the supported provider for access to SQL. Read more here: LINK
  • Fixed: Previously In UR8, we added support for customizing Memory Trimming on the Healthservice.exe process. The primary change in UR9 was adding this same capability to the MonitoringHost.exe processes. Description: In a scenario where SCOM monitors 100s of virtual machines hosted on a single Hyper-V server; every hour the MonitoringHost.exe of each Virtual machine will write into the VM page file simultaneously. Due to this concurrent paging, every hour disk I/O spikes. HealthService.exe and MonitoringHost.exe will continue to have Memory Trimming enabled by default on an hourly schedule. However, a new registry control option is provided to disable the memory trimming or control the duration:

Key: HKLM\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup\MonitoringHost\MemoryTrimming

REG_DWORD Decimal Value: Enable
SCOM default existing registry value: (not present)
SCOM default value in code = 1
Enable = 0 (trimming is disabled) Enable = 1 (trimming is enabled

REG_DWORD Decimal Value: DelayInSeconds
Time period in seconds the agent waits after initialization to start trimming
SCOM default existing registry value: (not present)
SCOM default value in code = 120

REG_DWORD Decimal Value: PeriodInSeconds
Recurring period in seconds at which the working set should be trimmed
SCOM default existing registry value: (not present)
SCOM default value in code = 3600
Minimum value = 3600 Maximum value = 4294967295