0 votesAnonymous shared this idea ·
Thanks for the comments, just a few questions to the gallery.
What platform is this issue with. I’m only seeing IOS devices in your comments, so wanted to double check.
Also, are you having this issue with shared devices or just re-deployment? Unclear from all the comments. Do you want to keep all installed apps on the devices? Depending on your platform, you should be able to already do this for shared devices.Anonymous commented
Windows devices please.
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.Anonymous commented
This would be very useful to have the device pick up a desired name during enrollment or self provisioning.
Here’s some more information about the public preview for Win32 app deployment.
And the video from Ignite: https://myignite.techcommunity.microsoft.com/sessions/64593?source=sessions#ignite-html-anchor
For those of you adding additional suggestions in the comments, please create them as new suggestions. When Win32 app deployment comes out of public preview, we’ll call this one complete and I don’t want your requests to get lost!
Thanks again for your support!