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

FOG service on 0.10.6 not restarting after reboot

Scheduled Pinned Locked Moved Solved
FOG Problems
8
50
21.5k
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
    tmerrick
    last edited by May 17, 2016, 7:49 PM

    I installed it fresh on a client without all of the CAD programs and it worked. So it is not a 10 Enterprise problem.

    I then did a fresh install on the client - Deleting the FOG program folder and re-installing (and resetting the Encryption key). And this also has worked.

    I have updated the server copy and I am sysprepping right now. I will let you know the results in about an hour.

    1 Reply Last reply Reply Quote 1
    • J
      JJ Fullmer Testers @Tom Elliott
      last edited by May 17, 2016, 7:52 PM

      @tmerrick
      @Tom-Elliott said in FOG service on 0.10.6 not restarting after reboot:

      @tmerrick Is it likely there’s an application causing a hangup on the startup of a dependency that FOG CLient is trying to use and cannot gain access to until far later?

      Did this occur before all the “custom software?”

      CAD software typically also includes licensing services. It is possible that one of them is causing trouble.
      I have one optiplex 790. So I’ll do some checking on that computer to see if perhaps this is happening and I missed something.

      Have you tried the FogApi powershell module? It's pretty cool IMHO
      https://github.com/darksidemilk/FogApi
      https://fogapi.readthedocs.io/en/latest/
      https://www.powershellgallery.com/packages/FogApi
      https://forums.fogproject.org/topic/12026/powershell-api-module

      J 1 Reply Last reply May 17, 2016, 8:25 PM Reply Quote 0
      • J
        JJ Fullmer Testers @JJ Fullmer
        last edited by May 17, 2016, 8:25 PM

        @Arrowhead-IT said in FOG service on 0.10.6 not restarting after reboot:

        I have one optiplex 790. So I’ll do some checking on that computer to see if perhaps this is happening and I missed something.

        Well poo. Mine is doing the same thing…
        @Jbob

        I checked it and the fog service was stopped. Which it did mid-update from .9.12 to .10.5. I started it and then after a couple minutes it updated itself to .10.6. Gave it a reboot and the service did not start. Checking this one another computer I’m testing. An Intel Computer Stick that I did a fresh install of windows 10 32 bit enterprise. The fog client is already on it and joined it to the domain. Checking that to see if I can isolate the issue.

        Have you tried the FogApi powershell module? It's pretty cool IMHO
        https://github.com/darksidemilk/FogApi
        https://fogapi.readthedocs.io/en/latest/
        https://www.powershellgallery.com/packages/FogApi
        https://forums.fogproject.org/topic/12026/powershell-api-module

        J 1 Reply Last reply May 17, 2016, 8:30 PM Reply Quote 0
        • J
          JJ Fullmer Testers @JJ Fullmer
          last edited by May 17, 2016, 8:30 PM

          On the fresh install of windows 10 32 bit LTSB it works perfectly fine.

          The other computer is a CB image, is it possible that this is a problem from a recent windows 10 update?

          Have you tried the FogApi powershell module? It's pretty cool IMHO
          https://github.com/darksidemilk/FogApi
          https://fogapi.readthedocs.io/en/latest/
          https://www.powershellgallery.com/packages/FogApi
          https://forums.fogproject.org/topic/12026/powershell-api-module

          1 Reply Last reply Reply Quote 0
          • T
            tmerrick
            last edited by May 17, 2016, 9:19 PM

            Mine definitely fails during the imaging process. The delayed start seems to make it work, but this is not a fix.

            The image is definitely up to date and may have the dreaded 1511 upgrade installed. I have not been able to tell if it does or not. It is not showing up under windows updates.

            J 1 Reply Last reply May 17, 2016, 10:43 PM Reply Quote 0
            • J
              JJ Fullmer Testers @tmerrick
              last edited by May 17, 2016, 10:43 PM

              @tmerrick Where did you get the windows 10 installation disk from? I’m assuming the windows volume licensing service center?
              If you don’t use the LTSB version, then the 1511 update is included in the install in all it’s default app resetting glory.

              Have you tried the FogApi powershell module? It's pretty cool IMHO
              https://github.com/darksidemilk/FogApi
              https://fogapi.readthedocs.io/en/latest/
              https://www.powershellgallery.com/packages/FogApi
              https://forums.fogproject.org/topic/12026/powershell-api-module

              J 1 Reply Last reply May 17, 2016, 10:53 PM Reply Quote 0
              • J
                JJ Fullmer Testers @JJ Fullmer
                last edited by May 17, 2016, 10:53 PM

                The more I’m looking into to whether or not this is happening, the more I am seeing it happen on any computer with the latest updates and on the windows 10 1511 upgrade.

                There was another program I have called papervision that stopped working on the latest version too. It worked perfectly fine before, but suddenly it can’t communicate with web browsers. Just giving another example of windows 10 updates breaking programs that were working before. At least they give the option to defer upgrades via group policy.

                Perhaps setting the fog service to delayed start is not to bad of a workaround?

                Have you tried the FogApi powershell module? It's pretty cool IMHO
                https://github.com/darksidemilk/FogApi
                https://fogapi.readthedocs.io/en/latest/
                https://www.powershellgallery.com/packages/FogApi
                https://forums.fogproject.org/topic/12026/powershell-api-module

                1 Reply Last reply Reply Quote 0
                • J
                  JJ Fullmer Testers
                  last edited by May 17, 2016, 11:07 PM

                  @Jbob @tmerrick
                  I found something in the event viewer
                  Event 7009 A timeout was reached (30000 milliseconds) while waiting for the FOGService service to connect.
                  followed by
                  Event 7000 The FOGService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

                  In the services console their are options for automatic recovery that we can try. I hadn’t noticed these before, perhaps they’re new? Either way I’m giving a 3 time minute delay a try.
                  0_1463526438059_Capture.PNG

                  Have you tried the FogApi powershell module? It's pretty cool IMHO
                  https://github.com/darksidemilk/FogApi
                  https://fogapi.readthedocs.io/en/latest/
                  https://www.powershellgallery.com/packages/FogApi
                  https://forums.fogproject.org/topic/12026/powershell-api-module

                  J 1 Reply Last reply May 18, 2016, 6:47 PM Reply Quote 0
                  • J
                    JJ Fullmer Testers @JJ Fullmer
                    last edited by May 18, 2016, 6:47 PM

                    @Arrowhead-IT The recovery options didn’t seem to do anything. Setting to delayed start seems to do the trick.

                    Have you tried the FogApi powershell module? It's pretty cool IMHO
                    https://github.com/darksidemilk/FogApi
                    https://fogapi.readthedocs.io/en/latest/
                    https://www.powershellgallery.com/packages/FogApi
                    https://forums.fogproject.org/topic/12026/powershell-api-module

                    J 1 Reply Last reply May 18, 2016, 7:30 PM Reply Quote 0
                    • J
                      JJ Fullmer Testers @JJ Fullmer
                      last edited by May 18, 2016, 7:30 PM

                      @Arrowhead-IT @jbob Scratch that, delayed start didn’t do the trick and I have discovered this issue happens on all windows 10 x64 1511 computers. Why oh why did I not just use LTSB to begin with?

                      Have you tried the FogApi powershell module? It's pretty cool IMHO
                      https://github.com/darksidemilk/FogApi
                      https://fogapi.readthedocs.io/en/latest/
                      https://www.powershellgallery.com/packages/FogApi
                      https://forums.fogproject.org/topic/12026/powershell-api-module

                      J 1 Reply Last reply May 18, 2016, 7:55 PM Reply Quote 0
                      • J
                        JJ Fullmer Testers @JJ Fullmer
                        last edited by May 18, 2016, 7:55 PM

                        @Arrowhead-IT What’s interesting is that on delayed start the Fog service may not start, but the fog user service and the fog tray pop up no problem.
                        With delayed start there is nothing in the event viewer concerning the fogservice, it simply never started.

                        Have you tried the FogApi powershell module? It's pretty cool IMHO
                        https://github.com/darksidemilk/FogApi
                        https://fogapi.readthedocs.io/en/latest/
                        https://www.powershellgallery.com/packages/FogApi
                        https://forums.fogproject.org/topic/12026/powershell-api-module

                        1 Reply Last reply Reply Quote 0
                        • J
                          Joe Schmitt Senior Developer
                          last edited by May 18, 2016, 10:18 PM

                          Does the issue present itself when you re-install the client on the machine (be sure to reset encryption data when doing so) with this update?

                          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.

                          J 1 Reply Last reply May 18, 2016, 10:51 PM Reply Quote 0
                          • J
                            JJ Fullmer Testers @Joe Schmitt
                            last edited by May 18, 2016, 10:51 PM

                            @Jbob You’d think I would have tried that since I suggested it to this guy, but I have not tried that because I am dumb.

                            Have you tried the FogApi powershell module? It's pretty cool IMHO
                            https://github.com/darksidemilk/FogApi
                            https://fogapi.readthedocs.io/en/latest/
                            https://www.powershellgallery.com/packages/FogApi
                            https://forums.fogproject.org/topic/12026/powershell-api-module

                            J 1 Reply Last reply May 18, 2016, 11:19 PM Reply Quote 1
                            • Wayne WorkmanW
                              Wayne Workman
                              last edited by May 18, 2016, 11:12 PM

                              I’ve actually been noticing that the fog client isn’t starting for me in Win10. I didn’t think anything of it, because manually starting the service works… I’ll have to look into that.

                              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!
                              Daily Clean Installation Results:
                              https://fogtesting.fogproject.us/
                              FOG Reporting:
                              https://fog-external-reporting-results.fogproject.us/

                              1 Reply Last reply Reply Quote 0
                              • J
                                JJ Fullmer Testers @JJ Fullmer
                                last edited by May 18, 2016, 11:19 PM

                                @jbob A re-install of the service appears to work. Should the service not be installed in the image for windows 10 and just be added as part of a firstlogon/sysprep type script?

                                Have you tried the FogApi powershell module? It's pretty cool IMHO
                                https://github.com/darksidemilk/FogApi
                                https://fogapi.readthedocs.io/en/latest/
                                https://www.powershellgallery.com/packages/FogApi
                                https://forums.fogproject.org/topic/12026/powershell-api-module

                                1 Reply Last reply Reply Quote 0
                                • J
                                  Joe Schmitt Senior Developer
                                  last edited by Joe Schmitt May 18, 2016, 5:21 PM May 18, 2016, 11:21 PM

                                  While that is a band aid, it should work until I can narrow down the root cause. Just use the msi’s switches in silent mode in your setup complete file (and then start it or restart the machine).

                                  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
                                  • J
                                    Joe Schmitt Senior Developer
                                    last edited by May 30, 2016, 5:27 AM

                                    @tmerrick do you still have some computers experiencing this issue? I am attempting to track down exactly what’s failing but can’t replicate 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.

                                    1 Reply Last reply Reply Quote 0
                                    • M
                                      Mentaloid
                                      last edited by Mentaloid May 30, 2016, 12:16 AM May 30, 2016, 6:09 AM

                                      I do - I had a lab of 28 computers imaged on a fresh image of win10 edu/1511. Setupcomplete re-enables FOGService after it was disabled for sysprep. Image has nothing else added except office 2016.

                                      Of the 28 computers, 2 of them failed to start fogservice during the setupcomplete, and 8 more of them failed to start fogservice after a snapin called for a reboot after install. All 28 computers are identical, bought at the same time. i5@2.3g,4gb ram.

                                      As with the other examples here, the fog.log has nothing in it except stating it’s gone to sleep - no exit info for shutting down with the system, and no startup. Zazzles.log doesn’t appear to exist…

                                      I’ve changes my setupcomplete.cmd to have this in it…

                                      sc config FOGService start= delayed-auto
                                      waitfor /t 5 null
                                      sc failure FOGService reset= 86400 actions= restart/60000/restart/60000/restart/60000
                                      waitfor /t 5 null
                                      sc failureflag FOGService 1
                                      waitfor /t 5 null
                                      sc start FOGService
                                      

                                      to see if this has any effect. Note that the failure flag of 1 tells the system to restart the service if it exits unexpectedly (non-0 exit code) using the failure sequence.

                                      This workaround won’t be tested until next deploy (next weekend maybe?)

                                      Also - I had periodically experienced this in a VM guest (VMware ESXi 6.0 host, 4virt cpu, 8gvem). Server was practically idle at the time, and is ridiculously fast (deploy, oobe, reboot, desktop takes about 6 minutes). This same guest after another reboot started the service fine, and had been used to test images repeatedly. I’d say it was only about a 5% rate of failure to start the service in the VM.

                                      1 Reply Last reply Reply Quote 0
                                      • J
                                        Joe Schmitt Senior Developer
                                        last edited by Jun 1, 2016, 12:31 AM

                                        v0.11 of the client should prevent this. The FOG Service will have a dependency of dnscache which is Window’s DNS Client. The DNS Client is one of the last network services to start and all version of Windows within reason use 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 1
                                        • J
                                          Joe Schmitt Senior Developer
                                          last edited by Jun 19, 2016, 10:28 PM

                                          v0.11.0 is released and fixes this issue. Can you test when you have a chance?

                                          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.

                                          G 1 Reply Last reply Jun 24, 2016, 4:57 PM Reply Quote 1
                                          • 1
                                          • 2
                                          • 3
                                          • 2 / 3
                                          • First post
                                            Last post

                                          208

                                          Online

                                          12.1k

                                          Users

                                          17.3k

                                          Topics

                                          155.4k

                                          Posts
                                          Copyright © 2012-2024 FOG Project