hmmm, maybe this was an issue with a previous svn. i just made a test iamge and deleted it and it was removed from the disk.

problem solved 🙂

Sorry for the delay. It was logging an error in the event log that the fog service hung I set it to delayed startup and that seems to be a reasonable workaround for the issue.

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?

@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:

I confirmed and was working on a fix. While I was at it, I cleaned up the management page. This is now pushed. 4248 should correct these issues.

Thanks for reporting.

i updated to 3709 and all numbers are matching up now. Thanks for the quick response guys.

thanks for the info guys. I ended up adding a command to setupcomplete.cmd and that seems to be working.
tzutil /s “applicable time zone”

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