Does NTLite auto-fill <ComputerName>*</ComputerName> when left blank?

[Selim GURSU]

Hi everyone,

I am building a semi-unattended Windows 10 Enterprise LTSC 2021 ISO. My goal is to ensure that Windows automatically generates a completely random computer name (e.g., DESKTOP-XXXXXXX) upon every single deployment, avoiding any static duplicate names across multiple machines.

I would like to clarify the exact behavior in NTLite under Unattended -> Shell -> Computer name:

1. If I leave the Computer name field completely blank, NTLite seems to automatically handle it as a dynamic random hostname generation (DESKTOP-XXXXXXX).
2. The tooltip mentions using an asterisk (*) for random dynamic computer names (and leveraging up to the first 7 characters of the 'Full Name' field as a prefix if populated).

Could you please confirm if leaving the Computer name field blank in NTLite writes <ComputerName>*</ComputerName> under the hood in autounattend.xml, or if explicitly entering * into the field is the required/best practice to guarantee dynamic random naming on every fresh install?

Thanks in advance!

 

[garlin]

1. NTLite is not responsible for creating a random hostname, Windows does that task.

You can use "*" or an empty value for the <ComputerName>. If you don't have a <FullName> or <Organization>, you will also get a "DESKTOP-(random)" hostname.

https://learn.microsoft.com/en-us/w...nd/microsoft-windows-shell-setup-computername

- If ComputerName is not specified, a random computer name is generated.

- If ComputerName set to an asterisk (*) or is included but empty (""), Windows creates a random 15-character name using up to 7 characters from FullName and Organization, then a dash, then more random characters.

2. If you use "[Prompt]", then NTLite will create a custom script that runs before OOBE, and asks for a hostname to be entered.

 

[WaffenFabrik]

Selim GURSU
Selim abi selamlar , Why don't you use a preconfigured autounattend.xml file? NTLite always strips off my disk configurations in my presets. Because of that I always use my own autounattend.xml files.
Abi neden önceden hazırladığın bir autounattend.xml dosyası kullanmıyorsun? NTLite preset içindeki disk yapılandırmasını hep tıraşlıyor benim ISO'larda. Onun için ben hep kendi autounattend.xml dosyamı kullanıyorum.

 

[FTSWAW]

Hi everyone,

I am building a semi-unattended Windows 10 Enterprise LTSC 2021 ISO. My goal is to ensure that Windows automatically generates a completely random computer name (e.g., DESKTOP-XXXXXXX) upon every single deployment, avoiding any static duplicate names across multiple machines.

I would like to clarify the exact behavior in NTLite under Unattended -> Shell -> Computer name:

1. If I leave the Computer name field completely blank, NTLite seems to automatically handle it as a dynamic random hostname generation (DESKTOP-XXXXXXX).
2. The tooltip mentions using an asterisk (*) for random dynamic computer names (and leveraging up to the first 7 characters of the 'Full Name' field as a prefix if populated).

Could you please confirm if leaving the Computer name field blank in NTLite writes <ComputerName>*</ComputerName> under the hood in autounattend.xml, or if explicitly entering * into the field is the required/best practice to guarantee dynamic random naming on every fresh install?

Thanks in advance!View attachment 16369

You might want to consider this option as well. This is the only option I personally use and it works extremely well. It uses the computer's Serial Number. I have never had an issue with it. I have about 400 devices in an RMM that I manage, so having the Serial Number serves more than one purpose for my case.