Add Wifi Mac Adress to existing laptop
-
@george1421 Man I wish I would have known number 3 for when I was doing the Host Kernel Args… I will have to keep it in mind for next time I run into that.
Just out of curiosity, can you have more than one argument?
-
@adukes40 yes you can have more than one. Just keep the kernel parameters stuck together
pci=noacpi
and then a space between the kernel parameterspci=noacpi video=vga magic=tom
and so on. -
@george1421 Good to know, thanks George.
-
@george1421 Hi, sorry for late response.
1- If I perform “hardware inventory” task on a laptop, no change, only LAN MAC address appears
2- for managing printer, maybe fog client uses name, but I thought it was based on MAC address, to confirm…
3- adding PCI=noacpi in global FOG_KERNEL_ARGS works (I can perform a quick registration on host after deletion) but I still have no other mac address…For other laptops, I just add LAN Mac address and and deploying image, fog client retrieve other MAC addresses and add them (pending macs in report management)
If someone has solution to add these others mac addresses to the host, it will be nice
-
@Matthieu-Jacquart Now that I have the luxury of time to think about it, the FOS Engine (linux OS) doesn’t support/have the wireless drivers installed. So of course you will not see the mac address So your inventory either at first or later will not register the mac address. But adding the mac address may not matter for snapin or printer deployment since the device should be referenced by name or host ID. I “think” the mac address is only used during pxe booting to help identify the device.
I would be interested to know your success/failure on this, because I could be wrong too…
-
@george1421 Indeed you’re absolutely right, I’ve just tested and fog client uses name and not mac address, so printer are well deployed even if only LAN mac address is in fog management.
So my problem is solved even if I don’t know why other mac addresses don’t appear in pending mac… -
@Matthieu-Jacquart Wonderful that it works by name. That will save a lot of admin pain not having to manage wireless mac addresses too.
I may not have explained it well before. The wireless mac addresses won’t be recorded by the FOG linux OS [FOS] that runs on the target computer because that version of linux doesn’t have the drivers required to see almost all wireless adapters. Without these drivers the wireless adapter is invisible.
-
@george1421 Yes I understood the last part with absence of wireless drier in FOS, but on my other laptops fog client send other mac addresses to the console, so I have them in pending mac and after approval they are added to the host… But it’s not a big deal !
-
@Matthieu-Jacquart is host register enabled? This is the module that deals with Mac address associations. Of course others are working fine which might just mean the client isn’t seeing the other Macs for whatever reason.
-
@Tom-Elliott Yes hosst register is enable for all hosts… As you said, I suppose for any reason Fog client can’t see other mac addresses, but finally it’s not important !
Can it be due to pci=noacpi parameter ?