Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?

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

NB! command-R is replaced with holding the power button on M1 macs.

With full reinstall (recommended)

   a. Boot into recovery using command-R during reboot, wipe the harddrive using Disk Utility, and select reinstall macOS

   b. Initial installation will run for approximately 1 hour, and reboot once

   c. It will then show a remaining time of about 10-15 minutes

   d. When it reboots again, be sure to press command-R to boot into recovery and continue with Main procedure

Without full reinstall

Boot to Recovery Mode by holding command-R during restart and continue with Main procedure

Main procedure

  1. Open Utilities → Terminal and type
$ csrutil disable
$ reboot
  1. Hold command-R during the reboot to enter Recovery Mode again

  2. Enter Disk Utility, and mount the Macintosh HD volume (or whatever your main volume is named). (It might already be mounted.)

  3. Exit Disk Utility, open Utilities → Terminal, and type

$ cd "/Volumes/Macintosh HD/System/Library"
$ cd ../../etc
$ echo "0.0.0.0 iprofiles.apple.com" >> hosts
$ echo "0.0.0.0 mdmenrollment.apple.com" >> hosts
$ echo "0.0.0.0 deviceenrollment.apple.com" >> hosts
$ echo "0.0.0.0 gdmf.apple.com" >> hosts
$ csrutil enable
$ reboot
  1. If you come to the “Choose your country/location” dialogue, make sure to not select a wireless network, but “continue without an internet connection”

  2. After a normal boot, you can verify the DEP status in Terminal:

$ profiles status -type enrollment
Enrolled via DEP: No
MDM enrollment: No
@psolom
Copy link

psolom commented Nov 3, 2022

Try adding albert.apple.com and acmdm.apple.com to your hosts file.

Thanks for the tip
I added those yesterday, but the notification appears today again, unfortunately

@Sailas2k6
Copy link

Sailas2k6 commented Nov 3, 2022

How I erase my Mac and get rid of the notifications:

Clean erase
Reinstall OS from recovery partition.
Aster first boot I turn off the router in my house so I can bypass the mdm screen an continue with the setup process.
I create a user so I can disable csrutil.

After all is done I restart and boot into recovery.
Open terminal and follow this procedure:

$ csrutil disable
$ reboot

Back in recovery and terminal

$ cd "/Volumes/Macintosh HD/System/Library"
$ cd ../../etc
$ echo "0.0.0.0 iprofiles.apple.com" >> hosts
$ echo "0.0.0.0 mdmenrollment.apple.com" >> hosts
$ echo "0.0.0.0 deviceenrollment.apple.com" >> hosts
$ echo "0.0.0.0 albert.apple.com" >> hosts
$ echo "0.0.0.0 acmdm.apple.com" >> hosts

$ csrutil enable
$ reboot

Never had any issues with the method.

@2ndMessiah
Copy link

2ndMessiah commented Nov 3, 2022

How I erase my Mac and get rid of the notifications:

Clean erase Reinstall OS from recovery partition. Aster first boot I turn off the router in my house so I can bypass the mdm screen an continue with the setup process. I create a user so I can disable csrutil.

After all is done I restart and boot into recovery. Open terminal and follow this procedure:

$ csrutil disable $ reboot

Back in recovery and terminal

$ cd "/Volumes/Macintosh HD/System/Library" $ cd ../../etc $ echo "0.0.0.0 iprofiles.apple.com" >> hosts $ echo "0.0.0.0 mdmenrollment.apple.com" >> hosts $ echo "0.0.0.0 deviceenrollment.apple.com" >> hosts $ echo "0.0.0.0 albert.apple.com" >> hosts $ echo "0.0.0.0 acmdm.apple.com" >> hosts

$ csrutil enable $ reboot

Never had any issues with the method.

Thx for sharing. Albert.apple.com / acmdm.apple.com are the ones missing in my list. I got gdmf.apple.com instead according to the OP thread. But I haven't encounter any problems so far too :)

@ink-splatters
Copy link

ink-splatters commented Nov 3, 2022

How I erase my Mac and get rid of the notifications:

Clean erase Reinstall OS from recovery partition. Aster first boot I turn off the router in my house so I can bypass the mdm screen an continue with the setup process. I create a user so I can disable csrutil.

After all is done I restart and boot into recovery. Open terminal and follow this procedure:

$ csrutil disable $ reboot

Back in recovery and terminal

