@demontraven Forgive my sounding rude, but this has no impact on actual functionality. (Sorry I know it’s rude, but I’m just being honest).

That said, for now please run this command:
wget -O /var/www/fog/lib/fog/fogcore.class.php https://raw.githubusercontent.com/FOGProject/fogproject/5726017bed15f89e25fc9ad8fc19ec1b523b4f88/packages/web/lib/fog/fogcore.class.php

This should fix the uptime issue for you.

@Wayne-Workman
Had to run the delete commands one more time after moving to RC11. It’s been okay since then other than needing to reset the encryption data.

@Joe-Schmitt
RC11 has started out well. I did need to rerun the install and reboot the system before the client updater started working. The GUI remains responsive even after all the clients start up in the morning. After a few days I may try shortening the client communication period from 900 so the snapins run more timely.

@Joe-Schmitt works perfect!
Thanks!

@Timo

Did you reset the encryption data on the specific host? If not give it a try and report back.

https://forums.fogproject.org/topic/8645/fog-client-auto-updating-hotfix

Found and fixed. Thanks for reporting.

Should be fixed in latest. Please test when you can and let me know.

@apathetic_admin I recommend doing the SQL query Wayne suggested instead.

UPDATE `hosts` SET `hostEnforce`='1';

@Tom-Elliott Ok thanks look forward to it your doing lots of great work.

I can confirm that this fix works on my end, too. I deployed an image and then sent out all snapins, and everything worked as expected.

Thanks, Tom.

@Tom-Elliott Updated and confirmed working 😃

@Tom-Elliott 53 and 54 were fine.

@Tom-Elliott Figured it out, it’s a different bug, made a new post
https://forums.fogproject.org/topic/8600/group-service-settings-not-applying-sort-of

@Tom-Elliott Yes, this log is just informative, in case you wanted to have a look.

I confirm that snapins now work (1.3.0 working-RC-11, version 39)

Problem solved in 1.3.0-RC-10. Thanks !

Found and fixed in RC-11 thanks for reporting.

@lukebarone Seems it wasn’t fixed in rc-10, tom says it’s fixed in 11 though, follow here:
https://forums.fogproject.org/topic/8558/reboot-host-on-hostname-changes-and-ad-changes-even-if-users-are-logged-in-button-not-saving

Confirmed the issue and have patched it for rc11. To fix immediately, go to line 1291, remove it and place it before the setAD function all.

@Joe-Schmitt this was an accidental issue I think on my side as it was sending wol tasks. Just for confirmation the client is simply checking if a task is reboot, if not it sets up as shutdown?

I’ve removed wol tasks from the client sender for RC 11 just would be good to know for sure.