KACE Product Support Question

Get/Set Computer Name

07/27/2018 854 views
I've used this task a bunch in the past (it's been a few years since I've used it) to automatically name machines with a text file, mac address = computer name, but now it's not working. I've got the setcomputername_x64.exe zipped up with the .txt file and I'm using the following command: SetComputerName_x64.exe /rdf:cak.txt /dfk:$Mac /debug
I also use sysprep creator & executor...where I join the machine to the domain. Is that my issue? That the computer needs to be named before it's joined to the domain? I've tried the naming task as a mid level and post install. 
Any help would be great! 
2 Comments   [ + ] Show comments


  • Do not Join to a domain via answer file.

    Is not good for the deployment to get hit with your GPO policies during the Deployment tasks.


  • I have an image that is not joined to the domain, and a setcomputername task with the SetComputerName_x64.exe & namefile.txt zipped up. I call the following command: SetComputerName_x64.exe /rdf:cakname.txt /dfk:$Mac /debug

    This is set as a post install task, but it's not finding any of the computer information. I can see that when it goes through the debug. Should this be a mid level task? I've tried that too, but it hasn't worked yet. I used to use this task/process to name computers 5 years ago, but now it's just not working...thoughts?
    • Set computer name is a mid level task, the name must be changed before Windows reads the unattend.xml file, Mid Level

Be the first to answer this question

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


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