$ cd "/Volumes/Macintosh HD/System/Library" $ cd ../../etc $ echo "0.0.0.0 iprofiles.apple.com" >> hosts $ echo "0.0.0.0 mdmenrollment.apple.com" >> hosts $ echo "0.0.0.0 deviceenrollment.apple.com" >> hosts $ echo "0.0.0.0 albert.apple.com" >> hosts $ echo "0.0.0.0 acmdm.apple.com" >> hosts

$ csrutil enable $ reboot

Never had any issues with the method.

I don't recall the reasons to actually disable SIP for MDM bypass discussed here. And though I might be wrong, it's not obvious.

Is't true that with the SIP on, macOS stops giving up on timeouts, in the middle of operations crucial to Apple's opinionated look on the system consistency thus improving the security, effectively considering multi-step operations transactional. Thus, some things can block indefinitely, causing deadlocks in some services. E.g just OS log-in can cause deadlock if some files are inaccessible for write (e.g. "chflagged"). In theory it might be the case when trying to access MDM-related resources, in the middle of something critical.
It can also be the other way around and SIP is definitely capable of ultimately dark evil things as, e.g. reverting literally everything seen "non-revertible", to its vanilla state, without even the OS reboot. Sometimes even reverting such ultimately "permanent" things which do require user interaction normally (e.g.chflags uchg,schg being wipable in a blink of an eye, without OS reboot by SIP / rootless interventions. That's been for a long while, obviously before 'Cryptexes' recently appeared in Ventura*

But it's important to know that SIP is there for a reason and significantly improves the quality of security response in case of real security threat, no matter if one likes it or not.**

@ink-splatters
Copy link

ink-splatters commented Nov 3, 2022

TL;DR The below is off topic which I still find relevant in connection with the previous post, but you might want to skip it if came here for MDM bypass


* SIP interventions have been there for a long time, obviously before 'Cryptexes' recently appeared in Ventura, which are in fact privileged DMG mounts 'stitched' using firm-links, without the restrictions of castrated "synthetic" mounts available to a mere mortal

man synthetic

And it's been always possible, or, at least for a long while, for the whole Safari thing to be upgradable without OS reboot. That covers obviously the app itself, as well as up to a dozen of its daemons / public and private frameworks / supporting files / name it.
It all resides in /Library/Apple/System/ on Data volume.

Looks the same is now applicable for the potentially error prone components previously seen part of System volume, by just plugging another DMG, stitching it with the system, with (allegedly) less buggy stuff.


** Unfortunately, there are now more justified reasons to disable SIP; one of disappointments comes e.g. with one's trying to disable system daemons seeing the most of them risen up from the hell again (agents as well, by the way).

Good to mention, that's only in Full Security mode and is not forced in reduced security. But Reduced Security kills Apple Pay. Still not enough for a full scale drama as it's not an iPhone in fact, for it to honour Apple Pay that seriously. Anyway, I find this frustrating enough, but pretty logical from the security perspective to control the environment which is crucial for achieving "proper" security level (as per Apple treatment of what the proper security level should be).

Along with the security related daemons, the dozens of services which are absolutely not crucial for security (from the first glance), are up as well. Funny that it's also additional attack surface, with impacts ranging from relatively innocent to pretty severe.

But, IMO, having all this up and running, in the combination along with the trusted boot chain, plus what's now called Sealed System Volume, allows Apple to fully take over the security of macOS, without the interference coming from false-positive security reporting and other noise caused by hacky users (apparently suffered being hacked by ones who occurred to be slightly hackier, thanks to the first cohort's lifting the security measures).

@Sailas2k6
Copy link

Sailas2k6 commented Nov 3, 2022

gdmf.apple.com - Used by an MDM server to identify which software updates are available to devices that use managed software updates

iprofiles.apple.com - Hosts enrollment profiles used when devices enroll in Apple School Manager or Apple Business Manager through Device Enrollment

mdmenrollment.apple.com - MDM servers to upload enrollment profiles used by clients enrolling through Device Enrollment in Apple School Manager or Apple Business Manager, and to look up devices and accounts

deviceenrollment.apple.com - DEP provisional enrollment

albert.apple.com - Device activation

acmdm.apple.com - can't find any info ... or the server name has changed

axm-adm-mdm.apple.com - MDM server

@iambulmaro
Copy link

iambulmaro commented Nov 4, 2022

