Summary of changes in Configuration Manager current branch, version 2107
Applies to: Configuration Manager (current branch, version 2107)
Summary of KB10096997
Release version 2107 of Microsoft Endpoint Configuration Manager current branch contains various fixes and feature improvements. Issues that are fixed list below isn't inclusive of all changes. Instead, it highlights changes the product development team believes are most relevant to the broad Configuration Manager customer base. Many of these changes were made in response to customer feedback about product issues and improvements.
- Version 2107 is available as an in-console update that can be installed at the top-tier site in a hierarchy.
- For installation information, see Checklist for installing update 2107 for System Center Configuration Manager.
- For more information about the changes that are included in version 2107, see What's new in version 2107 of Configuration Manager current branch.
Hotfixes that are included in this update
- KB10036164: Update rollup for Microsoft Endpoint Configuration Manager current branch, version 2103
- KB10216365: Unable to move site database to SQL Always On availability group in Configuration Manager, version 2103
- KB10372804: Using the MBAM Agent to escrow BitLocker recovery keys generates excessive policies in Configuration Manager, version 2103
Issues that are fixed
- If you have a remote management point (MP) that's in a different time zone than its primary site, when you deploy an OS to clients that are communicating with this MP, it creates a duplicate record in the database.
- Either the task sequence progress bar or the task sequence debugger is not visible immediately after Setup Windows and ConfigMgr task until a restart occurs.
- Importing a task sequence which includes references to driver packages does not import the driver package ID. Because of this issue, you needed to edit the task sequence and manually specify the Driver Package in the Upgrade Operating System task.
- Content for applications deployed to client devices can incorrectly get removed from the client cache even when Persist content in the client cache option was set.
ContentLibraryCleanup.exe fails if any package is found missing on the distribution point, and reports an error resembling the following:
System.InvalidOperationException: This content library cannot be cleaned up right now because package <Package ID> is not fully installed. at Microsoft.ConfigurationManager.ContentLibraryCleanup.CLContentLibrary.LoadDistributedPackagesFromProvider() at Microsoft.ConfigurationManager.ContentLibraryCleanup.CLContentLibrary.LoadValidContentData()
ContentLibraryCleanup.exe takes a long time and may fail after 5 minutes with an error resembling the following:
System.Management.ManagementException: Unable to load valid packages. Please check the specified site server location and ensure you have access to the site server and the provider. ---> System.Management.ManagementException: Call cancelled at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext() at Microsoft.ConfigurationManager.ContentLibraryCleanup.CLContentLibrary.LoadPackageToContentFromProvider() at Microsoft.ConfigurationManager.ContentLibraryCleanup.CLContentLibrary.LoadValidContentData()
- Content download history data that powers the Client sources dashboard in the Configuration Manager console is discarded if the client is offline for more than 2 days.
Reassigning a distribution point to another primary site may fail if the server previous had a site system role which was uninstalled. A message resembling the following is recorded in the
Server is already part of SMS site <SiteCode>.
- When you use a remote content library, content for a package or operating system image is not deleted from the content library after you delete the object.
Configuration Manager Console
- After you select a device in the Devices node, the Collections tab does not populate any results if the user does not have access to the default security scope for operations.
- Collection Evaluation Queue shows incorrect count of collections in the Incremental Evaluation Queue.
- Clients on internet using a PKI certificate do not switch to the next available internet-based Management Point or Cloud management gateway after a communication failure occurs.
- Clients are incorrectly considered to be in coexistence mode if Intune enrollment fails.
Script to set up BitLocker portals (
MBAMWebSiteInstaller.ps1) fails if a custom report exists at the root of the report server. An error resembling the following is reported by the script:
Microsoft.ReportingServices.Diagnostics.Utilities.WrongItemTypeException: The operation you are attempting on item '<Custom Report Name>' is not allowed for this item type.
- When a software update point (SUP) is reconfigured to require SSL, clients that were scanning for software updates using that SUP may switch to another SUP.
Run summarization task for a software update deployment fails to run on the central administration site (CAS). An error resembling the following is reported in
*** exec spProcessSingleSummarizationRequests *** [Microsoft][SQL Server Native Client 11.0][SQL Server]Could not find stored procedure 'spTask_SUM_AssignmentComplianceEvaluator'. : spProcessSingleSummarizationRequests
- Software Update Point Synchronization status node in the console shows success even when a Microsoft 365 Apps Update failed to synchronize.
- An available software update deployment shows as Required in the Deployments tab under collection properties.
- Simulated client operation tasks performed to monitor scenario health are visible in the Client Operations node in the Configuration Manager console. These tasks are executed every 30 minutes by default, and fill up the Client Operations node.
- Registry entity in CMPivot does not return the value of the
The following dependent components that are included with Configuration Manager version 2107 are added or updated to the specified versions:
- Microsoft Edge WebView2 Redistributable to version 90.0.818.51
- Microsoft .NET Framework to version 4.6.2
- Microsoft Visual C++ 2015-2019 Redistributable to version 14.28.29914.0
- Xceed.wpf.avalondock.themes.metroaccent.dll to 188.8.131.52
- Xceed.wpf.themes.dll to 184.108.40.206
- Xceed.wpf.themes.metro.dll to 220.127.116.11
- Xceed.wpf.toolkit.themes.metro.dll to 18.104.22.168
- Microsoft.aspnet.odata.versioning.dll to 4.0.7242.29043
- Microsoft.aspnet.webapi.versioning.dll to 4.0.7242.29042