ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

HostName ignored when deploying Windows 10 Image


Article ID: 39452


Updated On:


CA Automation Suite for Data Centers - Configuration Automation CA Client Automation - Asset Management CA Client Automation - IT Client Manager CA Client Automation CA Client Automation - Remote Control CA Client Automation - Asset Intelligence CA Client Automation - Desktop Migration Manager CA Client Automation - Patch Manager



  • When deploying a Windows 10 Image via OSIM the value defined for HostName is ignored and the target PC is allocated a generated name by Windows Setup.
  • In ..\windows\panther\setupact.log the following is seen

[Shell Unattend] ComputerName in unattend [<computer_name>] matches the current ComputerName [<computer_name>]

[Shell Unattend] skipping setting the same ComputerName


  • Windows 10 deployment via ImageX


  • This appears to be an issue in the GA Windows 10 release. 
  • If you attempt to deploy the new PC and give it the same name as the template used to generate the wim then it is ignored.


Ensure the HostName value used for the deployed PC's does not match the Host name used in the template PC used to generate the wim.


Release: UASIT.99000-12.9-Asset Intelligence