If you write all the aforementioned profiles in the hosts /private/etc/hosts after disabling csrutil it seems to work fine.

@Sailas2k6
Copy link

Sailas2k6 commented Nov 6, 2022

@stop-d-fomo
Copy link

stop-d-fomo commented Nov 11, 2022

How I erase my Mac and get rid of the notifications:

Clean erase Reinstall OS from recovery partition. Aster first boot I turn off the router in my house so I can bypass the mdm screen an continue with the setup process. I create a user so I can disable csrutil.

After all is done I restart and boot into recovery. Open terminal and follow this procedure:

$ csrutil disable $ reboot

Back in recovery and terminal

$ cd "/Volumes/Macintosh HD/System/Library" $ cd ../../etc $ echo "0.0.0.0 iprofiles.apple.com" >> hosts $ echo "0.0.0.0 mdmenrollment.apple.com" >> hosts $ echo "0.0.0.0 deviceenrollment.apple.com" >> hosts $ echo "0.0.0.0 albert.apple.com" >> hosts $ echo "0.0.0.0 acmdm.apple.com" >> hosts

$ csrutil enable $ reboot

Never had any issues with the method.

Once this is implemented, can mdm be enforced remotely by which I mean can the machine be wiped etc. ?

@Sailas2k6
Copy link

Sailas2k6 commented Nov 11, 2022

As long as the profiles are not installed, and profiles status -show enrollment are both on No the mac can not be erased.

@stop-d-fomo
Copy link

stop-d-fomo commented Nov 11, 2022

As long as the profiles are not installed, and profiles status -show enrollment are both on No the mac can not be erased.

So no control can be assumed remotely if both dep and mdm have a no status? Thanks for help.

@fitzroymckay
Copy link

fitzroymckay commented Nov 14, 2022

How I erase my Mac and get rid of the notifications:

Clean erase Reinstall OS from recovery partition. Aster first boot I turn off the router in my house so I can bypass the mdm screen an continue with the setup process. I create a user so I can disable csrutil.

After all is done I restart and boot into recovery. Open terminal and follow this procedure:

$ csrutil disable $ reboot

Back in recovery and terminal

$ cd "/Volumes/Macintosh HD/System/Library" $ cd ../../etc $ echo "0.0.0.0 iprofiles.apple.com" >> hosts $ echo "0.0.0.0 mdmenrollment.apple.com" >> hosts $ echo "0.0.0.0 deviceenrollment.apple.com" >> hosts $ echo "0.0.0.0 albert.apple.com" >> hosts $ echo "0.0.0.0 acmdm.apple.com" >> hosts

$ csrutil enable $ reboot

Never had any issues with the method.

Thank you!! Worked perfectly for me

edit: hmm, no it's back now - I'll update in a couple days

@djtjl
Copy link

djtjl commented Nov 16, 2022

I get following error when I try to edit hosts file....
Running MBP M1 with 12.6.1

xxxxx@xxxxxx-MBP etc % echo "0.0.0.0 iprofiles.apple.com" >> hosts
zsh: permission denied: hosts
xxxxx@xxxxxx-MBP etc % ls -l hosts
-rw-r--r-- 1 root wheel 213 Oct 12 23:06 hosts

Enrollment status is,
xxxxx@xxxxxx-MBP etc % profiles status -type enrollment
Enrolled via DEP: No
MDM enrollment: No
xxxxx@xxxxxx-MBP etc %

Integrity Status is
xxxxx@xxxxxx-MBP etc % csrutil status
System Integrity Protection status: enabled.
xxxxx@xxxxxx-MBP etc %

I am keep getting Remote management notification.
How can I get rid of that so It will not impact now or future with macOS updsates.

@stop-d-fomo
Copy link

stop-d-fomo commented Nov 16, 2022

I get following error when I try to edit hosts file.... Running MBP M1 with 12.6.1

xxxxx@xxxxxx-MBP etc % echo "0.0.0.0 iprofiles.apple.com" >> hosts zsh: permission denied: hosts xxxxx@xxxxxx-MBP etc % ls -l hosts -rw-r--r-- 1 root wheel 213 Oct 12 23:06 hosts

Enrollment status is, xxxxx@xxxxxx-MBP etc % profiles status -type enrollment Enrolled via DEP: No MDM enrollment: No xxxxx@xxxxxx-MBP etc %

