You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: memdocs/configmgr/core/plan-design/changes/whats-new-incremental-versions.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,13 +2,13 @@
2
2
title: Incremental versions
3
3
titleSuffix: Configuration Manager
4
4
description: Learn about what's new in the latest update for Configuration Manager.
5
-
ms.date: 04/08/2022
5
+
ms.date: 08/01/2022
6
6
ms.prod: configuration-manager
7
7
ms.technology: configmgr-core
8
8
ms.topic: conceptual
9
-
author: mestew
10
-
ms.author: mstewart
11
-
manager: dougeby
9
+
author: banreet
10
+
ms.author: banreetkaur
11
+
manager: apoorvseth
12
12
ms.localizationpriority: medium
13
13
---
14
14
@@ -26,11 +26,12 @@ Different update versions are identified by year and month. For example, version
26
26
27
27
Use the following links to discover what's new with each supported version:
28
28
29
+
-[What's new in version 2207](whats-new-in-version-2207.md)
29
30
-[What's new in version 2203](whats-new-in-version-2203.md)
30
31
-[What's new in version 2111](whats-new-in-version-2111.md)
31
32
-[What's new in version 2107](whats-new-in-version-2107.md)
32
33
-[What's new in version 2103](whats-new-in-version-2103.md)
33
-
-[What's new in version 2010](whats-new-in-version-2010.md)
34
+
34
35
35
36
36
37
Each update version remains in support for 18 months from its initial availability date. Stay current with the most recent update version. For more information, see [Support for Configuration Manager current branch versions](../../servers/manage/current-branch-versions-supported.md).
|**Windows Server 2022**<br>(10.1.20348) ||||||
36
37
|**Windows 10, version 2004**<br>(10.1.19041) ||||||
37
-
|**Windows 10, version 1903**<br>(10.1.18362) ||||||
Copy file name to clipboardExpand all lines: memdocs/configmgr/core/servers/deploy/install/release-notes.md
+12-34Lines changed: 12 additions & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,13 +2,13 @@
2
2
title: Release notes
3
3
titleSuffix: Configuration Manager
4
4
description: Learn about urgent issues that aren't yet fixed in the product or covered in a Microsoft Support knowledge base article.
5
-
ms.date: 04/08/2022
5
+
ms.date: 08/01/2022
6
6
ms.prod: configuration-manager
7
7
ms.technology: configmgr-core
8
8
ms.topic: troubleshooting
9
-
author: mestew
10
-
ms.author: mstewart
11
-
manager: dougeby
9
+
author: banreet
10
+
ms.author: banreetkaur
11
+
manager: apoorvseth
12
12
ms.localizationpriority: medium
13
13
---
14
14
@@ -24,11 +24,11 @@ This article contains release notes for the current branch of Configuration Mana
24
24
25
25
For information about the new features introduced with different versions, see the following articles:
26
26
27
+
-[What's new in version 2207](../../../plan-design/changes/whats-new-in-version-2207.md)
27
28
-[What's new in version 2203](../../../plan-design/changes/whats-new-in-version-2203.md)
28
29
-[What's new in version 2111](../../../plan-design/changes/whats-new-in-version-2111.md)
29
30
-[What's new in version 2107](../../../plan-design/changes/whats-new-in-version-2107.md)
30
31
-[What's new in version 2103](../../../plan-design/changes/whats-new-in-version-2103.md)
31
-
-[What's new in version 2010](../../../plan-design/changes/whats-new-in-version-2010.md)
32
32
33
33
> [!TIP]
34
34
> You can use RSS to be notified when this page is updated. For more information, see [How to use the docs](../../../../../use-docs.md#notifications).
@@ -56,34 +56,6 @@ When you look at the **Configurations** tab of the Configuration Manager control
56
56
57
57
This issue is fixed in the build of version 2107 that's now generally available for all customers. If you previously opted in to the early update ring, install the [Update for Microsoft Endpoint Configuration Manager version 2107, early update ring](../../../../hotfix/2107/10503003.md).
58
58
59
-
### Client notification actions apply to entire collection
60
-
61
-
<!-- 9021554 -->
62
-
63
-
_Applies to version 2010_
64
-
65
-
When you use a [client notification](../../../clients/manage/client-notification.md) action on a device in a collection, the action applies to all devices in the collection.
66
-
67
-
For example:
68
-
69
-
1. In the Configuration Manager console, go to the **Assets and Compliance** workspace, and select the **Device Collections** node.
70
-
71
-
1. Select a collection, and then choose the **Show Members** action.
72
-
73
-
1. Select a device in the collection. In the ribbon on the **Home** tab, select **Client Notification**, and choose an action such as **Restart**.
74
-
75
-
Because of this issue, this action applies to all members of the collection, not just the selected client.
76
-
77
-
> [!NOTE]
78
-
> This issue doesn't apply to the **Start CMPivot** or **Run Script** options.
79
-
80
-
To work around this issue, install the following hotfix: [Client notifications sent to all collection members in Configuration Manager current branch, version 2010](https://support.microsoft.com/help/4594177).
81
-
82
-
You can also use the **Devices** node. Find the device in the list and start the action from there.
83
-
84
-
> [!NOTE]
85
-
> This issue also applies to the [Invoke-CMClientAction](/powershell/module/configurationmanager/invoke-cmclientaction) PowerShell cmdlet and other SDK methods, if you don't include a collection object or ID.
86
-
87
59
## Set up and upgrade
88
60
89
61
### Version 2107 update fails to download
@@ -211,6 +183,12 @@ For more information, see [Create custom security roles](../configure/configure-
211
183
212
184
## Configuration Manager console
213
185
186
+
### Intune RBAC for Tenant Attached devices
187
+
<!--13058986-->
188
+
*Applies to: version 2207*
189
+
190
+
You'll now see a checkbox for a role-based access control (RBAC) setting in the cloud attach configuration wizard in the console. By default, Configuration Manager RBAC is enforced along with Intune RBAC when you're uploading your Configuration Manager devices to the cloud service. This checkbox is checked by default. If you want to enforce only Intune RBAC, you can uncheck the box. However, the enforcement of Intune RBAC only won't apply at this time. This release note and the [What's New in Intune](../../../../../intune/fundamentals/whats-new.md) will be updated when you're able to enforce Intune RBAC only. For more information, see, [Enable Microsoft Endpoint Manager tenant attach](../../../../../configmgr/tenant-attach/device-sync-actions.md)
191
+
214
192
### Unable to open console because extension installation loops
215
193
<!--12868458-->
216
194
_Applies to: version 2111_
@@ -219,7 +197,7 @@ In certain circumstances, you'll be unable to open the console due to an extensi
219
197
220
198
When you encounter this issue, it initially appears as a normal console extension installation. After the extension finishes installing, you select **Close** to restart the Configuration Manager console. When the console restarts, you're prompted to install the console extension again. The extension installation will continue to loop and the Configuration Manager console doesn't fully open.
221
199
222
-
To both prevent and workaround this issue, run the below SQL script on your CAS database and all of your primary site databases:
200
+
To both prevent and work around this issue, run the below SQL script on your CAS database and all of your primary site databases:
Copy file name to clipboardExpand all lines: memdocs/configmgr/tenant-attach/device-sync-actions.md
+9-5Lines changed: 9 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,13 +2,13 @@
2
2
title: Enable Microsoft Endpoint Manager tenant attach
3
3
titleSuffix: Configuration Manager
4
4
description: Upload your Configuration Manager devices to the cloud service and take actions from the admin center.
5
-
ms.date: 07/11/2022
5
+
ms.date: 08/01/2022
6
6
ms.topic: conceptual
7
7
ms.prod: configuration-manager
8
8
ms.technology: configmgr-core
9
-
manager: dougeby
10
-
author: mestew
11
-
ms.author: mstewart
9
+
manager: apoorvseth
10
+
author: banreet
11
+
ms.author: banreetkaur
12
12
ms.localizationpriority: high
13
13
ms.collection: highpri
14
14
---
@@ -32,11 +32,15 @@ When co-management is already enabled, edit the co-management properties to enab
32
32
- The default setting for device upload is **All my devices managed by Microsoft Endpoint Configuration Manager**. If needed, you can limit upload to a single device collection.
33
33
- When a single collection is selected, its child collections are also uploaded.
34
34
1. Check the option to **Enable Endpoint analytics for devices uploaded to Microsoft Endpoint Manager** if you also want to get insights for optimizing the end-user experience in [Endpoint Analytics](../../analytics/overview.md).
35
+
1. Check the option to **Enforce Role-based Access Control** for the devices uploading to cloud service. By default, SCCM RBAC will be enforced along with Intune RBAC when you are uploading your Configuration Manager devices to the cloud service. Hence, the checkbox will be checked by default. If you want to enforce only Intune RBAC, you can uncheck the box. However, the enforcement of Intune RBAC only won't apply at this time. The [Release notes](../../configmgr/core/servers/deploy/install/release-notes.md) and the [What's New in Intune](../../intune/fundamentals/whats-new.md) will be updated when you're able to enforce Intune RBAC only.
35
36
36
37
> [!Important]
37
38
> When you enable Endpoint analytics data upload, your default client settings will be automatically updated to allow managed endpoints to send relevant data to your Configuration Manager site server. If you use custom client settings, you may need to update and re-deploy them for data collection to occur. For more details on this, as well as how to configure data collection, such as to limit collection only to a specific set of devices, see the section on [Configuring Endpoint analytics data collection](../../analytics/enroll-configmgr.md#bkmk_cm_enable).
38
39
39
-
[](../../analytics/media/6051638-configure-upload-configmgr.png#lightbox)
40
+
[](../../configmgr/tenant-attach/media/13058986-configure-upload-configmgr.png#lightbox)
41
+
42
+
<!-- : : : image type="content" source="../../analytics/media/13058986-configure-upload-configmgr.png" alt-text="Upload devices to Microsoft Endpoint Manager admin center." : : : -->
43
+
40
44
1. Sign in with your *Global Administrator* account when prompted.
41
45
1. Select **Yes** to accept the **Create AAD Application** notification. This action provisions a service principal and creates an Azure AD application registration to facilitate the sync.
42
46
1. Choose **OK** to exit the co-management properties once you've done making changes.
Copy file name to clipboardExpand all lines: memdocs/intune/configuration/device-restrictions-android-for-work.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,7 +88,7 @@ For corporate-owned devices with a work profile, some settings only apply in the
88
88
-**Beam data using NFC (work-profile level)**: **Block** prevents using the Near Field Communication (NFC) technology to beam data from apps. When set to **Not configured** (default), Intune doesn't change or update this setting. By default, the OS might allow using NFC to share data between devices.
89
89
-**Developer settings**: Choose **Allow** to let users access developer settings on the device. When set to **Not configured** (default), Intune doesn’t change or update this setting. By default, the OS might prevent users from accessing developer settings on the device.
90
90
-**Microphone adjustment**: **Block** prevents users from unmuting the microphone and adjusting the microphone volume. When set to **Not configured** (default), Intune doesn't change or update this setting. By default, the OS might allow users to use and adjust the volume of the microphone on the device.
91
-
-**Factory reset protection emails**: Choose **Google account email addresses**. Enter the email addresses of device administrators that can unlock the device after it's wiped. Be sure to separate the email addresses with a semi-colon, such as `[email protected];[email protected]`. If an email isn't entered, anyone can unlock the device after it's restored to the factory settings. These emails only apply when a non-user factory reset is run, such as running a factory reset using the recovery menu.
91
+
-**Factory reset protection emails**: Choose **Google account email addresses**. Enter the email addresses of device administrators that can unlock the device after it's wiped. Be sure to separate the email addresses with a semi-colon, such as `[email protected];[email protected]`. These emails only apply when a non-user factory reset is run, such as running a factory reset using the recovery menu.
92
92
93
93
When set to **Not configured** (default), Intune doesn't change or update this setting.
0 commit comments