We have deployed some macOS devices to employees, where the devices are named based on the employee’s team and department. We’ve noticed that some users have changed the names of their devices, which can create a lot of confusion for us (I mean for the IT team😅). It becomes challenging to keep track of the devices when associating policies with a specific team. Is there any way to restrict users from changing the device name?
144 Views
Replies (3)
Marked SolutionPending Review
Participant
3 months ago
Marked SolutionPending Review
Hey @wilma, as far as I know, if the user has a standard account, they cannot change the name of the device. If the user is an administrator, they will have the privilege to change the device name. Unless the administrator permits it, the standard user shouldn’t be able to change it, right?
Marked SolutionPending Review
Participant
3 months ago
Marked SolutionPending Review
Yes, that should be the case, but in our situation, standard users are also able to change the device name without being prompted to enter admin credentials. This might be a random case, but we still want a solution for this, either in the form of a script or a configuration profile or another.
Marked SolutionPending Review
Hexnode Expert
3 months ago
Marked SolutionPending Review
Hi @wilma ,
Thanks for reaching out! We’ve got you covered, as Hexnode provides a restriction that prevents users from modifying the device name. Follow the below steps to configure the restriction:
- Log in to your Hexnode UEM portal.
- Navigate to Policies > New Policy, and assign a suitable name.
- Select macOS > Advanced Restrictions.
- Uncheck the ‘Users can modify Device Name’ option, which restricts users from changing the device name.
For more details, please refer to our help documentation on setting up macOS MDM restrictions.
Additionally, you can use the following configuration profile to restrict users from changing the device name:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 |
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>PayloadContent</key> <array> <dict> <key>PayloadDisplayName</key> <string>Loginwindow</string> <key>PayloadIdentifier</key> <string>com.apple.loginwindow.D0159395-658D-45C8-9B20-7C9F701ED067</string> <key>PayloadType</key> <string>com.apple.loginwindow</string> <key>PayloadUUID</key> <string>D0159395-658D-45C8-9B20-7C9F701ED067</string> <key>PayloadVersion</key> <integer>1</integer> <key>UseComputerNameForComputerRecordName</key> <true/> </dict> </array> <key>PayloadDisplayName</key> <string>Untitled</string> <key>PayloadIdentifier</key> <string>MacBook-Air.1D895636-75D9-4CE6-AF1B-B87A4E3FA846</string> <key>PayloadType</key> <string>Configuration</string> <key>PayloadUUID</key> <string>1D895636-75D9-4CE6-AF1B-B87A4E3FA846</string> <key>PayloadVersion</key> <integer>1</integer> </dict> </plist> |
You can utilize Hexnode’s Deploy Custom Configuration policy to deploy this configuration profile.
Regards,
John Cooper
Hexnode UEM
-
Expand
Save
Copy link
Scroll to top
