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/analytics/enroll-configmgr.md
+1-4Lines changed: 1 addition & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,10 +33,7 @@ Before you start this tutorial, make sure you have the following prerequisites:
33
33
34
34
### Licensing Prerequisites
35
35
36
-
Endpoint analytics is included in the following plans:
37
-
38
-
-[Enterprise Mobility + Security E3](https://www.microsoftvolumelicensing.com/ProductResults.aspx?doc=Product%20Terms,OST&fid=51) or higher
39
-
-[Microsoft 365 Enterprise E3](https://www.microsoft.com/en-us/microsoft-365/enterprise?rtc=1) or higher.
36
+
Devices enrolled in Endpoint analytics need a valid license for the use of Microsoft Endpoint Manager. For more information, see [Microsoft Intune licensing](../intune/fundamentals/licenses.md) or [Microsoft Endpoint Configuration Manager licensing](../configmgr/core/understand/learn-more-editions.md).
Copy file name to clipboardExpand all lines: memdocs/analytics/enroll-intune.md
+1-4Lines changed: 1 addition & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,10 +43,7 @@ To enroll devices to Endpoint analytics, they need to send required functional d
43
43
44
44
### Licensing Prerequisites
45
45
46
-
Endpoint analytics is included in the following plans:
47
-
48
-
-[Enterprise Mobility + Security E3](https://www.microsoftvolumelicensing.com/ProductResults.aspx?doc=Product%20Terms,OST&fid=51) or higher
49
-
-[Microsoft 365 Enterprise E3](https://www.microsoft.com/en-us/microsoft-365/enterprise?rtc=1) or higher.
46
+
Devices enrolled in Endpoint analytics need a valid license for the use of Microsoft Endpoint Manager. For more information, see [Microsoft Intune licensing](../intune/fundamentals/licenses.md) or [Microsoft Endpoint Configuration Manager licensing](../configmgr/core/understand/learn-more-editions.md).
Copy file name to clipboardExpand all lines: memdocs/configmgr/hotfix/2010/5001600.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,12 @@ ms.localizationpriority: medium
16
16
*Applies to: Configuration Manager (current branch, versions 1910 - 2010)*
17
17
18
18
## Summary of KB5001600
19
+
> [!NOTE]
20
+
> This update is replaced by the following newer version effective January 21, 2022
21
+
>
22
+
> [KB 12819689 Connected cache update for Microsoft Endpoint Configuration Manager version 2111](../../hotfix/2111/12819689.md)
23
+
>
24
+
19
25
Due to content delivery network changes, the Microsoft Connected Cache (MCC) server component installation fails when enabled for distribution points *after***March 5, 2021**.
20
26
This component is enabled by selecting the **Enable this distribution point to be used as Microsoft Connected Cache server** option in a distribution point's properties.
21
27
After March 5, 2021, once enabled, the component will retry installation three times before stopping.
title: Connected cache update for Microsoft Endpoint Configuration Manager version 2111
3
+
titleSuffix: Configuration Manager
4
+
description: Console update for 2111
5
+
ms.date: 1/21/2022
6
+
ms.prod: configuration-manager
7
+
ms.technology: configmgr-core
8
+
ms.topic: reference
9
+
ms.assetid: 41afa274-7561-4c0e-80af-2d0fe01699ef
10
+
author: bhuney
11
+
ms.author: brianhun
12
+
manager: dougeby
13
+
---
14
+
15
+
# Connected cache update for Microsoft Endpoint Configuration Manager version 2111
16
+
17
+
*Applies to: Configuration Manager (current branch, version 2111)*
18
+
## Summary of KB12819689
19
+
20
+
An update is available to resolve the following issue with Configuration Manager current branch, version 2111.
21
+
22
+
- The Microsoft Connected Cache (MCC) feature is not used as expected for Win32 apps deployed through Microsoft Intune in a co-managed environment.
23
+
Review of the IntuneManagementExtension.log file shows an internet-based **DownloadURL** value.
24
+
The MCC component is enabled by selecting the **Enable this distribution point to be used as Microsoft Connected Cache server** option in a distribution point's properties.
25
+
26
+
27
+
## Update information for Microsoft Endpoint Configuration Manager, version 2111
28
+
The following hotfix to resolve this problem is available for download from the Microsoft Download Center:
29
+
30
+
[Download this hotfix now](https://download.microsoft.com/download/a/3/a/a3af1ea3-79ba-4600-8953-c2a4b6b8b970/DoincInstall.exe).
31
+
32
+
After you download this hotfix, refer to the following installation instructions.
33
+
34
+
## Installation instructions
35
+
1. Confirm there is not currently an installation of the MCC component in progress. This is done by checking for status message **9522**, generated by the `SMS_DISTRIBUTION_MANAGER` component. The 9522 message indicates that installation is no longer being retried.
36
+
2. Copy the new version of `DoincInstall.exe`, version **1.5.5.9002**, to the `{SMSInstallDir}\bin\x64` folder on all site servers, including the Central Administration Site (CAS) if present, and any passive sites.
37
+
3. Uncheck the **Enable this distribution point to be used as Microsoft Connected Cache server** option in the affected distribution point’s properties.
38
+
4. Wait for the uninstall of MCC to complete on the distribution point. This can be confirmed by looking for a **9152** success status message, combined with the following entry in `distmgr.log`.
39
+
```text
40
+
Finished waiting for DoincInstall. InvocationState: UninstallCompleted. InvocationExitCode: 0. InvocationMessage: .
41
+
```
42
+
5. Recheck the **Enable this distribution point to be used as Microsoft Connected Cache server** option for the affected distribution point.
43
+
44
+
> [!TIP]
45
+
> For sites with a large number of distribution points, replace steps 4 - 5 above with the following.
46
+
> - Create an empty file named `resetdps.trn` and place it in the `{SMSInstallDir}\inboxes\distmgr.box` folder. This will reinstall all distribution points for that site using the latest version of `DoincInstall.exe` copied in step 3. above.
47
+
48
+
## Prerequisites
49
+
To apply this hotfix, you must be using Microsoft Endpoint Configuration Manager, versions 1910 through versions 2111.
50
+
51
+
## Restart information
52
+
You don't have to restart the computer after you apply this hotfix.
53
+
54
+
## Hotfix replacement information
55
+
This hotfix replaces the following previously released hotfix.
56
+
57
+
[KB5001600 Microsoft Connected Cache component fails to install on Configuration Manager current branch](../../hotfix/2010/5001600.md)
58
+
59
+
## File information
60
+
File information is available in the downloadable [KB12819689_FileList.txt](https://aka.ms/KB12819689_FileList) text file.
| Preview | Production tenant | Mobile capability owners, UX | Enduser scenario validation, user facing documentation | 7-14 days, post Quality Assurance |
55
+
| Preview | Production tenant | Mobile capability owners, UX | End-user scenario validation, user facing documentation | 7-14 days, post Quality Assurance |
56
56
| Production | Production tenant | Mobile capability owners, IT help desk | N/A | 7 days to several weeks, post Preview |
57
57
58
58
As the above table indicates, all changes to the App Protection Policies should be first performed in a pre-production environment to understand the policy setting implications. Once testing is complete, the changes can be moved into production and applied to a subset of production users, generally, the IT department and other applicable groups. And finally, the rollout can be completed to the rest of the mobile user community. Rollout to production may take a longer amount of time depending on the scale of impact regarding the change. If there is no user impact, the change should roll out quickly, whereas, if the change results in user impact, rollout may need to go slower due to the need to communicate changes to the user population.
@@ -106,7 +106,7 @@ The policies in level 1 enforce a reasonable data access level while minimizing
106
106
107
107
| Setting | Setting description | Value | Platform |
| Device conditions | SafetyNet device attestation | Basic integrity and certified devices / Block access | Android | <p>This setting configures Google's SafetyNet Attestation on enduser devices. Basic integrity validates the integrity of the device. Rooted devices, emulators, virtual devices, and devices with signs of tampering fail basic integrity. </p><p> Basic integrity and certified devices validates the compatibility of the device with Google's services. Only unmodified devices that have been certified by Google can pass this check.</p> |
153
-
| Device conditions | Require threat scan on apps | N/A / Block access | Android | This setting ensures that Google's Verify Apps scan is turned on for end user devices. If configured, the enduser will be blocked from access until they turn on Google's app scanning on their Android device. |
152
+
| Device conditions | SafetyNet device attestation | Basic integrity and certified devices / Block access | Android | <p>This setting configures Google's SafetyNet Attestation on end-user devices. Basic integrity validates the integrity of the device. Rooted devices, emulators, virtual devices, and devices with signs of tampering fail basic integrity. </p><p> Basic integrity and certified devices validates the compatibility of the device with Google's services. Only unmodified devices that have been certified by Google can pass this check.</p> |
153
+
| Device conditions | Require threat scan on apps | N/A / Block access | Android | This setting ensures that Google's Verify Apps scan is turned on for end user devices. If configured, the end-user will be blocked from access until they turn on Google's app scanning on their Android device. |
154
154
| Device conditions | Require device lock | N/A / Block access | Android | This setting ensures that Android devices have a device PIN, password, or pattern are set to enable a device lock. This condition does not distinguish between lock options or the complexity. |
155
155
156
156
#### Level 2 enterprise enhanced data protection
@@ -163,7 +163,7 @@ The policy settings enforced in level 2 include all the policy settings recommen
| Data Transfer |Backup org data to… | Block | iOS/iPadOS, Android ||
166
+
| Data Transfer |Back up org data to… | Block | iOS/iPadOS, Android ||
167
167
| Data Transfer | Send org data to other apps | Policy managed apps | iOS/iPadOS, Android | <p>With iOS/iPadOS, administrators can configure this value to be "Policy managed apps", "Policy managed apps with OS sharing", or "Policy managed apps with Open-In/Share filtering". </p><p>Policy managed apps with OS sharing is available when the device is also enrolled with Intune. This setting allows data transfer to other policy managed apps, as well as file transfers to other apps that have are managed by Intune. </p><p>Policy managed apps with Open-In/Share filtering filters the OS Open-in/Share dialogs to only display policy managed apps. </p><p> For more information, see [iOS app protection policy settings](app-protection-policy-settings-ios.md).</p> |
168
168
| Data Transfer | Select apps to exempt | Default / skype;app-settings;calshow;itms;itmss;itms-apps;itms-appss;itms-services; | iOS/iPadOS ||
169
169
| Data Transfer | Save copies of org data | Block | iOS/iPadOS, Android ||
0 commit comments