If MDM enrollment requires multi-factor authentication, and the user hasn't signed in with a supported second factor, Windows displays a toast notification to the user to enroll. This issue should be transient, as the device retries after a short time. When trying to automatically enroll to Intune, but the Azure AD configuration isn't fully applied.
#Monity co to license#
License of user is in bad state blocking enrollment MDM enrollment hasn't been configured yet on Azure AD, or the enrollment URL isn't expected. The following table lists the most common errors. These errors can come from the MDM component in Windows, the core Windows OS, or the Configuration Manager client. This table is a list of enrollment errors from devices.
Hover over a chart section to show the number of devices transitioned for the workload. For more information, see Workloads able to be transitioned to Intune. Select a state in the tile to drill through to a list of devices in that state.ĭisplays a bar chart with the number of devices that you've transitioned to Microsoft Intune for the available workloads. Look in the ComanagementHandler.log for the following entry:Įnrolling device with RegisterDeviceWithManagementUsingAADDeviceCredentials If the device token fails, it falls back to previous behavior with the user token. To support this behavior, the device needs to be running Windows 10, version 1803 or later. It doesn't need to wait for a user to sign in to the device for auto-enrollment to start. To reduce the number of devices in this pending state, a new co-managed device automatically enrolls to the Microsoft Intune service based on its Azure AD device token.Shows the breakdown of device status in the following categories: Hover over a graph section to show the percentage of devices in that OS group.Ī funnel chart that shows the number of devices with the following states from the enrollment process: Shows the number of client devices per OS by version. For version 2103 and earlier, select the Co-management node.In the Configuration Manager console, go to the Monitoring workspace, and select the Cloud Attach node. The graphs can help identify devices that might need attention. This dashboard helps you review machines that are co-managed in your environment.
Applies to: Configuration Manager (current branch)Īfter you enable co-management, monitor co-management devices using the following methods:
0 kommentar(er)
