Hello folks,
I am glad to share with you that Microsoft just released Update Rollup 8 (UR8) for System Center 2016.
Please find the description for each component that are fixed in System Center 2016 UR8 including the bugs that are fixed in System Center 2016 Virtual Machine Manager (SCVMM), and System Center 2016 Data Protection Manager (SCDPM).
System Center 2016 components that are fixed in Update Rollup 8 are the following:
Virtual Machine Manager 2016 UR8 (KB4518885 & KB4518886):
You can obtain and install the update package from Windows Update directly, Windows Server Update Services (WSUS), or you can go to the following websites and manually download the update packages from the Microsoft Update Catalog:
- Download the Virtual Machine Manager Server update package now.
- Download the Administrator Console update package now.
This UR update has a significant payload for VMM 2016, you can find the issues fixed below (around 20 bugs fixed and functionality updates):
- Service deployment through VMM fails if the domain name provided is greater than 15 characters.
- ‘Get-SCServicingWindow’ PowerShell commandlet fails to return active servicing windows if ‘-ServicingWindowFilter’ parameter is passed with the value ‘now’.
When importing a Vmware template for Windows Server 2016, ‘OS Configuration’ option is missing.- Note:
- Once the VMM 2016 UR8 patch is applied, VMware templates needs to be removed and re-imported after a VM refresher job is run for ‘OS configuration’ option to show-up. VM refresher job runs every 30 minutes by default.
- Virtual Machine performance counters in VMM fails to refresh.
- Bare Metal Deployment fails with the error ‘There was an error communicating with the endpoint. The server name or address could not be resolved’.
- When a host in untrusted domain is managed by VMM, events with ID ‘15030’ and ‘17140’ is logged in ‘Microsoft-Windows-Hyper-V-VMMS/Admin’ event channel every 30 minutes.
- Cross Cluster Migration fails for highly available VMware VMs managed in VMM.
- VMM does not detect the OS version of Windows client if the version is 1709 or greater.
- QOS settings set out of band is overwritten by VMM.
- Operations performed on a VM may fail in an environment which uses DHCP for IP address assignment while having VMM manage the same IP address range.
- Concurrent operations on Network Controller managed VMs may fail.
- Network Interface Card properties set OOB may get overwritten by a VMM VM refresher job in SDN v2 environment.
- The VLAN/subnet pairs under ‘Logical network connectivity’ sub-menu of Host Network adapter properties are unselected.
- VMM console crashes when a self-service user enumerates properties of a VM with shared disk.
- Updates to memory and processor of a VM fails when an update is performed on VM disk at the same time.
- SCVMM service may crash when multiple VMs are created concurrently.
- Deprecated VMM MP classes are instantiated when VMM is integrated with Operations Manager 2016 and above.
- Multiple VMs can be deployed concurrently from a VM stored in VMM Library Server.
- Performance improvements in time taken for Static IP pool creation.
After you download and install Update Rollup 8, VMM 2016 will be updated to Version: 4.0.2589.0 as well as the agent version on the managed Hyper-V host.
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
}
Data Protection Manager 2016 UR8 (KB4511102)
See the following Knowledge Base article for details about these fixes and installation instructions:
KB4511102 Update Rollup 8 for System Center 2016 Data Protection Manager.
This update includes a small number of fixes as follows:
- Data Protection Manager service crash with error “The directory is not empty” while failing to delete a replica path during the Garbage Collection process.
- Restore Operation for SQL workloads fails with an error “Consolidation of recovery points of the replica failed” due to timeout. Introduced registry key to extend timeout value. Refer More Information section for additional details.
- The backup operation fails when Certificate based authentication is configured and Null Ciphers are disabled.
- SharePoint backup fails when SQL server is different domain. Refer More Information section for additional details.
Please note that a fresh installation of the Update Rollup 8 of the DPM Agent could cause a restart of the protected server.
Do you learn more about System Center Data Protection Manager and Microsoft Azure Backup Server? I highly encourage you to check my recent published booked here.
Operations Manager 2016 UR8 (KB4514877)
See the following Knowledge Base article for details about these fixes and installation instructions. This update includes a large number of fixes.
KB4514877 Update Rollup 8 for System Center 2016 Operations Manager.
Orchestrator 2016 UR8 (KB4518887)
See the following Knowledge Base article for details about these fixes and installation instructions:
KB4518887 Update Rollup 8 for System Center 2016 Orchestrator.
Service Manager 2016 UR8 (KB4516987)
See the following Knowledge Base article for details about these fixes and installation instructions:
KB4516987 Update Rollup 8 for System Center 2016 Service Manager.
Service Management Automation
There are no updates to Service Management Automation 2016 in Update Rollup 8.
Service Provider Foundation
There are no updates to Service Provider Foundation 2016 in Update Rollup 8.
How to obtain and install Update Rollup 8 for System Center 2016?
Please see each KB article above to obtain the specific installation instructions for each component.
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-
