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
+3-1Lines changed: 3 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
@@ -89,6 +89,8 @@ Selecting a device name opens the **Application reliability** tab for that devic
89
89
90
90
## Known issues
91
91
92
+
[!INCLUDE [Endpoint analytics export to csv value mapping known issue](includes/known-issue-csv-mapping.md)]
93
+
92
94
### Some eligible, enrolled devices aren't appearing in the report due to a client certificate issue
93
95
94
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.
<!--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
- A script package can contain a detection script only or both a detection script and a remediation script.
62
64
- Ensure the scripts are encoded in UTF-8.
63
-
64
65
- The maximum allowed output size limit is 2048 characters.
65
-
66
66
- If the option **Enforce script signature check** is enabled in the [Settings](#bkmk_prs_deploy) page of creating a script package, the script runs using the device's PowerShell execution policy. The default execution policy for Windows client computers is **Restricted**. The default execution for Windows Server devices is **RemoteSigned**. For more information, see [PowerShell execution policies](/powershell/module/microsoft.powershell.core/about/about_execution_policies#powershell-execution-policies).
67
67
- Scripts built into Proactive remediations are signed and the certificate is added to the **Trusted Publishers** certificate store of the device.
68
68
- When using third-party scripts that are signed, make sure the certificate is in the **Trusted Publishers** certificate store. As with any certificate, the certificate authority must be trusted by the device.
Copy file name to clipboardExpand all lines: memdocs/analytics/scores.md
+10-2Lines changed: 10 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: Scores, baselines, and insights in Endpoint Analytics
3
3
titleSuffix: Microsoft Endpoint Manager
4
4
description: Learn about scores, baselines, and insights in Endpoint Analytics
5
-
ms.date: 12/15/2021
5
+
ms.date: 03/31/2022
6
6
ms.prod: configuration-manager
7
7
ms.technology: configmgr-analytics
8
8
ms.topic: conceptual
@@ -57,7 +57,11 @@ To help you identify devices that could be impacting user experience, Endpoint a
57
57
58
58
Selecting a device from the **Devices scores** tab loads a device page that gives you more information. From the device's **Startup performance** tab, review **Boot history** and **Sign-in history** for experience impacting trends. The **Application reliability** tab provides insight into potential issues for desktop applications on the managed device.
59
59
60
-
:::image type="content" source="media/8816759-per-device-scores.png" alt-text="Screenshot of a device's Endpoint analytics score with the startup performance and application reliability subscores." lightbox="media/8816759-per-device-scores.png":::
60
+
:::image type="content" source="media/8816759-per-device-scores.png" alt-text="Screenshot of a device's Endpoint analytics score with the startup performance and application reliability subscores." lightbox="media/8816759-per-device-scores.png":::
61
+
62
+
You can also access per device scores on a device's **User experience** page. From the **User experience** page you can review the **Endpoint analytics**, **Startup performance**, and **Application reliability** information for the specific device.
63
+
64
+
:::image type="content" source="media/user-experience-page.png" alt-text="Screenshot of a device's user experience page displaying the startup performance tab." lightbox="media/user-experience-page.png":::
61
65
62
66
### <aname="bkmk_drill-in"></a> Device level drill-in from reports
63
67
@@ -76,6 +80,10 @@ Use the **Add filter** option on tables to display items that match your criteri
76
80
> - The **Disk type** filter doesn't support the value **Unknown**<!--12829141-->.
77
81
> - Filtering on **Startup performance score** from **Overview** > **Device Scores** returns devices with a score of "--". <!--12829158-->
78
82
83
+
## Known issues
84
+
85
+
[!INCLUDE [Endpoint analytics export to csv value mapping known issue](includes/known-issue-csv-mapping.md)]
86
+
79
87
## Next steps
80
88
81
89
- Use [Proactive remediations](proactive-remediations.md) to gather more data and take action on devices
0 commit comments