Integrity Status is xxxxx@xxxxxx-MBP etc % csrutil status System Integrity Protection status: enabled. xxxxx@xxxxxx-MBP etc %

I am keep getting Remote management notification. How can I get rid of that so It will not impact now or future with macOS updsates.

did you start with csrutil disable and reboot before the echo commands?

@djtjl
Copy link

djtjl commented Nov 16, 2022

I get following error when I try to edit hosts file.... Running MBP M1 with 12.6.1
xxxxx@xxxxxx-MBP etc % echo "0.0.0.0 iprofiles.apple.com" >> hosts zsh: permission denied: hosts xxxxx@xxxxxx-MBP etc % ls -l hosts -rw-r--r-- 1 root wheel 213 Oct 12 23:06 hosts
Enrollment status is, xxxxx@xxxxxx-MBP etc % profiles status -type enrollment Enrolled via DEP: No MDM enrollment: No xxxxx@xxxxxx-MBP etc %
Integrity Status is xxxxx@xxxxxx-MBP etc % csrutil status System Integrity Protection status: enabled. xxxxx@xxxxxx-MBP etc %
I am keep getting Remote management notification. How can I get rid of that so It will not impact now or future with macOS updsates.

did you start with csrutil disable and reboot before the echo commands?

No. I have not.
I will try that again and update the thread.

@djtjl
Copy link

djtjl commented Nov 16, 2022

I get following error when I try to edit hosts file.... Running MBP M1 with 12.6.1
xxxxx@xxxxxx-MBP etc % echo "0.0.0.0 iprofiles.apple.com" >> hosts zsh: permission denied: hosts xxxxx@xxxxxx-MBP etc % ls -l hosts -rw-r--r-- 1 root wheel 213 Oct 12 23:06 hosts
Enrollment status is, xxxxx@xxxxxx-MBP etc % profiles status -type enrollment Enrolled via DEP: No MDM enrollment: No xxxxx@xxxxxx-MBP etc %
Integrity Status is xxxxx@xxxxxx-MBP etc % csrutil status System Integrity Protection status: enabled. xxxxx@xxxxxx-MBP etc %
I am keep getting Remote management notification. How can I get rid of that so It will not impact now or future with macOS updsates.

did you start with csrutil disable and reboot before the echo commands?

No. I have not. I will try that again and update the thread.

Update:
I tried this..https://blog.uchennaegbo.com/how-to-disable-remote-management-and-device-enrollment-notifications-on-mac-os
It worked for me. I was able to update the hosts file.
Hope I will not get the Remote Management notification again.

@Nicolas1203
Copy link

Nicolas1203 commented Nov 20, 2022

How I erase my Mac and get rid of the notifications:

Clean erase Reinstall OS from recovery partition. Aster first boot I turn off the router in my house so I can bypass the mdm screen an continue with the setup process. I create a user so I can disable csrutil.

After all is done I restart and boot into recovery. Open terminal and follow this procedure:

$ csrutil disable $ reboot

Back in recovery and terminal

$ cd "/Volumes/Macintosh HD/System/Library" $ cd ../../etc $ echo "0.0.0.0 iprofiles.apple.com" >> hosts $ echo "0.0.0.0 mdmenrollment.apple.com" >> hosts $ echo "0.0.0.0 deviceenrollment.apple.com" >> hosts $ echo "0.0.0.0 albert.apple.com" >> hosts $ echo "0.0.0.0 acmdm.apple.com" >> hosts

$ csrutil enable $ reboot

Never had any issues with the method.

Just did it a few days ago on a M2 13". Works like a charm.

I have a question though. If I understand correctly I have to do the same procedure again after any update, right ?

@Sailas2k6
Copy link

Sailas2k6 commented Nov 21, 2022

How I erase my Mac and get rid of the notifications:
Clean erase Reinstall OS from recovery partition. Aster first boot I turn off the router in my house so I can bypass the mdm screen an continue with the setup process. I create a user so I can disable csrutil.
After all is done I restart and boot into recovery. Open terminal and follow this procedure:
$ csrutil disable $ reboot
Back in recovery and terminal
$ cd "/Volumes/Macintosh HD/System/Library" $ cd ../../etc $ echo "0.0.0.0 iprofiles.apple.com" >> hosts $ echo "0.0.0.0 mdmenrollment.apple.com" >> hosts $ echo "0.0.0.0 deviceenrollment.apple.com" >> hosts $ echo "0.0.0.0 albert.apple.com" >> hosts $ echo "0.0.0.0 acmdm.apple.com" >> hosts
$ csrutil enable $ reboot
Never had any issues with the method.

