I’m guessing your Antivirus installs a Filter Driver in your Network Adapter. If correct, uncheck it, save, and try again.

@Wayne-Workman
Thank you Wayne. I am agree with you. I will use now command line to manage mysql.
This will be the opportunity to improve my knowledge in sql 😉

Have a good day

@sudburr what you performed is correct, if you already had a prior config laid out. Sorry I didn’t recognize this sooner but a fix for this has been added to the next working branch.

Essentially the variable was being set properly, but it was being overwritten when the fog settings file was imported.

Good News Everyone!!!

I was able to get ipxe.efi to work, got a new USB to Ethernet adapter. The client was able to load and run the full registration without issue.

USB Ethernet adapter that works is HP P/N829834-001, it’s a USB 3.0 to Gigabit adapter. May want to add this to the confirmed working hardware list.

Thank you @george1421 for all the help was just about to load the bootable usb when the adapters arrived.

@Tom-Elliott
Work fine, thanks a lot!

@Wayne-Workman I can confirm this is now working - I just had to re-image the system and sysprep it again. It’s now uploading fine.
Thanks for the help and suggestions 🙂

If you’re running FOG 1.3.0 Release Candidate, you can protect images so that they are less likely to be accidentally deleted.

Also, 1.3.0 Release Candidate has a table in the database called history that you can look through to see what user deleted what image, or did what action. So at least they can be accountable for their actions.

@Tom-Elliott said in "Could not find a Storage Node in this group, is there one enabled?":

which would explain the “is one enabled” message.

This is a higher than normal brought up message on the forums recently. Perhaps not on bug-scale but it is higher than average. I’m hoping these issues go away with RC-27’s fixes whenever that is released.

I agree with Quazz about updating to the latest RC. Every new RC has fixes.

Linking in similar thread: https://forums.fogproject.org/topic/8944/centos-7-2-uuid-for-swap-wrong

@Wayne-Workman It had nothing to do with PHP. It had to do with the FOG Services not being properly picked up. PHP code had nothing to do with any of these problems. (Not saying there wasn’t a coding problem, just want people to more properly know what/where a problem is.)

The php not installing proper wasn’t something I’ve been able to replicate. But after this, a fresh install didn’t start the proper portions of the services which has been addressed.

Ok, thanks for letting us know. Marking this as solved then.

@Mokomoko I’m free today if you want help. IM me.

@Wayne-Workman
I think i cracked it, after you mentioned DB connection issues i checked everything using workbench and found fogstorage user had no schema privaleges at all ! Not sure how they would dissapear but after adding back in fog seems to be picking other storagenodes correctly.
Thank you for the help and guidance.
This can be marked as no bug but maybe helpful for others to check if they encounter issues.

@tseraj First, troubleshoot that it is the device and not the network. Hookup a dumb switch (unmanaged consumer grade switch) between your building’s network and this computer, and try again. If it succeeds, it’s your network. If it’s the same issue, it’s something with the device. If it’s something with the device, You may need to use the 10-second delay boot ROMs that Tom recently added. What is the filename that you have set in DHCP option 067/filename ? There’s a directory on the fog server, I think it’s /tftpboot/10secdelay or something similar. What you need to try is rename your currently in-use to blah.old and then move the 10secdelay version of that file to the /tftpboot directory so that it starts getting used, and then try again.

@Wayne-Workman

This issue is resolved. I built a new server as you and Tom suggested. Thanks for the help.

@Tom-Elliott

After upgrading to RC-25 as you suggested, the issue is resolved. I can now image computers. Thank you and the other forum members for the help.

@Quazz said in Email notification format has changed, missing word wrap:

@x23piracy Looks this only happens with your Windows 10 1607 Office ProPlus image. Can you confirm?

edit: this could also be down to the mail client

Hi, yes i just need time to deploy other images, don’t want to do this for fun being busy here with other work but i am sure i need deploy other images in the next days, i get back…

@SharonLampe well this one is pretty interesting cause I’m seeing double vision on this one.

A quick diagram would be this.

Packets 31 to 35 are the same client saying hello I’m here world I need configuring. This is remarkable since this should only happen in one packet. Its the client sending out 4 dhcp discover requests rapid fire. I can see from this discover packet that this is a Dell computer that is running in bios mode. (so undionly.kpxe needs to be sent for dhcp option 67 {boot-file} and this is just a wild guess that is is one of the older dells (pre o7010). Packets 35 to 50 are replies from your dhcp server. This again is remarkable since there should only be one reply from your dhcp server. Looking at the time codes I can see these are in 3 groups of 4 responses each (which seems to align with the 4 packets send in step 1. looking at the dhcp server reply I can see that dhcp server 10.0.0.8 is replying to your client. And the address its replying with your IP address is 10.0.20.92 with a next server of 10.0.0.8 (your dhcp server!! which should be your FOG server if you want pxe booting to work). The subnet mask is 255.255.0.0 so both the dhcp server and the target computer are in the same subnet (this is good). Your upstream router is 10.0.0.1 (not really relevant). In that same conversation ID you have a second dhcp server 10.0.0.9 responding to the target computer with your IP address is 10.0.21.9 (not typically a good thing). Its telling the target computer that its next server (dhcp option 66) is itself 10.0.0.9 (still not good for pxe booting, this next server must be the FOG server).

OK from here I’ve seen enough to know why its not working.

Lets identify what servers are 10.0.0.8 and 10.0.0.9 are. Once that is figured out, we need to ensure they have dhcp options 66 {next-server} (should be your FOG server’s IP address) and dhcp options 67 {boot-file} (should be undionly.kpxe for bios based computers) values set. Right now they are not sending the client the proper information to boot via pxe.

And while this is only a suspicion I question why the target computer is ending out multiple dhcp discover requests. This is either because of a network misconfiguration, or something is not right with that target computer. There should be just one disover, with a reply from the dhcp server, then the target computer providing a full list of parameters its needs, and then finally the target computer responding with (OK got it). That should be 4 packets total to 30 ish packets.

@csa I need you to show me please. Screenshot, logs etc…?