You can rename a device from within Addigy in two ways — through an MDM command in GoLive, or by deploying a script directly to the device — depending on the device's platform and enrollment type.
Method 1: Changing a Device Name via MDM
Prerequisites
- The device is enrolled in Addigy's MDM.
- It's running a supported OS version.
- It has Supervision enabled.
Steps
- Navigate to a device's GoLive page.
- Select Change Name at the top of the page.
- Type the desired name and click Rename.
If the Name Doesn't Change
If a device's name isn't updating, the MDM connection to the device may be stuck or broken.
- macOS: see FAQ: Troubleshooting MDM Connectivity in Addigy
-
Non-macOS: try restarting the device, and confirm the push certificate hasn't expired by clicking MDM: in GoLive.
If the name still isn't changing after checking the above, reach out to our support team for further assistance.
Method 2: Changing a Device Name via Agent (macOS)
You can also rename a Mac by deploying a script to the device. See Creating and Running Scripts on Your Devices for a full walkthrough of pushing scripts.
Note: This workflow isn't supported for BYOD devices, since it relies on the Addigy agent.
Commands and Information
Addigy determines a device's display name based on its Computer Name. For uniformity, we recommend setting all three of the following to the same name.
HostName — usually provided by a network-based system via DHCP or DNS; not set by default on newer macOS versions.
sudo scutil --set HostName [Desired device name]
LocalHostName — used with Zeroconf networking tools such as Bonjour, AirPlay, AirDrop, and LAN Cache. Defaults to {user}s-{device-type}.local after Setup Assistant (for example, johns-macbook-pro.local).
sudo scutil --set LocalHostName [Desired device name]
ComputerName — the user-friendly name visible in the Sharing pane of System Preferences. Defaults to {user}'s {device type} after Setup Assistant (for example, John's MacBook Pro).
sudo scutil --set ComputerName [Desired device name]
The device name may not update until the DNS cache clears. Run the following to clear it immediately:
killall -HUP mDNSResponder