Belkin USB-C to Ethernet Adapter with new MacBook Pro with TouchBar

endor-moon
Contributor II

Hi Folks, I am testing bare metal imaging with Casper on the new MacBook Pro using NetBoot via the Belkin USB-C to Ethernet Adapter that is sold by Apple. Imaging works fine, but sometimes during the Setup Assistant, the presence of Ethernet isn't recognized. I was wondering if I need to run a script at postinstall time to ensure the Belkin adapter is discovered and enabled. Any thoughts?

I'm testing a basic Sierra image with nothing on it but Microsoft Office 2016. There is a hidden admin account and we are forcing setup of a new account on that third boot. However, Office doesn't get activated and I am wondering if it is because the network connection is down after imaging until that first user account is created and logged in.

Imaging log:

Initializing Imaging Process...
Mounting smb://*******/casper...
Preparing disk for block copy...
Performing Block Copy of osx_updated_170330-10.12.4-16E195.hfs.dmg...
Cleaning up after block copy...
Setting computer name to "MBProTouchBar15"...
Creating /private/etc/jamf.conf...
Creating /usr/local/bin/jamf...
Creating jamfHelper...
Flagging Apple's Setup Assistant to show at reboot...
Creating First Run Enroll Script...
Creating First Run Post Install Script...
Adding line to Fix ByHost Files...
Adding line to Create user imagemaster...
Adding line for installing Microsoft_Office_2016_Volume_Installer.pkg...
Copying Microsoft_Office_2016_Volume_Installer.pkg to FirstRun...
Ensuring system files are hidden...
Unmounting Distribution Point...
Blessing System...

Imaging scripts log:

Enroll 2017-04-21 07:01:39: Started enroll script
PostInstall 2017-04-21 07:01:39: Started postinstall script
Enroll 2017-04-21 07:01:39: Checking for the lock file
PostInstall 2017-04-21 07:01:39: Displaying lock screen
Enroll 2017-04-21 07:01:39: Writing lock file
Enroll 2017-04-21 07:01:40: Setting computer name
Enroll 2017-04-21 07:01:41: Checking JSS connection
PostInstall 2017-04-21 07:01:52: Sleeping for 3 seconds
PostInstall 2017-04-21 07:01:55: Fixing ByHost files
PostInstall 2017-04-21 07:01:58: Creating user imagemasterwithout an invitation
PostInstall 2017-04-21 07:02:04: Installing package Microsoft_Office_2016_Volume_Installer.pkg
Enroll 2017-04-21 07:02:15: Removing lock file
Enroll 2017-04-21 07:02:25: Exiting enroll script
PostInstall 2017-04-21 07:02:53: Deleting temporary user
PostInstall 2017-04-21 07:02:53: Removing postinstall directory and launch daemon
PostInstall 2017-04-21 07:02:53: Waiting for the enroll command to complete
PostInstall 2017-04-21 07:02:53: Done waiting
PostInstall 2017-04-21 07:02:53: Deleting temporary user account
PostInstall 2017-04-21 07:02:55: Rebooting immediately
Enroll 2017-04-21 07:03:11: Started enroll script
Enroll 2017-04-21 07:03:11: Checking for the lock file
Enroll 2017-04-21 07:03:11: Writing lock file
Enroll 2017-04-21 07:03:12: Setting computer name
Enroll 2017-04-21 07:03:14: Checking JSS connection
Enroll 2017-04-21 07:03:43: Removing lock file
Enroll 2017-04-21 07:03:53: Exiting enroll script
Enroll 2017-04-21 07:05:53: Started enroll script
Enroll 2017-04-21 07:05:53: Checking for the lock file
Enroll 2017-04-21 07:05:53: Writing lock file
Enroll 2017-04-21 07:05:53: Setting computer name
Enroll 2017-04-21 07:05:54: Checking JSS connection
Enroll 2017-04-21 07:06:21: Removing lock file
Enroll 2017-04-21 07:06:31: Exiting enroll script
Enroll 2017-04-21 07:08:31: Started enroll script
Enroll 2017-04-21 07:08:31: Checking for the lock file
Enroll 2017-04-21 07:08:31: Writing lock file
Enroll 2017-04-21 07:08:31: Setting computer name
Enroll 2017-04-21 07:08:32: Checking JSS connection
Enroll 2017-04-21 07:08:59: Removing lock file
Enroll 2017-04-21 07:09:09: Exiting enroll script
Enroll 2017-04-21 07:11:09: Started enroll script
Enroll 2017-04-21 07:11:09: Checking for the lock file
Enroll 2017-04-21 07:11:09: Writing lock file
Enroll 2017-04-21 07:11:09: Setting computer name
Enroll 2017-04-21 07:11:10: Checking JSS connection
Enroll 2017-04-21 07:11:37: Removing lock file
Enroll 2017-04-21 07:11:47: Exiting enroll script
Enroll 2017-04-21 07:13:47: Started enroll script
Enroll 2017-04-21 07:13:47: Checking for the lock file
Enroll 2017-04-21 07:13:47: Writing lock file
Enroll 2017-04-21 07:13:47: Setting computer name
Enroll 2017-04-21 07:13:49: Checking JSS connection
Enroll 2017-04-21 07:14:15: Removing lock file
Enroll 2017-04-21 07:14:25: Exiting enroll script
Enroll 2017-04-21 10:15:14: Started enroll script
Enroll 2017-04-21 10:15:14: Checking for the lock file
Enroll 2017-04-21 10:15:14: Writing lock file
Enroll 2017-04-21 10:15:14: Setting computer name
Enroll 2017-04-21 10:15:16: Checking JSS connection
Enroll 2017-04-21 10:15:38: JSS connection is working
Enroll 2017-04-21 10:15:38: No invitation.
Enroll 2017-04-21 10:15:38: Doing trustJSS.
Enroll 2017-04-21 10:15:40: Doing manage.
Enroll 2017-04-21 10:15:43: Doing recon.
Enroll 2017-04-21 10:15:45: Deleting Enroll directory and launch daemon for enroll, which also removes the lock file
1 ACCEPTED SOLUTION

endor-moon
Contributor II

I used my post-install script to run the VL serializer on the first boot after imaging is done. Works fine now.

/usr/sbin/installer -pkg /Library/AdminToolBox/Microsoft_Office_2016_VL_Serializer_2.0.pkg -target /

View solution in original post

3 REPLIES 3

brushj
New Contributor III

Are you running the Volume Serializer package in there at any point? It is a totally separate package from the 2016 install. We usually do that install after first boot.

endor-moon
Contributor II

In the workflow above, I was not running the VL Serializer, no, I was just doing the original installer. I normally do that, then the current update, and finish off with the VL Serializer but it does not license the product in any case; I always have to run the VL serializer manually and then it works.

Once I have all of this working I will split it into to configurations, one for "thin" imaging and the other for bare metal.

endor-moon
Contributor II

I used my post-install script to run the VL serializer on the first boot after imaging is done. Works fine now.

/usr/sbin/installer -pkg /Library/AdminToolBox/Microsoft_Office_2016_VL_Serializer_2.0.pkg -target /

View solution in original post