csrutil disable
Restart computer
In the terminal, type
sudo open /Applications/TextEdit.app /System/Library/LaunchDaemons/com.apple.ManagedClient.enroll.plist
change
<key>com.apple.ManagedClient.enroll</key>
<true/>
to
<key>com.apple.ManagedClient.enroll</key>
<false/>
So that the changes take effect
what’s supposed to be done ?
Anyone using Sonoma 14.4.1, after processing the post?
Anyone using Sonoma 14.4.1, after processing the post?
yes it's working normaly
hello
please i want to ask about mdm
i have M2 ventura 13 working and the apple asked me to update to sonoma
can i update it safely
and if i did , do i need to do something else to stop mdm
thank you
How to Upgrade to Sonoma Without Risking Activating DEP/MP?
There is some conflicting information here (and on YT), and I am not a pro user... Could someone kindly explain or point me to the current recommended process to upgrade from Ventura to Sonoma without risking my Mac being enrolled into DEP/MDM?
Originally, when I acquired this Mac, DEP/MDM was circumvented by blocking IPs on my router, installing from USB (clean install), and then editing hosts files. However, now I would like to upgrade a running system and Sonoma seems to have additional tricks to enroll us. Hope someone could help me run the upgrade to Sonoma without risking DEP/MDM (this is why I have not upgraded until now, but I have to do it now as a tool I use needs Sonoma now).
P.S. This means I am not DEP/MDM enrolled, correct?
Last login: Wed May 15 16:59:55 on console
admin@D-MBP-16-2021 ~ % sudo profiles show -type enrollment
Password:
Error fetching Device Enrollment configuration: (34000) Error Domain=MCCloudConfigurationErrorDomain Code=34000 "The device failed to request configuration from the cloud." UserInfo={NSLocalizedDescription=The device failed to request configuration from the cloud., CloudConfigurationErrorType=CloudConfigurationFatalError}
admin@D-MBP-16-2021 ~ %
Hi everyone. I updated to Sonoma 14.5 From Monterey yesterday and after installing I got a pop up saying remote management but just hit skip now and worked fine after. Today I tried using it and now the same pop up comes up taking over my whole screen without a “skip now” button. I tried everything on here but nothing has allowed me to use the Sudo codes in terminal in regular mode because the pop up comes up within 10 seconds of booting up Everytime. I don’t want to erase the MacBook because I have a lot of data on it I need.
Any help would be great. I am able to go into recovery mode find but that’s about it. Thank you!
Hi everyone. I updated to Sonoma 14.5 From Monterey yesterday and after installing I got a pop up saying remote management but just hit skip now and worked fine after. Today I tried using it and now the same pop up comes up taking over my whole screen without a “skip now” button. I tried everything on here but nothing has allowed me to use the Sudo codes in terminal in regular mode because the pop up comes up within 10 seconds of booting up Everytime. I don’t want to erase the MacBook because I have a lot of data on it I need.
Any help would be great. I am able to go into recovery mode find but that’s about it. Thank you!
try turning off ur wifi if the pop up still comes, delete all the wifi passwords saved on ur mac. this should allow you to put the command lines.After several tries it worked for me
Hi everyone. I updated to Sonoma 14.5 From Monterey yesterday and after installing I got a pop up saying remote management but just hit skip now and worked fine after. Today I tried using it and now the same pop up comes up taking over my whole screen without a “skip now” button. I tried everything on here but nothing has allowed me to use the Sudo codes in terminal in regular mode because the pop up comes up within 10 seconds of booting up Everytime. I don’t want to erase the MacBook because I have a lot of data on it I need.
Any help would be great. I am able to go into recovery mode find but that’s about it. Thank you!try turning off ur wifi if the pop up still comes. delete all the wifi passwords saved on ur mac. After several tries it worked for me
which codes did you put into terminal? what exact steps did you follow. i appreciate your help
Hi, I have been using my Intel 2019 MBP since 2020 with the host blocked. Im still on ventura.
I recently ran a script to see if my Mac was still under MDM. I got the results that it was not on a MDM server. I thought that maybe this was because I had the hosts blocked, I removed the host entry and ran the test again with the same result. I have now had the Mac running 24 hours without the hosts blocked and not received any pop up messages. Is it possible that my Mac has been released from MDM? How can I tell for sure before updating to Sonoma ? Thank you script. https://github.com/rtrouton/rtrouton_scripts/tree/main/rtrouton_scripts/check_mdm_enrollment
sudo profiles show -type enrollment
sudo profiles status -type enrollment
sudo profiles renew -type enrollment@sqig try
shell > perfis sudo mostram inscrição -type > status dos perfis sudo - tipo de inscrição > perfis sudo renovam a inscrição do tipo >> > @sqigtente Does this code check?
Hi, I have been using my Intel 2019 MBP since 2020 with the host blocked. Im still on ventura. I recently ran a script to see if my Mac was still under MDM. I got the results that it was not on a MDM server. I thought that maybe this was because I had the hosts blocked, I removed the host entry and ran the test again with the same result. I have now had the Mac running 24 hours without the hosts blocked and not received any pop up messages. Is it possible that my Mac has been released from MDM? How can I tell for sure before updating to Sonoma ? Thank you script. https://github.com/rtrouton/rtrouton_scripts/tree/main/rtrouton_scripts/check_mdm_enrollment
No, the script is only checking on the local system if the mdm profile is installed or not.
I have used a paid online MDM check and my Mac is still enrolled.
Model: MacBook Pro (15-inch, 2018) Space Gray Wi-Fi [A1989] [MacBookPro15,1]
Serial Number: C02XXXXXXX
MDM Lock: ON
Thank you
@sqig I can provide technical support for a fee.
Just adding that this post in reply to the above method is what got me sorted out. Clean install (didn't have to use USB), reboot to recovery at the MDM screen, run bypass script and reboot. Dead simple.