|
| 1 | +--- |
| 2 | +title: Summary of changes in Configuration Manager current branch, version 2111 |
| 3 | +titleSuffix: Configuration Manager |
| 4 | +description: Article listing changes in Configuration Manager current branch, version 2111 |
| 5 | +ms.date: 12/9/2021 |
| 6 | +ms.prod: configuration-manager |
| 7 | +ms.technology: configmgr-core |
| 8 | +ms.topic: reference |
| 9 | +ms.assetid: 1e6a292d-2c26-4ef9-8c47-d1c2ac55917f |
| 10 | +author: bhuney |
| 11 | +ms.author: brianhun |
| 12 | +manager: dougeby |
| 13 | +--- |
| 14 | + |
| 15 | +# Summary of changes in Configuration Manager current branch, version 2111 |
| 16 | + |
| 17 | +*Applies to: Configuration Manager (current branch, version 2111)* |
| 18 | + |
| 19 | +## Summary of KB11052354 |
| 20 | +Release version 2111 of Microsoft Endpoint Configuration Manager current branch contains fixes and feature improvements. |
| 21 | +The "Issues that are fixed" list 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. |
| 22 | +*Note* There is no additional update for customers that installed the publicly available early update ring version of Configuration Manager 2111. The early update ring and globally available release are the same. |
| 23 | + |
| 24 | +##### Notes |
| 25 | +- Version 2111 is available as an in-console update that can be installed at the top-tier site in a hierarchy. |
| 26 | +- For installation information, see [Checklist for installing update 2111 for System Center Configuration Manager](../../core/servers/manage/checklist-for-installing-update-2111.md). |
| 27 | +- For more information about the changes that are included in version 2111, see [What's new in version 2111 of Configuration Manager current branch](../../core/plan-design/changes/whats-new-in-version-2111.md). |
| 28 | +- This globally available release contains all of the fixes summarized in the following article. |
| 29 | + |
| 30 | + KB [11121541](../../hotfix/2107/11121541.md): Update rollup for Microsoft Endpoint Configuration Manager current branch, version 2107 |
| 31 | + |
| 32 | +## Issues that are fixed |
| 33 | +<!-- 6014443 --> |
| 34 | +- The secondary site upgrade process may fail if the maximum SQL Express database size (10GB) is exceeded due to replication of unnecessary data. |
| 35 | + |
| 36 | +<!-- 8770341, 10874715 --> |
| 37 | +- Installation of BitLocker management portals fails under either of the following conditions. |
| 38 | + 1. A localized non-English version of SQL Server Reporting Services is installed on the site server. |
| 39 | + 2. SQL Server and SQL Server Reporting Services are installed on a remote server and running under the context of a domain service account. |
| 40 | + |
| 41 | +<!-- 9462655 --> |
| 42 | +- Client push installation fails under the following conditions. |
| 43 | + - The Allow connection fallback to NTLM option is not selected in Client Push Installation properties. |
| 44 | + - The site server machine account is not in the local admin group on the client. |
| 45 | + - The Restrict NTLM: Incoming NTLM traffic group policy is set to Deny all domain accounts. |
| 46 | + |
| 47 | +Under these conditions, client push fails with errors resembling the following in the ccm.log file. |
| 48 | + ```text |
| 49 | + Unable to connect to remote machine "{Client_name}" using Kerberos with machine account, error - 0x80070005 |
| 50 | + ``` |
| 51 | + |
| 52 | +<!-- 9559973 --> |
| 53 | +- The download of installation files by CCMSetup is now randomized across available distribution points within a boundary group. |
| 54 | + |
| 55 | +<!-- 9578895, 9578899 --> |
| 56 | +- Orchestration group post-installation scripts may run prior to a computer reboot, causing unexpected results during deployments. After the computer reboot, the scripts may not run until the next maintenance window. |
| 57 | + |
| 58 | +<!-- 9763593 --> |
| 59 | +- In large environments the process of uploading Endpoint Analytics data may block database reindexing tasks, leading to further performance issues. |
| 60 | + |
| 61 | +<!-- 9838506 --> |
| 62 | +- State message processing may fail when the messages contain failure codes for Windows Feature Updates, such as error 0xC1900208. When this happens errors resembling the following are recorded in the statesys.log file. |
| 63 | + ```text |
| 64 | + SQL MESSAGE: spProcessStateReport - Error: Record 1 returned an 'invalid record' return code and failed processing with error 8114: ERROR 8114, Level 16, State 5, Procedure spProcessSUMEnforcementMsg, Line 5, Message: Error converting data type nvarchar to bigint. |
| 65 | + ``` |
| 66 | + |
| 67 | +<!-- 9975366 --> |
| 68 | +- The **Endpoint Protection and software updates compliance - Historical** report can contain inaccurate data where compliant devices are recorded as non-compliant. |
| 69 | + |
| 70 | +<!-- 10041469 --> |
| 71 | +- The issue described in the following article could still happen if the management point was unable to process a client discovery data record (DDR); this is now fully resolved. |
| 72 | + |
| 73 | + [A client computer can steal the Configuration Manager GUID of an Unknown Computer object during imaging](/troubleshoot/mem/configmgr/unknown-computer-object-guid-stolen) |
| 74 | + |
| 75 | +<!-- 10415702 --> |
| 76 | +- The Active Directory Forest Discovery method fails if it receives a "The server is not operational" exception during the discovery process, leading to incomplete discovery results. An error resembling the following is recorded in the ADForestDisc.log file. |
| 77 | + ```text |
| 78 | + ERROR: [ForestDiscoveryAgent]: Discovery is being aborted due to an unexpected exception. |
| 79 | + ``` |
| 80 | + |
| 81 | +<!-- 10422235 --> |
| 82 | +- The availability of a service window is incorrectly checked when a dependent/ nested task sequence runs for a user. This leads to application deployment failures if a computer restart happens after the initial top-level task sequence runs. |
| 83 | + |
| 84 | +<!-- 10520849 --> |
| 85 | +- Full database reinitialization may happen for a primary site during the update process because of a timing issue. |
| 86 | + |
| 87 | +<!-- 10526961 --> |
| 88 | +- The management point role fails to install on a server if the Visual C++ runtime is newer than version 14.28. |
| 89 | + |
| 90 | +<!-- 11121626 --> |
| 91 | +- Configuration manager clients generate Event ID 4662 entries in the security event log every 30 seconds when the **Audit Other Object Access Events** policy is configured. |
| 92 | + |
| 93 | +<!-- 11862459 --> |
| 94 | +- The client registration process for Azure Active Directory-joined clients is improved to increase efficiency and reduce the likelihood of state message processing backlogs. |
| 95 | + |
| 96 | +<!-- 8881094 --> |
| 97 | +- Logging associated with state message processing is improved to include filenames by default, improving the ability to troubleshoot processing issues. |
| 98 | + |
| 99 | +<!-- 9714050 --> |
| 100 | +- Remote Configuration Manager consoles may display a connection error when returning after a period of inactivity. The connection error typically happens when trying to open a property window from a list view in the console but could also happen in other scenarios. Errors may include variations on any of the following: |
| 101 | + - Microsoft.ConfigurationManagement.ManagementProvider.SmsConnectionException |
| 102 | + The object invoked has disconnected from its clients. (Exception from HRESULT: 0x80010108 (RPC_E_DISCONNECTED)) |
| 103 | + - One or more errors occurred, results may be incomplete |
| 104 | + Microsoft.ConfigurationManagement.ManagementProvider.SmsConnectionException |
| 105 | + The RPC server is unavailable. (Exception from HRESULT: 0x800706BA) |
| 106 | + - Microsoft.ConfigurationManagement.ManagementProvider.SmsException |
| 107 | + The underlying connection was closed: An unexpected error occurred on a receive. |
| 108 | + - Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException |
| 109 | + The SMS Provider reported an error. |
| 110 | + - Microsoft.ConfigurationManagement.ManagementProvider.SmsMultipleResultException |
| 111 | + Failed to update one or more result object(s) |
| 112 | + |
| 113 | +<!-- 1238621 --> |
| 114 | +- A task sequence that installs a Windows feature update may fail on slower computers. The feature update does install correctly, but the task sequence fails after a computer restart. |
| 115 | + |
| 116 | +## Hotfixes that are included in this update |
| 117 | +- KB [11121541](../../hotfix/2107/11121541.md): Update rollup for Microsoft Endpoint Configuration Manager current branch, version 2107 |
| 118 | +- KB [12636660](../../hotfix/2107/12636660.md): Client Update for Microsoft Endpoint Configuration Manager version 2107 |
| 119 | + |
| 120 | +## Dependency changes |
| 121 | +The following dependent components that are included with Configuration Manager version 2111 are added or updated to the specified versions: |
| 122 | +- Microsoft Edge WebView2 Redistributable to version 94.0.992.37 |
| 123 | +- MBAM support files to version 2.5.1152.0 |
| 124 | +- AppInsights SDK components to version 4.6.28619.01 |
0 commit comments