HostName ignored when deploying Windows 10 Image

book

Article ID: 39452

calendar_today

Updated On:

Products

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

Issue/Introduction

Problem:

  • 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

Environment:  

  • Windows 10 deployment via ImageX

Cause:

  • 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.

Workaround:

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.

Environment

Release: UASIT.99000-12.9-Asset Intelligence
Component: