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.
One more reason to have configurable computer names ( besides regulations) is because existing devices will be reused as modern managed devices.
- These devices have labels attached to them and we can,t simply exchange those.
- the computer name is used as an identifier in many other systems as it was assumed to be immutable. Changing identifiers is always hard, even more as we do not own these systems and even if we did it would create too much effort to build new migration tools.
@rob, but i’d end up with 20000 autopilot profiles if i have 20000 computers 😩 and would need 20000 groups and even have no clue at the moment how to create a dynamic query for those.
Thats why i still suggest to have a new field „assigned computer name“ along with new field to set an assigned users upn and friendly name
We really need a static computer name best assigned to the autopilot registered device, not autopilot profile.
The reason behind this are the processes we are bound to the name assigned by our asset central management system. All our various client management systems must follow these names.
Some processes like label printing also require the name assigned by the central management system.
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.
To me it could also be a json file that is pushed on a Intune synch.
The content to be pushed might come from the AAD device/user object including open extension values which seem made to copied to a registry key 😏
That way we could leverage Intunes push capabilities also for custom app configuration and do not invent our own transport mechanism
The new naming features are not sufficient for us as we need to follow the naming conventions imposed by our central asset management system. There is no way for us to escape from this.
My suggestion: like the new feature to set the name of the assigned user in autopilot we should have something corresponding for computer name