New! Configurator 360 2015 Keygen Again Zip Full
Keena Wiegert
I did not, still getting invalid profile when enrolling. If I go back in the setup wizard and forward a few times, I can get it to go through. Sounds like it's hitting a node that has an invalid cert or something.
Have you made sure to put the Serial Number of the device into the school manager? Maybe try running configurator, having it fail, enter the serial number and then seeing if you get the invalid profile still. Or add the serial number to the school manager before running configurator.
Follow these?
1. Add to DEP using Apple Configurator 2.5
2. Assign to your MDM in ABM/ASM
3. Assign to PreStage Enrolment Profile
4. Wipe/Restore the iOS devices again using Apple Configurator 2.5
Can you explain step #1 on your list? I've always plugged them into configurator, restored them to the latest OS, and then went through automated enrollment (making sure to select a WiFi profile first.)
Did you ever get this resolved? after days trying to follow various instructions to get something into mdm (and the solution being that the MDM is actually school.apple.com NOT our jamf URL grrrrr....) i now get stuck with this invalid profile message. I thought it was the wireless profile i was trying to apply (nothing can be fucking clear ever in apple land...) but i reformatted the ipod and used the USB internet sharing from a mac laptop to make the internet connection.
on the device itself remote management screen, i get "invalid profile" but i have no idea what its reffering to. On the apple configurator, i get the message as above "invalid profile [MCProfileErrorDomain - 0x3e8 (1000)]
Oh i just got it. actually the trick is that you do your prepare. Prepare finishes, and before you configure the ipod, you switch it in school manager to use jss as the mdm server. With that done, the remote management doesnt even run and it comes up as basically a unconfigured ipod. You walk through all the steps till you get to the home screen. Then you factory wipe the ipad.
I just had this exact error in my new development environment. The fix (for me) was to re-create the Organization profile as part of the Prepare steps. I'm testing MDM differences, so have two MDMs setup (Jamf and the other both had this same error).
So last thing to try was to choose the 'New Organization' option on the 'Assign to Organisation' option. It revalidated with the ABM apple ID and then the prepare went through on the iPad without error.
However, I now have two items in my Org list have exactly the same string, which isn't brilliant. 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. Date ranges are valid on both, as to why the older org profile is untrusted, I can only guess.
We get this all the time with devices not bought directly from Apple. It happens basically because Configurator adds it to Apple School Manager but there isn't a profile / enrollment waiting for it in Jamf yet. So basically you can ignore the error - go to ASM find the serial and assign it to your server - go to Jamf and add it to a prestage enrollment - erase the iPod and when it comes back on it will enroll.
I also found that if you are doing dynamic invitations and put the URL into Apple Configurator when you are first setting it up, AC will default to the static version. You will need to go and edit the server again to modify the server URL again.
Jamf's purpose is to simplify work by helping organizations manage and secure an Apple experience that end users love and organizations trust. Jamf is the only company in the world that provides a complete management and security solution for an Apple-first environment that is enterprise secure, consumer simple and protects personal privacy. Learn about Jamf.
This site contains User Content submitted by Jamf Nation community members. Jamf does not review User Content submitted by members or other third parties before it is posted. All content on Jamf Nation is for informational purposes only. Information and posts may be out of date when you view them. Jamf is not responsible for, nor assumes any liability for any User Content or other third-party content appearing on Jamf Nation.
On the apple configurator 2, during the restart process it tries to "Downloading activation records for device" and keeps going step 1 of 2, then 2 of 3, 3 of 4 etc.... It continuously fails and won't see the IPad as prepared.
I had a similar issue and here is what worked after so many attempts: - Use iTunes to Restored the ipad to the Factory setting- After restore, when it gets to the point where you are asked to set it up as a new iPad or restore from a backup, click CANCEL- Connect it to Apple Configurator again and prepare it.
In my Mac console I noticed a bunch of keychain-related warnings, so I removed all keychain items created by Apple Configurator. Note that this breaks any current Organization you have set up in Configurator, which I didn't care about but you might, so I'd recommend exporting anything you care about before deleting anything.
I'd been through the Erase process enough times this week to not have much luck that it would work, but I decided to try it one more time, and also log into a different iCloud account (that this device had never been associated with) when the device came back up. In the end the device was Supervised.
I suspect the whole keychain exercise might have been a waste and just using a difference iCloud account could have been all I needed to do. If I get a chance I'll try to narrow it down on another device I've been having problems with.
Device preparation was somehow broken for me. Turns out my Supervision Trust Profile was invalid on my machine. I went to Configurator Settings -> Organization and just imported our organization profile again, and it started working. Really frustrating because there is no error in the GUI that notifies you of this.
Why won't configurator let me have a configuration profile installed as well as installing an app. Whenever I have an configuration profile installed, I can't install any app. If there is not profile installed, I can install apps no problem. I work in a school, with a class set of iPads and this limits me from b eing able to keep the students from doing things like install their own apps, using the camera, etc, while I'm trying to teach.
I work for a school district too and feel your frustration. Seems that there are a lot of weird workarounds to get Configurator to do what we want it to do. Here's what I think is happening in your case.
The workaround is to do a "double sync." Uncheck the configuration profile that is on each iPad (the one that prevents installing apps) and do a quick sync to remove that configuration profile from the iPads. After the config profile has been removed from the iPads, do another sync to install all of the apps (with no config profiles). After that sync is complete, then checkmark the configuration profile to lock down installing apps and do a final sync. I guess its more of a "triple sync" than a "double sync" but should get the results you are looking for.
The first time we pushed apps or profile seemed to be working fine. But when we collected the iPads again to update apps and pushed new apps. We feel it's more complicated and got errors. Here was what we did:
As you can see, it's installing apps first before installing configuration (the profile). If your profile was set to not to allow the iPad to install apps (meaning you removed the App Store from the iPad), the AC can't push updated/new apps to the iPad. That's why you can't update the apps from iTunes at the beginning and that's why on step 3 you need to remove your initial profile before pushing updated/new apps.
If the apps in the AC already got updated through iTunes or there were new apps in the AC, that will pop up the "Can't install apps" error. If the apps in the AC are still the same version as those in the iPad, it won't pop up that error. That's why we do not update the apps through iTunes at the first beginning to make sure the apps versions in the iPads are still the same as those in the AC.
To summarize again, the iPads need the Apple Store back before they can be loaded with updated/new apps by the AC. The profile installed on the iPads were blocking the AC to push updated/new apps. That's why we have to remove that profile and put it back in the end.
Thanks, I will give that a try. Do you update all your iPads at once? I have 50 for our school, and I update in groups, because I update by plugging in, not wirelessly. It seems like this would work for the first group I plug in, but then when I get to the next group, I would be back to the same problem. I haven't tried yet so I don't know. Thanks for the information...I'm glad to have something to try out.
You are right. It only works for one group. If you plan to work on different groups, you have to put the initial version of apps back to AC so that they are the same version of apps as those in the 2nd group. It's a headache to keep doing this again and again, especially working on different groups of iPads that have different sets of apps.
So we just ordered JAMF and started using it. But JAMF also has the same problem that all third party MDM software companies have. They still can not go around the requirement of inputting Apple ID and password when pushing apps installation to the iPads.
7fc3f7cf58