How can I prevent non-admin users from renaming their Macbooks on MacOS Sonoma?

pbileci
Contributor

We track Macbooks by name in Jamf but students are easily able to rename their Macbooks by going to System Settings - General - About, and then just clicking and typing over the name that we set. When I look in restrictions, there's an option to restrict the entire General section but we don't want to do that. I just want to restrict the About section in General to prevent them from renaming the Mac.  

1 ACCEPTED SOLUTION

AJPinto
Esteemed Contributor

Removing admin access blocks most methods of changing the hostname. As for changing it in general, it's a configuration profile deploying the restrictions payload disallowing modifying the device name.

AJPinto_0-1718647183416.png

 

AJPinto_2-1718647236705.png

 

View solution in original post

7 REPLIES 7

AJPinto
Esteemed Contributor

Removing admin access blocks most methods of changing the hostname. As for changing it in general, it's a configuration profile deploying the restrictions payload disallowing modifying the device name.

AJPinto_0-1718647183416.png

 

AJPinto_2-1718647236705.png

 

You have to uncheck that box, right? Our restrictions policy has that box unchecked, so they should NOT be able to change the name.

DBrowning
Valued Contributor II

Correct.  Also need to make sure the device is running macOS 14 or higher.  

AJPinto
Esteemed Contributor

Yep, sorry I was lazy with my screenshots. And as @DBrowning pointed out the devices need to be on macOS 14 or better (This will apply to macOS 15 when it comes out later this year).

Very Helpful!

Question: this won't prevent the IT Admin profile i have pushed out over policy from having admin rights, will it?

Thanks!

AJPinto
Esteemed Contributor

Locking the hostname has nothing to do with removing admin access, it simply limits the ability to change the hostname locking it down to the MDM.

 

Food for thought, macOS must have at least one admin account. If you try to remove admin access from the only admin account you will get an error.

I didn't think so, and i got a little gun-shy, but I pushed the policy and it's working as expected. 

 

Thanks!