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

    Hostname changer is unable to rename computer

    Scheduled Pinned Locked Moved Solved
    Bug Reports
    5
    18
    5.7k
    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.
    • Matthieu JacquartM
      Matthieu Jacquart
      last edited by

      I confirm, if I delete host from AD before deployment it seems ok, but if I forgot it’s impossible to rename computer.
      It worked few weeks ago.

      Fog 1.5.9.138
      Debian 11
      Vmware ESXi

      1 Reply Last reply Reply Quote 0
      • JoeGJ
        JoeG
        last edited by JoeG

        I am experiencing the same problem with hostname changer not renaming the computer. Running trunk SVN 5673. I do not bind to AD during deployment.

        Additional info: I disable the FOG client service, sysprep, then capture the image. In my SetupComplete.cmd script I have included

        sc config FOGService start= auto
        net start FOGService
        

        This was necessary in order to avoid the “Windows could not complete the installation…” error but I wonder if this is keeping Hostname Changer from succeeding.

        Hostname Changer excerpt from fog.log on target machine, full log attached. The name should be MELLON

        ------------------------------------------------------------------------------
        --------------------------------HostnameChanger-------------------------------
        ------------------------------------------------------------------------------
         6/16/2016 9:20 AM Client-Info Client Version: 0.10.6
         6/16/2016 9:20 AM Client-Info Client OS:      Windows
         6/16/2016 9:20 AM Client-Info Server Version: 8088
         6/16/2016 9:20 AM Middleware::Response Success
         6/16/2016 9:20 AM HostnameChanger Users still logged in and enforce is disabled, delaying any further actions
        ------------------------------------------------------------------------------
        

        0_1466084279687_fog.log

        FOG 1.3.0-RC-8, Ubuntu 14.04 LTS

        Wayne WorkmanW Matthieu JacquartM 2 Replies Last reply Reply Quote 0
        • Wayne WorkmanW
          Wayne Workman @JoeG
          last edited by

          @JoeG If the fog client is indeed starting as it should post-sysprep, then no there should be no problems. I’ll tell you like we tell everyone here - we need the fog client log to really help in any sort of valuable way. It’s here on the host: c:\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!
          Daily Clean Installation Results:
          https://fogtesting.fogproject.us/
          FOG Reporting:
          https://fog-external-reporting-results.fogproject.us/

          JoeGJ 1 Reply Last reply Reply Quote 0
          • Matthieu JacquartM
            Matthieu Jacquart @JoeG
            last edited by

            @JoeG Hi, I disabled fogservice before sysprep and create cmd in c:\windows\setup\scripts, it works for activating fogservice but hostanme changer still having problem… I’ll try to do more test today and I come back with fog.log
            Important question : I use <ComputerName>*</ComputerName> in Sysprep, is it a good thing to do or it’s better to remove it ?
            Same for fog options “FOG_CHANGE_HOSTNAME_EARLY”, it’s uncheck, is it ok ?

            Fog 1.5.9.138
            Debian 11
            Vmware ESXi

            1 Reply Last reply Reply Quote 0
            • JoeGJ
              JoeG @Wayne Workman
              last edited by

              @Wayne-Workman sorry for forgetting the logs, it is now included in my original post below. I appreciate any insight, let me know what other info I can share. Thanks!

              FOG 1.3.0-RC-8, Ubuntu 14.04 LTS

              JoeGJ 1 Reply Last reply Reply Quote 0
              • JoeGJ
                JoeG @JoeG
                last edited by

                I have continued testing today and the hostname is changing correctly. I unchecked “FOG_CHANGE_HOSTNAME_EARLY” in FOG Settings. Sorry for the false alarm!

                FOG 1.3.0-RC-8, Ubuntu 14.04 LTS

                1 Reply Last reply Reply Quote 0
                • Matthieu JacquartM
                  Matthieu Jacquart
                  last edited by

                  It seems ok for me too (tested on one computer) with fogservice disabled before sysprep

                  Fog 1.5.9.138
                  Debian 11
                  Vmware ESXi

                  Matthieu JacquartM 1 Reply Last reply Reply Quote 0
                  • Matthieu JacquartM
                    Matthieu Jacquart @Matthieu Jacquart
                    last edited by

                    @Matthieu-Jacquart So it’s not ok 😞
                    I deployed 20 computers this morning, windows 10, removed from AD before deployment.
                    Result : AD integration for all of them, but only 3 were able to have the right name.
                    For the 17 others, random name.

                    For example computer name “BOIS-64RNM4FT88” in AD :

                    ------------------------------------------------------------------------------
                    --------------------------------HostnameChanger-------------------------------
                    ------------------------------------------------------------------------------
                     20/06/2016 09:52 Client-Info Client Version: 0.11.0
                     20/06/2016 09:52 Client-Info Client OS:      Windows
                     20/06/2016 09:52 Client-Info Server Version: 8169
                     20/06/2016 09:52 Middleware::Response Success
                     20/06/2016 09:52 HostnameChanger Checking Hostname
                     20/06/2016 09:52 HostnameChanger Removing host from active directory
                     20/06/2016 09:52 HostnameChanger Success, code =  0
                     20/06/2016 09:52 Power Creating shutdown request
                     20/06/2016 09:52 Power Parameters: /r /c "Host left active directory, restart needed" /t 0
                     20/06/2016 09:52 HostnameChanger Renaming host to S085P01
                     20/06/2016 09:52 Power Creating shutdown request
                     20/06/2016 09:52 Power Parameters: /r /c "FOG needs to rename your computer" /t 0
                     20/06/2016 09:52 HostnameChanger Success, code =  0
                     20/06/2016 09:52 Power Creating shutdown request
                     20/06/2016 09:52 Power Parameters: /r /c "Host joined to Active Directory, restart required" /t 0
                    ------------------------------------------------------------------------------
                    

                    But even after multiple reboot, “S085P01” name never appears in AD…

                    There’s line <ComputerName>*</ComputerName> in sysprep, is it really necessary ?

                    Fog 1.5.9.138
                    Debian 11
                    Vmware ESXi

                    Tom ElliottT 1 Reply Last reply Reply Quote 0
                    • Tom ElliottT
                      Tom Elliott @Matthieu Jacquart
                      last edited by

                      @Matthieu-Jacquart That line (<ComputerName>*</ComputerName>) creates the system with a very random name.

                      From @joe-schmitt:

                      early_hostname_changer + sysprep + client issues
                      Basically this is what was happening:
                      early hostname changer runs
                      Hostname is now updated
                      Sysprep runs, changes it but not fully
                      A reboot is needed
                      Client runs, and according to its checks hostname is right
                      So joins to ad
                      Reboots
                      Hostname is now wrong, and ad is joined
                      So client re-joins
                      Requiring 3 more reboot

                      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

                      Matthieu JacquartM 1 Reply Last reply Reply Quote 1
                      • Matthieu JacquartM
                        Matthieu Jacquart @Tom Elliott
                        last edited by

                        @Tom-Elliott ok, I understood how works ComputerName in sysprep, but I wonder if it’s a good or bad idea to have it in syprep with fog deployment…
                        Same thing for early hostname changer, do I have to check it (uncheck for me) ?

                        2 hours later I have 3 more PC with right name in AD, but still 14 with random name…

                        Fog 1.5.9.138
                        Debian 11
                        Vmware ESXi

                        Wayne WorkmanW 1 Reply Last reply Reply Quote 0
                        • Wayne WorkmanW
                          Wayne Workman @Matthieu Jacquart
                          last edited by

                          @Matthieu-Jacquart said in Hostname changer is unable to rename computer:

                          but still 14 with random name…

                          Is it possible to confirm that the client is doing it’s job without sysprep involved at all? Can we do this just as a test?

                          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/

                          Matthieu JacquartM 1 Reply Last reply Reply Quote 0
                          • Matthieu JacquartM
                            Matthieu Jacquart @Wayne Workman
                            last edited by

                            @Wayne-Workman Done, I renamed a computer and disjoined AD, after that AD integration is good but not the name…
                            0_1466492917005_fog.log

                            Fog 1.5.9.138
                            Debian 11
                            Vmware ESXi

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

                              Is this still an 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.

                              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

                              Matthieu JacquartM 1 Reply Last reply Reply Quote 0
                              • Matthieu JacquartM
                                Matthieu Jacquart @Tom Elliott
                                last edited by

                                @Tom-Elliott I hope it’s resolved with last client but I can’t be sure…
                                You can close the case, I couldn’t test more before mid-august…

                                Fog 1.5.9.138
                                Debian 11
                                Vmware ESXi

                                C 1 Reply Last reply Reply Quote 0
                                • C
                                  Claude Girard @Matthieu Jacquart
                                  last edited by

                                  @Matthieu-Jacquart said in Hostname changer is unable to rename computer:

                                  @Tom-Elliott I hope it’s resolved with last client but I can’t be sure…
                                  You can close the case, I couldn’t test more before mid-august…

                                  Yes I can confirm, client 0.11.2 resolves this issue

                                  1 Reply Last reply Reply Quote 0
                                  • 1 / 1
                                  • First post
                                    Last post

                                  149

                                  Online

                                  12.0k

                                  Users

                                  17.3k

                                  Topics

                                  155.2k

                                  Posts
                                  Copyright © 2012-2024 FOG Project