How are you automating device names in Active Directory?

For existing Windows devices, PowerShell's Rename-Computer is one option. You could generate the new name from a serial number or from attributes in AD, then feed it to the command.

Test on a small group first, especially if devices are remote. Check for duplicate names, make sure the account running the rename has the required permissions, and plan for the restart needed to apply the change.

If the devices are being provisioned through Windows Autopilot, check the deployment profile's device name template before building a separate rename script. A fixed prefix plus the serial number can keep the naming process automatic during deployment.

That helps with new deployments, but existing machines may need a separate rename plan.

Serial number with a short prefix is a pretty practical default. It gives support something to look up without encoding details that might change when a laptop moves sites.

Watch the length of the full name and check for duplicates, particularly if you shorten the serial. A truncated serial isn't automatically unique.

If every device has a visible asset tag, consider using the asset number as the hostname. Someone needing help can read the number off the device, and support can use the same identifier to find it.

That works best when asset numbers are assigned consistently and checked for uniqueness before provisioning.

There's no single best format. A site and device type prefix, followed by a unique number, can be handy if those details help your support team. For example, a name like LON-LT-0042 is easy to read.

The tradeoff is that site and device details can change, leaving the name out of date. Also consider whether changing the existing fleet is worth the work, particularly for remote machines. You can adopt a convention for new devices without renaming everything immediately.