Just did it a few days ago on a M2 13". Works like a charm.

I have a question though. If I understand correctly I have to do the same procedure again after any update, right ?

Nop, if you update it's OK. Only if you wipe the device !

@Nicolas1203
Copy link

Nicolas1203 commented Nov 21, 2022

How I erase my Mac and get rid of the notifications:
Clean erase Reinstall OS from recovery partition. Aster first boot I turn off the router in my house so I can bypass the mdm screen an continue with the setup process. I create a user so I can disable csrutil.
After all is done I restart and boot into recovery. Open terminal and follow this procedure:
$ csrutil disable $ reboot
Back in recovery and terminal
$ cd "/Volumes/Macintosh HD/System/Library" $ cd ../../etc $ echo "0.0.0.0 iprofiles.apple.com" >> hosts $ echo "0.0.0.0 mdmenrollment.apple.com" >> hosts $ echo "0.0.0.0 deviceenrollment.apple.com" >> hosts $ echo "0.0.0.0 albert.apple.com" >> hosts $ echo "0.0.0.0 acmdm.apple.com" >> hosts
$ csrutil enable $ reboot
Never had any issues with the method.

Just did it a few days ago on a M2 13". Works like a charm.
I have a question though. If I understand correctly I have to do the same procedure again after any update, right ?

Nop, if you update it's OK. Only if you wipe the device !

Alright, I will give it a go then. Thank you for your feedback!

Edit: Can confirm that the update from Monterey to Ventura went without any issue.

@djtjl
Copy link

djtjl commented Nov 21, 2022

I get following error when I try to edit hosts file.... Running MBP M1 with 12.6.1
xxxxx@xxxxxx-MBP etc % echo "0.0.0.0 iprofiles.apple.com" >> hosts zsh: permission denied: hosts xxxxx@xxxxxx-MBP etc % ls -l hosts -rw-r--r-- 1 root wheel 213 Oct 12 23:06 hosts
Enrollment status is, xxxxx@xxxxxx-MBP etc % profiles status -type enrollment Enrolled via DEP: No MDM enrollment: No xxxxx@xxxxxx-MBP etc %
Integrity Status is xxxxx@xxxxxx-MBP etc % csrutil status System Integrity Protection status: enabled. xxxxx@xxxxxx-MBP etc %
I am keep getting Remote management notification. How can I get rid of that so It will not impact now or future with macOS updsates.

did you start with csrutil disable and reboot before the echo commands?

No. I have not. I will try that again and update the thread.

Update: I tried this..https://blog.uchennaegbo.com/how-to-disable-remote-management-and-device-enrollment-notifications-on-mac-os It worked for me. I was able to update the hosts file. Hope I will not get the Remote Management notification again.

Update2: Did not receive any notification from last 5 days...

@lee-corey
Copy link

lee-corey commented Dec 1, 2022

When I try csrutil disable then it asks Enter password for user _mbsetupuser:
What should I type in here?

@lee-corey
Copy link

lee-corey commented Dec 1, 2022

Does this method no longer work? It seems to be holding up for me still.

If it works for you, perfect!

So csrutil disable in the terminal brings the message, “turning off system integrity protection requires modifying system security. Allow booting unsigned operating systems and any kernel extensions for OS Macintosh? Y/N?” I tried Yes and it asks for a password for user _mbsetupuser

How did you resolve this?

@Nicolas1203
Copy link

Nicolas1203 commented Dec 1, 2022

Does this method no longer work? It seems to be holding up for me still.

If it works for you, perfect!

So csrutil disable in the terminal brings the message, “turning off system integrity protection requires modifying system security. Allow booting unsigned operating systems and any kernel extensions for OS Macintosh? Y/N?” I tried Yes and it asks for a password for user _mbsetupuser

How did you resolve this?

Well you probably did not do the first steps which basically consist into:

  • erasing your OS
  • Re-installing from internet
  • unplug you router while it reboots to force the computer to create a new user
  • create a user, reboot, and enjoy the full permission to do the commands you want

You can find more details here : https://checkm8.info/bypass-mac-mdm-lock

Hope this helps.

@ink-splatters
Copy link

ink-splatters commented Dec 1, 2022

You just press enter.

