Trunk 5735 PC doesnt restart after joining the domain.
-
I was running a poweshell tail on it at the time (get-content -wait \computername\C$\fog.log) and I could see activity up to the point I posted. But when I checked the service it was indeed in the stopped state.
-
Alright, its another race condition. I’ll push a patch tonight. Basically the power api was informing all other threads that it had initiated a shutdown/reboot before it actually did. Thus the main thread killed the whole process before the power api could actually restart.
-
This is a Windows 10 Sysprep image.
the fog client is installed in the finalize stage of the sysprep in the setupcomplete.cmd -
@Greg-Plamondon Joe said it’s a bug, just be patient and wait for the new version. Did you know that Joe is the new client developer? He knows what he’s talking about.
-
@Wayne-Workman said in Trunk 5735 PC doesnt restart after joining the domain.:
@Greg-Plamondon Joe said it’s a bug, just be patient and wait for the new version. Did you know that Joe is the new client developer? He knows what he’s talking about.
Oh, I know who Joe is, I just didn’t want to be rude and ignore your question.
-
@Joe-Schmitt adding onto this issue, with 0.11.1 and trunk 8233, using power management immediate deployment for a shutdown task - the task does not work if a user is logged in.
The pop-up displays with buttons to abort and such, I didn’t click those, I just let it count down. Then nothing happened.
Computers without users logged in shutdown ok.
-
@Wayne-Workman is the service still running after the dialog closes? I’m assuming its the same race condition issue.
-
@Joe-Schmitt The FOGService’s “Status” in services is just blank, so no it’s no longer running.
-
This issue has been addressed in v0.11.2. Please test when you get a chance.
-
@Joe-Schmitt said in Trunk 5735 PC doesnt restart after joining the domain.:
This issue has been addressed in v0.11.2. Please test when you get a chance.
The Update worked for me Joe, Thanks!