Skip to content

Commit e3f505e

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/memdocs-pr into EnrollmentRestrctionsGuide
2 parents e86cb18 + 1f2dfb9 commit e3f505e

7 files changed

Lines changed: 38 additions & 9 deletions

File tree

memdocs/intune/fundamentals/azure-virtual-desktop-multi-session.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ This feature supports Windows 10 or Windows 11 Enterprise multi-session VMs, whi
7070
- 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.
7171
- [Configuration Manager co-management](/configmgr/comanage/overview).
7272
- 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.
7474

7575
> [!NOTE]
7676
> If you're joining session hosts to Azure Active Directory Domain Services, you can't manage them using Intune.

memdocs/intune/fundamentals/education-settings-configure-ios-shared.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -210,4 +210,4 @@ The assignment completes, and Intune deploys the Classroom profile to the target
210210

211211
## Next Steps
212212

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/).

memdocs/intune/includes/intune-notices.md

Lines changed: 30 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,42 @@ description: include file
44
author: ErikjeMS
55
ms.service: microsoft-intune
66
ms.topic: include
7-
ms.date: 06/16/2022
7+
ms.date: 08/09/2022
88
ms.author: erikje
99
ms.custom: include file
1010
---
1111

1212
These notices provide important information that can help you prepare for future Intune changes and features.
1313

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+
1443
### Update your certificate connector for Microsoft Intune
1544

1645
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.

memdocs/intune/remote-actions/device-rename.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -47,6 +47,9 @@ If a device isn't listed here, it's not supported.
4747

4848
This feature doesn't support renaming hybrid Azure AD Windows devices.
4949

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+
5053
## Rename a device
5154

5255
1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).

memdocs/intune/remote-actions/devices-wipe.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -34,9 +34,6 @@ ms.collection:
3434

3535
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.
3636

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-
4037
## Wipe
4138

4239
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.
-112 KB
Loading

windows-365/enterprise/report-remoting-connection.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -49,15 +49,15 @@ To get to the **Remoting connection** report, sign in to [Microsoft Endpoint Man
4949

5050
## Remoting connection tab
5151

52-
The **Remoting connection** tab lists the following information:
52+
The **Remoting connection** tab lists the following information:
5353

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.
5555

5656
- Good = 0-100 milliseconds
5757
- Average = 100-200 milliseconds
5858
- Poor = more than 200 milliseconds
5959

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 users to 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.
6161

6262
- Good = 0-30 seconds
6363
- Average = 30-60 seconds

0 commit comments

Comments
 (0)