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/app-reliability.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Application reliability in endpoint analytics
3
3
description: Get details about application reliability in endpoint analytics
4
4
titleSuffix: Microsoft Endpoint Manager
5
-
ms.date: 03/01/2021
5
+
ms.date: 03/31/2022
6
6
ms.prod: configuration-manager
7
7
ms.technology: configmgr-analytics
8
8
ms.topic: conceptual
@@ -66,6 +66,8 @@ For each application in the report, the following data is provided:
66
66
67
67
> [!NOTE]
68
68
> A maximum of 10 application crash events per application, per device, per day is used. This prevents excessive data collections from devices with severe application issues and helps prevent outlier devices from having undue influence over the reliability scores for individual applications.
69
+
>
70
+
> Applications with an insignificant amount of foreground usage (about 10 minutes or fewer) on a particular device may not be captured.
69
71
70
72
### App performance details
71
73
@@ -87,6 +89,8 @@ Selecting a device name opens the **Application reliability** tab for that devic
87
89
88
90
## Known issues
89
91
92
+
[!INCLUDE [Endpoint analytics export to csv value mapping known issue](includes/known-issue-csv-mapping.md)]
93
+
90
94
### Some eligible, enrolled devices aren't appearing in the report due to a client certificate issue
91
95
92
96
**Scenario**: In certain uncommon situations, devices may be missing from the **Application reliability** report. You can determine how many devices are reporting application reliability data by looking at the number of records in the table on the **Device performance** tab of the **Application reliability** report.
Copy file name to clipboardExpand all lines: memdocs/analytics/data-collection.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,11 +30,11 @@ Endpoint analytics is available in all Intune locations in global Azure. Endpoin
30
30
31
31
1. Devices send required functional data.
32
32
33
-
- For Intune and co-managed devices with the assigned policy, devices send require functional data directly to the Microsoft Endpoint Management Service in the Microsoft public cloud where is processed in near real time. For more information, see [Endpoints required for Intune-managed devices](troubleshoot.md#endpoints-required-for-intune-managed-devices).
33
+
- For Intune and co-managed devices with the assigned policy, devices send required functional data in near real time directly to the Microsoft Endpoint Management Service in the Microsoft public cloud where is processed every 24 hours. For more information, see [Endpoints required for Intune-managed devices](troubleshoot.md#endpoints-required-for-intune-managed-devices).
34
34
35
35
- For Configuration Manager-managed devices, data flows to the Microsoft Endpoint Management Service through the ConfigMgr [tenant attach](../configmgr/tenant-attach/device-sync-actions.md) connector. Devices don't need direct access to the Microsoft public cloud, but the ConfigMgr connector is cloud attached and requires connection to an Intune tenant. Devices send data to the Configuration Manager Server role every 24 hours, and the connector sends data to the Gateway Service every hour. For more information, see [Tenant attach data collection](../configmgr/tenant-attach/data-collection.md)
36
36
37
-
1. The Microsoft Endpoint Management service processes data for each device and publishes the results for both individual devices and organizational aggregates in the admin console using [MS Graph APIs](/graph/api/resources/intune-device-mgt-conceptual?view=graph-rest-beta&preserve-view=true). The maximum latency end to end is 25 hours and is gated by the time it takes to do the daily processing of insights and recommendations.
37
+
1. The Microsoft Endpoint Management service processes data for each device and publishes the results for both individual devices and organizational aggregates in the admin console using [MS Graph APIs](/graph/api/resources/intune-device-mgt-conceptual?view=graph-rest-beta&preserve-view=true). The maximum latency end to end is 96 hours.
38
38
39
39
> [!Note]
40
40
> When you first setup Endpoint analytics, add new clients to the [Intune data collection policy](settings.md#bkmk_profile), or [enable device upload](../configmgr/tenant-attach/device-sync-actions.md#bkmk_edit) for a new collection, the reports in endpoint analytics portal may not show complete data right away. The data required to compute the startup score for a device is generated during boot time. Depending on power settings and user behavior, it may take weeks after a device has been enrolled to show the startup score on the admin console.
description: In this quickstart, you enroll Configuration Manager devices into Endpoint analytics.
5
-
ms.date: 11/15/2021
5
+
ms.date: 05/03/2022
6
6
ms.prod: configuration-manager
7
7
ms.technology: configmgr-analytics
8
8
ms.topic: quickstart
@@ -33,7 +33,7 @@ Before you start this tutorial, make sure you have the following prerequisites:
33
33
34
34
### Licensing Prerequisites
35
35
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).
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). Proactive remediations has an additional licensing requirement, for more information see, the [Endpoint analytics licensing requirements overview](overview.md#licensing-prerequisites).
Copy file name to clipboardExpand all lines: memdocs/analytics/enroll-intune.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Quickstart - Enroll Intune devices
3
3
titleSuffix: Microsoft Endpoint Manager
4
4
description: In this quickstart, you enroll Intune devices into Endpoint analytics.
5
-
ms.date: 10/05/2021
5
+
ms.date: 05/03/2022
6
6
ms.prod: configuration-manager
7
7
ms.technology: configmgr-analytics
8
8
ms.topic: quickstart
@@ -43,7 +43,7 @@ To enroll devices to Endpoint analytics, they need to send required functional d
43
43
44
44
### Licensing Prerequisites
45
45
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).
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). Proactive remediations has an additional licensing requirement, for more information see, the [Endpoint analytics licensing requirements overview](overview.md#licensing-prerequisites).
<!--Don't apply H2 in this include file since they are context driven by article. Used in startup-performance.md, work-from-anywhere.md, app-reliability.md, and scores.md files -->
11
+
### Exported csv files display numerical values
12
+
13
+
When reporting data is exported to a `.csv` file, the exported data doesn't use the friendly names you're used to seeing in the online reports. Use the information below to map the data in the exported file into the meaning of the value:
14
+
15
+
**Application reliability report** </br>
16
+
17
+
- The `TotalAppUsageDuration` and `MeanTimeToFailure` columns in the `.csv` file are integer values with a unit of **minutes**
18
+
- A `MeanTimeToFailure` value of 2147483647 means `No crash events`
19
+
20
+
**Per device score report** </br>
21
+
22
+
- A value of `-1` or `-2` in the `EndpointAnalyticsScore`, `StartupPerformanceScore`, and `AppReliabilityScore` columns means the associated score is unavailable
23
+
- Health status: </br>
24
+
25
+
|HealthStatus `.csv` value| Report value|
26
+
|---|---|
27
+
|0|Unknown|
28
+
|1|Insufficient data|
29
+
|2|Needs attention|
30
+
|3|Meeting goals|
31
+
32
+
**Startup performance report** </br>
33
+
34
+
The `CoreBootTime`, `GPBootTime`, `CoreLogonTime`, `GPLogonTime`, `DesktopUsableTime`, `Median`, and `TimePerProcess` columns are integer values with a unit of **seconds**.
35
+
36
+
**Work from anywhere report** </br>
37
+
- Column name in `.csv` file: UpgradeEligibility </br>
38
+
Report column name: Windows 11 readiness status </br>
39
+
40
+
|`.csv` value| Report value|
41
+
|---|---|
42
+
|0|Upgraded|
43
+
|1|Unknown|
44
+
|2|Not capable|
45
+
|3|Capable|
46
+
47
+
- Column name in `.csv` file: GraphDeviceIsManaged </br> Report column name: Azure AD registered
0 commit comments