Solved Using FOG client to image MacOS
I’m new to FOG finding it really useful. I’ve been struggling to make an image of MacOS.
My FOG server is already setup on a CentOS machine. The imaging process shows up in Active Tasks, though nothing happens.
I was wondering if anyone could direct me to a link or a blog. I’ve attached a screenshot of the Active Tasks Dashboard.
@quicklet FOG works with PXE booting. Hosts that are scheduled for a task need to PXE boot to run the task. Be aware that Apple changed a couple of things over the last two years that makes imaging of any sort (not just with FOG I mean) almost impossible.
Hi @Sebastian-Roth ,
We already do a lot of cloning manually using the Carbon Copy Cloner App and it works fine.
I now was looking for ways to automate this instead of doing it manually.
Can you refer to any wiki or tutorial on how the PXE boot is done for macs?
@quicklet Which version of Mac OS X do you use?
The wiki article mention is here: https://wiki.fogproject.org/wiki/index.php/FOG_on_a_MAC
@Sebastian-Roth we are using macmini 7,1.
I’ve gone through the wiki. I’m couldn’t find any way the fog server will ping the mac client for taking it’s image. It’s logs show that it’s trying to reach the client. Apart from that, I haven’t been able to find how the fog will contact the host for imaging.
@quicklet Well we do have the fog-client software which you can install on Mac OS X (using Mono for .NET I think). This connects to the FOG server to be noticed about a task to be run and reboot the Mac. BUT this doesn’t solve the initial quest of PXE booting the MacMini to actually reveive the task!
@Sebastian-Roth hmm. So, I need to install the fog-client-software on the mac osx. I’ll try it out. I do not have a phyical access to the mac os machines, only the remote access.
Also, is there anywhere (a wiki, etc) where I could have the steps written for initiating the imaging process for mac?
On a side note, if I’m able to start the imaging successfully I’ll definitely update the said wikis from my end.
Currently, the fogscheduler logs print
[02-19-20 8:09:34 am] * Sending 1 wake on lan request.
[02-19-20 8:09:34 am] * 1 total mac attempting to wake up.
@Sebastian-Roth Is this only related to the macbooks with only USB-C ports? I have fog working (after much trial and error) fine for all of our apple devices up to 2017 model year, but we just started to purchase brand new machines for our staff, and im concerned about not being able to image over the network anymore. I need to buy some USBC to ethernet adapters before I test it, and if I do run into issues ill open a new thread, I just wanted to see if you had any more information before I started troubleshooting this.
@Smoblikat If you have 2017 (guess) or newer Apple started including the T2 chip, which is the security controller for the apple devices. All communications go through this T2 chip. You need a special FOS Linux kernel to get these systems to image correctly.
I would say lets create a new thread and we can discuss in detail there.