Category filter

Configuration profile to display host information at the login window of Mac

To allow IT admins to display additional information such as host name, system version, and IP address at the login window of their company’s macOS devices, we can use a custom configuration profile. Hexnode offers an efficient solution to remotely deploy this configuration profile to multiple enrolled macOS devices using the Deploy Custom Configuration feature. This is a simple method to ensure that users can view system information for compatibility checks, networking purposes, etc. without even having to log onto their devices.


The configuration profile provided below is adapted from a third-party open-source site.

Display host information at the login window of macOS devices

The device management profile configures the AdminHostInfo key, whose assigned value will be displayed as additional host information in the top bar of the login window. The possible values for the AdminHostInfo key include HostName, SystemVersion, or IPAddress. Prior to macOS version 10.10, this string could only display certain information (host name, system version, or IP address) at a time. But above macOS version 10.10, users can toggle through different host information values by clicking on the clock/time in the top-right of the login window, regardless of the key value chosen.

What happens at the device end?

Once the configuration profile to display host information at the login window of macOS devices is deployed, associated devices will promptly exhibit host information such as the host name, system version, and IP address on the login screen upon the subsequent user login.

Host information on the login window of the device showing host name.


  • To create and customize configuration profiles, you can use tools like Apple Configurator, Profile Manager or manually create them using text editors.
  • Use non-encrypted .mobileconfig, .xml, or plist files to deploy profiles across macOS devices.
  • Ensure that you do not associate conflicting configurations with the devices.
  • Use wildcards to fetch key values from the portal.
  • It is recommended to manually validate the configuration profile execution on a system before executing the action in bulk.
  • Hexnode will not be responsible for any damage/loss to the system on the behavior of the configuration profile.

  • Configuration Profile Repository