- Joined
- Oct 17, 2016
- Messages
- 203
- Reaction score
- 9
Hi again Cory,
Ok, but um, they already have that information. But I don't want to pound this to death. I agree they are unlikely to want to re-enroll it. Fair chance they won't want to bother with un-enrolling it too. Ticket to MacOfAllTrades unanswered so far.
I could of course be wrong given my novice status on this issue, but so far at least I seem to have found a way around the automatic Profile setup.
1) Install OSX on a backup drive connected to another Mac. Thus, Setup Assistant doesn't see affected Mac.
2) Copy that OSX over to the affected machine.
The MDM Profiles are not installed on the affected machine, but....
The affected machine does toss up a nag screen each time you boot asking you if want to install the MDM Profiles. I find this puzzling, but it's progress.
If I knew how to write an Applescript or other mechanism to auto-dismiss the nag screen, I think I'd be done. At least that's what it looks like now. It wouldn't surprise me to be further surprised however.
Thanks again for educating me on this issue. Without you I'd still be deep in the dark.
The point is this...it cannot be enrolled again after deletion, because they would need several pieces of information to re-enroll it: UUID, serial number, IP address, etc.
Ok, but um, they already have that information. But I don't want to pound this to death. I agree they are unlikely to want to re-enroll it. Fair chance they won't want to bother with un-enrolling it too. Ticket to MacOfAllTrades unanswered so far.
Because it is then enrolled in the MDM and registered with DEP, the security/tracking components come into play, as well as the ability to automatically configure it if it is erased completely, when it contacts Apple's servers during the Setup Assistant phase.
I could of course be wrong given my novice status on this issue, but so far at least I seem to have found a way around the automatic Profile setup.
1) Install OSX on a backup drive connected to another Mac. Thus, Setup Assistant doesn't see affected Mac.
2) Copy that OSX over to the affected machine.
The MDM Profiles are not installed on the affected machine, but....
The affected machine does toss up a nag screen each time you boot asking you if want to install the MDM Profiles. I find this puzzling, but it's progress.
If I knew how to write an Applescript or other mechanism to auto-dismiss the nag screen, I think I'd be done. At least that's what it looks like now. It wouldn't surprise me to be further surprised however.
Thanks again for educating me on this issue. Without you I'd still be deep in the dark.