FOG on a MAC
Contents
Server Install
It has been reported that the FOG server will run on a MAC without any issues.
Client Tutorial
Netbooting Apple Mac
Intel Macintoshs all use (U)EFI - where common PCs have a BIOS - to bootstrap and to some extent talk to hardware. Several different ways exist to make those Macs boot from network. Depending on your preference and setup choose whichever suites you.
Using stones (aka startup keys)
On startup (when you hear the sound, before Apple sign comes up) you can hold down different keys to make the Mac boot from network. Apple uses a kind of special protocol called BSDP which is partly similar to the well known DHCP protocol. But there is more to it. Find a detailed explanation here if you want to dig into it.
ISC DHCP Server
To make a Mac client boot from network you need to extend your DHCP server configuration. Add the following option to your subnet section:
subnet ... {
authoritative;
...
}
To issue special answers to Mac clients you also need to define a class:
class "Apple-Intel-Netboot" {
match if substring (option vendor-class-identifier, 0, 14) = "AAPLBSDPC/i386";
option dhcp-parameter-request-list 1,3,17,43,60;
if (option dhcp-message-type = 1) {
option vendor-class-identifier "AAPLBSDPC/i386";
option vendor-encapsulated-options 08:04:81:00:00:67;
}
filename "ipxe.efi";
next-server x.x.x.x;
}
Restart the DHCP server after saving the configuration. Then booting up your Mac client hold down the 'n' key and you will see a globe spinning instead of the usual apple sign. The Mac requests an IP from the DHCP server which advises it to load iPXE via TFTP and boot that up.
fancy
Newer Macs also have a fancy version of network booting. Hold down the 'alt' key and you will see different disks and network images to boot from. To make this work you need to modify the class definition:
class "Apple-Intel-Netboot" {
match if substring (option vendor-class-identifier, 0, 14) = "AAPLBSDPC/i386";
option dhcp-parameter-request-list 1,3,17,43,60;
if (option dhcp-message-type = 8) {
option vendor-class-identifier "AAPLBSDPC";
if (substring(option vendor-encapsulated-options, 0, 3) = 01:01:01) {
# BSDP List
option vendor-encapsulated-options 01:01:01:04:02:80:00:07:04:81:00:05:2a:09:0D:81:00:05:2a:08:69:50:58:45:2d:46:4f:47;
}
elsif (substring(option vendor-encapsulated-options, 0, 3) = 01:01:02) {
# BSDP Select
option vendor-encapsulated-options 01:01:02:08:04:81:00:05:2a:82:0a:4e:65:74:42:6f:6f:74:30:30:31;
filename "ipxe.efi";
next-server 192.168.11.11;
}
}
}
For more information about the rows of hex numbers see this excellent example.
DNSmasq
So far untested but seems pretty straight forward: http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2010q1/003638.html Edit /etc/dnsmasq.conf and add the following lines:
dhcp-boot=net:#apple-boot,ipxe.efi,,<your-tftp-server-ip> dhcp-vendorclass=apple-boot,AAPLBSDPC/i386 dhcp-option-force=net:apple-boot,43,08:04:01:00:0b:7e:82:0a:4e:65:74:42:6f:6f:74:30:30:31 dhcp-option-force=net:apple-boot,60,"AAPLBSDPC/i386"
Restart your DHCP server after the config change and try booting one of your Macintoshs holding down the 'n' key while it comes up. You should see a globe - instead of the apple - on the screen!
This method is called 'Using stones' as people use stones or other similar objects to boot a whole lab full of Mac clients but there are other ways to achieve this too!
Using bless
An Apple Mac can be 'blessed' to boot from whichever source you want via commandline. This setting is saved in NVRAM and not changed by cloning your Macs via FOG. I'd suggest activating SSH on your Macs and use clusterssh to bless all of them without having walk to and login to each and every client.
To 'bless' your Mac turn it on and let it boot up as usual. Login and open the Terminal App and run the following command (use a proper IP instead of x.x.x.x):
sudo bless --netboot --booter tftp://x.x.x.x/ipxe.efi
No special DHCP configuration is needed for this! BUT if your server ip changes for example you'd have to run this command on all your clients again.
Culprits
On some Macmini clients the bless-setting doesn't do the job. Up till now (Sept. 2015) it's still unclear why. Possibly a newer Boot-ROM Firmware version is the issue.
iPXE for Macintosh
As noted earlier there is a fundamental difference between Mac-EFI and PC-BIOS. Not just with configuring network boot but also when it comes to the binary being loaded via TFTP and executed on the client. To make iPXE work on Macs a lot of work has been done in 2014. Check out this thread if you are interested in the details: http://forum.ipxe.org/showthread.php?tid=7323
The mentioned DHCP class should point the client to the correct iPXE binary (ipxe.efi). FOG includes this binary in current SVN development tree or you can download a binary from the repository if you are still using an older version of FOG: https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/
Depending on the hardware you have this might work for you straight away. If not, please get in contact with us on the forums so we can work on it to find a solution!!
Working
Macbook1,1 ...
Macbook6,1 (W89452MK8PX), nVidia NForce MCP79 (PCI ID 10de:0ab0) - http://www.everymac.com/systems/apple/macbook/specs/macbook-core-2-duo-2.26-white-13-polycarbonate-unibody-late-2009-specs.html
Macmini5,2 (C07G3W4ADJD1), Broadcom NetXtreme BCM57765 (PCI ID 14e4:16b4) - http://www.everymac.com/systems/apple/mac_mini/specs/mac-mini-core-i5-2.5-mid-2011-specs.html
Known issues
Macmini6,2 (C07LR0UQDY3H), Broadcom NetXtreme BCM57766 (PCI ID 14e4:1686) - http://www.everymac.com/systems/apple/mac_mini/specs/mac-mini-core-i7-2.6-late-2012-specs.html Is not supported by iPXE yet. A simple patch exists to make it work. We try to get this patch integrated into the official ipxe source tree. Contact us if you have issues with this particular NIC.