I’m not at the context for now, sorry, but just in case: you won’t be able to change Local Boot Policy until some admin have obtained Secure Token / became owner of the volume (usually those come together)

It’s granted when:

  1. Upon the first (ever, since the system install) admin user is created. The token is then derived from one-time kind of nonce Secure Enclave stores for that purpose

  2. Every user which is created by secure token-owner, via GUI is granted the token either.

  3. using sysadminctl with “secure token unlock” grants the token to the newly created user; since Ventura AFAIK, if FV is enabled, explicit unlock might not be needed.

the fact that _mbsetupuser is the disk owner looks like result of tampering, which I used my own trying to grant it Secure Token before everyone else. To my best knowledge, it doesn’t work reliable in last Monterey releases and in Ventura:

Having done

dscl -f /Volumes/Data/private/var/db/dslocal/nodes/Default localonly
# in OD console:
cd /Local/Target/Users
append ../Groups/admin GroupMembers <type _mbsetupuser UUID>
append ../Groups/admin GroupMembership _mbsetupuser
create _mbsetupuser AuthenticationAuthority ;SecureToken;
passwd _mbsetupuser
# hit enter 

In the absence of other users, will make _mbsetupuser disk owner and lead to the prompt you see.

but likely the token won’t be granted so the system won’t be able to provision any user who would have had the token.

howeber, if instead of _mbsetupuser you create first user likewise, it will be granted token. But volume personalisation would have been needed to be initialised with the use of internet connection; AND it won’t work at all in Ventura at least, making you unable to boot from the volume.
in Monterey however this hack would allow to create user without any involvement of _mbsetupuser

@djtjl
Copy link

djtjl commented Dec 1, 2022

howeber, if instead of _mbsetupuser you create first user lik

@ink-splatters Do you mean to say that the with Ventura, disable DEP is not an option anymore.
Is my understanding is correct ? As I last tried with Monterey and it works but have not tried with Ventura.

@lucasmenares
Copy link

lucasmenares commented Dec 3, 2022

This worked for me on M1 Pro 2021 with MacOS Ventura, original method was for Big Sur but I changed it using a different type of domain block since the old method doesn't work anymore:

First of all, if you want to trigger the notification you can use this command:
sudo profiles show -type enrollment

Now we will start. First block your Mac from reaching the domain iprofiles.apple.com. For this you can use your hosts file like:
echo "0.0.0.0 iprofiles.apple.com" | sudo tee -a /etc/hosts
or blocking them from your firewall.

Then, I checked the current enrollment profile
sudo profiles show -type enrollment

This will show you the current enrollment configuration your Mac has, you can even block the domain mentioned in ConfigurationURL just to be safe, example:
echo "0.0.0.0 yourDomainMentionedInConfigurationURL" | sudo tee -a /etc/hosts

After that, I proceed to delete the profile, in my regular session, not recovery, although it would probably also work in recovery:
sudo profiles remove -all

Keep in mind that this command will delete all other profiles you may have, in my case, I didn't have any more.

Finally, you can check for the enrollment profile again. I would get an error saying that it could not retrieved given that I blocked the domain from where it's retrieved:

sudo profiles show -type enrollment
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}

And the notification is gone for good, hope it helps!

@JediRhymeTrix
Copy link

JediRhymeTrix commented Dec 3, 2022

Do the steps to disable the notification have to be repeated after upgrading from Monterey to Ventura?

@lucasmenares
Copy link

lucasmenares commented Dec 3, 2022

Do the steps to disable the notification have to be repeated after upgrading from Monterey to Ventura?

@JediRhymeTrix Not sure, but you can check it using the command to trigger the notification after your update:
sudo profiles show -type enrollment

@ink-splatters
Copy link

ink-splatters commented Dec 5, 2022

howeber, if instead of _mbsetupuser you create first user lik

@ink-splatters Do you mean to say that the with Ventura, disable DEP is not an option anymore. Is my understanding is correct ? As I last tried with Monterey and it works but have not tried with Ventura.

No, i didn't mean that and can't think of why it should be the case.

Whose test the link: https://idevice.me/macbook-mdm-bypass-activator-for-t1-t2-m1-m2/ Does it work, is the $50 worth it?

Whose test the link: https://idevice.me/macbook-mdm-bypass-activator-for-t1-t2-m1-m2/ Does it work, is the $50 worth it?

Lol, no :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment