@Wayne-Workman Based on the messages from the log, I’d say this is the old client, if it’s any help.

I solved this by doing chmod777 <folder> on the directory where i put all the trunk install files and then i re-ran the installer and realized last time i ran through i didnt update the database via the WebUI When it asked…

Group ad field settings do not maintain the settings. This is because, it updates all the hosts all at once. I don’t have a performance friendly option to do this checking.

So this setting in the group field is designed to blank out after it’s been updated. The hosts within the group, however, should be updated. Is this not happening?

@skotteru What operating system?

@rvieira That’s strange, isn’t it? 🙂 Glad it works though.

Here is part of the access log for each computer and it happens every minute, not 5 minutes that I thought that I had set above.
access_log.txt

For future readers, this is most commonly an FTP credentials problem, and the answer is located here: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP#Credentials_.2F_Passwords

Coming back to confirm that the 11e image completed both up and down using the .efi extension.

FOG Trunk fully supports windows 8.1

Here are some pointers, but some of these may not be needed anymore because @Tom-Elliott has made some changes specifically to fix some of the Win8 issues that past versions of FOG had.

https://wiki.fogproject.org/wiki/index.php/Windows_8_UEFI_Imaging_Tips

You might also peek at this for handing out UEFI boot files and Legacy boot files at the same time: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence

Thanks again Tom!

Well I ended up doing a fresh install of FOG (wiped existing FOG files and set it up again) and during setup I provided the password for MySQL this time. I have a GUI, so I’m going to continue testing and see if I hit any other issues.

I will do my best to figure this out! Thanks for the start.

Cheers.

@Tom-Elliott said:

0.0.0.0 just means to use any interface.

I believe just :69 means to use anything, so even if network is not up when it starts, it won’t crash simply because network does come up.

WiKi updated to reflect this: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_TFTP#Ubuntu:

/tmp/pigz1 is a temporary location where data is streamed for compression/decompression. that part of your system seems to be running fine. what it sounds like, however, is that your drive is not being re-sized to fill the disk after imaging completes.
what version of fog are you using?
i’m assuming this is a resizable image, is that correct?

thanks Tom, that has us up and running!

I’m solving this thread. It was caused simply because I overlooked a while loop. What was a while loop should’ve simply been an if statement. Basically it was looping as long as poll was invalid, which if the connection is dropped (such as the case during an upload task to change from one checkin to another element) would cause it to loop repeatedly forever because the array no longer existed.

This should now be solved and I’m sorry. Version 4264.

4258 should fix this.

I teamviewered in. Found that the redirect to static/index.html was not something FOG Was causing.

The NAS was NFS Mounted to the FOG Server. But as they had found out, the NFS From FOG Couldn’t redistribute the share as NFS. Because of this, Storage Node was pointed directly at the NAS and volume of the NAS to allow imaging to occur. However, when going to FOGConfigurationPage it was attempting to go to the NAS’s management portal, and because it was invalid, it was being redirected per the NAS’s settings.

Changed the Node to the FOG Server proper information and FOG Configuration Page loaded with no issues.

Invalid security token is your problem here please go to host management find this relevant post and select reset encryption data they should correct your problem

Awesome. I will be back onsite tomorrow.

You folks are awesome.