Skip to content

Commit c63bc18

Browse files
authored
Merge pull request #7882 from MicrosoftDocs/main
Publish to live - KB 14244456 Update rollup for Microsoft Endpoint Configuration Manager version 2203
2 parents 8b4ccbb + dc45854 commit c63bc18

3 files changed

Lines changed: 143 additions & 2 deletions

File tree

memdocs/configmgr/core/get-started/azure-template.md

Lines changed: 19 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Create a lab in Azure
33
titleSuffix: Configuration Manager
44
description: Automate the creation of a Configuration Manager technical preview lab or current branch evaluation lab using Azure templates
5-
ms.date: 03/14/2022
5+
ms.date: 06/20/2022
66
ms.prod: configuration-manager
77
ms.technology: configmgr-core
88
ms.topic: conceptual
@@ -17,6 +17,8 @@ ms.localizationpriority: medium
1717
*Applies to: Configuration Manager (current branch, technical preview branch)*
1818

1919
<!--3556017-->
20+
> [!Important]
21+
> As of June 20, 2022, there is a known issue with the Azure templates for lab environments. We are working on resolving the issue and we will update this message when it's resolved. For more information, see [known issues](#known-issues). <!--icm 314312504-->
2022
2123
This guide describes how to build a Configuration Manager lab environment in Microsoft Azure. It uses Azure templates to simplify and automate the creation of a lab using Azure resources. Two Azure templates are provided:
2224

