Ventura docs for M2 Macs in this comment: https://gist.github.com/henrik242/65d26a7deca30bdb9828e183809690bd?permalink_comment_id=4555340#gistcomment-4555340
Old Monterey docs in this old revision: https://gist.github.com/henrik242/65d26a7deca30bdb9828e183809690bd/32c410e3a1de73539c76fa13ea5486569c4e0c5d
Solution for Sonoma: https://gist.github.com/sghiassy/a3927405cf4ffe81242f4ecb01c382ac
is there any update about sequoia? anyone updated from 14.6 to 15?
I did this last year when I upgraded to Sonoma after I received a notification.
'# Block Mac from reaching the domain iprofiles.apple.com
0.0.0.0 iprofiles.apple.com'
Just recently I updated to 14.7 so far no problem.
To let you know I didn't do any bypass. I'm only blocking the domain.
I'm waiting for someone to let me know that I'll be safe with Sequoia after the update with this method.
is there any update about sequoia? anyone updated from 14.6 to 15?
I updated to 15 from the latest version of 14 Sonoma.
I made sure my host file was blocking all. Then I also blocked all the Apple sites on my router and updated
It was like a normal update nothing special
And works perfectly no alerts or pop ups and terminal commands to check MDM reports no.
@Jbb08 Thank you for your answer I will do the same and let everyone know.
Around 1 hour before I updated to 15. I'm using it without problem now.
Another one... anyone updated from MDM ventura (13.7) to 15? (2021 MBP M1)
Thanks
Another one... anyone updated from MDM ventura (13.7) to 15? (2021 MBP M1)
Thanks
I have the same questions. Used my instructions here on ventura but would like to migrate to 15.
https://gist.github.com/henrik242/65d26a7deca30bdb9828e183809690bd?permalink_comment_id=4620471#gistcomment-4620471
FYI, rebooted my MackbookPro 2,6 GHz 6-Core Intel Core i7 Sequoia the other day, hand had to hack back in. it worked with @joshworksit's last described approach (mix of setting up a new admin user and, changing settings and such).
echo "0.0.0.0 deviceenrollment.apple.com" >>/Volumes/Macintosh\ HD/etc/hosts
echo "0.0.0.0 mdmenrollment.apple.com" >>/Volumes/Macintosh\ HD/etc/hosts
echo "0.0.0.0 iprofiles.apple.com" >>/Volumes/Macintosh\ HD/etc/hosts
touch /Volumes/Data/private/var/db/.AppleSetupDone
rm -rf /Volumes/Macintosh\ HD/var/db/ConfigurationProfiles/Settings/.cloudConfigHasActivationRecord
rm -rf /Volumes/Macintosh\ HD/var/db/ConfigurationProfiles/Settings/.cloudConfigRecordFound
touch /Volumes/Macintosh\ HD/var/db/ConfigurationProfiles/Settings/.cloudConfigProfileInstalled
touch /Volumes/Macintosh\ HD/var/db/ConfigurationProfiles/Settings/.cloudConfigRecordNotFound
I did a direct update from working great Ventura 13.7 to Sequoia 15 and had no issues.
I did follow the instruction posted by @sonomadep after performing the upgrade. I didn't wait for any nag screens to appear, I just proactively did it.
I did a direct update from working great Ventura 13.7 to Sequoia 15 and had no issues.
I did follow the instruction posted by @sonomadep after performing the upgrade. I didn't wait for any nag screens to appear, I just proactively did it.
could u share how did u do it ? step by step?
@Jbb08 Thank you for your answer I will do the same and let everyone know. Around 1 hour before I updated to 15. I'm using it without problem now.
please share how did u update?
Ok so I tried to update straight from 13.7 to 15 in software update but it failed then update showed up Sonoma (14.7)
so I made sure my hosts were set blocking the usual suspects
went into my router (lynksis) and opened up parental controls found my mac in devices and blocked access to the same as hosts file.
then just updated to sonoma took a while but at went ok mac is working as normal no MDM or difference to previous.
Now the update to 15 has showed up in update so I've now installed the update to 15 no issues at all no MDM pop ups everything seems to be working as it should , Hosts file remains unchanged still blocking as it should.
TLDR; I just made sure my hosts file and router was blocking deviceenrollment.apple.com, mdmenrollment.apple.com, iprofiles.apple.com and just updated as normal. 13 - 14 - 15
thanks.
Hi everyone !
It's about to complete a year since I followed @joshworksit's bypass. M1 Pro 2021.
Since then I have always updated without problems.
I just updated (09/25/2024) from 14.6.1 to Sequoia 15.0.
Make sure to have it configured.
echo "0.0.0.0 deviceenrollment.apple.com" >>/Volumes/Macintosh\ HD/etc/hosts
echo "0.0.0.0 mdmenrollment.apple.com" >>/Volumes/Macintosh\ HD/etc/hosts
echo "0.0.0.0 iprofiles.apple.com" >>/Volumes/Macintosh\ HD/etc/hosts
I've been on Ventura, currently 13.6.9 M1 2020. After following the guide as well. For every update, I was able to just run this command
rm -r /private/var/db/ConfigurationProfiles
I wouldn't see the nagging pop-up anymore. Until the last update and I can't remove it anymore. Restricted access etc...
Can I still update to 15 without an issue? I've been hesitant for far to long if anyone can clarify what might happen??
Thank you!
If you don't want to toss or encounter difficulties, you can ask me for a paid solution, whether it's a command line or an automatic program.
Has anyone updated to MacOs Sequoia 15.0.1? I've been looking for a permanent solution for days to end this remote management blockage once and for all and not worry about future updates but I can't find it anywhere.
Hello, thanks to all of you with the detailed instructions to upgrade the system.
I managed to upgrade the system, but now after usage for about 1-2 hours, started getting those MDM profile notifications. How do I completely avoid such profile notifications, as the system is not letting me do anything unless I enrol.
Please suggest
Hi, I tried everything, but I only came to two conclusions.
Contact the company and ask them to unlink the Mac's serial number from their system, or hire a good Indian guy that I found on Telegram to resolve it for me, which is what I did lol.
Here is the link to the video that made me find it.
https://youtu.be/XIk-GWb4K_Q?si=FumfZpFsFCEFx6mS
Another one... anyone updated from MDM ventura (13.7) to 15? (2021 MBP M1)
ThanksI have the same questions. Used my instructions here on ventura but would like to migrate to 15. https://gist.github.com/henrik242/65d26a7deca30bdb9828e183809690bd?permalink_comment_id=4620471#gistcomment-4620471
My upgrade went smooth. Only thing I did preemptively in addition to my own instructions from the OG install is add the blacklist to the hosts file.
Hi, how can I get around this page without reinstalling macos and losing my data?
I have version 14.6
and how can I transfer my data without losing it?
Hi, how can I get around this page without reinstalling macos and losing my data? I have version 14.6
and how can I transfer my data without losing it?
Hey, i have encountered the same thing after updating my mac to sequoia. I was able to get around this page by booting the mac into recovery mode and open terminal and execute this command below, thanks to (holyMolyTolli) and everyone else who shared this
echo "0.0.0.0 deviceenrollment.apple.com" >>/Volumes/Macintosh\ HD/etc/hosts
echo "0.0.0.0 mdmenrollment.apple.com" >>/Volumes/Macintosh\ HD/etc/hosts
echo "0.0.0.0 iprofiles.apple.com" >>/Volumes/Macintosh\ HD/etc/hosts
Hello! I am a Macbook Pro M1 2020 user, I bought it in 2022, I used one of the commands that were placed in that year and so far it has not given me any problems and I can update it normally. But I am noticing my macbook is slow, I have never given it maintenance so I want to factory reset it. If I reset it, can the mdm profile be reactivated?
Hello! I am a Macbook Pro M1 2020 user, I bought it in 2022, I used one of the commands that were placed in that year and so far it has not given me any problems and I can update it normally. But I am noticing my macbook is slow, I have never given it maintenance so I want to factory reset it. If I reset it, can the mdm profile be reactivated?
Yes, it will be reactivated. The only way I found for factory reset is to install fresh big sur, apply the commands for deactivate mdm and then updating os versions.
@joshworksit Can you help me? I used your command and still getting this error message
@TomRider22 How did it end? Also sitting in front of this file. Did changing the "9" to a "0" have any effect, or is it irrelevant after all the previous steps @joshworksit described?