798 votesMathieu Ait Azzouzene commented
49 votesMathieu Ait Azzouzene commented
For example let's admit all Autopilot devices are corporate owned.Mathieu Ait Azzouzene shared this idea ·
As of the week of August 27, you can use a template to control how the machine will be automatically named. So not exactly static, but gets you away from total random. From the discussion, sounds like not total random was good enough for some, but not all, so I will switch this back to “noted”.
more detail about what we released in August:
When you create an autopilot deployment profile, you can designate a name, which must be 15 characters or less, and can contain letters, numbers, and hyphens. Names can’t be all numbers. Use the SERIAL macro to add a hardware-specific serial number. Alternatively, use the RAND:x macro to add a random string of numbers, where x equals the number of digits to add.
It’s only available with the Windows Insider build for now.
As of the October 2018 release, you can apply Autopilot profiles to enrolled Win 10 devices that have not already been registered for Autopilot. In the Autopilot profile, choose the Convert all targeted devices to Autopilot option to automatically register non-Autopilot devices with the Autopilot deployment service. Allow 48 hours for the registration to be processed. When the device is unenrolled and reset, Autopilot will provision it.
Does that get you what you want?
An update on this – this feature in flight but we are going to take a bit more time before we make it publicly available. Should be early in 2020. Thanks for your patience!