Good news! The Update Rollup 6 for Microsoft System Center 2016 has been released.
The Update Rollup 6 will include fixes for the following System Center components:
- Data Protection Manager
- Operations Manager
- Virtual Machine Manager
Data Protection Manager (DPM)
This update fixes the following issues:
- Virtual Hard Disk (VHD) missing during mount or unmount operations.
- VHD mount or unmount takes a long time to finish.
- Data Protection Manager performance is decreased because of multiple update agent jobs.
- Data Protection Manager console crashes while recovering data from online recovery points.
- Data Protection Manager crashes when you move protected clients to another disk.
- Data Protection Manager System State and Bare Metal Recovery (BMR) fails intermittently for multiple servers.
- Indefinite looping occurs for consistency check jobs for Resilient Change Tracking (RCT) on a virtual machine (VM) because of I/O errors.
- Update Rollup 5 for Data Protection Manager 2016 cannot enumerate SQL Server 2017 Availability Group databases for protection.
- Data Protection Manager 2016 Update Rollup Agent causes a restart of the protected server.
Note: A fresh installation of the Update Rollup Agent could cause a restart of the protected server.
Operations Manager (SCOM)
Improvements and issues that are fixed
- 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-nistp256, diffie-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.
- From this release onwards, customers have the option to install only scxagent. After scxagent is installed, there will be new “nologin” user and “omi” group.
- XPlat support matrix changes:
- SLES 10 is not supported.
- CentOS 5 is not supported.
- AIX 6.x is not supported.
Issues that are fixed:
- Configuration of “Get Service Status” is not saved after a check-in.
- “Write to Database” activity does not work if TLS 1.2 is enforced.
- Send platform event activity does not log the event after you upgrade to UR5 and the SCO database is reconfigured.
Virtual Machine Manager (SCVMM)
Issues that are fixed:
- Virtual Machine (VM) performance data for CPU Average and Assigned Memory displayed in the console is not reliable.
- VMs that have the same computer name are created when you try to create multiple VMs by using the # wildcard character in the name.
- VMM Run As accounts that are used for host management require Interactive logon rights. Interactive logon is no longer required.
- VM templates sometimes cannot be created from Gen-1 VMs through Windows 10 and Windows Server, version 1709 64-bit editions.
- Adding a storage device by using an SMP provider through the VMM UI fails.
- New-SCVirtualMachine PowerShell cmdlet does not honor the specified value set for DynamicMemoryMinimumMB when you create a VM.
- Simultaneous migrations of VMs that are connected to HNV version 1 VM networks cause network disconnection.
- SCVMM does not update host SMBIOS ID property after a BIOS update.
- VMM UI crashes when the physical disk is removed from storage pool if pool classification is not set.
- Host Refresh takes a long time after you upgrade VMM 2016 to Update Rollup 5.
Selecting clouds while scoping a user role does not work as intended if the scroll bar is enabled in the details pane.
- Bare Metal Deployment fails on hosts that have converged NICs.
- If you elect not to limit the bandwidth that’s available for Remote Access Gateway connections that are managed by SDN in the SCVMM UI, the available bandwidth is set to a default value.
- The VMM console does not open or takes a long time to open if you log on as Administrator or if you use the Delegated Administrator user role.
- “PRO Dynamic Memory VM Pressure” alerts are generated for VMs that have static memory that’s hosted on Windows Server 2016 Hyper-V servers.
- VMM 2016 Update Rollup 6 supports ESXi 6.5 hosts.