@Tom-Elliott Thanks Tom, yes that looks to have sorted it out thankyou…

I think this is an issue envolving this kind of nic hardware (Intel I226-V). I opened an issue (18125) where I have some appliances for pfsense, they have got four NICs with this kind of hardware, and we are not getting successfull to deploy an image because it’s not processing authentication, even typíng correct user and password.

My recommendation is as always when jumping OS versions like this. Spin up a new FOG server and then migrate your database and raw files. This does two things. First it gives you a clean OS and a clean install of FOG to build from. Second, if something happens with your upgrade your fog imaging is down. Yes I know you can always restore from a snapshot, but that still doesn’t address the first issue of having a clean OS (not upgraded).

Here is the process to migrate your fog install to a new server. https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG The only gotcha is don’t change the IP address of your new FOG server after FOG is installed (you can but its a bit of a pain to do so). With your new FOG server at a new IP address you will also need to update dhcp to point to your new fog server. On a plus note you can always fail back to your old fog server by just resetting dhcp back to your old fog server’s IP address.

Super that did work… thanks guys

@gordon-taylor The binary might have changes (refind.efi) though we don’t know what changed (we don’t write the refind program stuff.)

I’ve made scan_delay = 0 the default when 1.5.1 releases.

@Tom-Elliott Thanks i did svn up and then re-installed and it looks like its all good again 🙂

There’s ways to assign different .pxe boots to different clients. Sadly my google-fu is lacking right now but bringing VLANs into it is kind of a mess.