In this article, we will share with you all the new features and components that were fixed and introduced in System Center 2019 Update Rollup 5.
Table of Contents
Introduction
Hello folks,
I am glad to share with you that Microsoft just released Update Rollup 5 (UR5) in spring 2023 for System Center 2019. After nearly 10 months, this is the fifth update rollup that Microsoft released for System Center 2019 Update Rollup (UR4) which was released back in June 2022.
Microsoft is committed to helping System Center customers better manage and modernize their data center environments, they have been releasing update rollups frequently for all System Center products and they will continue to do so in the future.
You can find the description for each component that is fixed in System Center 2019 UR5 including the new features that are included in System Center 2019 Virtual Machine Manager (SCVMM), and System Center 2019 Data Protection Manager (SCDPM) UR5.
The components that are fixed in System Center 2019 Update Rollup 5 are the following:
Virtual Machine Manager 2019 UR5
You can obtain and install the update package from Windows Update directly, or Windows Server Update Services (WSUS), or you can go to the following URLs and manually download the update packages:
- Download the Virtual Machine Manager Server update package now.
- Download the Administrator Console update package now.
The UR5 update has a small payload for VMM 2019, you can find the issues fixed below (around 5 bugs fixed and functionality updates):
- VMM Console crashes with OutOfMemoryException when maintenance mode is started on hosts.
- The Add-SCVMNetworkGateway Job takes a very long time(2~4 hours) to finish.
- SCVMM mixes up Max Bandwidth values for host NICs with the same name.
- Replica VM loses network connection after migration.VMMService causes UDP port exhaustion and crashes.
In addition to these, all the issues fixed in System Center 2019 VMM UR4 and prior URs for VMM 2016 are also fixed in System Center VMM 2019 UR5.
Improvements and new features in SCVMM 2019 UR5:
- Discover Arc-enabled SCVMM from the VMM console. Learn more about how to extend Azure Arc to System Center Virtual Machine Manager (SCVMM).
- VMware vSphere 7.0 & 8.0 and ESXi 7.0 & 8.0 support is added.
You can run the following PowerShell script that will help you to automate the VMM agent update on all your managed Hyper-V hosts and clusters.
# Get SCVMM Admin Account
$AdminAccount = Get-SCRunAsAccount -Name 'SCVMM Admin'
# Get Current SCVMM Agent Version
foreach ($VMMHost in (Get-SCVMMManagedComputer)){
Get-SCVMMManagedComputer | FT ComputerName, AgentVersion -AutoSize
}
# Update SCVMM Agent
foreach ($VMMHost in (Get-SCVMMManagedComputer)){
Update-SCVMMManagedComputer -VMMManagedComputer $VMMHost -Credential $AdminAccount -RunAsynchronously
}
# Confirm SCVMM Agent Version
foreach ($VMMHost in (Get-SCVMMManagedComputer)){
Get-SCVMMManagedComputer | FT ComputerName, AgentVersion -AutoSize
}Data Protection Manager 2019 UR5
➡(KB5024231)
This UR update has a significant payload for DPM 2019, you can find the issues fixed below (around 13 bugs fixed and functionality updates):
- DPM crashes with Null ShadowCopy error when protecting to tape.
- DPM secondary protection configuration fails with VSSError.
- DPM works in IPv4 and IPv6 mixed environments automatically without the PingBeforeConnect registry key.
- Restore of VMware VMs to alternate locations fails with InvalidRequestFault if NIC is missing.
- DPM reporting cannot send SMTP emails via port 587 or O365 directly.
- Restore of Hyper-V VMs fails when an ISO is attached to the VM.
- DPM item-level recoveries to the original location mark replica as inconsistent, requiring an additional consistency check.
- DPM takes an additional snapshot after Bare Metal Recovery backups.
- DPM backups of VMware VMs disk to tape skips .vmdk disks.
- DPM online backups are stuck in a pending state for many days.
- DPM consumes extra storage during Hyper-V VM backup by retaining checkpoint .avhdx files that are not required in the replica.
- Item level restore from a large online recovery point fails due to ISCSI timeout.
- DPM Storage Pool Volumes are erroneously marked as missing resulting in backup failure.
Improvements and new features that were introduced in SCDPM 2019 UR5:
- Support for SQL Server 2022: DPM 2019 UR5 supports the backup and protects SQL Server 2022.
- Backup support for Windows Server 2022: DPM 2019 UR5 supports the backup and protects Windows Server 2022.
- End of support for vSphere 5.5: vSphere 5.5 has reached the end of general support, thus DPM 2019 UR5 and later versions won’t support backups for VMware VMs on vSphere 5.5.
- Support for vSphere 7.0: DPM 2019 UR5 support backups for VMware VMs on vSphere 7.0.
- Support for Microsoft 365 SMTP: DPM 2019 UR5 supports Microsoft/Office 365 without a relay agent. For receiving notification alerts and reports over email, you can now use and configure port 587 in addition to port 25 for secure SMTP. Check how to configure Microsoft 365 SMTP for DPM.
- Increase maximum parallel online backups: With DPM 2019 UR5 and MARS agent version 9249 and later, you can increase the number of maximum parallel online backup jobs to Azure from the default eight to a configurable number using the following registry keys (this of course if your underlying hardware and network bandwidth can support it). The following registry key example will increase the limit to 12 jobs:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Azure Backup\DbgSettings\OnlineBackup]
"MaxParallelBackupJobs"=dword:0000000C
[HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Data Protection Manager\Configuration\DPMTaskController\MaxRunningTasksThreshold]
"6e7c76f4-a832-4418-a772-8e58fd7466cb"=dword:0000000CTo learn more about System Center Data Protection Manager and Microsoft Azure Backup, I highly encourage you to check my recently published book here.
Operations Manager 2019 UR5
➡ (KB5025123)
It’s worth mentioning that Azure SCOM Managed Instance is also available for SCOM UR5 in public preview!
The SCOM managed instance is a service that provides SCOM functionality on Azure and it can be used to monitor all your workloads, whether on-premises, in Azure, or in any other cloud service. It is a PaaS Service that takes away the pain of infrastructure monitoring and allows you to monitor all your workloads, wherever they are running.
Learn More: Create a SCOM Managed Instance deployment.
All the issues that were fixed in SCOM 2016 UR10 and the earlier hotfixes for SCOM 2019 are also included in SCOM 2019 UR5.
Please see the KB article below to obtain the specific installation instructions for each SCOM 2019 UR5 component.
Download 5025123 Update Rollup 5 for System Center 2019 Operations Manager.
For the full list of features that are released in Update Rollup 5 for SCOM, check What’s New in System Center Operations Manager 2019 Update Rollup 5.
Service Manager 2019
There are no updates to System Center Service Manager 2019 in Update Rollup 5.
System Center Orchestrator 2019
There are no updates to System Center Orchestrator 2019 in Update Rollup 5.
Service Management Automation 2019
There are no updates to Service Management Automation 2019 in Update Rollup 5.
Service Provider Foundation 2019
There are no updates to Service Provider Foundation 2019 in Update Rollup 5.
Please remember to try the update first in a dev/test environment before you install them in production!
__
Thank you for reading my blog.
If you have any questions or feedback, please leave a comment.
-Charbel Nemnom-
