• 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.
  • S
    Sebastian Roth Moderator
    last edited by Sep 9, 2019, 5:28 PM

    @Jay-Bosworth Before you deploy your next machine may I ask you to use this debug enabled Modules.dll so we get more helpful output in the log file: https://github.com/FOGProject/fog-client/releases/download/0.11.16/Modules_debug_HostnameChanger.dll

    Stop FOGService (Windows services.msc), then go to C:\Program Files (x86)\FOG\ and rename Modules.dll. Now download the one from above and put in place of the original one. Now capture your master image from that machine and deploy to another host. Please grab fog.log after deployment and post the full contents 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 9, 2019, 5:48 PM Reply Quote 0
    • J
      Jay Bosworth @Sebastian Roth
      last edited by Sep 9, 2019, 5:48 PM

      @Sebastian-Roth Oh crap, I already captured my image already. I am running out of time today, so I might not be able try and create a whole new image again until tomorrow.

      1 Reply Last reply Reply Quote 0
      • S
        Sebastian Roth Moderator
        last edited by Sep 9, 2019, 5:59 PM

        @Jay-Bosworth There is an easy way around this. Don’t start the host immediately after you deployed the image to it. Copy the downloaded Modules.dll to a USB drive. Then schedule another debug deploy task for this same host, PXE boot it and when you get to the shell run the following commands (assuming your hard disk drive is /dev/sda and your USB drive is /dev/sdb😞

        mkdir -p /mnt/usb
        mkdir -p /mnt/win
        mount /dev/sdb1 /mnt/usb
        mount /dev/sdaX /mnt/win
        cd /mnt/win/Program\ Files\ \(x86\)/FOG/
        mv Modules.dll Modules_orig.dll
        cp /mnt/usb/Modules.dll .
        cd
        umount /mnt/win
        umount /mnt/usb
        

        Something along these lines. This is untested and I can’t promise you it’s working exactly like this as I don’t know your partition layout or drive specs.

        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

        G 1 Reply Last reply Sep 9, 2019, 7:48 PM Reply Quote 0
        • G
          george1421 Moderator @Sebastian Roth
          last edited by Sep 9, 2019, 7:48 PM

          @Sebastian-Roth @Jay-Bosworth Understand I’ve only read the last 2 posts, so I’m not sure where the thread is headed.

          BUT I can offer a comment. During Windows golden image development I’ve used a modified post download script (similar to the one for sending the drivers to the target computer) to patch the unattend.xml and replace dlls in a previously captured image. I only did this during golden image development or until the next time I built a golden image.

          The principles of this is outlined in this article: https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed

          The fog.copydrivers script could be modified to just copy over the one needed file from the fog server. In this section. Where clientdriverpath is the destination path and remotedriverpath is the path of the files to copy.

          dots "Preparing Drivers"
          clientdriverpath="/ntfs/Drivers"
          remotedriverpath="/images/drivers/$machine/$osn/$arch"
          
          debugPause
          
          if [[ ! -d "${remotedriverpath}" ]]; then
              echo "failed";
              echo " ! Driver package not found for ${machine}/$osn/$arch ! ";
              debugPause;
              return;
          fi
          echo "Ready";
          
          debugPause
          
          [[ ! -d $clientdriverpath ]] && mkdir -p "$clientdriverpath" >/dev/null 2>&1
          echo -n "In Progress"
          
          rsync -aqz "$remotedriverpath" "$clientdriverpath" >/dev/null 2>&1
          
          [[ ! $? -eq 0 ]] && handleError "Failed to download driver information for [$machine/$osn/$arch]"
          
          debugPause
          
          

          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
          • J
            Jay Bosworth
            last edited by Sep 11, 2019, 1:01 PM

            I apologize, I had to put this on the back burner for a couple of days. It is the beginning of the school year and things are nuts. I am starting to wonder if it does have something to do with my Sysprep process and changes between 17xx and 19xx that the file doesn’t like. When I pushed my audit image to remove the older FOG client and install the newer one, I forgot to uncheck the box in FOG that says “Name Change/AD Join Forced Reboot”. As soon as I installed the new FOG client on the audit image, it joined itself to the domain. I wiped it back to my original audit image and followed the same process but I first unchecked that box. I uploaded my audit image and then rechecked that box before uploading my sysprepped image. Upon deploy the sysprep image will still not automatically join to my domain.

            1 Reply Last reply Reply Quote 0
            • S
              Sebastian Roth Moderator
              last edited by Sep 11, 2019, 1:25 PM

              @Jay-Bosworth said in Another Domain Join Issue:

              Upon deploy the sysprep image will still not automatically join to my domain.

              Did you use the Modules.dll I provided? Please check the fog.log file on the client an 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 2 Replies Last reply Sep 11, 2019, 1:37 PM Reply Quote 0
              • J
                Jay Bosworth @Sebastian Roth
                last edited by Sep 11, 2019, 1:37 PM

                @Sebastian-Roth No, this was just something I noticed before you posted that request. Sorry, like I said, things have been nuts and I am a couple of days behind to work on this.

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

                  @Sebastian-Roth I apologize for the log delay in this. Here is the file after I used the other Modules.dll file.fog.log

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

                    @Jay-Bosworth Sorry but there is no valuable information in that log. every loop cycle on hostname changer is either “Users still logged in and enforce is disabled, delaying any further actions” or “A power operation is pending, aborting module” (offical scheduled reboot via fog-client). We can’t help you if we don’t see what’s exactly going on when it tries to join.

                    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 13, 2019, 10:27 AM Reply Quote 0
                    • J
                      Jay Bosworth @Sebastian Roth
                      last edited by Sep 13, 2019, 10:27 AM

                      @Sebastian-Roth So that’s it? I am just SOL? I can’t really change what it is doing automatically. I did exactly what you asked me to.

                      G Q 2 Replies Last reply Sep 13, 2019, 10:38 AM Reply Quote 0
                      • 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
                                          • 1
                                          • 2
                                          • 3
                                          • 2 / 3
                                          2 / 3
                                          • First post
                                            21/44
                                            Last post

                                          160

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project