Static computernames in Windows autopilot before Intune autoenrollment.
Maybe posting this to the wrong component-team but a suggestion would be to give the ability to set a static computername to the imported device when registering the csv file containing hardware information in "Autopilot deployment". The current functionality randomizes the computername after each factory reset or reinstallation. Seems pointless to perform a namechange after Intune autoenrollment. This would solve alot of of administrative issues within larger organizations.
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.
Yes please !
In lieu of this functionality, I've written a simple PowerShell script that fixes this ;)
Having defined the computer name in advance and already associated it with the device order would just be perfect for us in order to be able to continue our comfortable end device self services as they exist today.
E.g. our users are used to order a new computer and the set of applications on it in a self service portal. They can configure the applications at any point in time after they have ordered it. The device even doesn't have to be produced by the OEM yet.
Not sure if this is possible but if we have the computer name and the device has not yet been registered in the cloud by the OEM we might preregister it in AAD anyway and thus be able to add it to application groups. If this is not possible at least we could use the Graph API to add the computer automatically to the application groups as soon as we discover it in AAD.
By doing the application assignment in advance the oobe for our users will improve a lot as they get what they have configured as soon as they touch their device for the first time :-)
They won't need to go back to self service portal or an administrator to get the final set of applications they need to work.
From what i have seen at Ignite Windows Provisioning Packages seem another possibility to pre-load a set of applications on the computer but due to the large variety of software loads in our enterprise this seems very hard to manage and likely not possible with additional coding.
Actually we want to have our modern clients to be configured by Intune and Autopilot only and from a strategic perspective (and lessons learnt from SCCM) we want to use as few provisioning techniques as possible.