Client 0.11.12, Windows 10 1709 - Reboot fails
-
@UWPVIOLATOR @x23piracy can you try the following stops on a problematic machine?
- In an administrative CMD, stop the
fogserviceif it is still running:net stop fogservice - Download and extract this file anywhere on the machine: PowerDebugger.zip
- Run the
Debugger.execontained in the extracted folder as Administrator - Type the following commands into the debugger’s prompt (one at a time, and pressing enter after each line)
bus mode server power restartThe debugger will then schedule the client’s restart process in 60 seconds. Can you let me know if it successfully restarts the machine? If not I’ll need the full output of the Debugger window.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
- In an administrative CMD, stop the
-
@UWPVIOLATOR @x23piracy after running the debugger in the prior post, can you also try installing this build of the client on a few machines: https://build.jbob.io/Client/nightly/01-32-2018-win-dependencies-01/SmartInstaller.exe ?
It likely wont fix the shutdown issue, but it should allow the client to consistently start up with Windows.
-
“power restart” did restart my machine. Success!
-
@TrialAndError @UWPVIOLATOR @x23piracy @dclark I believe I have isolated the issues with Windows 1709 and patched them. Could you try installing this build of the client on a few machines to test? (You may need to hit
Reset Encryption Datafor the hosts if you are uninstalling an existing FOG Client and installing this build). With any luck it will fix all issues with the service failing to start, and not shutting down the computer correctly.https://build.jbob.io/Client/nightly/02-01-2018-win1709-04/SmartInstaller.exe
NOTE: This is a nightly build and is not production compatible! Imaging it may produce security warnings from Windows or your anti virus software.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
-
Sorry,
my machine still does not reboot. The desktop client shows up and vanishes but no power event is executed.
------------------------------------------------------------------------------ ----------------------------------UserTracker--------------------------------- ------------------------------------------------------------------------------ 02.02.2018 09:07 Client-Info Client Version: 0.11.12 02.02.2018 09:07 Client-Info Client OS: Windows 02.02.2018 09:07 Client-Info Server Version: 1.4.4 02.02.2018 09:07 Middleware::Response Success ------------------------------------------------------------------------------ 02.02.2018 09:07 Service Sleeping for 132 seconds 02.02.2018 09:08 Power Creating shutdown request 02.02.2018 09:08 Power Parameters: /r /c "FOG PowerManagement" /t 0 02.02.2018 09:08 Bus Emmiting message on channel: Power 02.02.2018 09:08 Power Attempt 1/6 to shutdown computer 02.02.2018 09:08 Power --> API call returned 0, will re-attempt in 5 minutes 02.02.2018 09:09 Power ERROR: Could not create shutdown command from request 02.02.2018 09:09 Power ERROR: Die Laufzeitbindung kann für einen NULL-Verweis nicht ausgeführt werden. -
@TrialAndError if you set the service to delayed start, or manually stop and start up the client after boot, then does it work?
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
-
@joe-schmitt
I manually stopped/started FOGService but no effect. -
@joe-schmitt I installed your nightly client build. It does not work and I can not even start the service. Gives me this error.
-
@UWPVIOLATOR can you try this build: https://build.jbob.io/Client/nightly/02-05-win1709-01/SmartInstaller.exe ?
@TrialAndError that’s actually good news, it means we can reliably replicate the issue, and its causing an error we can trace as well. I’ll send you a PM about this, but it’d be extremely helpful if I could remote into a computer to further debug on a machine with the issue.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
-
@joe-schmitt First try it broke Windows. Cant event get past setup.
-
For anyone watching the thread, I’m in contact with @UWPVIOLATOR about the issue.
-
@uwpviolator said in Client 0.11.12, Windows 10 1709 - Reboot fails:
@joe-schmitt First try it broke Windows. Cant event get past setup.
I did not remove the old client before installing this one. After I removed it then installed the new one it appears to work.
-
I can confirm: on a clean Windows 10 1709 installation the client now works.
The problem is now only my problem. Thread can be marked solved.
-
@TrialAndError to be clear, its the nightly build I posted that works, and not stock 0.11.12?
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
-
@joe-schmitt
I only testest the nightly.Downloading the SmartiInstaller.exe again is not possible because a trojan “FUERBOOS” is recognized.
-
@TrialAndError @UWPVIOLATOR v0.11.13 of the client (in the newest RC) patches the win1709 issues, thank you for your help debugging this!
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
-
@joe-schmitt Thank you. Question we are still on 1.4.4 can I use the new client with that or do we need to update the server?
-
@uwpviolator You should be able to use the new client, but it won’t automatically update. As far as the communications between the client the server, nothing has changed.
The only other difference, your devices won’t automatically update to 0.11.13, unless you download the files from github, place them in place of your current files (under /var/www/fog/client/), and then edit the /var/www/fog/lib/fog/system.class.php FOG_CLIENT_VERSION line to 0.11.13.
