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

@Tom-Elliott Thanks Tom :). I’ll have a chance to do a confirmation test in my setup sometime next week and let you know if I encounter any issues related to this.

It’s olivierl (wrong account)
Hye,

Ok i m sorry , i ve found my mystake .
I ve multiboot and before i make a other type for os image .
I change for linux and it’s working without do a new image.

Thank

@Tom-Elliott It’s ok now ! Thanks

@Wayne-Workman
We were running 1.12, up until sometime this spring. Since then we’ve been on a trunk version. The last update was from RC8.

I would say over 10k clients. I’ve turned off the client updater for now. We’ll use something else to get the legacy clients updated to version 11.

Top was showing a load average of 147 when class was in session in RC8. Often mysql would be the highest cpu utilization, but then there would be dozens and dozens of apache2 instances. With RC9 the load average doesn’t climb so high, but there’s a bit broken too.