Update Rollup 3 for System Center 2019 is Now Available

4 Min. Read

In this article, I will share with you all the new features and components that were fixed in System Center 2019 Update Rollup 3.

Introduction

Hello folks,

I am glad to share with you that Microsoft just released Update Rollup (UR3) in 2021 for System Center 2019. This is the third update rollup that Microsoft released for System Center 2019 after the second Update Rollup (UR2) which was released in August 2020.

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

System Center 2019 UR3

The components that are fixed in Update Rollup 3 are the following:

Update Rollup 3 for System Center 2019 is Now Available 1 Virtual Machine Manager 2019 UR3➡(KB4599687 & KB4599688):

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:

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

  • When restoring VM from a checkpoint, the VLAN checkbox gets cleared out and the VM goes offline.
  • VMM Cluster Refresh job takes too long to complete when a large number of CSVs are assigned to the cluster.
  • Replication status is displayed incorrectly in the VMM console after replication is resumed after a failure.
  • PowerShell scripts defined in the Operations Manager MP are non-executable as there are no script engines.
  • VMM SCOM integration fails with multiple ‘DiscoveryDataInvalidRelationshipSource ExceptionOM10’ exceptions.
  • A critical exception is thrown when network site assignment is changed for a logical network definition in the VMM console.
  • VM creation doesn’t use the right virtual Switch when there are duplicate VLAN IDs associated with unique subnets.
  • VMM service account’s Temp folder (C:\Users\<vmm service account>\AppData\Local\Temp) fills continuously with temp files in .LOG1 and .LOG2 extensions.
  • Upgrading from 2019 RTM to UR1/UR2 fails with Microsoft.VirtualManager.DB.CarmineSql exception.
  • VM doesn’t get assigned an IP address when the IPv6 dynamic option is selected.
  • Removing VMM service fails intermittently as Remove -SCService job hangs at 99% completion.
  • VMM console crashes when selecting properties of an S2D cluster.
  • Upgrading to 2019 UR1 or UR2 fails with SQL exception error.

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

Improvements and new features in SCVMM UR3:

  • Performance improvement in managing Storage providers added as part of S2D cluster management at scale.
  • SCVMM 2019 UR3 also has introduced new features:

You can run the following PowerShell script that will help you to automate the VMM agent update on all your managed Hyper-V hosts.

# 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
}

Update Rollup 3 for System Center 2019 is Now Available 1 Data Protection Manager 2019 UR3➡(KB5001202)

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

  • Restore of Windows Server 2016 NTFS deduped volumes with DPM 2019 running on Windows Server 2019 results in corrupted files.
  • Volume to volume migration might fail if there are recovery points that got deleted from the disk.
  • Unable to re-protect the inactive BMR or system protection server workloads because the size calculation in wizard never completes.
  • Backup fails because the protection agent was temporarily unable to respond as it was in an unexpected state.
  • Backup fails due to the error: replica couldn’t be mounted or unmounted due to open handle on the replica.
  • The recovery point schedule is not displayed in the Protection Group summary for file-folder or volume backup.
  • DPM service crash occurs when DPMRA is forcefully disconnected, and DPM is unable to get the OS version of the protected machine while processing the backup failure.
  • Consistency check might fail with Access denied error, if there is another open handle by a different process, on the volume to be mounted by DPM.
  • DPM Management console might crash while creating a Protection Group when underlying storage is legacy storage.
  • In some scenarios, the DPM Management console might not display Protection Group details in the Details pane.
  • DPM Management console might crash, when navigating to alerts in the Monitoring tab or when the job information is getting updated on the Recovery wizard.
  • DPM Management console might crash when recovering VMware VMs using an External DPM server.
  • DPM Management console might crash while re-cataloging an imported tape that contains VMWare backups, and then click the Recovery tab.

In addition to the above fixes, all the issues fixed in SC DPM 2016 Update Rollup 10, and prior UR for DPM 2016 are also included in SC DPM 2019 UR3.

No new features were introduced in System Center 2019 Data Protection Manager UR3, it has only bug fixes!!! Check the following article to learn more about the latest features that were introduced in SCDPM 2019 UR2.

To learn more about System Center Data Protection Manager and Microsoft Azure Backup, I highly encourage you to check my recent published book here.

Update Rollup 3 for System Center 2019 is Now Available 1Operations Manager 2019 UR3➡(KB4594078)

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

4594078 Update Rollup 3 for System Center 2019 Operations Manager.

Update Rollup 3 for System Center 2019 is Now Available 1Orchestrator 2019 UR3➡(KB4599686)

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

4599686 Update Rollup 3 for System Center 2019 Orchestrator.

Update Rollup 3 for System Center 2019 is Now Available 1 Service Manager 2019

There are no updates to Service Manager 2019 in Update Rollup 3.

Update Rollup 3 for System Center 2019 is Now Available 1Service Management Automation 2019

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

Update Rollup 3 for System Center 2019 is Now Available 1Service Provider Foundation 2019

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

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

Use Azure VPN Gateway To Route Traffic Between Spoke Networks

Monitor Azure Storage Account Activity Log With Azure Sentinel

Next

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Subscribe to Stay in Touch

Never miss out on your favorite posts and our latest announcements!

The content of this website is copyrighted from being plagiarized!

You can copy from the 'Code Blocks' in 'Black' by selecting the Code.

Please send your feedback to the author using this form for any 'Code' you like.

Thank you for visiting!