/build/static/layout/Breadcrumb_cap_w.png

Get/Set Computer name not working

Afternoon,

 I'm using the getcomputername.exe along with the command line of Getcomputername.exe /dialog /timeout:120 as a preinstallation task. The dialog box comes up and I am able to input in a pc name. As a Mid-Level task I have the Setcomputername.exe with command line SetComputerName.exe. However when my imaged PC is done I look at the PC name and it doesn't reflect what I had indicated.

The Get and Set are at the very first of thier respective tasks. I've also verified it is writing to the 'petemp' folder on my kace box.

Any ideas?


1 Comment   [ + ] Show comment
  • Are you using the appropriate arch versions of those tasks (x86 and x64)? - nheyne 10 years ago

Answers (1)

Answer Summary:
Posted by: SDNBTP 10 years ago
Third Degree Blue Belt
0

Are you using a sysprep image? If so, make sure you have this line in the appropriate area of your unattend file: <ComputerName>*</ComputerName>

If you do not have this line, the set exe is not able to inject the name into the unattend file. Since you can see it in PETemp, you know the get task is working. If you uncheck auto restart when you deploy the image, then browse to your unattend file in Kace when it's done, you should see the new name in the unattend: <ComputerName>NameFromGetTask</ComputerName>


Comments:
  • prior to updating to version 3.580613, the unattended xml was created on the root of C. With the update the unattended xml file is no longer created there, and now it does not properly name the PC. In the new version does it get created somewhere else? Or where should it be created? - jgolden 10 years ago
    • Perhaps better served in a new thread my friend. Since my original question was answered and resolved. - jason.rfpco 10 years ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