Disable Device Enrollment Program (DEP) notification on macOS Ventura.md

Disable Device Enrollment Program (DEP) notification on macOS Ventura.md

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

I think it's not allowed for Apple to change your hosts file, especially if you have some custom ones. Sounds illegal to me.

Apple can not modify your hosts file, however when updating macos it can delete it and create a new blank one.
Apple can also bypass it at their will.
However, most of the time when they ignore it not necessarly because they intended to do so but because the daemon is not loaded yet as the upgrade process is not considered complete, and the boot is not complete until you click launch macOS
Why can they delete it?
Firstly, it is stored in a system path(/etc), not a user path(/usr). macOS can alter at will whatever is being stored in any system path, just like Windows and any other operating system or program within its working directory.
Secondly, as an example, hypothetically I am an Apple macOS Developer and I discovered a bug in the network manager and fix said bug. After fixing the bug I would either have the option to tell the OS that during the update it should delete the hosts file and create a new one in order to limit conflicts or problems that might arise from having the old file format, or it might actually be a software development protocol to mark for deletion related files to the service I have made major changes to.

Well, I don't get the alert, I just have that annoying notification. I still can't find how to delete it...​

1. Shut down your Mac and enter Recovery.
2. Open up the terminal in Recovery and type to disable SIP:
3. csrutil disable
4. Reboot your Mac and open up a terminal after booting in macOS.
5. Finally, to remove the annoying notification, enter the following:

sudo rm /var/db/ConfigurationProfiles/Settings/.cloudConfigHasActivationRecord 
sudo rm /var/db/ConfigurationProfiles/Settings/.cloudConfigRecordFound 
sudo touch /var/db/ConfigurationProfiles/Settings/.cloudConfigProfileInstalled
sudo touch /var/db/ConfigurationProfiles/Settings/.cloudConfigRecordNotFound 
sudo launchctl disable system/com.apple.ManagedClient.enroll
sudo launchctl disable system/com.apple.mdmclient.daemon 
sudo launchctl disable system/com.apple.mdmclient
sudo launchctl disable system/com.apple.devicemanagementclient.teslad

You can then either keep SIP off or turn it back on in recovery by typing csrutil enable in the recovery terminal

Thanks friend, it doesn't work for me, what other option do you think works...?

I am on bypassed Ventura with no notification/popup. If I want to upgrade to Sonoma without doing a clean install or wiping anything, what exactly do I need to do?

This is what I'm looking for. Can someone do step by step in one post going from Ventura to Sonoma please?

I am on bypassed Ventura with no notification/popup. If I want to upgrade to Sonoma without doing a clean install or wiping anything, what exactly do I need to do?

This is what I'm looking for. Can someone do step by step in one post going from Ventura to Sonoma please?

Did you get an answer? In the same boat and cant afford to made a mistake. Thanks.

I am running Sonoma, just upgrade manually and make sure to have blocked in the hosts file and in the router's settings the domains listed in this thread. After upgrading, check your hosts file and make sure that the services are still disabled. Additionally, you could block access to the internet of the services using a firewall like Little Snitch to make sure that even if Apple has added an additional domain or whatever type of check, all the traffic to and from the services is blocked.

Can you possibly walk me through this??

Well, I don't get the alert, I just have that annoying notification. I still can't find how to delete it...​

1. Shut down your Mac and enter Recovery.
2. Open up the terminal in Recovery and type to disable SIP:
3. csrutil disable
4. Reboot your Mac and open up a terminal after booting in macOS.
5. Finally, to remove the annoying notification, enter the following:

sudo rm /var/db/ConfigurationProfiles/Settings/.cloudConfigHasActivationRecord 
sudo rm /var/db/ConfigurationProfiles/Settings/.cloudConfigRecordFound 
sudo touch /var/db/ConfigurationProfiles/Settings/.cloudConfigProfileInstalled
sudo touch /var/db/ConfigurationProfiles/Settings/.cloudConfigRecordNotFound 
sudo launchctl disable system/com.apple.ManagedClient.enroll
sudo launchctl disable system/com.apple.mdmclient.daemon 
sudo launchctl disable system/com.apple.mdmclient
sudo launchctl disable system/com.apple.devicemanagementclient.teslad

You can then either keep SIP off or turn it back on in recovery by typing csrutil enable in the recovery terminal

Worked like a charm! Thanks for sharing this :)

I am running Sonoma, just upgrade manually and make sure to have blocked in the hosts file and in the router's settings the domains listed in this thread. After upgrading, check your hosts file and make sure that the services are still disabled. Additionally, you could block access to the internet of the services using a firewall like Little Snitch to make sure that even if Apple has added an additional domain or whatever type of check, all the traffic to and from the services is blocked.

Can you possibly walk me through this??

I am on bypassed Ventura with no notification/popup. If I want to upgrade to Sonoma without doing a clean install or wiping anything, what exactly do I need to do?

This is what I'm looking for. Can someone do step by step in one post going from Ventura to Sonoma please?

Here's the link to my comment above(click on the link or just scroll until you see it) with step-by-step instructions.

Let me know if you need any help

Well, I don't get the alert, I just have that annoying notification. I still can't find how to delete it...​

1. Shut down your Mac and enter Recovery.
2. Open up the terminal in Recovery and type to disable SIP:
3. csrutil disable
4. Reboot your Mac and open up a terminal after booting in macOS.
5. Finally, to remove the annoying notification, enter the following:

