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

Another Domain Join Issue

Scheduled Pinned Locked Moved Solved
FOG Problems
6
44
8.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.
  • G
    george1421 Moderator @Jay Bosworth
    last edited by Sep 13, 2019, 10:38 AM

    @Jay-Bosworth Its possible that changes in release 1903 have caused difficulties with the fog client. I’ve noticed a lot of posts regarding the fog client and 1903 lately. There has to be something going on that we don’t understand just jet.

    While I can’t really help with the fog level connect to domain, I can say that I don’t use the fog client for naming the host or connecting it to AD, I let the unattend.xml file do that. I don’t have a problem using this method.

    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!

    J 1 Reply Last reply Sep 13, 2019, 11:28 AM Reply Quote 0
    • Q
      Quazz Moderator @Jay Bosworth
      last edited by Sep 13, 2019, 11:15 AM

      @Jay-Bosworth That client is awaiting a scheduled reboot as far as I can tell, which is why other actions aren’t happening, you need to sort that out before any useful info is logged to begin with.

      1 Reply Last reply Reply Quote 0
      • J
        Jay Bosworth @george1421
        last edited by Sep 13, 2019, 11:28 AM

        @george1421 Thanks for the reply. That makes sense to me. I figured it has to be something small and new with 1903 because it never happened before and nothing on my server has changed. Luckily right now I only have a handful of machines to image and I can wait it out until a new version comes out or something. Worst case as you said, I can add it to my unattend file. Thanks again.

        1 Reply Last reply Reply Quote 0
        • S
          Sebastian Roth Moderator
          last edited by Sep 13, 2019, 3:58 PM

          @george1421 While we did have several requests about fog-client issues on Windows 10 1903 none of them had clearly to do with 1903 as far as I remember (feel free to prove me wrong on this - I have so many things going on and can’t follow it all 100%).

          @Jay-Bosworth From the logs posted so far I simply can’t see there being a fog-client issue. Don’t get me wrong. I am not saying there is none but we just have not nailed it down if there is 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 0
          • S
            Sebastian Roth Moderator
            last edited by Sep 14, 2019, 6:26 AM

            @Jay-Bosworth Ok, re-reading the whole topic again I think we should try to tackle this from scratch again:

            • Have the new 0.11.16 fog-client installed before capturing the image.
            • Exchange the file C:\Program Files (x64)\FOG\Modules.dll with the one downloaded here.
            • Make sure there is no task scheduled for the host you want to test this on (as we have seen in one of the fog.log files)!
            • Enable the checkbox to forced rename/join for this host (FOG web UI -> host list -> test host’s settings -> Active Directory tab -> Name Change/AD Join Forced reboot?

            Now deploy the machine, let it boot up, wait for it to do all the automatic background stuff plus another 10 minutes. Then grab a copy of fog.log and post here.

            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

            J 1 Reply Last reply Sep 18, 2019, 7:43 PM Reply Quote 0
            • J
              Jay Bosworth @Sebastian Roth
              last edited by Sep 18, 2019, 7:43 PM

              @Sebastian-Roth Okay, I am apparently a bit of a dolt, but it has led to another issue along the same lines… Let me explain.

              Somewhere between upgrading to the new FOG client 0.11.16 and capturing my audit image, I failed to create the scripts folder and add my setup complete file to it. FOG Service was remaining disabled, that is why the log file was recording no information.

              I took care of that and recaptured the image. Now when I deploy the image, it is not starting the FOG service it is setting the service to “automatic” but the service is never actually starting. Each time I go into the system after restarting, the FOG service is stopped. Is there something I needed to change in the setupcomplete file for the new FOG client?

              This is the contents of my setupcomplete file that I have been using flawlessly for the past several years:

              sc config FOGService start= auto
              shutdown -t 0 -r

              Thank you,

              1 Reply Last reply Reply Quote 0
              • S
                Sebastian Roth Moderator
                last edited by Sep 18, 2019, 7:46 PM

                @Jay-Bosworth try this (ref😞

                sc.exe config FOGService start=delayed-auto
                sc.exe failure FOGService actions= restart/60000/restart/60000/restart/ reset= 120
                

                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

                J 1 Reply Last reply Sep 19, 2019, 11:57 AM Reply Quote 0
                • J
                  Jay Bosworth @Sebastian Roth
                  last edited by Jay Bosworth Sep 19, 2019, 6:01 AM Sep 19, 2019, 11:57 AM

                  @Sebastian-Roth I replaced the code I had in my “setupcomplete” file with what you sent me in the previous message. I am still seeing the same behavior. After deploy, the Fog service is stopped even though it is set to Delayed-Automatic. When I try to start the Fog Service manually, it immediately stops. I don’t see anything in the FOG log that indicates why it is immediately stopping.

                  I went into Event viewer and here are the two errors it is showing when I try to start the service.

                  error2.jpg

                  error1.jpg

                  1 Reply Last reply Reply Quote 0
                  • S
                    Sebastian Roth Moderator
                    last edited by Sep 19, 2019, 12:50 PM

                    @Jay-Bosworth Can you please scroll further down in the message for the second event log entry where it says: “Exception Info: System.IO.FileNotFoundException” - does it say which file is not found??

                    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

                    J 1 Reply Last reply Sep 19, 2019, 1:16 PM Reply Quote 0
                    • J
                      Jay Bosworth @Sebastian Roth
                      last edited by Sep 19, 2019, 1:16 PM

                      @Sebastian-Roth Is this what you need?

                      error3.jpg

                      1 Reply Last reply Reply Quote 0
                      • S
                        Sebastian Roth Moderator
                        last edited by Sep 19, 2019, 2:57 PM

                        @Jay-Bosworth Do you have the file Modules.dll in C:\Program Files (x86)\FOG\??

                        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

                        J 2 Replies Last reply Sep 19, 2019, 3:07 PM Reply Quote 0
                        • J
                          Jay Bosworth @Sebastian Roth
                          last edited by Sep 19, 2019, 3:07 PM

                          @Sebastian-Roth Let me check that. I have had to change my audit and sysprep images so many times through this troubleshooting that it is possible I moved the file you sent into the folder and didn’t rename it to modules.dll.

                          1 Reply Last reply Reply Quote 0
                          • J
                            Jay Bosworth @Sebastian Roth
                            last edited by Sep 19, 2019, 5:15 PM

                            @Sebastian-Roth I think we are close. FOG is still not starting automatically though. I checked the event viewer and there are no errors there so I think it just isn’t getting the command to start as opposed to last time when it was trying but was erroring out. I tried starting it manually and then restarting and it does eventually start running in that case. Without doing that, I have been waiting about 45 minutes and the status hasn’t changed to running yet.

                            1 Reply Last reply Reply Quote 0
                            • S
                              Sebastian Roth Moderator
                              last edited by Sep 19, 2019, 8:36 PM

                              @Jay-Bosworth Do you have all the latest Windows updates installed on the image before capturing? Just asking because we have reports of the FOG client failing on systems where Windows Update kicks in.

                              It sounds strange that the service wouldn’t properly start by itself. Have not seen this before. Do other services start normally?

                              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

                              J 1 Reply Last reply Sep 20, 2019, 11:56 AM Reply Quote 0
                              • J
                                Jay Bosworth @Sebastian Roth
                                last edited by Sep 20, 2019, 11:56 AM

                                @Sebastian-Roth Yes, all of the Windows updates have been applied. I do all of that before I capture my audit image. I even double checked this time before I created it. Other services appear to be starting just fine.

                                1 Reply Last reply Reply Quote 0
                                • S
                                  Sebastian Roth Moderator
                                  last edited by Sep 20, 2019, 12:41 PM

                                  @Jay-Bosworth Do you see if the service is starting and crashing over and over again?

                                  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

                                  J 1 Reply Last reply Sep 20, 2019, 5:08 PM Reply Quote 0
                                  • J
                                    Jay Bosworth @Sebastian Roth
                                    last edited by Sep 20, 2019, 5:08 PM

                                    @Sebastian-Roth No, nothing in the event viewer like the last time. Like I said, if I manually start the service the first time it then automatically starts after about ten minutes or so on subsequent reboots.

                                    D 1 Reply Last reply Sep 23, 2019, 12:56 PM Reply Quote 0
                                    • D
                                      David Osinski @Jay Bosworth
                                      last edited by David Osinski Sep 23, 2019, 6:58 AM Sep 23, 2019, 12:56 PM

                                      @Jay-Bosworth
                                      Jay on a side note while the guys are trying to troubleshoot the problem with services, ect., can you go ahead and try to spin up a new virtual machine and load widows from scratch. Mabey every try audit mode again but dont disable services (i never do and it works perfect) like you mentioned in your original post. Just install fog client and %WINDIR%\system32\sysprep\sysprep.exe /generalize /shutdown /oobe
                                      If your running a unattended.xml, please make sure your not doing post scripts for the test. Just try to make it as bare bones as possible. This will test to make sure
                                      1 your fog enviroment is running functionally
                                      2 you are building your windows images correctly

                                      If it works, you need to evaluate on how your building your images.
                                      If it doesnt work, then im going to leave it to the other guys

                                      J 1 Reply Last reply Sep 23, 2019, 5:42 PM Reply Quote 1
                                      • J
                                        Jay Bosworth @David Osinski
                                        last edited by Sep 23, 2019, 5:42 PM

                                        @David-Osinski Okay, I can try to start from scratch. It has been working fine for years with dozens of images that I created, so I am pretty sure that process is fine. I might have missed something on the past two I created, but I kind of doubt it. The only thing that is really different this time is the addition of the 1903 update.

                                        1 Reply Last reply Reply Quote 0
                                        • J
                                          Jay Bosworth
                                          last edited by Sep 23, 2019, 6:55 PM

                                          I think we can chalk this one up as solved. I went back to my original audit image and I undid pretty much everything I had tried with the exception of using the newer FOG client. With my original SetupComplete file and everything else back to the way it was, it seems to be working now.

                                          I truly believe the fix was just a matter of updating the FOG client to 11.16 I apologize for all of the hassle but I appreciate all of the help you tried to give me.

                                          1 Reply Last reply Reply Quote 3
                                          • 1
                                          • 2
                                          • 3
                                          • 2 / 3
                                          2 / 3
                                          • First post
                                            31/44
                                            Last post

                                          140

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project