|
| 1 | +--- |
| 2 | +title: Summary of changes in Configuration Manager current branch, version 2203 |
| 3 | +titleSuffix: Configuration Manager |
| 4 | +description: Article listing changes in Configuration Manager current branch, version 2203 |
| 5 | +ms.date: 04/26/2022 |
| 6 | +ms.prod: configuration-manager |
| 7 | +ms.technology: configmgr-core |
| 8 | +ms.topic: reference |
| 9 | +ms.assetid: 6261ac6f-d5d6-499f-8c67-77ebfeeaee4c |
| 10 | +author: bhuney |
| 11 | +ms.author: brianhun |
| 12 | +manager: dougeby |
| 13 | +--- |
| 14 | + |
| 15 | +# Summary of changes in Configuration Manager current branch, version 2203 |
| 16 | + |
| 17 | +*Applies to: Configuration Manager (current branch, version 2203)* |
| 18 | + |
| 19 | +## Summary of KB13174460 |
| 20 | +Release version 2203 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 | + |
| 23 | +##### Notes |
| 24 | +<!-- TEMPLATE: Make sure to update the links below to reference version-specific articles, including the update rollup for the prior release. Use relative links. --> |
| 25 | +- Version 2203 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 2203 for System Center Configuration Manager](../../core/servers/manage/checklist-for-installing-update-2203.md). |
| 27 | +- For more information about the changes that are included in version 2203, see [What's new in version 2203 of Configuration Manager current branch](../../core/plan-design/changes/whats-new-in-version-2203.md). |
| 28 | +- This globally available release contains all of the fixes summarized in the following article. |
| 29 | + |
| 30 | + KB [12896009](../../hotfix/2111/12896009.md): Update rollup for Microsoft Endpoint Configuration Manager current branch, version 2111 |
| 31 | + |
| 32 | +## Issues that are fixed |
| 33 | +<!-- 2837936 --> |
| 34 | +- The collection evaluation process is optimized during startup of the SMS_Executive service (*smsexec.exe*) to reduce the overall time required to complete evaluations. |
| 35 | +<!-- 3305474 --> |
| 36 | +- The SMS Agent Host service (*CCMExec.exe*) hangs in a **Stop Pending** state on clients that are also configured as pull-distribution points. When this issue happens, the thread count for CCMExec.exe in Task Manager will show over 500 threads. |
| 37 | +<!-- 5094600 --> |
| 38 | +- The **Get-CMSoftwareUpdateDeployment** and **Get-CMSoftwareUpdateDeploymentStatus** PowerShell cmdlets do not run as expected under the context of an account with the Software Update Manager role. |
| 39 | +<!-- 5904616 --> |
| 40 | +- SQL queries against the **vLogs** view can fail with an XML parsing error which delays data replication service troubleshooting efforts. |
| 41 | +<!-- 9196080 --> |
| 42 | +- The FailoverManager.log file is improved to remove ambiguous log entries related to site certificates. |
| 43 | +<!-- 10266992 --> |
| 44 | +- State message processing is now more resilient to intermittent SQL errors. |
| 45 | +<!-- 10565692 --> |
| 46 | +- The Client Health Dashboard is updated to reduce false negatives related to status messages. |
| 47 | +<!-- 11047682 --> |
| 48 | +- The Distribution Manager component of the SMS_Executive service on a child site makes unnecessary network calls back to the parent site for package source details such as file size. This delays package processing times in environments with a large number of packages and/ or distribution points across a hierarchy. |
| 49 | +<!-- 11155525 --> |
| 50 | +- The content size filter for an automated deployment rule does not return any results when an exact value is used instead of a comparison, such as greater than or less than. |
| 51 | +<!-- 12505551 --> |
| 52 | +- User available programs are incorrectly shown under the Featured section in the company portal. |
| 53 | +<!-- 12570698 --> |
| 54 | +- Opening a software center notification from the system tray icon bypasses the high impact task sequence notification. |
| 55 | +<!-- 12590180 --> |
| 56 | +- Starting with Configuration Manager current branch, version 2107, newly installed workgroup clients are not automatically approved as expected in environments using PKI-issues certificates. |
| 57 | +<!-- 12708814 --> |
| 58 | +- Co-managed clients no longer receive Intune Win32 content via the Microsoft Connected Cache feature. |
| 59 | +<!-- 12727584 --> |
| 60 | +- Clients fail to receive policy data during an operating system deployment scenario when the dynamic media was created at one site, but the client is within the boundaries of a different site. |
| 61 | +<!-- 12873596 --> |
| 62 | +- Automated queries against the **SMSCOMPONENTS** WMI class may eventually fail. Event ID 5612 is generated with text resembling the following: |
| 63 | + ```text |
| 64 | + Wmiprvse.exe exceeded handle quota limit |
| 65 | + WMI has stopped WMIPRVSE.EXE because a quota reached a warning value. Quota: PrivatePageCount |
| 66 | + ``` |
| 67 | +<!-- 12917816 --> |
| 68 | +- The **Recommended version of Microsoft .NET Framework** prerequisite checker warning is updated to clarify requirements. |
| 69 | +<!-- 12953268 --> |
| 70 | +- Files larger than 4GB fail to download from a cloud management gateway when the **BranchCache** feature is enabled. The DTS.log on the client contains an error resembling the following: |
| 71 | + ```text |
| 72 | + Failed to add file C:\Windows\ccmcache\{content_path}\sources/{filename} to range download. Error - 0x8020002c |
| 73 | + ``` |
| 74 | +<!-- 13008375 --> |
| 75 | +- Operating system deployment task sequences may fail to put the Configuration Manager client into provisioning mode due to a timing issue. This can lead to application installation failures, unintended client patching, or other unexpected side effects. When this happens, the SMSTS.log file contains the following: |
| 76 | + ```text |
| 77 | + Failed to create instance of progress UI (0x80040154) |
| 78 | + ``` |
| 79 | +<!-- 13028713 --> |
| 80 | +- Improvements for readability are made to the UpdateDeployment and DCMAgent log files. |
| 81 | +<!-- 13034131 --> |
| 82 | +- The SMS Agent Host service (CCMExec.exe) takes up more memory than expected on a management point if there is a problem reading the *\{MP_installation_directory}\Statistic\CurrentData* file. With verbose debug logging enabled, the CCMStatistics.log contains entries resembling the following: |
| 83 | + ```text |
| 84 | + Statistic initialization failed 0x87d00217 |
| 85 | + ``` |
| 86 | +<!-- 13089286 --> |
| 87 | +- Logging for Active Directory discovery methods is improved to include more precise troubleshooting information, such as specific error codes if domain names fail to resolve. |
| 88 | +<!-- 13106423 --> |
| 89 | +- CMPivot and the Microsoft Edge installer are currently signed with the **Microsoft Code Signing PCA 2011** certificate. If you set PowerShell execution policy to **AllSigned**, then you need to make sure that devices trust this signing certificate. You can now export the certificate from a computer where you've installed a Configuration Manager version 2203 site server. View the certificate on *SMSInstallDir*\cd.latest\SMSSETUP\BIN\X64\CMPivot.ps1, and then export the code signing certificate from the certification path. Then import it to the *machine's* **Trusted Publishers** store on managed devices. You can use the process in the following blog, but make sure to export the *code signing certificate* from the certification path: [Adding a Certificate to Trusted Publishers using Intune](https://techcommunity.microsoft.com/t5/intune-customer-success/adding-a-certificate-to-trusted-publishers-using-intune/ba-p/1974488). |
| 90 | +<!-- 13250530 --> |
| 91 | +- After updating to Configuration Manager current branch, version 2111, the hman.log file contains errors resembling the following: |
| 92 | + ```text |
| 93 | + Failed to read certificate context from file 'readme.txt', 0x8009310b |
| 94 | + Failed to process TPM certs cab, 0x8009310b |
| 95 | + ``` |
| 96 | + This error does not effect normal site operations but can hinder other troubleshooting efforts. |
| 97 | +<!-- 13323720 --> |
| 98 | +- The **Run summarization task** for a software update deployment fails to run on the central administration site (CAS). The statesys.log contains an error resembling the following: |
| 99 | + ```text |
| 100 | + *** exec spProcessSingleSummarizationRequests |
| 101 | + *** [42000][2812][Microsoft][SQL Server Native Client 11.0][SQL Server]Could not find stored procedure 'spTask_SUM_AssignmentComplianceEvaluator'. : spProcessSingleSummarizationRequests |
| 102 | + ``` |
| 103 | + |
| 104 | +## Hotfixes that are included in this update |
| 105 | +- KB [10096997](../../hotfix/2111/11052354.md) Summary of changes in Configuration Manager current branch, version 2111 |
| 106 | +- KB [12709700](../../hotfix/2111/12709700.md) Update for Microsoft Endpoint Configuration Manager version 2111 |
| 107 | +- KB [12959506](../../hotfix/2111/12959506.md) Client update for Configuration Manager current branch, version 2111 |
| 108 | +- KB [12819689](../../hotfix/2111/12819689.md) Connected cache update for Microsoft Endpoint Configuration Manager version 2111 |
| 109 | +- KB [12896009](../../hotfix/2111/12896009.md) Update rollup for Microsoft Endpoint Configuration Manager version 2111 |
| 110 | + |
| 111 | +## Dependency changes |
| 112 | +The following dependent component that is included with Configuration Manager version 2203 is updated to the specified version: |
| 113 | +- Newtonsoft.Json to version 13.0.1 |
0 commit comments