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

    Windows 10 Client 0.11.4 Windows Service

    Scheduled Pinned Locked Moved Solved
    Bug Reports
    6
    32
    9.4k
    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.
    • x23piracyX
      x23piracy @RLane
      last edited by x23piracy

      @RLane you should not use delayed-auto if so there is a race condition for breaking the image when deploying, for some machines you could have luck and for some maybe you will get an error.

      In short when using OEM you can’t use SetupComplete.cmd without calling it by unattend.xml section firstlogoncommands.
      If you are not using OEM you can use SetupComplete.cmd as normal but stay away from delayed auto.

      @Tom-Elliott @Joe-Schmitt Could someone add this information to the wiki?
      If OEM call setupcomplete.cmd via unattend.xml section firstlogoncommands
      if no OEM use Setupcomplete.cmd as normal

      Check here: https://forums.fogproject.org/post/74436

      Regards X23

      ║▌║█║▌│║▌║▌█

      R 1 Reply Last reply Reply Quote 1
      • R
        RLane @x23piracy
        last edited by

        @x23piracy I’m not using OEM. I’m using a KMS key - Windows 10 x64 for Education. I had no issue with the same setupcomplete.cmd and unattend file with 0.11.2. After upgrading to the RC’s, it began to give me issues.

        1 Reply Last reply Reply Quote 0
        • M
          Max Kern @RLane
          last edited by

          @RLane Hi,
          Yes this worked for me very well on about 60 machines.
          I put the delayed-auto into the SetupComplete an deactivate the Service like it says the wiki.

          x23piracyX 1 Reply Last reply Reply Quote 0
          • J
            Joe Schmitt Senior Developer
            last edited by Joe Schmitt

            I will look into this when I get a chance. Could you describe in detail the hardware that has this issue and the OS config (e.g. if its sysprep please provide the unattend and setup complete) also the exact OS info. I need to figure out how to replicate this on my vms.

            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.

            M 2 Replies Last reply Reply Quote 1
            • x23piracyX
              x23piracy @Max Kern
              last edited by x23piracy

              @Max-Kern said in Windows 10 Client 0.11.4 Windows Service:

              @RLane Hi,
              Yes this worked for me very well on about 60 machines.
              I put the delayed-auto into the SetupComplete an deactivate the Service like it says the wiki.

              Well but i like that it works with any machine i try from vm to high end workstation.
              some days ago the wiki was itself talking about delayed auto but this has changed and that for a good reason.

              Well if you only using one special type of hardware you sure could stay with delayed auto and your good to go.

              Read this i think he knows what he’s talking about 😉 https://forums.fogproject.org/post/73883

              Regards X23

              ║▌║█║▌│║▌║▌█

              1 Reply Last reply Reply Quote 0
              • M
                Max Kern @Joe Schmitt
                last edited by

                @Joe-Schmitt I will do it tomorrow when im at work.

                1 Reply Last reply Reply Quote 0
                • M
                  Max Kern @Joe Schmitt
                  last edited by

                  @Joe-Schmitt Hi,
                  In this Textfile you see the Hardware of two diffrent machines, the Bluechip with the SSD work with the auto and delayed auto option, the HP 6300 Pro Clients with the WD Hdd only working with the delayed-auto option.
                  0_1469777655120_Spec 112 113.rtf
                  Unattend:
                  0_1469777856949_unattend.xml

                  SetupComplete:
                  sc config FOGService start= delayed-auto
                  net start FOGService

                  Software:
                  Windows 10 education 64 bit
                  Office 2016 32 bit
                  AndroidStudio
                  Eclipse IDE
                  VLC
                  OpenOffice
                  Chrome
                  Firefox
                  All updates of Office and Windows are installed, also it is the current Version of the other Software.

                  1 Reply Last reply Reply Quote 0
                  • J
                    Joe Schmitt Senior Developer
                    last edited by

                    Can you update your setup complete to restart as described in the updated wiki article?

                    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.

                    R 1 Reply Last reply Reply Quote 0
                    • R
                      RLane @Joe Schmitt
                      last edited by

                      @Joe-Schmitt I did. I’ve tried with the reboot - didn’t work. I’ve tried with automatic-delay - didn’t work either.

                      1 Reply Last reply Reply Quote 0
                      • J
                        Joe Schmitt Senior Developer
                        last edited by Joe Schmitt

                        @RLane are there any entries in fog.log?

                        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.

                        R 1 Reply Last reply Reply Quote 0
                        • R
                          RLane @Joe Schmitt
                          last edited by

                          @Joe-Schmitt There isn’t because the service is not starting until a manual reboot. In event viewer, it shows that the service failed to start after 3000 ms or something, failed twice like this.

                          Good news though… works well on an SSD. Any machine with a 7200 HDD, it doesn’t start the service in time. I haven’t had a computer fail yet with an SSD.

                          Wayne WorkmanW 1 Reply Last reply Reply Quote 0
                          • J
                            Joe Schmitt Senior Developer
                            last edited by

                            Yes I understand, I need to see if any entries are being made in the fog.log on the failed start.

                            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
                            • Wayne WorkmanW
                              Wayne Workman @RLane
                              last edited by

                              @RLane You can’t expect support for the new FOG Client without giving the senior developer of the new FOG Client a log, which he needs to give support.

                              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
                                Joe Schmitt Senior Developer
                                last edited by

                                The v0.11.5 release candidate should fix this issue. More testing needs to occur before I mark this as solved though.

                                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.

                                Tom ElliottT 1 Reply Last reply Reply Quote 0
                                • Tom ElliottT
                                  Tom Elliott @Joe Schmitt
                                  last edited by

                                  @Joe-Schmitt Do you think it’s safe to solve this thread?

                                  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.

                                  Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                                  Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                                  1 Reply Last reply Reply Quote 0
                                  • J
                                    Joe Schmitt Senior Developer
                                    last edited by

                                    v0.11.5 of the client prevents premature startups of the service. You will still need to disable the client before syprepping and restart the computer when sysprep is complete though (as described in the updated FOG Client wiki article).

                                    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
                                    • 1
                                    • 2
                                    • 2 / 2
                                    • First post
                                      Last post

                                    170

                                    Online

                                    12.0k

                                    Users

                                    17.3k

                                    Topics

                                    155.2k

                                    Posts
                                    Copyright © 2012-2024 FOG Project