@Tom-Elliott working good now, thanks!

Thank you for your help.

Best regards.

i dont know how to update topic status to solved

Thanks a lot for the help, it is working.

I believed that the “fog.advancedlogin” menu item is itself the advanced sub-menu item, and every other menu item that i configure to show with " Advanced Login Required" will be an item in that sub-menu. Since that was not working i fuzzed with fog.advanced, and fog.advancedlogin, menu visibilities, and the "advanced menu login.

TBH now i’m very confused, but at least i have a working solution. Thanks a lot again.

@Albertus The hosts that aren’t working, please place them into a group and select:

Reset Encryption Data

I’m seeing the message:

2016/12/14 4:28 PM Middleware::Response Invalid security token

@Warrender6 Here’s an example. You should just re-write this whole configuration. ISC-DHCP can support both BIOS and UEFI at the same time, you don’t need to go in there commenting and uncommenting filename lines.
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Example_2

Updated to RC36, and both full & quick registration worked as expected!

I found nothing abnormal in the interfaces. Not knowing what to do, I completely reinstalled my virtual server, which restored the functioning of fog. Thank you for your answers

Did FOS in 1.2.0 reboot on error in 1 minute or 2, I thought it was 2?

@Olduser are you creating a pack or a normal snapins?

If others of the same model work, but only some have issues, it could be a hardware issue. You could try updating the firmware, or try swapping the HDD with one from a working system and seeing if that makes a difference or not.

@Quazz Thanks, this will work, setting it to 87000 so it is just over 24hrs, that way I can unthrottle it and have the service start at 2am. Each image takes about 30 mins so I cannot imagine this being a problem at 7am when people start showing up. Thanks!

@Tom-Elliott Thanks! This worked.

Awesome thanks Tom. It worked 🙂

@msheikh said in PXE-E51 Error after fresh installs:

I had to edit the field for ‘range dynamic-bootp’ to conform to the 192.168.1.xx subnet

Ah, forgot about that part. I glanced at next-server and saw it was right, idk what I was thinking.

Here’s a couple more links that might help me finish that dang article:

https://forums.fogproject.org/topic/5019/fog-nfs-challenge-can-you-do-it/14
https://forums.fogproject.org/topic/2861/latest-development-fog/369

@Wayne-Workman Thanks! I ended up needing rename /opt/fog/.fogsettings and run the installer fresh but it was able to update successfully.

Good Day

For the first time after loading new server FOG 1.3.0 RC 30 my scheduled cron tasks does work.

Thank You

FOG Client log is always the 1st place to look for anything concerning the FOG Client, always.

For the already registered what version of fog are you running?

For the kernel panic, maybe there’s a firmware update for these? Also, how are the clients booting to the menu (efi or bios?? I suspect potentially problem in efi boot code.)