sudo rm /var/db/ConfigurationProfiles/Settings/.cloudConfigHasActivationRecord 
sudo rm /var/db/ConfigurationProfiles/Settings/.cloudConfigRecordFound 
sudo touch /var/db/ConfigurationProfiles/Settings/.cloudConfigProfileInstalled
sudo touch /var/db/ConfigurationProfiles/Settings/.cloudConfigRecordNotFound 
sudo launchctl disable system/com.apple.ManagedClient.enroll
sudo launchctl disable system/com.apple.mdmclient.daemon 
sudo launchctl disable system/com.apple.mdmclient
sudo launchctl disable system/com.apple.devicemanagementclient.teslad

You can then either keep SIP off or turn it back on in recovery by typing csrutil enable in the recovery terminal

Thanks friend, it doesn't work for me, what other option do you think works...?

Did you add in the hosts file these domains?

• mdmenrollment.apple.com
• iprofiles.apple.com
• deviceenrollment.apple.com
• gdmf.apple.com
• acmdm.apple.com

Also, did you restart after you ran the commands? If you didn't can you try to do that first and let me know
And just making sure did disable SIP in recovery before running the commands? If you did and you did restart too get little snitch or any other firewall and block internet access to the following services:
/usr/libexec/mdmclient
/usr/libexec/teslad

So on both my wife's laptop (2019 13" MBP) and her iMac (2020 5K iMac) I went into the Host files and blocked it there. Once you get the computer up and running (off internet) or block in router. do this.

Open Terminal
sudo nano /etc/hosts
write in the following lines

0.0.0.0 mdmenrollment.apple.com
0.0.0.0 iprofiles.apple.com
0.0.0.0 deviceenrollment.apple.com

save it and reboot

I went from Ventura to Sonoma on both NO problems at all. no popups and worked via OTA.
Just an FYI the gdmf.apple.com is the OTA updates installer. if you add that into the list, it will NOT pull updates via system preferences and you have to manually install the OS for every update its SUPEr annoying. So far any update has not overwritten these in the Hosts and it checks out that its not MDM any time.

you can check via these 2 commands
sudo profiles status -type enrollment
---this will tell you if it had DEP or MDM should say "NO" to both
sudo profiles show -type enrollment
--this will try to ping the servers for MDM enrollment, if you did it correctly you should get "Error fetching Device Enrollment config...blah blah" this is meaning that when it fetches 0.0.0.0 doesn't exist...obviously!

But anyway using this method I upgraded with NO problems at all! and did it OTA as well.

So on both my wife's laptop (2019 13" MBP) and her iMac (2020 5K iMac) I went into the Host files and blocked it there. Once you get the computer up and running (off internet) or block in router. do this.

Open Terminal sudo nano /etc/hosts write in the following lines

0.0.0.0 mdmenrollment.apple.com 0.0.0.0 iprofiles.apple.com 0.0.0.0 deviceenrollment.apple.com

save it and reboot

I went from Ventura to Sonoma on both NO problems at all. no popups and worked via OTA. Just an FYI the gdmf.apple.com is the OTA updates installer. if you add that into the list, it will NOT pull updates via system preferences and you have to manually install the OS for every update its SUPEr annoying. So far any update has not overwritten these in the Hosts and it checks out that its not MDM any time.

you can check via these 2 commands sudo profiles status -type enrollment ---this will tell you if it had DEP or MDM should say "NO" to both sudo profiles show -type enrollment --this will try to ping the servers for MDM enrollment, if you did it correctly you should get "Error fetching Device Enrollment config...blah blah" this is meaning that when it fetches 0.0.0.0 doesn't exist...obviously!

But anyway using this method I upgraded with NO problems at all! and did it OTA as well.

Can you elaborate for a simpleton like myself? How do you go into the host file and block there? And block what exactly? Also block what and where? Either way, my situation is that i am on Ventura on a bypassed MDM MacBook Pro 16" M2 Pro and i want to do a normal update to Sonoma and need assistance. Thank you.

