Issue
The computer name does not match what was entered in the Device Name Prompter during Provisioning.
Cause
This is commonly caused by:
- A different unattend file being processed by windows
- The name from the prompter not being placed into the Unattend file
Steps
When using the Device Name Prompter, make sure it is positioned BEFORE the Inject Script action.
The Device Name Prompter will append the injected script, and update <ComputerName>%ldHostname%</ComputerName> to reflect what is entered in the prompter.
Note: This means the unattend being used
must use the %ldHostname% variable in the ComputerName field.
Example: If you enter "Workstation7" in the Device Name Prompter, it will attempt to change modify the script from <ComputerName>%ldHostname%</ComputerName> to <ComputerName>Workstation7</ComputerName>
After verifying that the actions are in the right order, add a wait action after the inject script action, and use the 'wait' time to open the script as it was injected at c:\windows\panther\unattend.xml.
Verify that the name that was put in the prompter appears in the xml here:<ComputerName>VALUE_FROM_PROMPTER</ComputerName>
Once the name has been verified as correct in the xml that was injected to the Panther folder, allow the machine to process through the CTOS action and reboot into windows.
Once in windows, check if the name matches the prompter.
If no, check this log: "C:\Windows\Panther\UnattendGC\setupact.log"
In this log it will tell you what unattend.xml file it uses:
2015-06-02 14:53:24, Info [windeploy.exe] Found unattend file: [C:\Windows\Panther\unattend.xml]
It will also tell you about windows reading the unattend to name the computer:
2015-12-18 07:45:29, Info [Shell Unattend] ComputerName set to VALUE_FROM_PROMPTER
If more than one unattend is found on the computer, Windows may be selecting an unintended file to process. If this is found to be the case, it is recommended to:
- Delete the extra unattend files and recapture the image.
or
- Add logic in the provisioning template to delete the extra templates
- This method is less desirable as it may result in other unattends still being missed, which could cause the issue to recur but on another unattend that windows finds on the hard drive.