milidog.blogg.se

1. #Apple configurator 2 invalid profile mcprofileerrordomain install#
2. #Apple configurator 2 invalid profile mcprofileerrordomain pro#

One of the more interesting events of April 28th Reason not to focus solely on death and destruction today. Mentioning a dead Volvo owner in my last Spark and so there appears to be no

#Apple configurator 2 invalid profile mcprofileerrordomain pro#

Spark! Pro Series - April 28th, 2023 Water Cooler.That's the only way the client will trust the profile if it's a. However, that means that, in order for a device to load the profile at startup (from the Welcome screen process) and trust the server, you need to set up Internet Sharing to share the server's Ethernet connection over WiFi (setting up a hotspot), and at the Welcome screen, select the server's hotspot for the internet connection. local hostname of your server, and it needs to have its DNS server turned on with an entry for its own hostname pointed at its own static IP. Note that if you are using a local server that does not yet have a real domain name, your devices need to have their DNS server entry set to the.

#Apple configurator 2 invalid profile mcprofileerrordomain install#

Only devices that you manually install profiles onto using Configurator 2 will honor that password restriction, and even then, Enterprise support tells me that if it's not a DEP device, the user can put the device in DFU mode to clear the profile (of course they may not be able to activate it if it was locked to an Apple ID, but that's another issue). I'd like to note that I was having this problem too, and another issue you will face is that if you're not a DEP member, that for any configuration profiles that you install from over the network %u2014 even on to a supervised device %u2014 your users will be able to manually delete those profiles off of the devices without needing to provide the password you set up to prevent profile removal. 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. 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.