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. Apple may provide or recommend responses as a possible solution based on the information provided every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums.
INVALID PROFILE APPLE CONFIGURATOR 2 UPDATE
Then we exported a Profile from the “Automated Enrollment” page set up as follows: Enable Automated Enrollment: True Platform: Apple iOS Staging Mode: None. Solution: In Device Console > Organization > Settings > Apple DEP tab > click on the name of the DEP account > DEP Tab > click Update DEP. You can also recreate the attached mobileconfig in your MDM tool by specifying the Apple Team ID and Jun 01. 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. kext into your Library/Extensions folder. 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. 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. 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. When we try to enroll devices via Apple Configurator 2 using a pre-configured blueprint, the AC2 throws the error MCErrorProfileDomain 0x3e8 (1000). 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. On the DEP Server Setting page, click Set DEP Default Profile. When we try to enroll devices via Apple Configurator 2 using a pre-configured blueprint, the AC2 throws the error “ MCErrorProfileDomain 0x3e8 (1000)“. Set DEP profiles Go to Setting > iOS > DEP Server Setting. 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 kommentar(er)
