I’ve marked the thread as solved so as to ensure I don’t go crazy looking at “unsolved” threads. RC-8 will have the fix for the replication issues as well as a few other fixes that were rather not issues (in the directest sense of the word) but just redundant.

The additional fixes just ensure that if all files are matching, it doesn’t try to resync the data between the two sides (causing unnecessary load – if only for a second or two).

A part of the “whole” is it will also enable ALL services to update their loop update times properly. Only MulticastManager had been working properly apparently, not that many would’ve noticed a serious issue. It will properly check the new sleep times and start using the new sleeptime after the next cycle runs (if it isn’t already running).

For example, say your FOGMulticastManager is setup to go in 10 second intervals (which is the default) and you want FOGMulticastManager to go in 300 second (5 minute) intervals, if you updated the FOGMulticastManager sleeptime to use 300, it will update after the next check, or when this current check is complete.

v0.11.5 of the client prevents premature startups of the service. You will still need to disable the client before syprepping and restart the computer when sysprep is complete though (as described in the updated FOG Client wiki article).

@jbender So that will be available relatively soon in the “RC” cycles (unless we decide to go full fledged lol).

All is good to go now…

@Tom-Elliott I did not see that one. Thank you good sir.

@Raymond-Bel
it’s from line endings not being read properly.
^M translates to (Native) mode line endings (but it confuses installers).
fix hopefully in SVN now.

It’s not something I can tell when submitting either. It’s only when one informs me like this, so thanks.

Found the issue and was able to fix. Fix will be available for RC-6.

Thank you for reporting.

@Wayne-Workman Thanks, yes I may move to 64 bit. However it’s good that my issue has highlighted the inconsistency in the code which sounds like it only shows up in 32 bit OS’s. I’m guessing there mustn’t be too many others with my setup out there, otherwise this would have been reported a while ago. Glad its a relatively easy fix, I’ve rebuilt these boxes a few times recently and didn’t wish to have to do it again. Regards, Mark

I feel I should add, the reference error isn’t the cause of the issue, not directly at least.

@Wayne-Workman Fixed issue will be available in RC 6.

Issue would only occur in the case a user made a change, then hit the “back” button.

I’ve corrected the action of this for all elements that have these same type of actions. Will be good for RC-6.

@ablohowiak As a side note here, if you’re 100% new client in your environment, remove the legacy password in fog, just blank it out in the fog config defaults, and on hosts via groups. The legacy pass has security vulnerabilities.

Great! Compliments for the super quick response and fix. That’s what makes Fog stand out!

This is already fixed for rc 6.

Group snapins should properly deploy. Will be available for RC-5.

Issue confirmed. I was tryign to fix a bad status update in the repo earlier and apparently one of my links ended up in the mix.

I deleted the entire repo and readded what was requried back.

This should be fixed now.

Please re-pull your repo (this only affected git users).

One node crashed this morning. I was rebuilding it. The node was still enabled in fog - and because it wasn’t responding it caused the above error and a chainloading issue on hosts. The node that was not working was not the node that technicians were trying to deploy from.

Great! Thank you!

Already fixed in RC-3