Trunk 5735 PC doesnt restart after joining the domain.
-
After successfully imaging the PC it doesn’t want to reboot even though the log says it should.
------------------------------------------------------------------------------ --------------------------------HostnameChanger------------------------------- ------------------------------------------------------------------------------ 6/22/2016 3:09 PM Client-Info Client Version: 0.11.1 6/22/2016 3:09 PM Client-Info Client OS: Windows 6/22/2016 3:09 PM Client-Info Server Version: 7853 6/22/2016 3:09 PM Middleware::Response Success 6/22/2016 3:09 PM HostnameChanger Checking Hostname 6/22/2016 3:09 PM HostnameChanger Hostname is correct 6/22/2016 3:09 PM HostnameChanger Attempting to join active directory 6/22/2016 3:09 PM HostnameChanger Success, code = 0 6/22/2016 3:09 PM Power Creating shutdown command in 60 seconds 6/22/2016 3:09 PM Bus { "self": true, "channel": "Power", "data": "{\r\n \"action\": \"request\",\r\n \"period\": 60,\r\n \"options\": 2,\r\n \"command\": \"/r /c \\\"Host joined to Active Directory, restart required\\\" /t 0\",\r\n \"message\": \"This computer needs to perform maintenance.\"\r\n}" } 6/22/2016 3:09 PM Bus Emmiting message on channel: Power ------------------------------------------------------------------------------ 6/22/2016 3:09 PM Service Power operation being requested, checking back in 30 seconds 6/22/2016 3:10 PM Service Power operation being requested, checking back in 30 seconds 6/22/2016 3:10 PM Power Creating shutdown request 6/22/2016 3:10 PM Power Parameters: /r /c "Host joined to Active Directory, restart required" /t 0```
-
Well I know that the restart function works on 0.11.1, I saw it today.
We need more info about this image.
Sysprep? OS?
Are you sure the image was not already bound to the Domain?
-
Is the service currently stopped on this machine?
-
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!