@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!
Thank you for the assistance. This issue was resolved. I’m not sure how to mark this as resolved though.
@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!