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

    reboot needed for FOG Client

    Scheduled Pinned Locked Moved Solved
    Windows Problems
    5
    17
    3.9k
    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.
    • MRCURM
      MRCUR Testers @ITCC
      last edited by

      @ITCC Try adding this to SetupComplete.cmd:

      net start FOGService

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

        @ITCC the log snippet you posted won’t cause any issues. That registry key simply can’t be set on certain configurations. There is something else stopping the client, can you post the whole 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.

        I 1 Reply Last reply Reply Quote 0
        • I
          ITCC @Joe Schmitt
          last edited by

          @Jbob
          Sure, Will do next time it happens. i’m deploying tests all day so it shouldn’t take long.

          1 Reply Last reply Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by

            @ITCC Any news on this?

            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
            • I
              ITCC
              last edited by

              Yep, sorry for the delay.

              Noticed that if you just reboot the machine it works next time. Seems to be the 1st full windows boot it doesn’t work (not always)

              I syspreped on 17/03/2016 @ 11:57 (so anything after is a deployment record)

              0_1458220821253_fog.log

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

                @ITCC is the service running when you perform the sysprep, or do you stop fogservice first?

                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
                • I
                  ITCC
                  last edited by

                  The service is still running.

                  1 Reply Last reply Reply Quote 0
                  • I
                    ITCC
                    last edited by

                    should I be stopping it 1st?

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

                      @ITCC It may be worth trying to stop the service before running the sysprep command. I am not sure if it will make any difference, but it’s worth a shot.

                      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
                      • george1421G
                        george1421 Moderator
                        last edited by george1421

                        While I didn’t read the entire thread (sorry being a bit lazy), so if this is a bit off-point just ignore me.

                        When we install the fog client through mdt, I’ll stop the service right away and then using sc set the service to disabled. We don’t want it mucking about with the reference image before we’re ready.

                        Then in the setupcomplete.cmd on the target (deployed) system we’ll use the sc command again to set it to auto start and then do the net start on the service. That way the seutp is fully done before the fog client is functional.

                        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!

                        1 Reply Last reply Reply Quote 1
                        • I
                          ITCC
                          last edited by

                          Sounds like a plan. I’ll complete anyway and report back next week sometime.

                          1 Reply Last reply Reply Quote 0
                          • S
                            Sebastian Roth Moderator
                            last edited by Sebastian Roth

                            @Jbob @ITCC While the OP is not new I somehow stumbled upon a missing backslash in the reg key just now!! Didn’t see that before. Shouldn’t it be SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerName\ComputerName (the OP missed the last one)…?

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

                              @Sebastian-Roth that registry key is perfectly fine. The reason it looks like it’s missing a backslash is because of a bug in the registry handler logging mechanism in pre-0.9.12. But even if it was missing that slash, that registry key will not affect anything of importance

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

                              228

                              Online

                              12.0k

                              Users

                              17.3k

                              Topics

                              155.2k

                              Posts
                              Copyright © 2012-2024 FOG Project