Computer name change isn't working about imagr

[clburlison]

Hey @efranklin, I haven't imaged a computer since June but last time I used the same workflow you are referring to without error. The firstboot log is located at /var/log/first-boot.log.

[grahamgilbert]

What name are you using? The script to set the name is literally

#!/bin/bash

NAME="{{computer_name}}"

/usr/sbin/scutil --set ComputerName "$NAME"
/usr/sbin/scutil --set HostName "$NAME"
/usr/sbin/scutil --set LocalHostName "$NAME"

So it's possible we need to do some more parsing to eliminate invalid names, but that remains to be seen

I just Imaged a basic VM (10.10.4, clear reg package and an admin user) and it worked as expected

As Clayton said, the logs will be helpful.

[efranklin]

I won't be back to that location until Friday and I'll get you the logs then. This is one of the names I've tried to use: AB355-180180

[efranklin]

I figured out why it wasn't working. I initially put the "computer_name" script as the first item in the "components" array. I moved it after the "image" script and it worked fine. Is this expected behavior?

Also, the "computer_name" script doesn't show in the "first-boot.log" file.

[grahamgilbert]

Yes, expected behaviour. Workflow components are applied in the order they are specified in the plist. The only reason you are asked for a name prior to imaging is I didn't want to have to wait around!

Graham Gilbert
Sent from my iPhone

On 30 Jul 2015, at 18:57, efranklin [email protected] wrote:

I figured out why it wasn't working. I initially put the "computer_name" script as the first item in the "components" array. I moved it after the "image" script and it worked fine. Is this expected behavior?

Also, the "computer_name" script doesn't show in the "first-boot.log" file.

—
Reply to this email directly or view it on GitHub.

[efranklin]

Good to know. Thank you for your help.