|
| 1 | +--- |
| 2 | +title: Update rollup for Microsoft Endpoint Configuration Manager version 2107 |
| 3 | +titleSuffix: Configuration Manager |
| 4 | +description: Update rollup for Configuration Manager 2107 |
| 5 | +ms.date: 10/27/2021 |
| 6 | +ms.prod: configuration-manager |
| 7 | +ms.technology: configmgr-core |
| 8 | +ms.topic: reference |
| 9 | +ms.assetid: 6fb1ecf7-f7fa-4221-a3af-a6165862e1cb |
| 10 | +author: bhuney |
| 11 | +ms.author: brianhun |
| 12 | +manager: dougeby |
| 13 | +--- |
| 14 | + |
| 15 | +# Update rollup for Microsoft Endpoint Configuration Manager version 2107 |
| 16 | + |
| 17 | +*Applies to: Configuration Manager (current branch, version 2107)* |
| 18 | + |
| 19 | +## Summary of KB11121541 |
| 20 | + |
| 21 | +This article describes issues that are fixed in this update rollup for Microsoft Endpoint Configuration Manager current branch, version 2107. This update applies both to customers who opted in through a PowerShell script to the early update ring deployment, and customers who installed the globally available release. For more information on changes in Configuration Manager version 2107, see: |
| 22 | + |
| 23 | +- [What’s new in version 2107 of Configuration Manager current branch](../../core/plan-design/changes/whats-new-in-version-2107.md) |
| 24 | +- [Summary of changes in Microsoft Endpoint Configuration Manager current branch, version 2107](../../hotfix/2107/10096997.md) |
| 25 | + |
| 26 | +This update also adds support for devices running Windows 11 ARM64. For more information, see [Support for Windows 11 in Configuration Manager](../../core/plan-design/configs/support-for-windows-11.md#windows-11-on-arm64). |
| 27 | + |
| 28 | +## Issues that are fixed |
| 29 | + |
| 30 | +<!-- 11892479 --> |
| 31 | +- After upgrading to version 2107, one or more applications in a task sequence fail with an error resembling the following in the `smsts.log`. |
| 32 | + |
| 33 | + ```text |
| 34 | + Install Static Applications failed, hr=0x87d00267 |
| 35 | + ``` |
| 36 | + |
| 37 | +<!-- 11993093 --> |
| 38 | +- Offline Servicing for Windows Server 2022 operating system image fails to detect updates as applicable. |
| 39 | + |
| 40 | +<!-- 10555301 --> |
| 41 | +- The **Installation Status** tab in Software Center hangs without loading completely. When this issue occurs, errors resembling the following are repeated in the `scclient.log`. |
| 42 | + |
| 43 | + ```text |
| 44 | + Getting all instances of CCM_Application |
| 45 | + Getting all instances of CCM_Program |
| 46 | + Getting all instances of CCM_SoftwareUpdate |
| 47 | + ``` |
| 48 | + |
| 49 | +<!-- 10692952 --> |
| 50 | +- The **CMTrace** log file viewer does not display all characters at the beginning of a line. |
| 51 | + |
| 52 | +<!-- 10732477 --> |
| 53 | +- Syntax highlighting for PowerShell ignores the back quote escape character (\`\) when escaping double quotation marks. |
| 54 | + |
| 55 | +<!-- 10732503 --> |
| 56 | +- The site server may stop processing state messages, resulting in a backlog of files, due to a primary key constraint violation. Errors resembling the following are recorded in the `statesys.log` file. |
| 57 | + |
| 58 | + ```text |
| 59 | + SQL MESSAGE: spProcessStateReport - Error: Message processing encountered a SQL error 2627 at record 100 for TopicType 500, StateID 1: "Violation of PRIMARY KEY constraint 'SR_MissingMessageRanges_PK'. Cannot insert duplicate key in object 'dbo.SR_MissingMessageRanges'. The duplicate key value is (123456, 112233).", Line 0 in procedure "" |
| 60 | + ``` |
| 61 | + |
| 62 | +<!-- 10732515, 10745070 --> |
| 63 | +- A console extension may fail to import with an error resembling the following recorded in the `AdminUI.ExtensionInstaller.log` file. |
| 64 | + |
| 65 | + ```text |
| 66 | + Return code indicates unhandled case. Result: Exception of type 'System.OutOfMemoryException' was thrown. |
| 67 | + ``` |
| 68 | + |
| 69 | +<!-- 10745061, 10745082 --> |
| 70 | +- The Configuration Manager console generates an exception when selecting **View Collection** from the Collections tab in the Devices node. The exception contains information resembling the following. |
| 71 | + |
| 72 | + ```text |
| 73 | + The requested object information could not be retrieved. Refresh the Configuration Manager console to verify that another administrator has not moved or deleted the object, or that the role-based administration security scopes or security roles for the object or current user have not changed. |
| 74 | + ConfigMgr Error Object: |
| 75 | + instance of __ExtendedStatus |
| 76 | + { |
| 77 | + Operation = "GetObject"; |
| 78 | + ParameterInfo = "SMS_DeviceCollectionMember.SiteID=\"{Site_ID}\""; |
| 79 | + ProviderName = "WinMgmt"; |
| 80 | + }; |
| 81 | + Error Code: |
| 82 | + NotFound |
| 83 | + ``` |
| 84 | + |
| 85 | +<!-- 10745095 --> |
| 86 | +- The Configuration Manager client is blocked from sending endpoint analytics sensor events to the management point. This happens when there are backlogs in the CCM_SensorMessageQueue in WMI. Errors resembling the following are recorded in the `SensorEndpoint.log` file. |
| 87 | + |
| 88 | + ```text |
| 89 | + Invoke SensorWmiProvider succeeded. |
| 90 | + QueryTraceW returned=234 for SensorFramework-Live-Etw... |
| 91 | + Failed to get the next message to send. 0x80041032 |
| 92 | + ``` |
| 93 | + |
| 94 | +<!-- 10748788 --> |
| 95 | +- The Configuration Manager console terminates unexpectedly if a Reporting Services Point is installed while the SQL Server Reporting Services (SSRS) service is stopped. The `AdminUI.log` file contains errors resembling the following. |
| 96 | + |
| 97 | + ```text |
| 98 | + System.ArgumentException |
| 99 | + Version string portion was too short or too long. |
| 100 | + ``` |
| 101 | + |
| 102 | +<!-- 10789923 --> |
| 103 | +- The **Configuration Manager Support Center Client Tools** application terminates unexpectedly on a Windows 11 computer selecting different deployments. |
| 104 | + |
| 105 | +<!-- 10789925 --> |
| 106 | +- The Cloud Management Gateway Azure Storage Account can now be configured to use TLS 1.2 through the Configuration Manager console. For more information, see [Enforce TLS 1.2](../../core/clients/manage/cmg/security-and-privacy-for-cloud-management-gateway.md#enforce-tls-12). |
| 107 | + |
| 108 | +<!-- 10800388 --> |
| 109 | +- Improvements to the Data Warehouse synchronization process are included to prevent the SQL Server TempDB from filling up. |
| 110 | + |
| 111 | +<!-- 10800703 --> |
| 112 | +- Endpoint analytics sensor data now includes the system SKU and processor name, and Microsoft Surface Model information, for Windows 11 hardware readiness. |
| 113 | + |
| 114 | +<!-- 10944353 --> |
| 115 | +- The cloud service configuration file (.csfg) is not updated after deploying a cloud management gateway. Errors resembling the following are recorded in the `CloudMgr.log` file. |
| 116 | + |
| 117 | + ```text |
| 118 | + ERROR: TaskManager: Task [UpdateServiceConfigurationTask: Service {ID}] has failed. Exception Hyak.Common.CloudException, ChangeDeploymentConfigurationOperationFailed: The Change Deployment Configuration operation failed for the domain '{ID}' in the deployment slot 'Production' with the name '{ID}-deployment': 'The specified configuration settings for Settings are invalid. Verify that the service configuration file is a valid XML file, and that role instance counts are specified as positive integers.'..~~ |
| 119 | + ``` |
| 120 | + |
| 121 | +<!-- 10959492 --> |
| 122 | +- Incremental collection updates don't work when the WQL statements contain custom properties. |
| 123 | + |
| 124 | +<!-- 10973090 --> |
| 125 | +- In some scenarios the maximum client policy size is incorrectly limited to 16MB instead of 32MB. This results in errors resembling the following in the `smsts.log` file. |
| 126 | + |
| 127 | + ```text |
| 128 | + Request was successful. |
| 129 | + dwBodyLength <= m_nMaxReplySize, HRESULT=80004005 |
| 130 | + reply message body length is too long (18291682, 16777216) |
| 131 | + ``` |
| 132 | + |
| 133 | +<!-- 10997261 --> |
| 134 | +- The BitLocker recovery key is only escrowed for the first user on a computer instead of all users that log on. |
| 135 | + |
| 136 | +<!-- 11007543 --> |
| 137 | +- Clients fail to download content from a peer cache source under the following conditions: |
| 138 | + |
| 139 | + - The content is deleted from a distribution point but remains in the peer cache. |
| 140 | + - The client is on a low bandwidth connection that causes the BITS download job to take over 24 hours to complete. |
| 141 | + |
| 142 | +<!-- 11041519 --> |
| 143 | +- The device collection is unexpectedly empty when selected from the device graph on the Windows 10 dashboard. |
| 144 | + |
| 145 | +<!-- 11184150 --> |
| 146 | +- The list of BitLocker recovery keys is blank for Azure Active Directory-joined devices. |
| 147 | + |
| 148 | +## Hotfixes that are included in this update |
| 149 | + |
| 150 | +- KB [10503003](../../hotfix/2107/10503003.md) Update for Microsoft Endpoint Configuration Manager version 2107, early update ring |
| 151 | + |
| 152 | +## Known issues in this release |
| 153 | + |
| 154 | +- The **Log Analytics connector for Azure Monitor** feature was removed from Configuration Manager version 2107. However, the pages that allow an administrator to view and delete the **OMS Connector** are still present but don't function. For more information, see [Deprecated features](../../core/plan-design/changes/deprecated/removed-and-deprecated-cmfeatures.md#unsupported-and-removed-features). |
| 155 | + |
| 156 | +## Update information for Microsoft Endpoint Configuration Manager current branch, version 2107 |
| 157 | + |
| 158 | +This update is available in the Updates and Servicing node of the Configuration Manager console for environments that were installed by using early update ring or globally available builds of version 2107. |
| 159 | + |
| 160 | +Members of the Configuration Manager Technology Adoption Program (TAP) must first apply the private TAP rollup before this update is displayed. |
| 161 | + |
| 162 | +To verify which build is in use, look for a Package GUID by adding the Package GUID column to the details pane of the Updates and Servicing node in the console. The update applies to installations from packages that have the following GUIDs: |
| 163 | + |
| 164 | +- **248DC1EB-4B98-4483-BAF3-08C678C1CD0A** |
| 165 | +- **142D394F-4E40-4574-AB8F-D182200DF03C** |
| 166 | +- **8D0F9A5B-B21D-438F-AC56-38428FECB787** |
| 167 | +- **86FE4AF1-68A1-4AD4-B435-91995D30ECD6** |
| 168 | +- **E392EF90-DB2C-47BB-ACB8-11E702D0F451** |
| 169 | +- **42E1CF6E-95A1-4A8D-96AD-311E6247B3FB** |
| 170 | + |
| 171 | +The update is also applicable to TAP builds with the private TAP rollup installed. |
| 172 | + |
| 173 | +### Restart information |
| 174 | + |
| 175 | +This update does not require a computer restart but will initiate a [site reset](../../core/servers/manage/modify-your-infrastructure.md#bkmk_reset) after installation. |
| 176 | + |
| 177 | +### Additional installation information |
| 178 | + |
| 179 | +After you install this update on a primary site, pre-existing secondary sites must be manually updated. To update a secondary site in the Configuration Manager console, select **Administration** > **Site Configuration** > **Sites** > **Recover Secondary Site**, and then select the secondary site. The primary site then reinstalls that secondary site by using the updated files. Configurations and settings for the secondary site are not affected by this reinstallation. The new, upgraded, and reinstalled secondary sites under that primary site automatically receive this update. |
| 180 | + |
| 181 | +Run the following SQL Server command on the site database to check whether the update version of a secondary site matches that of its parent primary site: |
| 182 | + |
| 183 | + ```code |
| 184 | + select dbo.fnGetSecondarySiteCMUpdateStatus ('SiteCode_of_secondary_site') |
| 185 | + ``` |
| 186 | + |
| 187 | +- If the value 1 is returned, the site is up to date, with all the hotfixes applied on its parent primary site. |
| 188 | +- If the value 0 is returned, the site has not installed all the fixes that are applied to the primary site, and you should use the **Recover Secondary Site** option to update the secondary site. |
| 189 | + |
| 190 | +## Version information |
| 191 | + |
| 192 | +The following major components are updated to the versions specified: |
| 193 | + |
| 194 | +| Component | Version | |
| 195 | +|-------------------------------|------------------| |
| 196 | +| Configuration Manager console | 5.2107.1059.3700 | |
| 197 | +| Client | 5.0.9058.1047 | |
| 198 | + |
| 199 | +## File information |
| 200 | + |
| 201 | +File information is available in the downloadable [KB11121541_FileList.txt](https://aka.ms/KB11121541_FileList) text file. |
| 202 | + |
| 203 | +## Release history |
| 204 | + |
| 205 | +- October 27, 2021: Initial hotfix release |
| 206 | + |
| 207 | +## References |
| 208 | + |
| 209 | +[Updates and servicing for Configuration Manager](../../core/servers/manage/updates.md) |
0 commit comments