for apple instal Print.Test.Page.OK 3.01

Is there a better way to ensure the network interfaces are set properly for each Mac model and variations of network I'm currently working on a similar solution for our builds.

Networksetup -createlocation Automatic populate Networksetup -createlocation TempLoc populate # Create a temporarily Network location and recreate the Automatic location. Log 'Adjust Network Locations to correctly add network ports' Log 'Begin script 100_resetNetworkLocationAndPorts.sh' LogFile='/private/var/log/OurCompany.log' The script is the first script to run after reboot. I also think it retains the model specific service orders. Instead, I came up with the following script that appears to work and covers if the laptop arrives with either type of removable network adapter.

I was going to create a first boot script that checked for a working network connection or halted until the tech ensured the thunderbolt or usb ethernet adapter was detected and had a valid IP address.

But it appears that it's more likely that with the full screen jamfhelper and/or the temp account that is used to login At Reboot, the Network panel isn't adding the removable network adapter.

But without the working network connection, many systems being deployed to the end user that are not bound to the domain, which then leads to calls to the Help Desk.Īt first, we thought it was because the Mac wasn't obtaining a IP address quick enough post boot. All of the apps and settings are installed perfectly. We've had an on going issue with factory fresh Macs that are netbooted, Casper imaged with a thin configuration, and not having a working network connection after the first reboot.

For apple instal Print.Test.Page.OK 3.01