@george1421 So I figured it out in the BIOS. The Dells are latitude 7370, and the thunderbolt netboot setting was turned off as well as USB network boot. I enabled both of those options and the laptop is now seeing the FOG server. Thank you in advance.

@Sebastian-Roth Thank you for the tips and tricks. So I’ve gotten past the TFTP failures, it’s finding the server now. To answer your question, yes they are on two different subnets. I tried an ethernet to thunderbolt network connection, but the boot up doesn’t try to set up a DHCP address through that network method. It forces me to use a wireless connection, which I’ve set up to be available and connected when I start the boot-up process on the laptop. What I did to resolve the TFTP issue was use the secondary NIC on our Ubuntu server, set the static ip address to match that of the subnet that the laptop is connecting to via WiFi. But now I’m running into an http Timeout, it’s pointing to the primary NIC that I created the server on. Is it possible for FOG to utilize two Ip addresses for web management? I only see the ability to change it to one IP address, but if it can manage multiple addresses on it’s respective NICs, I might just be able to get this Mac fully connected to FOG.

Many thanks again in advance.

@TaTa @Sebastian-Roth Thank you for this help so far. After I attempted the steps above, I receive an error on the laptop:

iPXE 1.0.0+ (356f) – Open Source Network Boot Firmware – http://ipxe.org
Features: DNS FTP HTTP HTTPS iSCSI NFS TFTP SRP VLAN AoE EFI Menu
Configuring (net0 aa:bb:cc:dd:ee:ff)…ok
Received DHCP answer on interface net0
Please enter tftp server: xx.xx.xx.xx (I entered the ip address of our fog server)
tftp://xx.xx.xx.xx/default.ipxe…Connection timed out (http://ipxe.org/4c126092)
Chainloading failed, hit ‘s’ for the iPXE shell; reboot in 10 seconds

I’ve also blessed the laptop before attempting to boot to the EFI USB device, after running csrutil on Recovery-boot startup. Both commands completed successfully when I ran them; so are my next step(s) to try the other *.efi files in the tftpboot directory of the server and re-name them to bootx64.efi?

Thank you all in advance for this help.

@george1421 Yes, thank you george.

Server

• FOG Version: 1.4.4
• OS: Ubuntu 16.04

Client

• Service Version:
• OS: Mac OS X 10.12 Sierra

Description

Hey everyone, I’m new to attempting to boot a Mac to FOG, and eventually capturing the image for deployment. I’ve done it with Windows machines but I understand with Macs that it’s a bit more involved. Would someone be able to point me in the right direction as to the best standard to do this? Thank you very much in advance, we’re in a mixed environment using Windows server 2012 R2 for DHCP and DNS and end users that are Windows 10, 7, and OS X 10.10-.12, but I’m only concerned with Sierra devices.

@george1421 So I figured it out in the BIOS. The Dells are latitude 7370, and the thunderbolt netboot setting was turned off as well as USB network boot. I enabled both of those options and the laptop is now seeing the FOG server. Thank you in advance.

@george1421 Thank you for getting back to me so quickly. I’ll be in at work tomorrow to verify the firmware option for pxe boot, is that option found in the device manager? And to answer the Ethernet question, no these do not have Ethernet ports. I had to use an Ethernet to USB-C Dell adapter to hard wire the device to the network.

Forgot to mention, I’ve set up option 066 to point to the FOG server’s IP address, and option 067 to be ipxe.efi. The Dells are running Windows 10 as well, and have the latest updates run on the would-be image capture device.

Hey everyone,

I’ve used FOG in the past, probably around 5 years ago. Recently we’re moving away from our interim imaging system and I’ve set up another Ubuntu server (16.04) with the latest update of FOG on it. I’m running into an issue though, as the new Dells that we’ve received (I believe Latitude 3570 is what my supervisor ordered) do not have PXE boot under it’s Legacy options in BIOS. I have a windows server 2012 R2 running dhcp and dns, so FOG isn’t managing addresses. Anyone know how I can get this machine to find and connect to FOG on startup to send it’s image? Let me know if there are any other details needed.

Thanks in advance.