@fernando-gietz I feel foolish now. This taught me the lesson that I shouldn’t change multiple variables when trying to troubleshoot an issue.

Here is a screen shot of my working config:
0_1529084567169_fogworks.PNG

I think I had an incorrect group search DN set. When I put the correct DN I also messed around with the Group Member Attribute. I changed it back to sAMAccountName and presto! Thanks for everything boys!

Thanks I figured as much but was wondering why my storage nodes only had minimal traffic between them even though i had re-uploaded an image.

@george1421 Just went through the UBNT thread, that appears to be working! One thing, in case others come across this, that tripped me up was in the command there are " written out. At first, I thought this was something to do with the character escaping on the forums but it is not, you literally need the command as follows:

set subnet-parameters "filename "ipxe.efi";"

You can also do this via the Config Tree in the GUI, just copy everything between the first and last double quotes and paste into the subnet-parameters section of the subnet.

@george1421 I appreciate your assistance here! I guess I will be going to Ubiquiti to see if I can find/file a bug report to fix that up.

[Edit] Not sure why, but I can’t seem to mark your post as the right answer… I’ve marked mine summerizing everything instead. Have an up-vote though 🙂

Follow up documentation from UBNT Help

Notes
In the example above the custom option string requires quotes to be injected directly into the dhcpd.conf. As literal quotes are not allowed in the cli command we replace our quotes with the special entity format for a quote " this will be translated back to a literal quote when building the dhcpd.conf

While I don’t use IE, can you white list the FOG URL in your IE pop-up blocker? I would think there should be a way to allow pop-ups from specific web sites since many responsive web sites use these type of pop-ups.

Ok, found the problem. I didn’t realize that one of the other guys had setup the 2 boot options in the Superscope options and I was setting them in the Scope. This has been sorted.

Sorry to waste your time and thank you for the quick reply.

@tom-elliott I am willing to try I am already at 1.5.3 on SL69…

so writing with george1421… I issued those commands.:

git clone https://github.com/FOGProject/fogproject.git
cd fogproject
git checkout working
cd bin
[root@fog:/opt/fogproject/bin ]% ./installfog.sh
installing…

Yes. it is working !
file /etc/httpd/conf.d/fog.conf was rewritten correctly.

then I switched back to the master
git checkout master
thank you all.

@quinniedid Sure!

Base steps were I created a new image in GPT format.

Afterwards, on the FOG server itself I edited the config file located at /var/www/fog/service/ipxe/refind.conf

Below are what I have the values at. This was after some troubleshooting so some may be back to their default values.

timeout -1
scanfor internal,external (I also have both lines commented out at the moment)
uefi_deep_legacy_scan is uncommented
scan_delay 5

From my memory that is all that is changed. After the imaging is completed in UEFI, it will boot straight to the OS instead of pushing itself through FOG and/or rEFInd.

Hope this works for you!

I’d recommend running nothing except FOG on your FOG server. We’re not able to troubleshoot integration with other 3rd party software, that’s on you.

Yes, I also think that this stick is faulty. I posted this question here hoping that it was not the case.

Anyway, thank you very much for the answers guys.

I’ll just use this PC for some other project. Thank you all again.

Bye

@george1421 Your suggestion worked! Thank you very much.

@george1421 George, thank you. The issue has actually been resolved. For some reason, checking what was using .1.25 did not cross my mind. As soon as I did a scan of our network, I found that someone had booted up our old imaging server which was located at 1.25. Once I turned it back off, Fog returned back to normal.

Issue has been resolved!

I have 1.5.2 version

@sebastian-roth it’s working now. I had the wrong bootfile Name in option 67 on my DHCP server.

@sebastian-roth I disabled legacy. It works. thanks.

@sebastian-roth Thanks Sebastian!

Unset the dhcp option 60. If you have a proxy dhcp server it sets dhcp option 60 to indicate it exists to the client. Your error message 4011 is caused by dhcp option 60 being set without having a proxy dhcp server running.

@szeraax Open a new thread up the next time you want to do something to get some suggestions. This is a benefit of a project with an active community.

@tom-elliott Awesome, working like a charm, thank you.

This is now working thanks to @george1421’s help. What happend was that I had two versions of dnsmasq installed causing this issue. I was able to remove the 2.75 version that came with the OS and recompile and reinstall 2.76. Now everything is working as expected.

@drapalsfj Once you have 2.76 then you need to use my config file for 2.76 or later. Once you have that you can pxe boot both firmware types. But if you are installing 2012 dhcp server that is a better longer term solution. If you need to circle back to dnsmasq let me know and we can finish your setup.