@Tom-Elliott Just wondering if I could have your input here.

@AlexisPHC said in Use serial number as hostname in Fog:

did you ever get round to writing a guide for this?

Yes. I think the previous comment to your post referenced the files.

https://forums.fogproject.org/topic/14278/creating-custom-hostname-default-for-fog-man-reg?_=1762381023512

the file fog.customhostname uses a linux command dmidecode to extract the serial number from the smbios. And the rest of the ‘hack’ will pump that name into the full registration files. When I wrote that script I worked for a company that had a composite host name with the site code, a hardware type and then the dell asset tag appended onto the end. That is what this tutorial shows.

Now Tom mentioned that {SYSSERIAL} in the quick registration field works too. I wasn’t aware of that feature, it must be new. I know FOG version 0.30 had that feature but it was removed when FOG 1.x was released. If its back, that’s great!! that makes my script(s) unnecessary.

I tried reinstalling the Capone plugin, but that didn’t work.

I checked my other machines that show the fog.capone option and I manually added it in using the New iPXE Menu Entry option with the same values as my other machines. I haven’t tested if this is the solution yet. Here’s a screenshot of my values:
d4f5f292-a652-4796-ad66-2531d9920b01-image.png

Finally found out why I couldn’t auth over 636, I needed to add my domain’s CA cert to the FOG server’s root cert store. Once I did that I can now use my AD creds over 636 on the web UI and iPXE menu items.

@AlexisPHC said in Issues with Windows DHCP Server:

because we run them in HA mode

but there doesn’t seem to be another DHCP server present

My interpretation of these two statements sounds in opposition.

If you are running windows server in HA or failover mode, make sure that both dhcp servers have the dhcp boot options configured. If I remember right these settings are not copied over between the dhcp HA nodes. Understand this might have changed with later releases of dhcp server but with 2016 the pxe boot stuff needed to be set on each node individually.

@Tom-Elliott latest pull resolved the issue. Appreciate your help on this!

@88fingerslukee Thank you, I promise I will try your project and leave a feedback.

@Tom-Elliott no stress, with so many posts it’s normal to miss some 😉

@youzersef What if your router providing next server is pfsense.

What needs to be changed in pfsense? My current settings are that of fog.

Pfsense : 10.22.24.1 : (controls DHCP, next server, etc)
Fog 10.22.24.5 : (Working flawless)
iVentoy : 10.22.24.13

Everything I try is sending client back to pfsense, and then errors because it’s getting the boot file for fog, when it’s expecting iventoy_loader_16000

Thanks ! Time to get this project wrapped up 🙂

@Tom-Elliott Thank you. Logging out with 1.5.10.1730 works properly.

@DanCan Hi This is currently a known issue on some motherboards. Honestly not sure what is causing this to happen. I am working on a fix to this issue just haven’t had too much time lately.

@sega said in FOG Multicast on different VLANs:

Is there something that I can look up, to see where the problem is?

Well your router supporting PIM is a good sign. Some routers have a service called igmp proxy or igmp relay, or even igmp snooping (you will find this more on switches, but check). This service typically has a number of interfaces to listen on and then a master interface where your multicast source lives. Its job is to relay the multicast requests to the proper interface.

PIM has two modes sparse and dense, that may be just for switches, I don’t remember. Sparse mode only sends the multicast traffic to the subscriber’s port, where dense just blasts out the muticast to all ports. You want sparse mode if possible, that way only the ports with a multcast receiver will see the traffic and not flood your network.

@george1421 Thanks, George.