@Troye-Johnson I’d wait for 1.5.6 as we have improved things like client communication in the dev-branch a fair bit. Not sure when we get to the next release though.

@Sebastian-Roth thank you for pointing me at the DHCP! I found the problem! All files are fine, but our company DHCP was not! After trying it in a seperated VMware Network it worked like a charm! So all the effort was in vain - i am sorry

We have an old fog running 1.4.4 in our DHCP config for managing the PXE Menu because we are running multiple (i)PXE Services in one subnet. I created a new boot menu item to forward the pxe boot to the new fog server.

like this:

iseq ${net0/mac} a0:36:9f:bd:XX:XX && goto testing || :testing set pxeserver:ipv4 FOG-IP set next-server ${pxeserver} chain tftp://FOG-IP/default.ipxe exit

Got it from here in 2017: https://forums.fogproject.org/topic/9648/add-a-second-pxe-boot-option

Worked fine, until now … And by now, i understand why no certification cmds were availibe because it got stuck in the old fog enviroment. Need sth. to reload the enviroment i think. I will take a look into it to find a way. Maybe i will open a new topic here!

Thank you @Sebastian-Roth for taking the time! Your scrips are fine - it was my fault …

@Sebastian-Roth Awesome, thank you!

Hi Sebastian,
it works thx.
i forget that there was a scheduled reboot 😉
sometimes it is so easy but it costs a lot of time ;))
Thanks 🙂

Hi,
i had the same problem with DELL Precision 3630.
no bootable device was found because the internal PCIe SSD was in Raid 0 mode.
I switched it to non RAID0 an then it works. But pay attention. I had to reinstall the OS.
Hope that helps.
Greets

@bmorine Sorry, I lost track of this in the busy time before X-Mas. I found and fixed this issue in the dev-branch so this will be part of the next release. If you want to use it beforehand feel free to switch to the dev-branch.

@Quazz I do the following:

click Images multicast image give session name client count (12) timeout (0) choose image Start!

The strange thing is, sometimes it reaches the client count. Sometimes not.

@dirtrunner21 Almost forgot to tell you that you need to upgrade all your nodes if you go from 1.5.4 to 1.5.5 or dev-branch. See the release notes on 1.5.5!

@Rudy-Delsaut Would you tell us how you solved the issue?

@Sebastian-Roth this can be addressed from the location plugin under the fog configuration. Location adds a fog setting for allowing snapins to be downloaded from the host location or the master storage node the snap in resides within.

@BrentC @fry_p Thanks heaps for reporting this. I just fixed it. You’ll find the very latest kernel at the top of the page again. Version 4.19.6 as of now.

@Tom-Elliott
Thanks Bro. It’s WORKING I JUST CHANGE MY HOSTNAME which one is my computer name in windows 10…
hats off…:-)

@waveydavey Topic Tools->Marked Solved

I took care of that for you.

@Sebastian-Roth thanks. i’ll try this and get back to you with an image of the details if it fails

@agray Yes, you should only have to answer the questions the first time, because the next time you run the setup script it pulls from the /opt/fog/.fogsettings file.

@thegiantcat

I rebooted the server, and recreated / restarted the task. After this it completed without issue.

@Sebastian-Roth on the fog server itself. it is not relevant to the error previosly posted sorry. i saw it when i logged into my vm server.

@agray Best to use the script (see the linked forum post on instructions) to change back your FOG IP to the one you have in the internet network (192.168.105.238). Then re-run the installer - hopefully running through. Now move your server back to the other network and again change its IP (now to 192.168.1.105) using the same script again.

No need for internet after the install. But if you ever need to re-run the installer… same procedure again.

Thank you everyone for your help. I had networking team move to same vlan and it worked fine. Then i had them move to seperate vlan and use wireshark. I found out we had sccm pxe setup. This was done long time ago. No one removed the forwards on the router.

Now we have it working once we removed the entries.