6/21/2023 0 Comments Apple configurator invalid profile![]() Tried Automator with iPad using HotSpot instead of the company provisioning SSID and it worked as expected. No prompt for Data Privacy, Touch ID, Passcode or Apps & Data. Tried with HotSpot alone and it worked as expected. Received Location services prompt ( as usual)ĭevice is now enrolled and process worked as expected. Received message: Awaiting final configuration (as usual) Once the iPad joined the HotSpot, it bypassed all prompts and it went directly to Remote Management. I went a few screens back to Wi-Fi and changed it to use my HotSpot. Then I get Remote Management, followed by an error: The Configuration for your iPad could not be downloaded. + Apps & Data (for Migration) (my AirWatch DEP Profile is set to bypass it) + Passcode (my AirWatch DEP Profile is set to bypass it) + Touch ID (my AirWatch DEP Profile is set to bypass it) + Showed Data Privacy (my AirWatch DEP Profile is set to bypass it) Using same company SSID used for device provisioning. Next, try manual process, as opposed to Automator. (Domain: MCCloudConfigErrorDomain Code: 33001) cfgutil: error: The configuration is not available. (Domain: MCCloudConfigErrorDomain Code: 33001). The Action: ' Prepare Devices Using Automated Enrollment' encountered an error: ' cfgutil: error: The Configuration is not available. (Using company SSID for device provisioning, been using it for 2 years.) Started Automator workflow process to enroll devices.ģ) Prepare Devices Using Automated Enrollment. In DEP, I assigned device to the correct MDM Server. ![]() Jeremy, et all - this is what I just tried.ĪW: Groups & Setting -> All Settings -> Devices & Users -> Apple -> Device Enrollment ProgramĪW: Uploaded Server Token and Completed AW configuration as usual. When you try to provision again without a full device wpie (Erase All Content And Settings), the serial number check has already been done and therefore the device activation record is already set.Įrasing all Content and Settings reset the activation record, forcing the iPad to go back to the Apple servers. These steps work for me and this is the reason I believe why.Ī device enrollment was attempted, however it failed becuase the device was not yet discoverd by AirWatch. What to do? In Apple Configurator 2, Version 2.9 (3J40) > Anything other than 'Unactivated' will make it fail. Once you can see the serial numbers under the Enrollment Status page, continue:ġ) connect the iPad to a mac os client running Apple Configuator.Ģ) When the device is connected, what is the activation status? If the serial numbers are NOT listed, do this: Devices listed under Enrollment status, Yes, OK. Does anybody have any suggestions that might be helpful?ĪPNs, good. It isn't affecting iOS device that are already enrolled just new enrollments. I've tried renewing the APNS cert as well as the DEP cert, even though neither were expired, I've verified that the firewall is open and allowing all Apple traffic. 9th for this issue and I'm lucky if I can get support to respond to an email once a day so I'm coming here for help. I've had a support ticket open since Aug. Today I upgraded to version 1907 and the issue still remains. I did the patch and it installed successfully but the error still persisted. At the time we were on version 9.6.0.8 and support suggested installing a patch to version 9.6.0.25. This happened on DEP devices assigned to the AirWatch server, DEP devices not assigned to the AirWatch server, and non-DEP devices. Invalid profile.' when enrolling iOS devices. So I assume this untrusted cert is the root of the error, have now removed accordingly.A couple of weeks ago we started seeing the message, ' The configuration for you iPad/iPod/iPhone could not be downloaded. Date ranges are valid on both, as to why the older org profile is untrusted, I can only guess. So I head on over to Configurator 2 Preferences, Orgs, and then look for the one that has the older certificate date when you click on 'Show Supervision Identity.' - this is where I find that the older idendity appears to have an untrusted cert, and the newer one is trusted. However, I now have two items in my Org list have exactly the same string, which isn't brilliant. It revalidated with the ABM apple ID and then the prepare went through on the iPad without error. So last thing to try was to choose the 'New Organization' option on the 'Assign to Organisation' option. I'm testing MDM differences, so have two MDMs setup (Jamf and the other both had this same error). The fix (for me) was to re-create the Organization profile as part of the Prepare steps. I just had this exact error in my new development environment.
0 Comments
Leave a Reply. |