@@ -151,3 +153,19 @@ The prefix that you specified in the deployment template is the VM name prefix.
151153
- Only for Configuration Manager current branch evaluation template
152154
- Windows 10
153155
- Configuration Manager client
156+
157+
158+
## Known issues
159+
<!--icm 314312504-->
160+
As of June 20, 2022, there is a known issue with the Azure templates for lab environments. We are working on resolving the issue and we will update this message when it's resolved. This issue occurs during deployment of the template and the following error message is displayed:
161+
162+
```text
163+
{
164+
"status": "Failed",
165+
"error": {
166+
"code": "VMExtensionProvisioningError",
167+
"message": "VM has reported a failure when processing extension 'WorkFlow'. Error message: \"DSC Configuration 'Configuration' completed with error(s). Following are the first few: Failed to create an object of PowerShell class SetupDomain. The SendConfigurationApply function did not succeed. LCM failed to start desired state configuration manually.\"\r\n\r\nMore information on troubleshooting is available at https://aka.ms/VMExtensionDSCWindowsTroubleshoot "
168+
}
169+
}
170+
171+
```
Lines changed: 121 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,121 @@
1+
---
2+
title: Update rollup for Microsoft Endpoint Configuration Manager version 2203
3+
titleSuffix: Configuration Manager
4+
description: Update rollup for Configuration Manager 2203
5+
ms.date: 06/24/2022
6+
ms.prod: configuration-manager
7+
ms.technology: configmgr-core
8+
ms.topic: reference
9+
ms.assetid: 002574f1-a121-4ce7-908b-cc763d7e9689
10+
author: bhuney
11+
ms.author: brianhun
12+
manager: dougeby
13+
---
14+
15+
# Update rollup for Microsoft Endpoint Configuration Manager version 2203
16+
17+
*Applies to: Configuration Manager (current branch, version 2203)*
18+
19+
## Summary of KB14244456
20+
This article describes issues that are fixed in this update rollup for Microsoft Endpoint Configuration Manager current branch, version 2203. 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.
21+
For more information on changes in Configuration Manager version 2203, see:
22+
- [What’s new in version 2203 of Configuration Manager current branch](../../core/plan-design/changes/whats-new-in-version-2203.md)
23+
- [Summary of changes in Microsoft Endpoint Configuration Manager current branch, version 2203](../../hotfix/2203/13174460.md)
24+
25+
## Issues that are fixed
26+
<!-- 14244881 -->
27+
- Application approvals through email don't work with a cloud management gateway due to a missing Azure Active Directory token.
28+
29+
<!-- 14359451 -->
30+
- Metadata revisions to previously published metadata-only updates aren't synchronized to Windows Server Update Services (WSUS) as expected.
31+
32+
<!-- 14246530 -->
33+
- The Task Sequence Editor running on Windows Server 2022 fails to apply changes to a task sequence if the window is left open for several minutes. When this occurs the following message is displayed onscreen.
34+
```text
35+
Error connecting to provider, smsprov.log may show more details.
36+
```
37+
38+
<!-- 14342965 -->
39+
- BitLocker compliance status won't be accurate for a brief period of time if the **Client checking status frequency (minutes)** value is set below 60.
40+
41+
<!-- 14359434 -->
42+
- The SMS_AZUREAD_DISCOVERY_AGENT thread of the SMS_Executive service incorrectly removes some users and their group memberships when the site server is configured with a non-US English locale. The removal happens when the discovery cycle runs after the 12th day of the month. Errors resembling the following are recorded in the SMS_AZUREAD_DISCOVERY_AGENT.log file at different times during the discovery cycle.
43+
```text
44+
ERROR: Encountered SqlException The conversion of a nvarchar data type to a datetime data type resulted in an out-of-range value.
45+
ERROR: Exception message: [The conversion of a nvarchar data type to a datetime data type resulted in an out-of-range value.]
46+
ERROR: Group full sync request failed. Exception: System.NullReferenceException: Object reference not set to an instance of an object.
47+
```
48+
49+
<!-- 14463370 -->
50+
- When adding a CMPivot query as a favorite it is split into two lines and characters are removed.
51+
52+
<!-- 14497732 -->
53+
- The *Name* criteria isn't available when searching Software Update Groups in the Configuration Manager console.
54+
55+
<!-- 14561174 -->
56+
- The *Browse* button for **Content location** in the properties for a deployment returns an empty location instead of the value previously shown.
57+
58+
<!-- 14577483 -->
59+
- An application that is targeted to a device collection but deployed in the context of the user won't honor the implicit uninstall setting.
60+
61+
<!-- 14561145 -->
62+
- Typing a *Name* value in the **Create Orchestration Group** wizard is unexpectedly slow.
63+
64+
<!-- 14561157 -->
65+
- A misleading error message (false negative) is generated on a target distribution point that is co-located with a site server. This happens during content distribution from a parent site to a child site. The misleading error in distmgr.log resembles this entry:
66+
```text
67+
~RDC:Failed to set access security on \\<SiteServerFQDN>\SMSSIG$\<PkgID>.1.tar for package <PkgID> signature file
68+
```
69+
70+
## Hotfixes that are included in this update
71+
- KB [13953025](../../hotfix/2203/13953025.md)Update for Microsoft Endpoint Configuration Manager version 2203, early update ring
72+
- KB [14480034](../../hotfix/2203/14480034.md)Registration fails for PKI clients after updating to Configuration Manager current branch, version 2203
73+
74+
## Update information for Microsoft Endpoint Configuration Manager current branch, version 2203
75+
76+
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 2203.
77+
78+
Members of the Configuration Manager Technology Adoption Program (TAP) must first apply the private TAP rollup before this update is displayed.
79+
80+
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:
81+
82+
- **08AA4546-8F69-4F42-9C24-5A022ECEEB87**
83+
- **56DB32EE-4377-460E-BB19-5095FBCFBE1D**
84+
- **26D18D89-CDCA-4499-ACCC-9029E60D6C66**
85+
- **89735386-930A-490A-909B-65101BA8C02C**
86+
87+
The update is also applicable to TAP builds with the private TAP rollup (**40CA6011-70E7-49DF-A05F-5400C85B971A**) installed.
88+
New installations from 2203 media, as opposed to updates from prior versions, will not have any package GUIDs listed.
89+
90+
### Restart information
91+
92+
This update doesn't require a computer restart but will initiate a [site reset](../../core/servers/manage/modify-your-infrastructure.md#bkmk_reset) after installation.
93+
94+
### Additional installation information
95+
96+
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 aren't affected by this reinstallation. The new, upgraded, and reinstalled secondary sites under that primary site automatically receive this update.
97+
98+
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:
99+
```sql
100+
select dbo.fnGetSecondarySiteCMUpdateStatus ('SiteCode_of_secondary_site')
101+
```
102+
If the value 1 is returned, the site is up to date, with all the hotfixes applied on its parent primary site.
103+
104+
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.
105+
106+
## Version information
107+
The following major components are updated to the versions specified:
108+
109+
| Component | Version |
110+
|---|---|
111+
| Configuration Manager console | 5.2203.1063.2400 |
112+
| Client | 5.0.9078.1025 |
113+
114+
## File information
115+
File information is available in the downloadable [KB14244456_FileList.txt](https://aka.ms/KB14244456_FileList) text file.
116+
117+
## Release history
118+
- June 24, 2022: Initial hotfix release
119+
120+
## References
121+
[Updates and servicing for Configuration Manager](../../core/servers/manage/updates.md)

memdocs/configmgr/hotfix/TOC.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,10 @@ items:
77
href: 2203/13174460.md
88
- name: KB 13953025 Early update ring
99
href: 2203/13953025.md
10-
- name: KB 14480034 Client registration fails in Configuration Manager 2203
10+
- name: KB 14480034 PKI Client registration fails in Configuration Manager 2203
1111
href: 2203/14480034.md
12+
- name: KB 14244456 Update rollup for Microsoft Endpoint Configuration Manager version 2203
13+
href: 2203/14244456.md
1214
- name: Version 2111
1315
items:
1416
- name: KB 10096997 Summary of changes in 2111

0 commit comments

Comments
 (0)