• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

(Client 0.11.12 -) Client 0.11.14, Windows 10 1709 - Reboot (or other power event) fails

Scheduled Pinned Locked Moved Solved
Bug Reports
2
5
1.1k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T
    TrialAndError
    last edited by Feb 17, 2018, 11:17 PM

    Same problem again: 1135

    I started with a fresh Windows 10 1709. In the beginning the client initiated power events successfully.
    Then I started to rebuild my machine. And now after a couple of apps like browsers, java, office (no regedit or something comparable at all) the reboot fails again.

    --------------------------------HostnameChanger-------------------------------
    ------------------------------------------------------------------------------
     17.02.2018 23:45 Client-Info Client Version: 0.11.14
     17.02.2018 23:45 Client-Info Client OS:      Windows
     17.02.2018 23:45 Client-Info Server Version: 1.5.0-RC-13
     17.02.2018 23:45 Middleware::Response Success
     17.02.2018 23:45 HostnameChanger Checking Hostname
     17.02.2018 23:45 HostnameChanger Hostname is correct
     17.02.2018 23:45 HostnameChanger Attempting to join domain
     17.02.2018 23:46 HostnameChanger Success, code =  0
     17.02.2018 23:46 Power Creating shutdown request
     17.02.2018 23:46 Power Parameters: /r /c "Host joined to Active Directory, restart required" /t 0
     17.02.2018 23:46 Bus Emmiting message on channel: Power
     17.02.2018 23:46 Power Attempt 1/6 to shutdown computer
     17.02.2018 23:46 Power --> API call returned 0, will re-attempt in 5 minutes```
    1 Reply Last reply Reply Quote 0
    • T
      TrialAndError @TrialAndError
      last edited by Feb 28, 2018, 5:02 PM

      client 0.11.15

      Power events are executed on many (most?) machines again! Thank you for your work!

      1 Reply Last reply Reply Quote 0
      • J
        Joe Schmitt Senior Developer
        last edited by Joe Schmitt Feb 21, 2018, 11:09 AM Feb 21, 2018, 5:09 PM

        @TrialAndError could you perform a few debugging steps for me? It’d help narrow down why the shutdown is failing:

        • Check the Windows log for any reported issues around 17.02.2018 23:46
        • Set the client to Automatic (Delayed) startup, and see if that solves the issue
        • If both of those fail, try running this build instead: https://build.jbob.io/Client/nightly/02-18-2018-powerdebug-01/SmartInstaller.exe . It will hopefully log a more specific error message, but you’d need to first uninstall any existing client on the machine, and reset encryption data on it before installing

        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.

        1 Reply Last reply Reply Quote 0
        • T
          TrialAndError
          last edited by Feb 25, 2018, 2:46 PM

          On the “fresh” Win10 1709 switching to “Delayed” worked. The client 0.11.14 executed power events again.

          On the “old” Win 10 - no change. And either with 0.11.14 nor the nightly any events a logged in the Windows log files around the time the error is logged in fog.log.

          T 1 Reply Last reply Feb 28, 2018, 5:02 PM Reply Quote 0
          • T
            TrialAndError @TrialAndError
            last edited by Feb 28, 2018, 5:02 PM

            client 0.11.15

            Power events are executed on many (most?) machines again! Thank you for your work!

            1 Reply Last reply Reply Quote 0
            • J
              Joe Schmitt Senior Developer
              last edited by Feb 28, 2018, 5:04 PM

              @TrialAndError phew, I’m glad the issue is mostly fixed. Thanks for helping me debug it!

              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.

              1 Reply Last reply Reply Quote 0
              • 1 / 1
              1 / 1
              • First post
                1/5
                Last post

              160

              Online

              12.1k

              Users

              17.3k

              Topics

              155.3k

              Posts
              Copyright © 2012-2024 FOG Project