![]() For example, they'll see this error if Intune has been set as the MDM authority, but the user has a System Center 2012 R2 Configuration Manager license. Users must have the correct license type for the mobile device management authority. The device can't be enrolled because the user's account isn't yet a member of a required user group or the user does not have the correct license. Make sure that your user's device is running iOS/iPadOS version 8.0 or later. Confirm that device is running iOS/iPadOS version 8.0 or later. The mobile device type that you're trying to enroll isn't supported. The user might have tried to enroll using a non-iOS device. For Microsoft 365, see Create an APNs Certificate for iOS devices. For Intune standalone, see Renew Apple MDM push certificate. If you replace the certificate, you have to re-enroll all iOS/iPadOS devices in Intune. Important: Make sure that you renew the APNs certificate. Renew the APNs certificate, and then re-enroll the device. Enrollment will fail and this message will appear if: There's a problem with the certificate that lets the mobile device communicate with your company's network. Review the information about how to set up users in Sync Active Directory and add users to Intune and organizing users and devices. The steps to get an APNs certificate weren't completed, or.The Apple Push Notification Service (APNs) provides a channel to contact enrolled iOS/iPadOS devices. Remove the app, validate user credentials, and then resinstall the app. The Company Portal app on the device is out of date or corrupted. ![]() The user must remove one of their currently enrolled mobile devices from the Company Portal before enrolling another. Too many mobile devices are enrolled already. ![]() For instructions, see Set up iOS/iPadOS and Mac device management, Get an Apple MDM push certificate, and Renew Apple MDM push certificate. Check that enrollment has been set up correctly and that iOS/iPadOS as a platform is enabled. The Apple Push Notification Service (APNs) certificate is missing, invalid, or expired. The following table lists errors that end users might see while enrolling iOS/iPadOS devices in Intune. See Troubleshoot device enrollment in Microsoft Intune for additional, general troubleshooting scenarios. I dearly hope someonce can provide advice to what we are doing wrong, or what might be the solution to it.This article helps Intune administrators understand and troubleshoot problems when enrolling iOS/iPadOS devices in Intune. We then bundled that to a Blueprint in AC, which we configured using the " Automated Enrollment" option loading a WiFi-Profile and the exported Profile from WS1 to it set no Username or Password, and prepared it, which failed. Then we exported a Profile from the "Automated Enrollment" page set up as follows: Enable Automated Enrollment: True Platform: Apple iOS Staging Mode: None. Next, we set up our company in the AC2, and exported the Supervision Identity Certificate to the profile in WS1 within "Device Enrollment Program" as mentioned above. We've got a Profile for it, in which we have selected the following: Require MDM Enrollment: True Supervision: Enabled Lock MDM Profile: Enabled Device Pairing: Enabled Custom Enrollment: Enabled Custom Prompt: Disabled Authentication: fixed to True Await Configuration: True. Therefore, we have the "Device Enrollment Program" set up as (we think it's) required, there is a valid Token, and everything syncs just fine. New Devices from our suppliers/partners automatically show up here, and we have no problems directly enrolling them to WS1. We have an up and running ABM connected to our WorkspaceONE Console. ![]() By not completing the Preperation process a couple of times, we obviously never truly set up our first device using AC2, but there are now six registrations showing up in ABM for that particular iPad. The weird part is, the registration, even though it seemingly failed, is active in ABM. If you were to ignore that, the Remote Management Page during the Device's setup says "invalid profile", and it takes you back to the WiFi Settings. When we try to enroll devices via Apple Configurator 2 using a pre-configured blueprint, the AC2 throws the error " MCErrorProfileDomain 0x3e8 (1000)". Since we now want to use all of the functionalities that come with it, we want to enroll existing Devices to it using Apple Configurator 2. We recently joined the Apple Business Manager, formerly DEP Program. ![]()
0 Comments
Leave a Reply. |