How to remove the MDM notification on ventura and be able to update to any version without having to redo the process. With this method, Sonoma does not pull anything from the MDM because the MDM will be blocked. If it worked, comment below cause I`m new here. c;

**

--------Remembering (If you redo the process via pendrive, you must redo the process from scratch, the update is only valid when you install the new version through the Apple system in the update tab and not via pendrive.------------

**

To remove this notification, first redo the process, otherwise it won't work. after installing ventura configured to not pull the mdm just install the autotool in the link: https://mega.nz/file/E6EWgbCb#kFq52LfsJ1XSxuClq-fxTBTbLrq4a7bGqboAz-o5588
click on "AutoTools_MAC.command and then click on open and then press 6 and enter and that's it, just be happy. I did it on an m2 max and I'm able to update the system. I was on ventura, I did the process and updated. Today I'm on ventura build 1 beta 2. the system when updating does not pull anything. But if you need to format via pendrive you will have to redo the process. But if you are going to update you can continue as it will not pull anything.
It doesn't even feel like I'm using my Mac with MDM because I can update just fine and not worry.

(If anyone is having trouble installing Ventura on an MDM computer, I'll post the step-by-step instructions here.)

follow step by step:

1- install ventura again, repeat the process. (remembering that it is the same process as above of installing ventura and installing root and installing a new user. When you get to the home screen, do this process.).

2- After completing the above process, download the autotools that I left in the link.

3- open the file and click open

4- after opening, put option 6 and enter

7- just be happy and be able to update the system without pulling anything from the mdm as it will be unlocked

prints:

@Ran-Xing what do you mean?

What’s new for Enterprise in macOS Sonoma

Enterprise changes in macOS Sonoma

macOS Sonoma includes new features such as declarative device management for software updates, account-driven enrollment, and enhancements to Managed Apple IDs.

Device Management

• MDM can enforce software updates by a certain date and time and users get additional information in System Settings when an update is requested and when it’s enforced.
• Automated Device Enrollment can be enforced after Setup Assistant.
• MDM can enable account-driven User Enrollment and account-driven Device Enrollment to allow users to enroll their Mac using their Organization ID in System Settings. Profile-based User Enrollment is deprecated and will be removed in a future release.
• The notification that requests the user enroll in MDM is replaced with a full-screen Setup Assistant experience for a Mac using Automated Device Enrollment.
• New features in platform single sign-on.
• Enhancements to password requirement enforcement.
• MDM can granularly restrict more individual settings in System Settings.
• MDM can require admin users to turn on FileVault during Setup Assistant.
• macOS now supports Managed Device Attestation.
• Declarative device management can manage a set of configurations for some built-in services.
• New declarations support the deployment of certificates and identities.
• A new built-in network relay supports secure and transparent tunneling of traffic as an alternative to using VPN when accessing internal resources.
• MDM can set the order in which transparent proxy extensions handle network traffic.
• macOS now supports the creation of hardware-bound private keys for certificates issued using the ACME protocol.
• Screen sharing capabilities are improved between Mac computers with Apple silicon over high-bandwidth connections.

Credits: https://mrmacintosh.com/macos-sonoma-14-0-23a344-is-live-whats-new/

Didn't say you

@Ran-Xing Yeah, but I was curious.

So on both my wife's laptop (2019 13" MBP) and her iMac (2020 5K iMac) I went into the Host files and blocked it there. Once you get the computer up and running (off internet) or block in router. do this.
Open Terminal sudo nano /etc/hosts write in the following lines
0.0.0.0 mdmenrollment.apple.com 0.0.0.0 iprofiles.apple.com 0.0.0.0 deviceenrollment.apple.com
save it and reboot
I went from Ventura to Sonoma on both NO problems at all. no popups and worked via OTA. Just an FYI the gdmf.apple.com is the OTA updates installer. if you add that into the list, it will NOT pull updates via system preferences and you have to manually install the OS for every update its SUPEr annoying. So far any update has not overwritten these in the Hosts and it checks out that its not MDM any time.
you can check via these 2 commands sudo profiles status -type enrollment ---this will tell you if it had DEP or MDM should say "NO" to both sudo profiles show -type enrollment --this will try to ping the servers for MDM enrollment, if you did it correctly you should get "Error fetching Device Enrollment config...blah blah" this is meaning that when it fetches 0.0.0.0 doesn't exist...obviously!
But anyway using this method I upgraded with NO problems at all! and did it OTA as well.

Can you elaborate for a simpleton like myself? How do you go into the host file and block there? And block what exactly? Also block what and where? Either way, my situation is that i am on Ventura on a bypassed MDM MacBook Pro 16" M2 Pro and i want to do a normal update to Sonoma and need assistance. Thank you.

This is what I did..

open terminal app (on my Ventura M2 Max) this is found in Applications/Utilities
Then type
sudo nano /etc/hosts

enter your password
then add the following entries ensure they aren’t hashed out # aka there is nothing in front of the 0

0.0.0.0 mdmenrollment.apple.com
0.0.0.0 iprofiles.apple.com
0.0.0.0 deviceenrollment.apple.com

once added hit control x to save and exit type Y to accept changes.

To be even more safe I use a Linksys Velop router so I went into Parental controls and on the MacBook Pro Device selected I also blocked the 3 specific sites above. This should stop that device from accessing those sites ever…

I went into settings and upgraded to Sonoma as per usual.

it rebooted, I logged in as normal
Opened terminal and used the same command sudo nano /etc/hosts
And my entires were still there, no alerts or notifications.

All working.

@henrik242 : THANK YOU THANK YOU THANK YOU!!! This saved my 2019 era Mac Pro from the depths of faux security hell!!

	sudo rm /var/db/ConfigurationProfiles/Settings/.cloudConfigHasActivationRecord
	sudo rm /var/db/ConfigurationProfiles/Settings/.cloudConfigRecordFound
	sudo touch /var/db/ConfigurationProfiles/Settings/.cloudConfigProfileIls -nstalled
	sudo touch /var/db/ConfigurationProfiles/Settings/.cloudConfigRecordNotFound

FTW!

This might be a dumb comment / question, but nothing changes after running csrutil disable, i.e., the device management windows remains and I cannot open the terminal to run the other commands. What can I do / what am I missing?

Hi even after holding on recovery it still opens up this screen, any way to bypass this?

Hi, I have the same problem. Were you able to remove the lock? Can you please tell me how you did it?

@xxxx04170208 I think your mac has T2 chip in it, so there is nothing we can do to bypass it.

sudo profiles show -type enrollment

Did this work correctly, coz I'm using an intel MacBook Pro 2018 and I was constantly getting this MDM Enrollment notification pop up on sonama and one day the pop up won't go, It stayed there with no option to cancel.

Then I wiped the disk and went back to Mojave, then I've come back to Ventura following the steps mentioned in your post, setting the IP address of the mentioned websites to 0.0.0.0.

Now can I upgrade to Sonama??

Bem, eu não recebo o alerta, só tenho essa notificação irritante. Ainda não consigo encontrar como excluí-lo... > > > > 1. Desligue seu Mac e entre na Recuperação. > > 2. Abra o terminal na Recuperação e digite para desativar o SIP: > > 3. csrutil disable > > 4. Reinicie seu Mac e abra um terminal após a inicialização no macOS. > > 5. Finalmente, para remover a notificação irritante, insira o seguinte: > > > > > > sudo rm /var/db/ConfigurationProfiles/Settings/.cloudConfigHasActivationRecord > > sudo rm /var/db/ConfigurationProfiles/Settings/.cloudConfigRecordFound > > sudo touch /var/db/ConfigurationProfiles/Settings/.cloudConfigProfileInstalled > > sudo touch /var/db/ConfigurationProfiles/Settings/.cloudConfigRecordNotFound > > sudo launchctl disable system/com.apple.ManagedClient.enroll > > sudo launchctl disable system/com.apple.mdmclient.daemon > > sudo launchctl disable system/com.apple.mdmclient > > sudo launchctl disable system/com.apple.devicemanagementclient.teslad > > > > > > > > Você pode então manter o SIP desligado ou ativá-lo novamente na recuperação digitando csrutil enable no terminal de recuperação > > Funcionou como um encanto! Obrigado por compartilhar isso :) sP.>>>>>> Pessoal, boa noite! posso atualizar numa boa? No meu funcionou, segundo dia sem o pups chato. Posso atualizar para o Sonoma 14.1?

sSeteP

might be a stupid question and off topic, but would apple accept one of these bypassed M2 Pro Macbook Pro's for a trade in?

might be a stupid question and off topic, but would apple accept one of these bypassed M2 Pro Macbook Pro's for a trade in?

They will accept it, but you won't get any benefits 😔

Hello all,
Does anybody know is the file ".deviceConfigurationBits" is needed or can be removed? If I'm doing cat of it I can see parameter "DeviceConfigurationFlags" with value 9. I have changed it to 0. Tried to find info regarding this parameter and value but seems it is not a lot info regarding it.
https://github.com/mosen/macdocs/blob/master/source/DEP/ios-activation.rst?plain=1#L143

**** WORKING!!! ******. HI EVERYONE! I have a simplified way I figured out today to bypass DEP today with Ventura against a M2 Macbook Air

Need 3 things

1. A separate M1/M2 Mac (could be anytjhing, macbook, studio, etc). this machine must not have DEP/Business Manager enabled
2. Create a USB Boot installer flash drive with Ventura - you can google the instructions on how to create a boot usb drive.
3. An external SSD that you can install a fresh OS on. I just use a sandish extreme USB 3.1 256GB drive.

Steps I did On the non-DEP M1/M2 Mac

1. USB BOOT installer and install Ventura on the External SSD --- using the non-DEP Mac
2. Once installed, go thru the account creation so you have an account
3. Boot from USB SSD drive just to make sure it is working.

Now you have a bootable external disk.

On the DEP enabled M1/M2 Mac

1. Boot to recovery mode
2. Disk Utility
3. Erase the internal physical disk
4. Click on internal disk and use the RESTORE option, FROM the external SSD
5. Let it run - will take a while.

Now you jsut copied the clean ventura to the internal drive.

Once the restore is finished. Remove the External SSD Boot from the internal disk

You WILL get an error that it cannot find the OS or some other stupid errors like no owner, or some other silly error... don't worry.

Now you boot again using the USB BOOT Ventura disk. REINSTALL Ventura again on the internal disk - DO NOT DO ANY DISK FORMATTING this time.

Once USB Installer is done, reboot - you will get to the login prompt of the user you created on the initial fresh install. you will have a working Ventura M1/M2 that just bypassed DEP/Business Manager.

Why this works? Because you first lay down the image on internal disk but due to some apple security, it will never boot unless you "fresh install" it. But the good things about fresh installs, Apple doesn't really wipe the system, it just lays whatever that is necessary for the OS. This means it will fix the ownership of the disks, do whatever it does but won't overwrite local accounts etc. so you will not get prompted for DEP enrollment. I don't know the actual internal details but I just know this works.

Enjoy. took me a while to figure this out after trying many things.

I do not need to do any /etc/hosts hacks, csrutil, etc. nothing. It's pretty simple to do but it does require a double install but it's easier than editing files.

You could in theory transfer a fully working Mac to another Mac now but I don't need to do that so I did the clean Ventura Install.

Now I can use this method to clean/wipe any DEP enabled machine and have myself a "pre-built" machine with certain things like chrome etc already installed. I can just boot from the external SSD periodically to get new updates of OS and software and continue to use it on any new Macs I wipe.

Thanks a lot for your detailed guide, I just tried to remove MDM for M2 MacBook with Ventura 13.6.1 and it works like a charm after some trial and errors. The caveat is to make sure that you wiped your internal disk before restoring the external one to the internal one. Some steps are failing for me for the first time so just reboot your computer when it doesn’t work and try it again. The first time when all the steps were completed, I got an error saying the macOS does not match the one Apple provides, so I just tried everything from scratch again. When trying to restore the disk, I often get the seal broken error and can to be fixed by actually booting into the system. For the last step when we do a “fresh” install and overwrite the disk, you can directly do it via the recovery menu, it doesn’t have to be installed from the external drive if the macOS version matches.

Thanks again for the nice guide and hope this comment is helpful for other people as well on this.

Tested with macOS Ventura 13.6.1, Nov 2023. I used this alternative, because the services kept starting after re-activating SIP.

Boot into Recovery Mode from any csrutil status and run:

VOL="/Volumes/Macintosh HD"                                                       # Your HD name
mount -uw $VOL                                                                    # Bypass read-only
cd $VOL/System/Library

mkdir -p LaunchAgents-inactive LaunchDaemons-inactive                             # Remove service configs
mv -v LaunchAgents/com.apple.{ManagedClient,mdmclient}* LaunchAgents-inactive
mv -v LaunchDaemons/com.apple.{ManagedClient,mdmclient}* LaunchDaemons-inactive

bless --mount $VOL --create-snapshot --bootefi                                    # Create bootable, unsigned snapshot
csrutil authenticated-root disable                                                # Boot from unsigned snapshots
reboot

Confirm the services are disabled and show your new bootable snapshot:

diskutil apfs listSnapshots /
sudo launchctl list | egrep -i 'ManagedClient|mdmclient'

Hello everyone!

I could resolve it using macOs Ventura 13.6.1. I followed 2 posts. November 2023.

One to get ride of DEP screen and another to get ride of that annoying message every minute.

1 - Many thanks @joshworksit! It worked with macOS Ventura 13.6.1. Amazing stuff you shared it took me 5 minutes. I would be very glad to donate anything. Thanks again.

2 - @pritpalspall I could get ride of that message for good. Thank you so much!

You guys rock.

Uhh... where is @joshworksit 's post @fmodesto30 ?

Does anyone know if the M3 version of Apple Silicon can be bypassed with the host file method?

…

On Sun, Nov 26, 2023 at 10:33 AM BuckLearnsCode ***@***.***> wrote: ***@***.**** commented on this gist. ------------------------------ Uhh... where is @joshworksit <https://github.com/joshworksit> 's post @fmodesto30 <https://github.com/fmodesto30> ? — Reply to this email directly, view it on GitHub <https://gist.github.com/henrik242/65d26a7deca30bdb9828e183809690bd#gistcomment-4773185> or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASBUU7QMRN72LG3AKPGLLGTYGODQ7BFKMF2HI4TJMJ2XIZLTSKBKK5TBNR2WLJDHNFZXJJDOMFWWLK3UNBZGKYLEL52HS4DFQKSXMYLMOVS2I5DSOVS2I3TBNVS3W5DIOJSWCZC7OBQXE5DJMNUXAYLOORPWCY3UNF3GS5DZVRZXKYTKMVRXIX3UPFYGLK2HNFZXIQ3PNVWWK3TUUZ2G64DJMNZZDAVEOR4XAZNEM5UXG5FFOZQWY5LFVEYTAMBRGYYTCMRSU52HE2LHM5SXFJTDOJSWC5DF> . You are receiving this email because you commented on the thread. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> .

Uhh... where is @joshworksit 's post @fmodesto30 ?

https://gist.github.com/henrik242/65d26a7deca30bdb9828e183809690bd?permalink_comment_id=4493654#gistcomment-4493654

**** WORKING!!! ******. HI EVERYONE! I have a simplified way I figured out today to bypass DEP today with Ventura against a M2 Macbook Air
Need 3 things

1. A separate M1/M2 Mac (could be anytjhing, macbook, studio, etc). this machine must not have DEP/Business Manager enabled
2. Create a USB Boot installer flash drive with Ventura - you can google the instructions on how to create a boot usb drive.
3. An external SSD that you can install a fresh OS on. I just use a sandish extreme USB 3.1 256GB drive.

Steps I did On the non-DEP M1/M2 Mac

1. USB BOOT installer and install Ventura on the External SSD --- using the non-DEP Mac
2. Once installed, go thru the account creation so you have an account
3. Boot from USB SSD drive just to make sure it is working.

Now you have a bootable external disk.
On the DEP enabled M1/M2 Mac

1. Boot to recovery mode
2. Disk Utility
3. Erase the internal physical disk
4. Click on internal disk and use the RESTORE option, FROM the external SSD
5. Let it run - will take a while.

Now you jsut copied the clean ventura to the internal drive.
Once the restore is finished. Remove the External SSD Boot from the internal disk
You WILL get an error that it cannot find the OS or some other stupid errors like no owner, or some other silly error... don't worry.
Now you boot again using the USB BOOT Ventura disk. REINSTALL Ventura again on the internal disk - DO NOT DO ANY DISK FORMATTING this time.
Once USB Installer is done, reboot - you will get to the login prompt of the user you created on the initial fresh install. you will have a working Ventura M1/M2 that just bypassed DEP/Business Manager.
Why this works? Because you first lay down the image on internal disk but due to some apple security, it will never boot unless you "fresh install" it. But the good things about fresh installs, Apple doesn't really wipe the system, it just lays whatever that is necessary for the OS. This means it will fix the ownership of the disks, do whatever it does but won't overwrite local accounts etc. so you will not get prompted for DEP enrollment. I don't know the actual internal details but I just know this works.
Enjoy. took me a while to figure this out after trying many things.
I do not need to do any /etc/hosts hacks, csrutil, etc. nothing. It's pretty simple to do but it does require a double install but it's easier than editing files.
You could in theory transfer a fully working Mac to another Mac now but I don't need to do that so I did the clean Ventura Install.
Now I can use this method to clean/wipe any DEP enabled machine and have myself a "pre-built" machine with certain things like chrome etc already installed. I can just boot from the external SSD periodically to get new updates of OS and software and continue to use it on any new Macs I wipe.

Thanks a lot for your detailed guide, I just tried to remove MDM for M2 MacBook with Ventura 13.6.1 and it works like a charm after some trial and errors. The caveat is to make sure that you wiped your internal disk before restoring the external one to the internal one. Some steps are failing for me for the first time so just reboot your computer when it doesn’t work and try it again. The first time when all the steps were completed, I got an error saying the macOS does not match the one Apple provides, so I just tried everything from scratch again. When trying to restore the disk, I often get the seal broken error and can to be fixed by actually booting into the system. For the last step when we do a “fresh” install and overwrite the disk, you can directly do it via the recovery menu, it doesn’t have to be installed from the external drive if the macOS version matches.

Thanks again for the nice guide and hope this comment is helpful for other people as well on this.

Hi guys,
I followed this and managed to bypass my MacBook (needed to repeat some steps a few times but finally worked)! Thank you for the great instruction!
I have two questions:
1- Would updating from Ventura to Sonoma void the bypass?
2- I keep getting a pop up message suggesting to enroll again to the original organization. I can press "cancel" and pass it, but I was wondering if there is a way to prevent those occasional pop-ups.

@visionguy55 If you see such a notification, you have not fully bypassed mdm. If you upgrade your OS to Sonoma you will be blocked after reboot or some short time after it.

**** WORKING!!! ******. HI EVERYONE! I have a simplified way I figured out today to bypass DEP today with Ventura against a M2 Macbook Air
Need 3 things

1. A separate M1/M2 Mac (could be anytjhing, macbook, studio, etc). this machine must not have DEP/Business Manager enabled
2. Create a USB Boot installer flash drive with Ventura - you can google the instructions on how to create a boot usb drive.
3. An external SSD that you can install a fresh OS on. I just use a sandish extreme USB 3.1 256GB drive.

Steps I did On the non-DEP M1/M2 Mac

1. USB BOOT installer and install Ventura on the External SSD --- using the non-DEP Mac
2. Once installed, go thru the account creation so you have an account
3. Boot from USB SSD drive just to make sure it is working.

Now you have a bootable external disk.
On the DEP enabled M1/M2 Mac

1. Boot to recovery mode
2. Disk Utility
3. Erase the internal physical disk
4. Click on internal disk and use the RESTORE option, FROM the external SSD
5. Let it run - will take a while.

Now you jsut copied the clean ventura to the internal drive.
Once the restore is finished. Remove the External SSD Boot from the internal disk
You WILL get an error that it cannot find the OS or some other stupid errors like no owner, or some other silly error... don't worry.
Now you boot again using the USB BOOT Ventura disk. REINSTALL Ventura again on the internal disk - DO NOT DO ANY DISK FORMATTING this time.
Once USB Installer is done, reboot - you will get to the login prompt of the user you created on the initial fresh install. you will have a working Ventura M1/M2 that just bypassed DEP/Business Manager.
Why this works? Because you first lay down the image on internal disk but due to some apple security, it will never boot unless you "fresh install" it. But the good things about fresh installs, Apple doesn't really wipe the system, it just lays whatever that is necessary for the OS. This means it will fix the ownership of the disks, do whatever it does but won't overwrite local accounts etc. so you will not get prompted for DEP enrollment. I don't know the actual internal details but I just know this works.
Enjoy. took me a while to figure this out after trying many things.
I do not need to do any /etc/hosts hacks, csrutil, etc. nothing. It's pretty simple to do but it does require a double install but it's easier than editing files.
You could in theory transfer a fully working Mac to another Mac now but I don't need to do that so I did the clean Ventura Install.
Now I can use this method to clean/wipe any DEP enabled machine and have myself a "pre-built" machine with certain things like chrome etc already installed. I can just boot from the external SSD periodically to get new updates of OS and software and continue to use it on any new Macs I wipe.

Thanks a lot for your detailed guide, I just tried to remove MDM for M2 MacBook with Ventura 13.6.1 and it works like a charm after some trial and errors. The caveat is to make sure that you wiped your internal disk before restoring the external one to the internal one. Some steps are failing for me for the first time so just reboot your computer when it doesn’t work and try it again. The first time when all the steps were completed, I got an error saying the macOS does not match the one Apple provides, so I just tried everything from scratch again. When trying to restore the disk, I often get the seal broken error and can to be fixed by actually booting into the system. For the last step when we do a “fresh” install and overwrite the disk, you can directly do it via the recovery menu, it doesn’t have to be installed from the external drive if the macOS version matches.
Thanks again for the nice guide and hope this comment is helpful for other people as well on this.

Hi guys, I followed this and managed to bypass my MacBook (needed to repeat some steps a few times but finally worked)! Thank you for the great instruction! I have two questions: 1- Would updating from Ventura to Sonoma void the bypass? 2- I keep getting a pop up message suggesting to enroll again to the original organization. I can press "cancel" and pass it, but I was wondering if there is a way to prevent those occasional pop-ups.

You still have to disable MDM notifications: https://gist.github.com/henrik242/65d26a7deca30bdb9828e183809690bd?permalink_comment_id=4553175#gistcomment-4553175

Thank you @TomRider22 and @fmodesto30 for your replies. Please see mine below:

@visionguy55 If you see such a notification, you have not fully bypassed mdm. If you upgrade your OS to Sonoma you will be blocked after reboot or some short time after it.

@TomRider22 Does it really mean that I have not bypassed mdm? Because I have full control over the machine and there is no other signs other than this advisory message:

Could I be getting this message because I setup my MS Outlook with the same organization account?

BTW, this popping up message seems to be gone after following @fmodesto30 's comment.

@visionguy55 This message about device enrollment is triggered by mdm mechanism, and the only reason for it is that it(mdm) was not disabled. Showing this type of message is a part of mdm and unfortunately, it is not connected with the MS Outlook account. The main idea of the DEP - Device Enrollment Program is that the company enrolls their laptops or laptops of their contractors to the Apple business manager. In the Apple business manager laptops are enrolled by their serial numbers. Macos has a default mechanism of checking Apple mdm servers which the Apple business manager is part of. And if the serial number of the laptop is found in the database first of all it will send and hardcode setting to the laptop that it belongs to some organization and is a part of DEP. Then depending on the OS version it will notify you that you need to enroll your device or if it's Sonoma it will block the screen with an enrolment message so you can't postpone or escape from it. It's a good mechanism to prevent corporate laptops from being stolen but in the case of it being a personal laptop enrolled to some company's mdm and then not unenrolled properly creates a bunch of problems for second market users.

@TomRider22 Thank you for the comprehensive explanation of the MDM mechanism. It appears that my attempt to bypass the MDM was not entirely successful. However, in line with @fmodesto30 's suggestion, the pop-up notification prompting enrollment with DEP has disappeared for now. I just hope that it won't reappear after any future system updates!

@BXYMartin Thanks again for sharing the instruction to bypass the MDM. I believed I exactly followed the instruction, however, it looks like my MDM bypassing was not fully successful. Do you have any comments or suggestions?

I'm running Sonoma 14.1 from a fresh installation. I've bypassed the MDM and added entries to the hosts file.

Is it possible to update it to Sonoma 14.1.2?

@OMeryCoN Probably.

In case someone also interested:

1. Ive go to login to laptop in safe mode(on startup hold Shift)
2. Login as a normal used account
3. Create a new admin account in a settings
4. Delete old one time account created with MDM

greeting i am on sonoma 14 and don't have any mdm notification
can i direct update to 14.2? is it safe? anyone did that direct?

greeting i am on sonoma 14 and don't have any mdm notification can i direct update to 14.2? is it safe? anyone did that direct?

i did, and it still works fine.

greeting i am on sonoma 14 and don't have any mdm notification can i direct update to 14.2? is it safe? anyone did that direct?

i did, and it still works fine.

Is there anything need to do before the upgrade? Or just the skipmdm bypass done before?

Hi! I've been struggling with MDM quite a lot and found the easiest, but a little long solution to the problem, but you won't get mdm blocking and profile upload notifications. I have described as much detail as possible for different cases, so find your own and follow the instructions.
I'll tell you the pros and cons at the very end, and now let's move on to the beginning:

Preparatory Stages:

1. If you are on macOS Ventura or Monterey and you have no problems with MDM, then download this utility https://checkm8.info/bypass-mac-mdm-lock and make a Bypass (this is a precautionary measure, without doing this, I cannot guarantee you a successful system update), if you have already done this before, then immediately proceed to the main stages.

2. If you are on macOS Ventura or Monterey or Sonoma and you did not turn off the Internet during installation, then the MacBook will download the corporate profile and be blocked. In this case, there are 2 possible scenarios ->

Scenario 1: If your data is not on the computer, then feel free to format the disk and install Monterey/Ventura without the Internet, as soon as you have created a user and configured a MacBook, you can connect to the Internet and bypass MDM using this utility https://checkm8.info/bypass-mac-mdm-lock once you have bypassed MDM with this utility, you can proceed to the main stages.
Scenario 2: If you had Monterey/Ventura and received a lock after upgrading to Sonoma, then the data can still be saved if there was still +-100gb of free space on the disk or if you have an external hard drive

If you still have disk space and you need to restore data from a system blocked by your corporate profile, then follow these steps:

1. Turn off your MacBook
2. Reboot into recovery mode by pressing the touch id button
3. Go to Settings
4. Disk utility
5. Divide your disk into 2 independent containers, it is important to note that we do not add a VOLUME for the disk, namely a CONTAINER
6. Install Monterey/Ventura without internet in a new, empty container and bypass MDM using this utility https://checkm8.info/bypass-mac-mdm-lock
7. Now in the Finder, find your other user from another container and transfer all the files of interest from the old disk container to the new one
8. You can proceed to the main stages

If you have an external hard drive and you need to recover data from a locked corporate system profile, then follow these steps:

1. Install Monterey/Ventura without internet and bypass MDM using this utility https://checkm8.info/bypass-mac-mdm-lock
2. Now find your other user in the Finder and transfer all the files of interest from the internal drive to the external hard drive
3. You can proceed to the main stages

The main steps:

1. So, in order to upgrade to Sonoma without problems, we need an external SSD or HDD (we will save our backup copy of all data via time machine to it)
2. Using the disk utility, format the external hard drive in APFS and in the settings in the main section select Time Machine, and in it select your external hard drive and then create a backup copy of all data
3. As soon as the backup is created (you don't have to worry about data security, time machine saves literally everything you can), turn off your MacBook
4. Enter recovery mode by pressing the touch id button.
5. Disk utility
6. Format your internal drive
7. (Pre-create a bootable USB flash drive with macOS Sonoma) Start installing Sonoma without the Internet, configure your MacBook until you are prompted to transfer data from a time machine backup, select this item
8. Restore all data from the backup and then complete the installation
9. That's it, you don't need to do anything else, successful bypass!

The advantages of my method:

1. Personally tested by me on a macbook pro 13" m1 and has been tested without any problems for a week now
2. An easy way to bypass the regular macos methods
3. Do you need more advantages besides reliability and simplicity? :)
   Minuses:
4. Quite a long time

(This article got hidden because of a problem with my account, so I try again):

I managed getting rid of spyware and worse w/ Sonoma (14.3.1).

System Info (redacted, personal information filtered)

>sudo sysinfo
Software:

    System Software Overview:

      System Version: macOS 14.3.1 (23D60)
      Kernel Version: Darwin 23.3.0
      Boot Volume: Macintosh HD
      Boot Mode: Normal
      Computer Name: <>
      User Name: System Administrator (root)
      Secure Virtual Memory: Enabled
      System Integrity Protection: Enabled
      Time since boot: <>

Hardware:

    Hardware Overview:

      Model Name: MacBook Pro
      Model Identifier: Mac15,9
      Model Number: <>
      Chip: Apple M3 Max
      Total Number of Cores: 16 (12 performance and 4 efficiency)
      Memory: 128 GB
      System Firmware Version: 10151.81.1
      OS Loader Version: 10151.81.1
      Serial Number (system): <>
      Hardware UUID: <>
      Provisioning UDID: <>
      Activation Lock Status: Disabled

>sudo profiles list
There are no configuration profiles installed in the system domain

>sudo profiles show -type enrollment
Error fetching Device Enrollment configuration: We can't determine if this machine is DEP enabled.  Try again later.

Approach: Clean Wipe, Router Filter, skipmdm.com Script

This approach assumes you are able to create a bootable installer and wipe your system disk (be sure to have a backup in place!).

Prerequisites

• Create bootable installer (I followed these instructions: https://mrmacintosh.com/how-to-create-a-macos-sonoma-usb-boot-disk-installer-in-5-min/)
• Have another external drive (e.g. USB stick) at hand and save the skipmdm.com script (https://raw.githubusercontent.com/skipmdm-phoenixbot/skipmdm.com/main/Autobypass-mdm.sh) on it.
• You have access to the internet router you use to activate macOS.

Block Apple URLs

Before starting at all, make sure you block the following URLs in the internet router. I used a Fritz!Box and here the ("Blocked websites" filter) to block these URLs:

iprofiles.apple.com
mdmenrollment.apple.com
deviceenrollment.apple.com
gdmf.apple.com
acmdm.apple.com
albert.apple.com

Make sure the blocker works (i.e. ping from another device)!

Clean Install

In recovery mode, wipe the hard disk and start a clean install with the bootable installer.

Activate the system

Connect to the internet once to activate the system (I could not proceed without). As the installer fails to connect to the enrollment servers, an error message will be displayed indicating that the status of the enrollment could not be verified.

Run the Script

In recovery mode, open Terminal and e.g. try to delete /var/db/ConfigurationProfiles/Settings - you should get a prompt for the installation user (starting w/ "_m...") - which is a good sign (no other users set up so far)!

Now just run the script from the USB stick. Hint: directly enter the username you'd like to use later (instead going w/ Apple:1234 - saves some time). The script should run without any errors (despite the long previous discussions).

Postwork

Block URLs in /etc/hosts

Before you proceed with the installation, reboot in recovery mode and change /etc/hosts by adding:

0.0.0.0 iprofiles.apple.com
0.0.0.0 mdmenrollment.apple.com
0.0.0.0 deviceenrollment.apple.com
0.0.0.0 gdmf..apple.com
0.0.0.0 acmdm.apple.com
0.0.0.0 albert.apple.com

Disable agents

>sudo launchctl disable system/com.apple.ManagedClientAgent.enrollagent
>sudo launchctl disable system/com.apple.mdmclient.daemon
>sudo launchctl disable system/com.apple.devicemanagementclient.teslad
# You might check other services and disable them - know what you do!
>sudo launchctl print system | sort | grep enabled

Little Snitch

Finally a firewall comes in handy to possibly add even more security: I blocked

/usr/libexec/teslad
/usr/libexec/mdmclient

(for both user + system).

This works well for me and shows that it's possible to stop companies from installing spyware on their employees' devices - even on M3. B.t.w. - in many countries these practices are unlawful, so I see following this approach justified as a way of self-defense.

can any brother here guide me for amazon locked mac book pro 2017 non touch model inel model When i bought it used it was working perfectly, i even upgraded it to ventura, however when i formatted it for selling, it now asks for amaon remote. please help step by step.

Hi even after holding on recovery it still opens up this screen, any way to bypass this?

I have the same issue. I can't boot to recovery mode because of this. Do you have recommendations to go through this?
I have Macbook Pro M1 2021 14"
@aviloveN @predragcvetkovski @Jbb08 @eternalgod @maclover696 @mikevic18

Hi even after holding on recovery it still opens up this screen, any way to bypass this?

I have the same issue. I can't boot to recovery mode because of this. Do you have recommendations to go through this? I have Macbook Pro M1 2021 14" @aviloveN @predragcvetkovski @Jbb08 @eternalgod @maclover696 @mikevic18

Seems like it has been locked by administrator after being enrolled in the MDM. you need another device with T2 chip to reinstall this one via DFU mode.
Try this：https://www.youtube.com/watch?v=S8r9w4dduEw

Hi even after holding on recovery it still opens up this screen, any way to bypass this?

I have the same issue. I can't boot to recovery mode because of this. Do you have recommendations to go through this? I have Macbook Pro M1 2021 14" @aviloveN @predragcvetkovski @Jbb08 @eternalgod @maclover696 @mikevic18

Seems like it has been locked by administrator after being enrolled in the MDM. you need another device with T2 chip to reinstall this one via DFU mode. Try this：https://www.youtube.com/watch?v=S8r9w4dduEw

Worked like a charm with my MDM macbook.

Do you happen to know if this would also work with icloud issue macbook?

If someone's interested, I made a gist with some sh scripts that should allow you to setup a MDM locked Mac as brand new;

https://gist.github.com/c22dev/e3a1223fa63b20f1b4e95a7119277cb9