Microsoft released the Update Rollup 10 for System Center 2012 R2.
Update Rollup 9 contains Fixes and Updates for SCDPM, SPF, VMM, Windows Azure Pack.
As we know, there is the possibility that the actual Update Rollup can contain some Bugs, so maybe wait a few days to install, or try it on a Test Environment.
Get all Information’s about Update Rollup 10 for System Center 2012 R2:
Here are some Details
System Center Data Protection Manager (KB3164172)
- If you try to exclude a page file for a VM running on Microsoft Hyper-V Server 2012 R2 server, DPM may still continue to back up the page file.
- DPM provides an Active Directory schema extension tool to make required changes to Active Directory for DPM End-User Recovery. However, you may the tool may not work on System Center 2012 R2 Data Protection Manager.
- If you try to protect a SharePoint content database that has Always On enabled, and there is a failover of the database, you may notice that new sites, lists, and items are not displayed on the Recovery tab. This applies only to new items that are created after failover. Additionally, the issue is automatically resolved after failback.
- If you run Update Rollup 7 for System Center 2012 R2 Data Protection Manager, or a later version, and then try to do item level recovery for a Hyper-V VM, you may receive the following error message when you click the VHDX file on the Recovery tab:
DPM Cannot browse the contents of the virtual machine on the protected computer DPMServerName.
- The DPM Console crashes when you try to open any of the six built-in DPM reports.
- Optimized item level recovery doesn’t work for a SharePoint farm. This causes the full farm data to be copied to the staging server that’s running Microsoft SQL Server.
- The DPM UI crashes when you try to recover online recovery points by using another DPM server that is registered to the same backup vault as the original server.
- The Get-DPMJob cmdlet does not provide any information about recovery jobs that are performed through the external DPM server.
- This update revises the message of error code 33504 to add details about the issue and steps to resolve the issue.
- If you try to protect Microsoft Exchange Server 2016 while you create a protection group, the server that’s running Exchange Server is displayed as „Exchange 2013 Database“ instead of „Exchange 2016 Database.“
- If you use the DPM Central console, and you receive an EvalShareInquiryAlert (3123) alert on DPM, the alert is still displayed as active in System Center Operations Manager even though the issue is resolved on DPM.
- DPM crashes when you try to configure SMTP settings.
- If you try to stop protection of a data source in which the FQDN contains more than 64 characters, the DPM service crashes.
Michael Seidl aka Techguy