MAC Address Questions
-
Running Version 1.4.0-RC-14
SVN Revision: 6069
Client: 0.11.12I have configured all my hosts with their Ethernet MAC address in our FOG server. I have not configured their Wi-Fi MAC as I do not know of a way to PXE boot on Wi-Fi given my current hardware. But much to my horror, the FOG client will task restart the host when connected to Wi-Fi, which ends up in a boot-loop and a very concerned end-user.
What are your thoughts on this matter?
-
Ignore the wifi mac from client operations?
-
@Tom-Elliott Is that an option? If so how is it implemented? I suspect the Wi-Fi Mac’s are what keeps annihilating my pending MAC’s list.
-
@AngryScientist On the host page, there are checkboxes on the right next to each MAC to exclude them.
-
@Quazz Would the exclude prevent snapin deployments on Wi-Fi? If so that would be crippling.
-
@AngryScientist There are two checkboxes, one excludes only for imaging, the other for all I believe. Not sure if that works for you.
-
Yes it would prevent any client actions from happening purely over WiFi. Understand though that this isn’t a 100% perfect system. There are pro’s and con’s to everything you need/do and FOG is not any better with these kinds of things. It’s not granular enough to know certain modules aren’t to be used with the mac address. Sorry.
-
@Tom-Elliott Yes Tom, I am in no way demanding, I am fully aware of the volunteer nature of FOG. I am merely determining the scope of the current functionality, as the Wiki, which is just as volunteer maintained, is somewhat behind the current release. This is one of the times where my understanding of system features and internal mechanics did not match up to the production environment.
-
@AngryScientist Please don’t take my information there to be offensive. I’m just informing. I’m not that skilled still so I understand the pitfalls, I even understand what’s potentially wanted/needed. I don’t understand how to provide it yet though :(.
-
@AngryScientist said in MAC Address Questions:
But much to my horror, the FOG client will task restart the host when connected to Wi-Fi, which ends up in a boot-loop and a very concerned end-user.
So to avoid this, just don’t create imaging tasks for laptops unless they are hooked up to the network with a patch cable, and leave all your MACs enabled so you can still use snapins.
I don’t know what your setup looks like or how your operations go where you are, but the way I did laptops in great numbers was I hooked up an 8 port 1Gbps switch on a big table, hooked that up to the building network, setup myself some power strips and some laptop adapters, and I used my pre-made FOG Groups to queue all of the turned-off laptops for unicast imaging. Then I hooked up 8 at a time and powered them on. When one completed imaging & domain joining & snapins, I shut it down afterwards and hooked up another.