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
Copy file name to clipboardExpand all lines: memdocs/analytics/startup-performance.md
+6-2Lines changed: 6 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: Startup performance in Endpoint Analytics
3
3
titleSuffix: Microsoft Endpoint Manager
4
4
description: Get details about device startup performance in Endpoint Analytics
5
-
ms.date: 11/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
@@ -47,7 +47,7 @@ The **Startup performance** page also provides a prioritized list of **Insights
47
47
48
48
Startup performance provides an insight on the number of devices on which the boot drive is a hard disk. Hard disk drives typically result in boot times three to four times longer than solid-state drives. We also report the expected improvement to start up performance you would gain by moving to solid-state drives.
49
49
50
-
Click though to see the list of devices that have hard disk drives. The recommended action is to upgrade these devices to solid-state drives.
50
+
Click through to see the list of devices that have hard disk drives. The recommended action is to upgrade these devices to solid-state drives.
51
51
52
52
### <aname="bkmk_gp"></a> Group Policy
53
53
@@ -74,6 +74,10 @@ The **Startup performance** page has reporting tabs that provide support for the
74
74
-**Median delay**: The median delay time of the process for the counted devices.
75
75
-**Total delay**: The sum of the delays for all of the counted devices.
76
76
77
+
## Known issues
78
+
79
+
[!INCLUDE [Endpoint analytics export to csv value mapping known issue](includes/known-issue-csv-mapping.md)]
80
+
77
81
## Next steps
78
82
79
83
- Use the [Work from anywhere report](work-from-anywhere.md).
Copy file name to clipboardExpand all lines: memdocs/autopilot/enrollment-autopilot.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
@@ -52,7 +52,7 @@ ms.collection:
52
52
53
53
-**Group type**: Select **Security**.
54
54
-**Group name** and **Group description**: Enter a name and description for your group.
55
-
-**Azure AD roles can be assigned to the group (Preview)**: **Yes** allows Azure AD roles to be assigned to the group you're creating. Once set, the group is permanently and always allowed to be assigned Azure AD roles. When set to **No**, Azure AD roles aren't assigned to the this group.
55
+
-**Azure AD roles can be assigned to the group**: **Yes** allows Azure AD roles to be assigned to the group you're creating. Once set, the group is permanently and always allowed to be assigned Azure AD roles. When set to **No**, Azure AD roles aren't assigned to this group.
56
56
57
57
For more information, see [Use cloud groups to manage role assignments in Azure AD](/azure/active-directory/roles/groups-concept).
Copy file name to clipboardExpand all lines: memdocs/autopilot/windows-autopilot-hybrid.md
+9-4Lines changed: 9 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -126,10 +126,13 @@ The Intune Connector requires the [same endpoints as Intune](../intune/fundament
126
126
4. Open the downloaded Connector setup file, *ODJConnectorBootstrapper.exe*, to install the Connector.
127
127
5. At the end of the setup, select **Configure**.
128
128
6. Select **Sign In**.
129
-
7. Enter the user Global Administrator or Intune Administrator role credentials.
129
+
7. Enter the Global administrator or Intune administrator role credentials.
130
130
The user account must have an assigned Intune license.
131
131
8. Go to **Devices** > **Windows** > **Windows enrollment** > **Intune Connector for Active Directory**, and then confirm that the connection status is **Active**.
132
132
133
+
> [!NOTE]
134
+
> The Global administrator role is a temporary requirement at the time of installation.
135
+
133
136
> [!NOTE]
134
137
> After you sign in to the Connector, it might take a couple of minutes to appear in the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431). It appears only if it can successfully communicate with the Intune service.
135
138
@@ -204,6 +207,7 @@ Here is a list of VPN clients that are known to be tested and validated:
204
207
- Checkpoint (Win32 client)
205
208
- Citrix NetScaler (Win32 client)
206
209
- SonicWall (Win32 client)
210
+
- FortiClient VPN (Win32 client)
207
211
208
212
**Not supported clients:**
209
213
- UWP-based VPN plug-ins
@@ -246,9 +250,10 @@ It takes about 15 minutes for the device profile status to change from *Not assi
246
250
-**Name**: Enter a descriptive name for the new profile.
247
251
-**Description**: Enter a description for the profile.
248
252
-**Platform**: Select **Windows 10 and later**.
249
-
-**Profile type**: Select **Domain Join**.
250
-
3. Select **Settings**, and then provide a **Computer name prefix**, **Domain name**.
251
-
4. (Optional) Provide an **Organizational unit** (OU) in [DN format](/windows/desktop/ad/object-names-and-identities#distinguished-name). Your options include:
253
+
-**Profile type**: Select **Templates**, choose the template name **Domain Join** and select **Create**.
254
+
3. Enter the **Name** and **Description** and select **Next**.
255
+
5. Provide a **Computer name prefix** and **Domain name**.
256
+
6. (Optional) Provide an **Organizational unit** (OU) in [DN format](/windows/desktop/ad/object-names-and-identities#distinguished-name). Your options include:
252
257
- Provide an OU in which you've delegated control to your Windows 2016 device that is running the Intune Connector.
253
258
- Provide an OU in which you've delegated control to the root computers in your on-prem Active Directory.
254
259
- If you leave this blank, the computer object will be created in the Active Directory default container (CN=Computers if you never [changed it](https://support.microsoft.com/help/324949/redirecting-the-users-and-computers-containers-in-active-directory-dom)).
Copy file name to clipboardExpand all lines: memdocs/configmgr/apps/deploy-use/deploy-edge.md
+7-3Lines changed: 7 additions & 3 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: Deploy and update Microsoft Edge, version 77 and later
3
3
titleSuffix: Configuration Manager
4
4
description: How to deploy and update Microsoft Edge, version 77 and later with Configuration Manager
5
-
ms.date: 10/13/2021
5
+
ms.date: 04/07/2022
6
6
ms.prod: configuration-manager
7
7
ms.technology: configmgr-app
8
8
ms.topic: conceptual
@@ -16,11 +16,11 @@ ms.localizationpriority: medium
16
16
17
17
*Applies to: Configuration Manager (Current Branch)*
18
18
19
-
The all-new Microsoft Edge is ready for business. You can deploy [Microsoft Edge, version 77 and later](/deployedge/) to your users. A PowerShell script is used to install the Edge build selected. The script also turns off automatic updates for Edge so they can be managed with Configuration Manager.
19
+
The all-new Microsoft Edge is ready for business. You can deploy [Microsoft Edge, version 77 and later](/deployedge/) to your users. A PowerShell script is used to install the Microsoft Edge build selected. The script also turns off automatic updates for Microsoft Edge so they can be managed with Configuration Manager.
20
20
21
21
## <aname="bkmk_Microsoft_Edge"></a> Deploy Microsoft Edge
22
22
<!--4561024-->
23
-
Admins can pick the Beta, Dev, or Stable channel, along with a version of the Microsoft Edge client to deploy. Each release incorporates learnings and improvements from our customers and community.
23
+
Admins can pick the Beta, Dev, or Stable channel, along with a version of the Microsoft Edge client to deploy. Each release incorporates learnings and improvements from our customers and community. For more information, see [Microsoft Edge release schedule](/DeployEdge/microsoft-edge-release-schedule).
24
24
25
25
### Prerequisites for deploying
26
26
@@ -100,6 +100,8 @@ Starting in Configuration Manager 2002, the Microsoft Edge Management dashboard
100
100
101
101
### Prerequisites for the dashboard
102
102
103
+
For Configuration Manager version 2203 or later, the [WebView2 console extension](../../core/servers/manage/admin-console-extensions.md#bkmk_notification) must be installed. If needed, select the notification bell in the top right corner of the console to install the extension.<!--10024154-->
104
+
103
105
Enable the following properties in the below [hardware inventory](../../core/clients/manage/inventory/extend-hardware-inventory.md) classes for the Microsoft Edge Management dashboard:
@@ -114,6 +116,8 @@ Enable the following properties in the below [hardware inventory](../../core/cli
114
116
- BrowserName
115
117
- UsagePercentage
116
118
119
+
120
+
117
121
### View the dashboard
118
122
119
123
From the **Software Library** workspace, click **Microsoft Edge Management** to see the dashboard. Change the collection for the graph data by clicking **Browse** and choosing another collection. By default your five largest collections are in the drop-down list. When you select a collection that isn't in the list, the newly selected collection takes the bottom spot on your drop-down list.
0 commit comments