![]() ![]() ![]() When I try testing the URL in a browser I get this error which seems to confirm that its responding. I have double checked the URL for the MDM server and made sure to replace the "myserver" part of the URL with the name of the OS X Server. There is some step in the setup that I have forgotten or misconfigured somehow that is preventing this stage from working. My thoughts are this is where the break down is. It is then that I am prompted to authenticate, which I have not been able to do using any credentials, domain or local. LoginPrompt = "Please enter your credentials for \U201cDesignworks Clothing Co\U201d:" US Desc: The username or password was incorrect. Error: NSError:ĭesc : The username or password was incorrect. Aborting.Īpr 21 09:25:56 iPhone Setup : (Error) MC: failed to communicate to the server. Text Apr 21 09:25:56 iPhone profiled : SecTrustEvaluate Īpr 21 09:25:56 iPhone Setup : (Error) MC: We have failed too many times. (EDIT: Updated instructions above as per danclarke5's comment, for clarity. In the Profile manager Web UI, make sure the below is set for the user or group that is applying the profile to the device and you should be good to go! =) SO! for those of you struggling with this too, that mystery setting is this. I was also able to isolate an issue with respect to time zones and getting the correct time on the device in order for authentication to work, which we reported as a bug on my behalf. So after a few days of not hearing anything, it turns out that Jason went to the trouble of replicating my environment and replicated the issue himself and also resolved it via an undocumented requirement of a User setting in Profile Manager. The console logs seemed to point to this being the issue but there was no documentation that he could refer to to confirm, hence ending the call to do some more research and follow up. So while we couldn't find the exact cause of the issue during the call, after completely resetting my Server install back to defaults I might add (something I was fortunately in a position to do because it was really only a test environment) we ended the call with Jason to follow up on what we thought the issue was. The whole support experience was excellent.) (BTW despite speaking to a few people who couldn't help me, at least they identified it quickly and escalated my case until I got in touch with someone who could. Update: Enterprise Support was able to get on a call and provide information from Engineering, indicating that they see the device inside of DEP but somehow "also not associated with your organization." Sounds like a partially-enrolled device but stuck in a halfway point.So I called Apple Support and got my call escalated to the Enterprise Team after a few false starts and scheduled callbacks and eventually got to spend a few hours with a friendly chap by the name of Jason who helped me as best he could. Much thanks in advance for any ideas or asssistance. Some research on the various strings in the error message only found some strings from the Setup Assistant binary that provided a possible error code "CLOUD_CONFIG_INVALID_DEVICE_ERROR", but I'm not able to come up with any reason as to why that would be showing up - as far as I'm aware, this isn't a fake Apple device, nor am I trying to enroll a non-Apple computer. I'm working with Enterprise Support, but I'm worried that a resolution won't be anytime soon, as the escalation questions that I was asked to provided were all specific to Configurator 2 on macOS. Switched from my home DNS server to Google publicĮthernet connection, share WiFi settings from currently-connected network on iPhone, use known good configuration profile. Tested on multiple networks: iPhone hotspot, residential network without DPI, corporate network without DPI Revive and restore from a freshly downloaded macOS 12.1 IPSW USEnglishDescription = "Provisional Enrollment failed." : The cloud configuration service could not verify the identity of this device.ĬloudConfigurationErrorType = CloudConfigurationFatalError ![]() : The cloud configuration service could not verify the identity of this device.ĭesc. When attempting to enroll after finding the pairing animation in the viewfinder of the app, Configurator lists a green check on the history for the Mac but the MBP fails with the same Provisional Enrollment failure: I'm trying to enroll a recently-purchased (~1 week?) M1 MBP from the Apple refurbished store into my ABM account using the Configurator 1.0 app released to the public. Hoping someone might be able to help with some more information or background on what's going on: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |