SOLVED Fog Client seems to deal different since 1703
x23piracy last edited by x23piracy
- FOG Version: 1.4.4
- Service Version: 0.11.12
- OS: Windows 10 1703
in the past i used Windows 10 1607 and had 1 auto logon in my unattend.xml because i need Firstlogoncommands to trigger setupcomplete.cmd (Windows 10 OEM), in the past the local admin (unattend.xml) has been logged on, seconds later the FOG Client comes active and was renaming the client and joining the domain and did a reboot on it’s own (not shutdown -r -t 0 -f in setupcomplete.cmd!) after the reboot i could logon the first domain user.
Today with 1703 and maybe a newer Fog Client sometimes no reboot happens, when i then check Hostname and Domain status i can see Hostname has changed and the client belongs to the domain but it doesn’t reboot anymore.
@Joe-Schmitt did we had significant changes that doesnt require a reboot anymore? If so i need to add a shutdown in my script (wasn’t necessary before).
@x23piracy we can then close the issue?
@x23piracy Is this still an issue?
@sebastian-roth sorry i was to busy today, i will answer to all of this if i had the time.
@x23piracy Do you see anything in the fog-client log or windows system event logs?
@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 i need to deploy my older image to see which fog version was inside, yes it was definitely older then the current version.
@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…