I not how understand to make ? (beginner question)
-
Server
- FOG Version: 1.3.5
- OS: Debian
Client
- Service Version: Imac 2K13
- OS: MAC OS
Description
Hello everyone, it’s me again ._. ^^!
(Sorry for my bad english)
FOG is very great, it’s work with Windows, so big thank’s to all programmer !But… I have a little problem with FOG on MAC, i try to add MAC image to fog server and deploy but… I don’t understand this tutorial https://wiki.fogproject.org/wiki/index.php?title=FOG_on_a_MAC if somebody can help me ?!
Thank’s all for u reading !
(Si un français passe par là, et qu’il peut m’aider je le remercie !)
-
I’m sorry I can’t help you understand the MAC and FOG, I have seen a MAC in a picture book before. (Actually I have not touched a MAC since 1995)
I can tell you that MACs use a different pxe boot method than IBM PCs. MACs use something called netboot (not pxe boot). Netboot (from BSD Unix) requires more information in dhcp than PXE boot.
One of the FOG developers @Sebastian-Roth has personal experience with network booting MACs in a previous job. He may be able to provide some additional info. I did find one of his posts with a bit more information: https://forums.fogproject.org/topic/9189/macpro6-1-pxe-boot/20
You can also search in google “netboot macbook” in your native language to see if you can find specific instructions. It is possible to boot and image with FOG once you can get the target MAC to network boot.
-
Is FOG doing DHCP? The FOG installer sets up DHCP on the FOG server (if you choose to use it) in such a way that it already supports netbooting Macs. I’m pretty sure that Windows DHCP is incapable of doing the checks that ISC-DHCP is setup to do for Macs on the FOG server.
-
No, FOG isn’t my DHCP I use Windows DHCP, so it’s impossible to work with Mac…?
-
@Warget Are your MAC clients on the same vlan (subnet) as your dhcp server? I found a solution that appears to work (via google) if you have 2 vlans one for your servers and one for your client computers. This deals with using the dhcp-helper (dhcp-relay) service already on your router between the vlans to help with the setup.
ref: https://groups.google.com/forum/#!topic/macenterprise/N1241W7fImQ
Please understand this isn’t a fog issue yet, but rather an Mac issue because of they way they netboot. Once we can get the iPXE boot kernel to the Mac then FOG can take over.
-
@george1421 I am sorry to say this but I doubt that you can make it work by simply putting in another layer (VLAN) here. The link you posted says it:
The workstation gets an IP from Windows, then broadcasts BSDP packets, the helper forwards these to the MacOS server, it responds via the router, machine boots.
So for this to work you need a MacOS server (or other BSDP capable server) as well. As far as I know you cannot make a Mac-Client netboot when you only have a Windows DHCP server at hand.
-
@Sebastian-Roth If I understand the post correctly (and where I’m thinking). If you have your clients on a different vlan with a centralized ms windows dhcp server (the solution has nothing to do with vlan, only the fact that if you have vlans then you have subnets, and if you have subnets there may be a route in place using a dhcp helper service). You will on your router probably be running a dhcp helper service. If I understand the post correctly, you will add the BSPD capable dhcp server to the end of the dhcp helper server list. What will happen is the first server in the list will get notified of the dhcp request, but all other servers in the list will get notified too of the dhcp request so they are aware of the dhcp request.
We would do this same thing if we had a ProxyDHCP server in the mix, where the primary dhcp server could not supply the next server and boot file parameters.
SOooooo, the idea is to do the same thing in this situation too. But in stead of dnsmasq being the last dhcp server in the helper list we place the ICS dhcp server running on FOG (which is netboot capable according to Wayne). In the case of the post, it recommended that you don’t assign an address pool to this server so the target will only get an IP address from the primary dhcp server, but the ics server running on the FOG server will fill in the netboot stuff.
Understand this is only a theory in my mixed up brain. I don’t have any of the hardware to prove if it works or not. It sounds like it should, but…
-
@george1421 said in I not how understand to make ? (beginner question):
I’m sorry I can’t help you understand the MAC and FOG, I have seen a MAC in a picture book before. (Actually I have not touched a MAC since 1995)
I can tell you that MACs use a different pxe boot method than IBM PCs. MACs use something called netboot (not pxe boot). Netboot (from BSD Unix) requires more information in dhcp than PXE boot.
One of the FOG developers @Sebastian-Roth has personal experience with network booting MACs in a previous job. He may be able to provide some additional info. I did find one of his posts with a bit more information: https://forums.fogproject.org/topic/9189/macpro6-1-pxe-boot/20
You can also search in google “netboot macbook” in your native language to see if you can find specific instructions. It is possible to boot and image with FOG once you can get the target MAC to network boot.
Just hold down N during the boot. The Mac will do the rest of the work. (Apple certified Mac Technician)
-
@TTellez Excellent info to know.
If I may ask you, is a netboot server required for PXE booting FOG or have you not tested that function?
-
@george1421 in laymans terms, if you have something pushing DHCP to the device and a server delivering data, the netboot SHOULD pick it right up and the capture or deploy function should work. However, I have never actually imaged with Fog on a mac, more just delivering the “how to netboot” answer…
-
@Warget said in I not how understand to make ? (beginner question):
Remercions tout pour u lire!
Yeha it’s me again, thank’s for ur help ! I use bless --netboot for boot via Ipxe it’s work but… I have only one more problem… When i download Fog client on mac he say : “Pinning FOG Project (fail)”
Realy thank’s ! -
@Warget What I would recommend that you create a new thread for this one. Make sure you title it correctly for the proper group to respond. This is a client issue not FOG server.