Skip to content

Commit 5e0006e

Browse files
mestewmestew
committed
Merge branch 'release-cm2203-tp' of https://github.com/MicrosoftDocs/memdocs-pr into 2203tp-finalize
2 parents 5697d9f + b5d0e8d commit 5e0006e

11 files changed

Lines changed: 194 additions & 23 deletions

File tree

‎memdocs/autopilot/enrollment-autopilot.md‎

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,6 +73,9 @@ ms.collection:
7373

7474
3. Select **Create**.
7575

76+
[!NOTE]
77+
Anything assigned to these attributes will only be assigned if the device is Autopilot registered.
78+
7679
## Add devices
7780

7881
For information about formatting and using a CSV file to manually add Windows Autopilot devices, see [Manually register devices with Windows Autopilot](add-devices.md).
@@ -131,4 +134,4 @@ You can group Windows devices by a correlator ID when enrolling using [Autopilot
131134

132135
After you have created a device group, you can configure and apply a Windows Autopilot deployment profile to each device in the group. Deployment profiles determine the deployment mode, and customize the OOBE for your end users. For more information, see [Configure deployment profiles](profiles.md).
133136

134-
For more information about managing your Windows Autopilot devices, see [What is Microsoft Intune device management?](../intune/remote-actions/device-management.md)
137+
For more information about managing your Windows Autopilot devices, see [What is Microsoft Intune device management?](../intune/remote-actions/device-management.md)

‎memdocs/autopilot/known-issues.md‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,10 @@ This article describes known issues that can often be resolved by configuration
2828

2929
## Known issues
3030

31+
### Device goes through Autopilot deployment without an assigned profile
32+
33+
When a device is registered in Autopilot and no profile is assigned, it will take the default Autopilot profile. This is by design to ensure that all devices registered with Autopilot, goes through the Autopilot experience. If you do not want the device to go through an Autopilot deployment, you must remove the Autopilot registration.
34+
3135
### White screen during HAADJ deployment
3236

3337
There is a UI bug on Autopilot HAADJ deployments where the Enrollment Status page is displayed as a white screen. This issue is limited to the UI and should not impact the deployment process.

‎memdocs/autopilot/profiles.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -103,6 +103,8 @@ After you've created an Autopilot deployment profile, you can edit certain parts
103103
> [!NOTE]
104104
> Changes to the profile are applied to devices assigned to that profile. However, the updated profile won't be applied to a device that has already enrolled in Intune until after the device is reset and reenrolled.
105105
106+
If a device is registered in Autopilot and a profile is not assigned, it will receive the default Autopilot profile. If you do not want a device to go through Autopilot, you must remove the Autopilot registration.
107+
106108
## Alerts for Windows Autopilot unassigned devices
107109
<!-- 163236 -->
108110

‎memdocs/autopilot/registration-overview.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,8 @@ Registration can also be performed within your organization by collecting the ha
4444
- [Automatic registration](automatic-registration.md)
4545
- [Manual registration](manual-registration.md)
4646

47+
Once a device is registered in Autopilot if a profile is not assigned, it will receive the default Autopilot profile. If you do not want a device to go through Autopilot, you must remove the Autopilot registration.
48+
4749
## Terms
4850

4951
The following terms are used to refer to various steps in the registration process:

‎memdocs/configmgr/core/get-started/2022/includes/2203/10454717.md‎

Lines changed: 33 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,42 @@
11
---
2-
author: mestew
3-
ms.author: mstewart
2+
author: aczechowski
3+
ms.author: aaroncz
44
ms.prod: configuration-manager
55
ms.technology: configmgr-core
66
ms.topic: include
77
ms.date: 03/01/2022
88
ms.localizationpriority: medium
99
---
1010

11-
## <a name="bkmk_anchor"></a> Feature Name
12-
<!--CMADO#-->
11+
## <a name="bkmk_blmts"></a> Escrow BitLocker recovery password to the site during a task sequence
1312

13+
<!--10454717-->
14+
15+
You can now configure the **Enable BitLocker** step of a task sequence to escrow the BitLocker recovery information for the OS volume to Configuration Manager. Previously, you had to escrow to Active Directory, or wait for the Configuration Manager client to receive BitLocker management policy after the task sequence. This new option makes sure that the device is fully protected by BitLocker when the task sequence completes, and that you can recover the OS volume immediately.
16+
17+
For more general information, see [Plan for BitLocker management](../../../../../protect/plan-design/bitlocker-management.md).
18+
19+
### Prerequisites for escrowing BitLocker recovery password during a task sequence
20+
21+
The client will only escrow its key to the Configuration Manager site if you configure one of the following options:
22+
23+
- Create and use a certificate to encrypt the site database for BitLocker management.
24+
25+
- Enable the BitLocker client management policy option to **Allow recovery information to be stored in plain text**.
26+
27+
For more information, see [Encrypt recovery data in the database](../../../../../protect/deploy-use/bitlocker/encrypt-recovery-data.md).
28+
29+
### Try it out!
30+
31+
Try to complete the tasks. Then send [Feedback](../../../../understand/product-feedback.md) with your thoughts on the feature.
32+
33+
1. If needed, first [create a task sequence to deploy an OS](../../../../../osd/deploy-use/manage-task-sequences-to-automate-tasks.md).
34+
35+
1. [Use the task sequence editor](../../../../../osd/understand/task-sequence-editor.md) to edit the task sequence.
36+
37+
1. If the task sequence doesn't already include the **Enable BitLocker** step, add it. For more information, see [About task sequence steps: Enable BitLocker](../../../../../osd/understand/task-sequence-steps.md#BKMK_EnableBitLocker).
38+
39+
1. On the properties of the **Enable BitLocker** step, select the option to **Automatically store the recovery key**, and then select **The Configuration Manager database**.
40+
41+
> [!NOTE]
42+
> If Configuration Manager can't escrow the key, by default this task sequence step fails.

‎memdocs/configmgr/hotfix/2111/12896009.md‎

Lines changed: 136 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,136 @@
1+
---
2+
title: Update rollup for Microsoft Endpoint Configuration Manager version 2111
3+
titleSuffix: Configuration Manager
4+
description: Update rollup for Configuration Manager 2111
5+
ms.date: 03/02/2022
6+
ms.prod: configuration-manager
7+
ms.technology: configmgr-core
8+
ms.topic: reference
9+
ms.assetid: 7bd4295d-20c0-4d5f-b2e4-fa770ebc2ca6
10+
author: bhuney
11+
ms.author: brianhun
12+
manager: dougeby
13+
---
14+
15+
# Update rollup for Microsoft Endpoint Configuration Manager version 2111
16+
17+
*Applies to: Configuration Manager (current branch, version 2111)*
18+
19+
## Summary of KB12896009
20+
This article describes issues that are fixed in this update rollup for Microsoft Endpoint Configuration Manager current branch, version 2111. 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 2111, see:
22+
- [What’s new in version 2111 of Configuration Manager current branch](../../core/plan-design/changes/whats-new-in-version-2111.md)
23+
- [Summary of changes in Microsoft Endpoint Configuration Manager current branch, version 2111](../../hotfix/2111/11052354.md)
24+
25+
## Issues that are fixed
26+
27+
<!-- 12905440 -->
28+
- The Configuration Manager console fails to open after installing an updated version of a required console extension.
29+
30+
<!-- 12923578 -->
31+
- Users without the **Read Client Status Settings** permission on the **Site** object are unable to see the client health dashboard.
32+
33+
<!-- 12905525 -->
34+
- Windows LEDBAT isn't automatically enabled or disabled for a distribution point when selecting the **Adjust the download
35+
speed to use the unused network bandwidth (Windows LEDBAT)** setting in site properties.
36+
37+
<!-- 12909958 -->
38+
- Automatic registration of the Configuration Manager PowerShell module (*ConfigurationManager.psd1*) can trigger a false positive alert from security software.
39+
40+
<!-- 12785033 -->
41+
- The Configuration Manager console now allows wildcards when defining Microsoft Defender Attack Surface Reduction (ASR) rules.
42+
43+
<!-- 12785058 -->
44+
- CMPivot queries against the **Processor** entity may fail with an "Invalid query" error.
45+
46+
<!-- 12905518 -->
47+
- Clients that aren't Intune enrolled will record the following error in the execmgr.log file after receiving a task sequence policy.
48+
```text
49+
Failed to check enrollment url, 0x00000001:
50+
```
51+
52+
<!-- 12981663 -->
53+
- The OneTrace log file viewer (*CMPowerLogViewer.exe*) may terminate unexpectedly when opening a log file.
54+
55+
<!-- 12952864 -->
56+
- The **Show Table** link in the Windows Servicing dashboard displays repetitive information after selecting different collections.
57+
58+
<!-- 13059770 -->
59+
- The Post Installation task **Installing SMS_EXECUTIVE service** displays a status of *Completed with warning* even though it was successful and no warnings are recorded in the sitecomp.log file.
60+
61+
<!-- 13069590 -->
62+
- Clients will now throttle communication with a cloud management gateway if they make five unsuccessful contact attempts in five minutes.
63+
64+
<!-- 13104384 -->
65+
- If a client computer is offline for multiple days with a pending state message resync request, it will receive duplicate policies for the resync when it comes back online. This leads to repeated resynchronization of the same messages.
66+
67+
<!-- 13039356 -->
68+
- When the Configuration Manager console is installed on a computer with an x86 processor, it doesn't detect the installation state of console extensions.
69+
70+
<!-- 13219303 -->
71+
- The built-in cloud features notification message continues to display in the Configuration Manager console even after it is dismissed.
72+
73+
<!-- 13104468 -->
74+
- A remote control session doesn't display as expected when the target computer has multiple monitors and the display has a custom scale over 125 percent.
75+
76+
<!-- 13515162 -->
77+
- Internet-based clients fail to register over the cloud management gateway when the management point is hosted on a remote site system. This occurs for clients installed using a Windows Imaging Task sequence and boot media over an internet connection.
78+
79+
<!-- 13486459 -->
80+
- After updating to Configuration Manager version 2111, client policies for **Windows Defender Firewall Remote Management** that were previously disabled may be re-enabled.
81+
82+
83+
## Hotfixes that are included in this update
84+
85+
- KB [12709700](../../hotfix/2111/12709700.md) Update for Microsoft Endpoint Configuration Manager version 2111
86+
- KB [12959506](../../hotfix/2111/12959506.md) Client update for Configuration Manager current branch, version 2111
87+
88+
## Update information for Microsoft Endpoint Configuration Manager current branch, version 2111
89+
90+
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 2111.
91+
92+
Members of the Configuration Manager Technology Adoption Program (TAP) must first apply the private TAP rollup before this update is displayed.
93+
94+
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:
95+
96+
- **653BACCA-5BCE-4B4C-9A83-10932A561F71**
97+
- **B07144F6-3B8E-4587-B1F0-BB47DA54C566**
98+
- **C77888E5-7499-4885-9EED-811BB2D958C0**
99+
- **44CE0720-6C46-4554-89CF-C9713E9C06C6**
100+
101+
102+
The update is also applicable to TAP builds with the private TAP rollup (**C30077BF-D610-4C8A-BDB1-9B2D5442380E**) installed.
103+
New installations from 2111 media, as opposed to updates from prior versions, will not have any package GUIDs listed.
104+
105+
### Restart information
106+
107+
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.
108+
109+
### Additional installation information
110+
111+
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.
112+
113+
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:
114+
```code
115+
select dbo.fnGetSecondarySiteCMUpdateStatus ('SiteCode_of_secondary_site')
116+
```
117+
If the value 1 is returned, the site is up to date, with all the hotfixes applied on its parent primary site.
118+
119+
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.
120+
121+
## Version information
122+
The following major components are updated to the versions specified:
123+
124+
| Component | Version |
125+
|---|---|
126+
| Configuration Manager console | 5.2111.1052.2500 |
127+
| Client | 5.0.9068.1026 |
128+
129+
## File information
130+
File information is available in the downloadable [KB12896009_FileList.txt](https://aka.ms/KB12896009_FileList) text file.
131+
132+
## Release history
133+
- March 2, 2022: Initial hotfix release
134+
135+
## References
136+
[Updates and servicing for Configuration Manager](../../core/servers/manage/updates.md)

‎memdocs/configmgr/hotfix/TOC.yml‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,8 @@ items:
1111
href: 2111/12959506.md
1212
- name: KB 12819689 Connected cache update for Microsoft Endpoint Configuration Manager version 2111
1313
href: 2111/12819689.md
14+
- name: KB 12896009 Update rollup for Microsoft Endpoint Configuration Manager version 2111
15+
href: 2111/12896009.md
1416
- name: Version 2107
1517
items:
1618
- name: KB 10096997 Summary of changes in 2107

‎memdocs/configmgr/hotfix/index.yml‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,8 @@ landingContent:
2525
url: 2111/11052354.md
2626
- text: KB 12709700 Update for Configuration Manager 2111
2727
url: 2111/12709700.md
28+
- text: KB 12896009 Update rollup for Configuration Manager 2111
29+
url: 2111/12896009.md
2830
- title: Configuration Manager 2107
2931
linkLists:
3032
- linkListType: overview

0 commit comments

Comments
 (0)