Skip to main content

Device Name Auto‑Renaming for Smart Groups

Updated yesterday

Swif's Device Name Auto‑Renaming feature lets you automatically standardize computer names for devices in a Smart Group based on assigned users, group attributes, and device details. This helps keep your fleet organized and makes it easier to search, report, and apply policies consistently.


Where you’ll see Device Name Auto‑Renaming

Device Name Auto‑Renaming is available for Smart Groups in two places:

  1. Create New Device Group (Smart Group)

    • As an Additional settings card called Device Name Auto‑Renaming.

  2. Device Group Details → Overview

    • As a read‑only section showing the current auto‑renaming configuration for that group.


What Device Name Auto‑Renaming does

When enabled, Device Name Auto‑Renaming:

  • Defines a naming pattern for computers in the group (e.g., company-dept-username-serial).

  • Controls when the name is updated (on assignment / on join).

  • Handles devices with no assigned user using fallback naming rules.

  • Avoids duplicates by appending a numeric suffix when needed.

All of these settings are stored with the Device Group and are re‑loaded whenever you edit that group.


Configuring Device Name Auto‑Renaming

You can configure this during Smart Group creation, or when editing an existing Smart Group.

1. Open the Device Name Auto‑Renaming settings

  1. Go to Devices → Device Groups.

  2. Click Create Smart Group or open an existing Smart Group.

  3. In the Additional settings area, locate the Device Name Auto‑Renaming card.


2. Set the device name format

The Device name format controls how each device name is constructed.

Key behaviors:

  • You build the format using variables exposed as clickable chips/buttons.

  • Clicking a variable inserts it at the current cursor position in the format field.

  • Hyphens (-) are added automatically between variables when you insert them.

  • The field supports:

    • Typing text manually

    • Inserting variables in the middle of existing text

    • Editing and deleting characters or variables at any time

Example usage:

  1. Place your cursor in the Device name format field.

  2. Click variables (for example: Group name, User name, Serial number) in sequence.

  3. Swif will build something like:

    • group-name-user-name-serial-number

    The hyphens are automatically inserted between variables; you don’t need to type them.

  4. Optionally, type your own static text (e.g., a location or environment tag like nyc or prod).

Tip: Use a consistent pattern across groups (e.g., company-location-user-serial) to make searching and reporting easier.


3. Choose the rename trigger

The Rename trigger dropdown determines when Swif will apply or update the auto‑generated device name.

Available options:

  1. On assignment or when joining this group

    • Rename when:

      • A device is assigned a user, or

      • A device joins this Smart Group.

    • Best when you want device names to stay in sync whether changes come from user assignment or group membership.

  2. On assignment only

    • Rename only when a device is assigned a user.

    • Group membership changes alone will not trigger a rename.

  3. When joining this group only

    • Rename only when a device first joins this Smart Group.

    • User assignment changes after that will not trigger another rename (unless the device leaves and rejoins, depending on your flows).

Choose the option that best fits how you manage device lifecycles and group logic.


4. Handle devices with no assigned user

The If device has no assigned user dropdown controls what happens for devices that do not have a user assigned at the time of renaming.

Available options:

  1. Keep current computer name

    • Swif does not change the device’s current hostname.

    • Use this if you only want to enforce naming once a user is assigned.

  2. Use group name + serial number

    • Swif constructs the device name using:

      • The Smart Group’s name

      • The device serial number

    • Example: marketing-00ABC1234

  3. Use device model + serial number

    • Swif constructs the device name using:

      • The device model (e.g., MacBookPro16,1)

      • The device serial number

    • Example: MacBookPro-00ABC1234

These rules apply only when no user is assigned. Once a user is assigned, the main device name format (with user‑based variables) will be used according to your rename trigger.


5. Avoid duplicates with a unique suffix

The Add unique suffix if a duplicate name exists control is a toggle/checkbox.

  • When enabled:

    • If Swif is about to set a device name that already exists in your environment, it will append a numeric suffix.

    • Example:

      • First device: marketing-jdoe-00ABC1234

      • Second device with the same computed name: marketing-jdoe-00ABC1234-2

  • When disabled:

    • Swif will not auto‑append a suffix; behavior in the presence of duplicates will follow your standard platform logic or constraints.

Use this option if you expect many similar configurations (e.g., shared accounts, repeated models, or cloned devices) and want to ensure uniqueness.


Saving and viewing your configuration

  • When you save or create the Smart Group:

    • All Device Name Auto‑Renaming settings are persisted with the group.

  • When you later open Device Group Details → Overview:

    • The current configuration is shown in a read‑only Device Name Auto‑Renaming section so you can quickly review:

      • Device name format

      • Rename trigger

      • Behavior for devices without a user

      • Whether unique suffixing is enabled

If you edit the group, these values are re‑hydrated into the UI so you can adjust them and save again.


Behavior summary (what to expect)

Once configured:

  • Devices that meet your Smart Group criteria and/or have user assignments—depending on your Rename trigger—will have their names updated based on:

    • The Device name format, including inserted variables

    • The fallback rule for devices without an assigned user

    • The unique‑suffix setting if a duplicate name would be created

  • These rules apply only to this specific Smart Group; different groups can have different naming standards.


Did this answer your question?