Using unattend.xml without setting the device name

[rolfhh]

We have a PowerShell script that uses Rename-Computer to set the device name after looking it up in our inventory system. At the moment we're using unattend.xml to run this script in the specialize phase of the deployment. Prefixes.txt contains a single prefix, FFU-.

The Rename-Computer command that our script runs appears to be overridden by the auto-generated name FFU Builder puts into unattend.xml.

Is there any way to use unattend.xml without also enabling FFU Builder's device name functionality?

[rbalsleyMSFT]

Not currently, but now that unattend.xml is being used for more than just naming, I can look into changing it. Now that there's a UI, I can make naming much more intuitive.

When is Rename-Computer being run?

[rolfhh]

Rename-Computer is executed by the second of two PowerShell scripts (Registrer-PCINetBox.ps1) that run through RunSynchronousCommand nodes. Shown below is the complete unattend.xml file.

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
  <settings pass="specialize">
    <!--<ComputerName> must be in the first Component Element  "Microsoft-Windows-Shell-Setup" . Do not change the order or remove it -->
    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <ComputerName>ehdgs</ComputerName>
      <!--Leave Default will be renamed-->
    </component>
    <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <RunSynchronous>
        <RunSynchronousCommand wcm:action="add">
          <Order>1</Order>
          <Path>cmd.exe /c "FOR %i IN (D E F G H I J K L N M) DO IF EXIST %i:\Scripts\Set-DellBiosSettings\Set-DellBiosSettings.ps1 Powershell -executionpolicy ByPass %i:\Scripts\Set-DellBiosSettings\Set-DellBiosSettings.ps1"</Path>
          <Description>Configure standard BIOS settings for Dell computers via Dell Command PowerShell Provider.</Description>
        </RunSynchronousCommand>
        <RunSynchronousCommand wcm:action="add">
          <Order>2</Order>
          <Path>cmd.exe /c "FOR %i IN (D E F G H I J K L N M) DO IF EXIST %i:\Scripts\Registrer-PCINetBox\Registrer-PCINetBox.ps1 Powershell -executionpolicy ByPass %i:\Scripts\Registrer-PCINetBox\Registrer-PCINetBox.ps1"</Path>
          <Description>Register or update computer info in NetBox.</Description>
        </RunSynchronousCommand>
      </RunSynchronous>
    </component>
  </settings>
  <settings pass="oobeSystem">
    <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
      <InputLocale>0414:00000414</InputLocale>
      <!--Set your Keybaord and System Local https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-8.1-and-8/hh825682(v=win.10) -->
      <SystemLocale>nb-NO</SystemLocale>
      <UILanguage>nb-NO</UILanguage>
      <UserLocale>nb-NO</UserLocale>
    </component>
    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
      <OOBE>
        <HideEULAPage>true</HideEULAPage>
        <!--Hide the End User License agreement -->
      </OOBE>
    </component>
  </settings>
</unattend>

[rolfhh]

Actually, I had a look at ApplyFFU.ps1 and PR #150. Perhaps adding support for an external PowerShell script to get the computer name would make more sense, and be more potentially useful? I think it could be implemented in a very similar manner to the CSV file support from PR #150.

Basically:

1. Look for the naming script in the unattend folder
2. If the script exists, execute it with the computer's serial number as a parameter
3. Use the name returned by the script if it looks reasonable, otherwise default to a randomized name

Do you have any objections to this idea, like wanting to avoid calling external scripts from ApplyFFU.ps1? If not I can have a go at implementing it and eventually presenting it as a pull request.

[rbalsleyMSFT]

I have some ideas I want to pursue with naming that will handle this a bit better. I wouldn't take a PR for this now since I'll expand on this a bit more instead of just using the prefix + serial number (can use random characters to make it more in line with Autopilot), make it more intuitive to create your prefixes.txt, and allow a custom naming script to name however you want, and make the CSV file support integrated in the UI (outside of the PR and release notes, the CSV file support isn't really documented). And also just make it so you can choose not to name at all yet still use unattend.xml.

Lots of things to think about here.

[rolfhh]

Sounds great, I look forward to see how things develop.