• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • 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.
  • J
    JoeG @JoeG
    last edited by Jun 16, 2016, 6:03 PM

    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
    • M
      Matthieu Jacquart
      last edited by Jun 16, 2016, 6:05 PM

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

      Fog 1.5.9.138
      Debian 11
      Vmware ESXi

      M 1 Reply Last reply Jun 20, 2016, 7:59 AM Reply Quote 0
      • M
        Matthieu Jacquart @Matthieu Jacquart
        last edited by Jun 20, 2016, 7:59 AM

        @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

        T 1 Reply Last reply Jun 20, 2016, 10:45 AM Reply Quote 0
        • T
          Tom Elliott @Matthieu Jacquart
          last edited by Jun 20, 2016, 10:45 AM

          @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

          M 1 Reply Last reply Jun 20, 2016, 11:05 AM Reply Quote 1
          • M
            Matthieu Jacquart @Tom Elliott
            last edited by Jun 20, 2016, 11:05 AM

            @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

            W 1 Reply Last reply Jun 20, 2016, 10:35 PM Reply Quote 0
            • W
              Wayne Workman @Matthieu Jacquart
              last edited by Jun 20, 2016, 10:35 PM

              @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/

              M 1 Reply Last reply Jun 21, 2016, 7:08 AM Reply Quote 0
              • M
                Matthieu Jacquart @Wayne Workman
                last edited by Jun 21, 2016, 7:08 AM

                @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
                • T
                  Tom Elliott
                  last edited by Jun 29, 2016, 10:07 AM

                  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

                  M 1 Reply Last reply Jun 29, 2016, 11:08 AM Reply Quote 0
                  • M
                    Matthieu Jacquart @Tom Elliott
                    last edited by Jun 29, 2016, 11:08 AM

                    @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 Jun 30, 2016, 7:45 AM Reply Quote 0
                    • C
                      Claude Girard @Matthieu Jacquart
                      last edited by Jun 30, 2016, 7:45 AM

                      @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

                      181

                      Online

                      12.0k

                      Users

                      17.3k

                      Topics

                      155.2k

                      Posts
                      Copyright © 2012-2024 FOG Project