@Louis-CSUSA @Sebastian-Roth

I also tried messing with SELinux (setting it to passive/disabled) and the 503 error goes away (like the first time) enabling it back on puts me back at the 503 error.

@Louis-CSUSA
error.log

@Sebastian-Roth

To rule out (my) user error, I reinstalled Fedora 29 client and FOG 1.5.5 again and this time I’m getting a 503 service unavailable error (tried to access it when the installer asks for you to). I’ve reattached the error log with this attempt.

IP is static assigned as 10.51.0.110.

Hello Sebastian,

I did see errors on the error_log file, see attached.error.log

Hi All,

Just did a clean install of Fedora 29 workstation and FOG 1.5.5 and ran into no problems with it, up until the fact that I needed to pull up the management page (<IP>/fog/management/)

Any ideas?

Hello FOG Community,

I’m currently at a school deployment trying to get FOG (fresh install) to work with our Mac fleet. We’re planning on imaging MacBook Airs, MacBook Pros, and iMacs. It’s been a few years since I’ve actively worked with FOG so I’ve set it up using Fedora 28 Workstation and running 1.5.4 on it.

I’ve been trying to search the forums for the best way to pull up the PXE menu. I assume (due to Sierra) that an external USB is the best way to go, but I cannot find any guide/walkthrough using the new version(s).

I’m sorry in advance if this has been covered in another post/thread, just came back to using this (awesome) product.

Thank you guys.

@Sebastian-Roth This would have to be done at a per-machine basis, no?

If so, that wouldn’t work for our large deployments.

@Tom-S Is there a guide somewhere on how to create the FOG USB bootable?

Also, for your Macbook Air, I’m assuming you are using a ThunderBolt Ethernet adapter to image it? If so, how do you keep track of the hosts since the MAC address is based off the adapter and not the machine’s mac?

@Jbob

I’m back at it again! We reimaged our testing unit with El Capitan and we ran into a different snag all-together. With El Cap, they implemented System Integrity Protection (SIP) so our usual Bless commands aren’t working anymore.

I’ve been trying to do research for the past week to figure out how to do vendor-class based DHCP custom settings for the system. It’s a late-2013 iMac (iMac14,1). However I’ve had no success with it thus far. The linked article below is the closest I’ve got to a solution.

https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28r1_and_later.29_DHCP_Policy

Tried “iMac14,1” and “AAPLBSDPC” but neither have worked (so far).

Should I create a different thread for this topic?

@Jbob Since this is our first time doing this, we can reimage this unit again and start from scratch tomorrow. I want to make sure that user-error (on our side) isn’t giving you bad data. We will report back more tomorrow.

Thank you very much @Jbob!