You dont have javascript enabled! Please enable it!

Update Rollup 4 for System Center 2019 is Now Available

4 Min. Read

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 4.

Introduction

Hello folks,

I am glad to share with you that Microsoft just released Update Rollup (UR4) in mid-2022 for System Center 2019. After more than one year, this is the fourth update rollup that Microsoft released for System Center 2019 Update Rollup (UR3) which was released in March 2021.

You can find the description for each component that is fixed in System Center 2019 UR4 including the new features that are included in System Center 2019 Virtual Machine Manager (SCVMM), and System Center 2019 Data Protection Manager (SCDPM) UR4.

The components that are fixed in System Center 2019 Update Rollup 4 are the following:

Virtual Machine Manager 2019 UR4

➡(KB5014156 & KB5014158)

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:

The UR4 update has a significant payload for VMM 2019, you can find the issues fixed below (around 20 bugs fixed and functionality updates):

  • VMM integration with SCOM connector causes high memory consumption.
  • Remediating a cluster fails with an error, “No suitable host is available for migrating the existing highly available virtual machines”.
  • Migrating or cloning a virtual machine from WS2019 to WS2016 fails with an error “VMM cannot migrate or clone the virtual machine Test Clone because the version of the virtualization software on the destination host is not compatible with the version of the virtualization software on the source host.”
  • Console crashes when one of the network adapters has missing uplink port profile configurations.
  • VLAN settings for the virtual network adapter are missing during VM migration.
  • CPU performance (%) graph on Fabric > Overview page incorrectly displays the value as 0%.
  • The server in maintenance mode stays online and is NOT paused in the cluster console.
  • VMM Console crashes after opening VM properties with an empty VM subnet.
  • Host Optimization task times out and fails with an error message, “An unknown error occurred while executing the PowerShell script. The connection to the VMM management server was lost”.
  • Unable to create file share in VMM 2019 UR3 using NetApp file share storage.
  • Unable to add a new network adapter and assign it to a VLAN-based network.
  • Static IP Pools are displayed more than once when there are greater than 30 network sites in a logical network.
  • Console crashes when a logical network has more than 30 network sites and multiple static IP pools.
  • Automatic Storage Dynamic Optimization jobs fail when VM is assigned to a cloud.
  • Unable to assign “VMNetwork with no VLAN” to VMs using VMM Console.
  • Console crashes when selecting properties of a Cluster in the SCVMM console.
  • VM with static MAC address created from Hyper-V host could not be restored from VMM due to MAC unavailability.
  • Orphaned checkpoint data causes a VMM console crash with Out Of Memory Exception.
  • V2V job calculates free space for wrong CSV Volume.
  • Trunk mode is incorrectly enabled for creating VMs with the HNV network.

In addition to these, all the issues fixed in System Center 2019 VMM UR3 and prior URs for VMM 2016 are also fixed in System Center VMM 2019 UR4.

Improvements and new features in SCVMM UR4:

  • Added support to manage Windows Server 2022 & Windows 11 guest virtual machines.
  • Smart card support has been added to enhanced session Mode in SCVMM Console.

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 UR4

➡(KB5014054)

This UR update has a significant payload for DPM 2019, you can find the issues fixed below (around 8 bugs fixed and functionality updates):

  • Restoring tapes with DPM 2019 UR3 for VMware VMs results in boot failure.
  • BMR backup is not handling replica creation correctly, which results in running out of disk space.
  • DPM 2019 does not detect resilient change tracking (RCT).
  • Online restore fails due to missing data source volume mapping.
  • DPM2019 UI crashes when searching files and folders under-recovery.
  • Unable to deploy or attach agent with Smart Card Authentication.
  • Post backup script fails to execute.
  • Unable to delete online data sources from either inactive or active protection group (due to malfunction of PIN functionality) while using Central Console.

Improvements and new features that were introduced in SCDPM UR4:

  • Removed File Catalog dependency for online backup of file/folder workloads: DPM 2019 UR4 removes the dependency on File Catalog which was needed to restore individual files and folders from the Online recovery points. DPM now uses the iSCSI mount method to provide individual file restoration. This also improves the backups time as the upload of file catalog metadata is not needed anymore.
  • Private endpoint support: With DPM 2019 UR4, you can use a private endpoint to take online backup to the Azure Backup Recovery Services vault.
  • Improvements VHDX mounting and unmounting: This improvement is done for VHDX file mounting and unmounting. To mount or unmount VHDX files, Microsoft now uses Win32 APIs by default. This is a change from the previous approach, which leveraged WMI.
  • Improved DPM reliability after DPM agent uninstallation: With DPM 2019 UR4, you can restore previously backed up data, even after DPM agent uninstallation. This is a big improvement.

Download 5014054 Update Rollup 4 for System Center 2019 Data Protection Manager.

To 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 UR4

➡(KB5013427)

Please see the KB article below to obtain the specific installation instructions for each component.

Download 5013427 Update Rollup 4 for System Center 2019 Operations Manager.

Service Manager 2019 UR4

➡(KB5013428)

Please see the KB article below to obtain the specific installation instructions for each component.

Download 5013428 Update Rollup 4 for System Center 2019 Service Manager.

Orchestrator 2019

There are no updates to System Center Orchestrator 2019 in Update Rollup 4.

Service Management Automation 2019

There are no updates to Service Management Automation 2019 in Update Rollup 4.

Service Provider Foundation 2019

There are no updates to Service Provider Foundation 2019 in Update Rollup 4.

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-

Related Posts

Previous

Migrate Gen1 to Gen2 VMs on Azure

Let me know what you think, or ask a question...

error: Alert: The content of this website is copyrighted from being plagiarized! You can copy from the 'Code Blocks' in 'Black' by selecting the Code. Thank You!