AutoDMG and WiFi Configuration

Hey Scott,

Is it possible to post a secure portion of the script to see if there is something that can be modified to ensure the wifi interface is being detected? You could also try putting a verbose output log into the script to see if that can point you to the reason why your script isn't enabling Wifi on the targeted device.

This should create a script log after it runs:

#!/bin/sh -vx 

exec > /path/to/mylog.log 2>&1

To my knowledge AutoDMG wouldn't really have anything to do with the Wifi being enabled or not. I suspect it's a script/OS problem.

Hope this helps.

Thanks for your quick response. Below is a copy of the script I'm using with the password changed. I left special characters in this replacement password with escapes because my real password contains a special character.

I do think it's important to note that after the image runs if I login and run the exact same script manually it works just fine.

I'm going to try adding the verbose logging at your suggestion and I'll be back with the results.

Something I also forgot to mention that is odd. After imaging with Casper Imaging and rebooting (a couple times for testing) and having it never join the WiFi I booted to the Recovery partition and it connected to the WiFi configured in the script. That confused me quite a bit.

#!/bin/sh

# Determines which network interface is the the Wi-Fi radio. 
wifi_device=$(/usr/sbin/networksetup -listallhardwareports | awk '/^Hardware Port: (Wi-Fi|AirPort)/,/^Ethernet Address/' | head -2 | tail -1 | cut -c 9-)

# Feedback for the log file.
echo "Setting airport SSID to myssid."

# Sets the Wi-Fi network to the defined network name and password.
/usr/sbin/networksetup -setairportnetwork "$wifi_device" "myssid" "$omeP@$sword"

So what happens if you just run that script on the newly-imaged Mac - does it work?
You're sure that you made no other changes to the Configuration other than choosing the new AutoDMG?

How exactly are you running these scripts? Are they part of Casper Imaging? Or are you running it in a package that you add AutoDMG to create a custom base OS?

Also what happens if you run that script manually on a 10.11.2 computer? In terminal, do:
sh -x /path/to/script.sh

Yes, if I run the script on any 10.11.2 Mac that I can get logged into it works.

I added the scripts through Casper and they are part of the configuration and seen in Casper Imaging. I didn't add anything or make any changes to the DMG produced by AutoDMG.

I made the changes to the script to get a verbose output. I imaged a test machine, but here is the problem; the hidden user Casper that is configured to be created by Casper Imaging as part of the configuration isn't created. So I have no way to login to the machine after it images and reboots. This user is created just fine if the only change I make to the configuration is to uncheck Base10.11.2.dmg and check Base10.11.1.dmg in the configuration. Everything else stays the same.

I suspect since the Casper hidden, admin user is never created it can't run the wireless (or any other script) successfully. Is this plausible? As I mentioned earlier if when rebooting after the imaging process I connect a thunderbolt network adapter it will create the Casper user, talk to the JSS and do further configuration, but it never connects to WiFi. It will only do this if I connect the wired network before the first boot. If I tried to reboot after that and connect it to a wired connection it doesn't work.

You need to check the log. Target Disk Mode that machine to your computer and look at the logs. Don't plug in the Thunderbolt Ethernet adapter. You obviously want to see why exactly that command is failing.

I just connected to a newly imaged machine with Target Mode to check the log and the output of the networksetup command was "All Wi-Fi network services are disabled".

Do I need to start something or check for something running in the script? Should i put a short delay in the beginning of the script to make sure it waits for a service to start?

Ahh - I saw a thread the other day where someone found 10.11.2 was doing that.
Let me search...

OK, my memory was off, but this is similar to what you're seeing...what version of JSS are you running?

Wifi disabled...

JSS is 9.8.1

Tried adding "sleep 5" in the script to delay it running...no change.

Scott,

Do you have this script priority in the JSS or Casper Imaging set to run "At Reboot" by chance?

Yes, all 3 scripts (including wireless configuration) are set to run "At Reboot".

In Casper Imaging under the Network tab can we ensure that the Connection Type is set to Airport and try again? If you're not seeing these options, click "Show Custom" in the upper left corner of the Casper Imaging pane.

That's awesome Scott, glad you got it working!

Thanks for everyone's help. I wouldn't have tracked it down without the assistance.

I know with our Active Directory binding we have to make sure we run the script to set the network time and run the sync because if there is a time offset of more then 4 minutes between the computer and the Active Directory server then the binding fails.

@sapalmerBCS What does the script look like with the sleep command in it?

#!/bin/sh -vx 

exec > /Users/WirelessSetup.log 2>&1

#Wait 25 seconds
sleep 25

# Determines which network interface is the the Wi-Fi radio. 
wifi_device=$(/usr/sbin/networksetup -listallhardwareports | awk '/^Hardware Port: (Wi-Fi|AirPort)/,/^Ethernet Address/' | head -2 | tail -1 | cut -c 9-)

# Feedback for the log file.
echo "Setting airport SSID to ssid."

# Sets the Wi-Fi network to the defined network name and password.
/usr/sbin/networksetup -setairportnetwork "$wifi_device" "ssid" "password"