Keep PC name after automation imaging

[Cody Dirrigle]

I want to have techs start using automation imaging again the issue I am running into is the pc is setting itself to a random name after imaging is done, I swear this use not be an issue when we used automation. I have a tried this in the answer file

<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">
<TimeZone>Central Standard Time</TimeZone>
<ComputerName>%COMPNAME%</ComputerName>
<ProductKey>@license</ProductKey>
<CopyProfile>true</CopyProfile>

In the answer file it would keep the name from altiris, I also tried removing that from the answer file but same thing, random name which means it ends up in our staging OU.

At some point it kept that name so any idea how to fix this? Win 10 1909, maybe I was doing something with a token but just recall it working without any name issues

[Cody Dirrigle]

I have also tried ComputerID, Compname with @ nothing works. ​​

[Sergei Zjaikin]

How this random name looks like? dsXXXXXXXXXXXX ?

[Cody Dirrigle]

Win-xxxxxxxxxx

---
Sent from Workspace ONE Boxer

[Sergei Zjaikin]

This looks like name generated by Windows setup itself. Deployment Solution generates dsxxxxxx names.

[Cody Dirrigle]

Correct it seems to be the answer file doing it, I had older answer files where I had removed the name section part just for automation but tried that and still not going,  is there steps to follow that will allow the name  to stay the same for the device. These are all in altiris and not new devices they would imaging with automation. 

---
Sent from Workspace ONE Boxer

[Sergei Zjaikin]

Are you deploying the image to the same machine where image was taken?
If yes then it looks like the issue appears for Windows version 1803 and above.
Unfortunately there is no fix in the code. Could you try deploying the image to some other machine and see what will happen?

[Cody Dirrigle]

No this is a different machine, using our normal gold image. I had hoped we could have the whole process automated in the cases where the pc name would not be changing so the tech could just send the automation job and since the name was the same it would still be in all the same filters etc. makes sense about this changing with 1803, thinking the last time I had them using automation was with 1709 maybe. 

---
Sent from Workspace ONE Boxer

[Sergei Zjaikin]

The internal testing showed that the problem exist on 1809 but does not on 20H2 .

[Cody Dirrigle]

What did you use in the computer name field in the answer file? Did you remove it or did you have compname?

---
Sent from Workspace ONE Boxer

[Sergei Zjaikin]

you have to have 
<ComputerName>@compName</ComputerName>
in answer file in the task

[Cody Dirrigle]

Good news, tested with 21h2 and the devices keep their name again