Fog Client seems to deal different since 1703

[Sebastian Roth]

@x23piracy As Joe is very busy these days I am trying to answer this as good as I can (having played with the client code for several days now).

If fog-client version has not changed (I suspect it hasn’t as 0.11.12 is the most current) why should the client behave differently? Did you use an older version before? Which version?

Sorry, more questions than answers…

[x23piracy]

@sebastian-roth i need to deploy my older image to see which fog version was inside, yes it was definitely older then the current version.

[Sebastian Roth]

@x23piracy Please let me know which version you had in the old image. It’s hard enough to find the needle in the hay stack but at least I need to know how big it is!

[Sebastian Roth]

@x23piracy Never mind, I might have found it. See here. It checks if domain join was successful and does reboot then. So either there is something different in 1703 where joining works but it does not return success or the reboot is broken altogether.

[Sebastian Roth]

@x23piracy Do you see anything in the fog-client log or windows system event logs?

[x23piracy]

@sebastian-roth sorry i was to busy today, i will answer to all of this if i had the time.

[Sebastian Roth]

@x23piracy Is this still an issue?

[x23piracy]

@sebastian-roth no

[george1421]

@x23piracy we can then close the issue?

[x23piracy]

@george1421 yes