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/intune/fundamentals/azure-virtual-desktop-multi-session.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
@@ -70,7 +70,7 @@ This feature supports Windows 10 or Windows 11 Enterprise multi-session VMs, whi
70
70
- Configured with [Active Directory group policy](/windows/client-management/mdm/enroll-a-windows-10-device-automatically-using-group-policy), set to use Device credentials, and set to automatically enroll devices that are Hybrid Azure AD-joined.
- Azure AD-joined and enrolled in Microsoft Intune by enabling [Enroll the VM with Intune](/azure/virtual-desktop/deploy-azure-ad-joined-vm#deploy-azure-ad-joined-vms) in the Azure portal.
73
-
- Licensing: The appropriate Microsoft Intune license is required if a user or device benefits directly or indirectly from the Microsoft Intune service, including access to the Microsoft Intune service through a Microsoft API. For more information, see [Microsoft Intune licensing](../fundamentals/licenses#additional-information.md)
73
+
- Licensing: The appropriate Microsoft Intune license is required if a user or device benefits directly or indirectly from the Microsoft Intune service, including access to the Microsoft Intune service through a Microsoft API. For more information, see Microsoft Intune licensing.
74
74
75
75
> [!NOTE]
76
76
> If you're joining session hosts to Azure Active Directory Domain Services, you can't manage them using Intune.
Copy file name to clipboardExpand all lines: memdocs/intune/fundamentals/education-settings-configure-ios-shared.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
@@ -210,4 +210,4 @@ The assignment completes, and Intune deploys the Classroom profile to the target
210
210
211
211
## Next Steps
212
212
213
-
Now students can share devices between students, and students can pick up any iPad in a classroom, log in with a PIN and have it personalized with their content. For more information about Shared iPads, see the [Apple website](https://www.apple.com/education/it/).
213
+
Now students can share devices between students, and students can pick up any iPad in a classroom, log in with a PIN and have it personalized with their content. For more information about Shared iPads, see the [Apple website](https://www.apple.com/education/).
Copy file name to clipboardExpand all lines: memdocs/intune/includes/intune-notices.md
+30-1Lines changed: 30 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,13 +4,42 @@ description: include file
4
4
author: ErikjeMS
5
5
ms.service: microsoft-intune
6
6
ms.topic: include
7
-
ms.date: 06/16/2022
7
+
ms.date: 08/09/2022
8
8
ms.author: erikje
9
9
ms.custom: include file
10
10
---
11
11
12
12
These notices provide important information that can help you prepare for future Intune changes and features.
13
13
14
+
### Plan for Change: Ending support for Windows Information Protection
15
+
16
+
Microsoft Windows [announced](https://go.microsoft.com/fwlink/?linkid=2202124) they are ending support for Windows Information Protection (WIP), Microsoft Endpoint Manager will be discontinuing future investments in managing and deploying WIP. In addition to limiting future investments, we will remove support for WIP *without enrollment* scenario by the end of calendar year 2022.
17
+
18
+
### How does this affect you or your users?
19
+
20
+
If you have enabled WIP policies, you should turn off or disable these policies.
21
+
22
+
### How can you prepare?
23
+
24
+
We recommend that you take action to disable WIP to ensure users in your organization do not lose access to documents that have been protected by WIP policy. Read the blog [Support tip: End of support guidance for Windows Information Protection](https://aka.ms/Intune-WIP-support) for more details and options for removing WIP from your devices.
25
+
26
+
### Plan for Change: Ending support for Windows 8.1 <!-- 14740233 -->
27
+
28
+
Microsoft Intune will be ending support for devices running Windows 8.1 on **October 21, 2022**. Additionally, the sideloading key scenario for line-of-business apps will stop being supported since it is only applicable to Windows 8.1 devices.
29
+
30
+
Microsoft strongly recommends that you move to a supported version of Windows 10 or Windows 11, to avoid a scenario where you need service or support that is no longer available.
31
+
32
+
### How does this affect you or your users?
33
+
34
+
If you are managing Windows 8.1 devices those devices should be upgraded to a supported version of Windows 10 or Windows 11. There is no impact to existing devices and polices, however, you will not be able to enroll new devices if they are running Windows 8.1.
35
+
36
+
### How can you prepare?
37
+
38
+
Upgrade your Windows 8.1 devices, if applicable. To determine which users’ devices are running Windows 8.1 navigate to [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) > **Devices** > **Windows** > **Windows devices**, and filter by OS.
39
+
40
+
**Additional information**
41
+
-[Manage operating system versions with Intune](../fundamentals/manage-os-versions.md)
42
+
14
43
### Update your certificate connector for Microsoft Intune
15
44
16
45
As of June 1, 2022, Intune certificate connectors earlier than version 6.2101.13.0 may no longer work as expected and stop connecting to the Intune service. See [Certificate Connectors for Microsoft Intune](../protect/certificate-connector-overview.md) for additional information on the certificate connector lifecycle and support.
Copy file name to clipboardExpand all lines: memdocs/intune/remote-actions/device-rename.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,6 +47,9 @@ If a device isn't listed here, it's not supported.
47
47
48
48
This feature doesn't support renaming hybrid Azure AD Windows devices.
49
49
50
+
> [!NOTE]
51
+
> Renaming of Android Enterprise devices will only change the name in Intune and not on the device itself. The Device name in Intune is a friendly name that users are free to change.
52
+
50
53
## Rename a device
51
54
52
55
1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
Copy file name to clipboardExpand all lines: memdocs/intune/remote-actions/devices-wipe.md
-3Lines changed: 0 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,9 +34,6 @@ ms.collection:
34
34
35
35
By using the **Retire** or **Wipe** actions, you can remove devices from Intune that are no longer needed, being repurposed, or missing. Users can also issue a remote command from the Intune Company Portal to devices that are enrolled in Intune.
36
36
37
-
> [!NOTE]
38
-
> Before you remove a user from Azure Active Directory (Azure AD), use the **Wipe** or **Retire** actions for all devices that are associated with that user. If you remove users that have managed devices from Azure AD, Intune can no longer wipe or retire those devices.
39
-
40
37
## Wipe
41
38
42
39
The **Wipe** action restores a device to its factory default settings. The user data is kept if you choose the **Retain enrollment state and user account** checkbox. Otherwise, all data, apps, and settings will be removed.
Copy file name to clipboardExpand all lines: windows-365/enterprise/report-remoting-connection.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,15 +49,15 @@ To get to the **Remoting connection** report, sign in to [Microsoft Endpoint Man
49
49
50
50
## Remoting connection tab
51
51
52
-
The **Remoting connection** tab lists the following information:
52
+
The **Remoting connection** tab lists the following information:
53
53
54
-
**Round Trip Time (ms)** is the speed and reliability of network connections from the user location. Times are given for the most recent time (p95 (Last)) and the Median time. The times for the ratings are:
54
+
**Round Trip Time (ms)** is the time taken for traffic from users' devices to reach Cloud PC and return. This metric is an indicator of the quality of the connection and can be used to determine the user’s experience. Values displayed are the median time and 95th percentile value of the most recent reading of the metric (p95 Last). A rating is provided for these values based on the criteria below.
55
55
56
56
- Good = 0-100 milliseconds
57
57
- Average = 100-200 milliseconds
58
58
- Poor = more than 200 milliseconds
59
59
60
-
**Sign in time (sec)** is the time taken for traffic from users' devices to reach Cloud PC and return. This metric is an indicator of the quality of the connection and can be used to determine the user’s experience. Values displayed are for the median time of the most recent reading of the metric’s 95th percentile value (p95 (Last)). A rating is provided for these values based on the criteria below. The times for the ratings are:
60
+
**Sign in time (sec)** is the total time taken for usersto connect to the Cloud PC. Values displayed are the median time and 95th percentile value of the most recent reading of the metric(p95 Last). A rating is provided for these values based on the criteria below.
0 commit comments