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

HostnameChanger Hostname is correct

Scheduled Pinned Locked Moved Solved FOG Problems
12 Posts 3 Posters 3.0k Views
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.
  • D
    dolf
    last edited by dolf Jul 27, 2016, 12:37 AM Jul 27, 2016, 6:37 AM

    I’m having the same problem as this: HostNameChanger says hostname is correct

    Running Version 1.3.0-RC-1
    SVN Revision: 5936
    

    Ubuntu 14.04

    I added a bunch of new clients and imaged them last night. Identical hardware and images to what I already have in the lab. The log says:

    ------------------------------------------------------------------------------
    --------------------------------HostnameChanger-------------------------------
    ------------------------------------------------------------------------------
     2016/07/14 08:19 PM Client-Info Client Version: 0.11.3
     2016/07/14 08:19 PM Client-Info Client OS:      Windows
     2016/07/14 08:19 PM Client-Info Server Version: 8595
     2016/07/14 08:19 PM Middleware::Response Success
     2016/07/14 08:19 PM HostnameChanger Checking Hostname
     2016/07/14 08:19 PM HostnameChanger Hostname is correct
    ------------------------------------------------------------------------------
    

    But the hostname stays something like username-randomnumber.

    Output of http://lab2-server.ee.sun.ac.za/fog/service/ipxe/boot.php?mac=problematicmac:

    #!ipxe
    set fog-ip my.fog.server.ip
    set fog-webroot fog
    set boot-url http://${fog-ip}/${fog-webroot}
    sanboot --no-describe --drive 0x80
    

    I can log in as the local user and join the domain manually.

    1 Reply Last reply Reply Quote 0
    • J
      Joe Schmitt Senior Developer
      last edited by Aug 8, 2016, 9:03 PM

      v0.11.5 of the client prevents premature startups of the service. You will still need to disable the client before syprepping and restart the computer when sysprep is complete though (as described in the updated FOG Client wiki article).

      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 2
      • D
        dolf
        last edited by Jul 27, 2016, 12:21 PM

        Yes I am sysprepping. If I deploy the same image to a PC that was in my FOG db before, it works. The new PCs are also identical hardware to the ones we already had (Dell Optiplex 990 USFF). If I deploy to one of the new PCs, it doesn’t join the domain. One some of them (about 10%, at random) the hostname changes, but it never joins the domain.

        I’ve been running around, joining them manually today because it was urgent… 🙂

        I don’t know what “early hostname changer” is.

        1 Reply Last reply Reply Quote 0
        • J
          Joe Schmitt Senior Developer
          last edited by Jul 27, 2016, 12:23 PM

          @dolf If you are sysprepping is the client disabled on startup and then re-enabled in setup complete?

          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
          • W
            Wayne Workman
            last edited by Jul 27, 2016, 12:30 PM

            In addition to what Joe said,

            You have to disable the fog service before capture, and create a setupcomplete.cmd file that re-enables it and turns it on, and then capture your image.

            Early Hostname Changer must also be off for this to work right.

            details:
            https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

            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/

            1 Reply Last reply Reply Quote 1
            • D
              dolf
              last edited by Jul 27, 2016, 12:33 PM

              Ooh… Didn’t know that. My setupcomplete.cmd only deletes the unattend.xml file. I have nothing that touches the FOG Client in any way. Looks like I’ll have to change the image, then? I just installed the FOG Client without any further configuration, and it works for all PCs which were added to the FOG db last year.

              W 1 Reply Last reply Jul 27, 2016, 12:53 PM Reply Quote 0
              • J
                Joe Schmitt Senior Developer
                last edited by Jul 27, 2016, 12:35 PM

                @dolf if you can, after you update your image could you try deployments with early hostname changer both on and off? If I’m right the issues that early hostname changer had with sysprep should have been fixed.

                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.

                D 1 Reply Last reply Jul 27, 2016, 12:51 PM Reply Quote 1
                • D
                  dolf @Joe Schmitt
                  last edited by Jul 27, 2016, 12:51 PM

                  @Joe-Schmitt Will do!

                  Any idea why it would work for the old PCs but not the new ones? It find it strange.

                  1 Reply Last reply Reply Quote 0
                  • W
                    Wayne Workman @dolf
                    last edited by Jul 27, 2016, 12:53 PM

                    @dolf said in HostnameChanger Hostname is correct:

                    I just installed the FOG Client without any further configuration, and it works for all PCs which were added to the FOG db last year.

                    It’s a race condition. You were playing with fire and got lucky until now.

                    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/

                    1 Reply Last reply Reply Quote 0
                    • D
                      dolf
                      last edited by Jul 27, 2016, 12:55 PM

                      Thanks. Makes sense. Will fix my stuff.

                      1 Reply Last reply Reply Quote 0
                      • J
                        Joe Schmitt Senior Developer
                        last edited by Aug 8, 2016, 9:03 PM

                        v0.11.5 of the client prevents premature startups of the service. You will still need to disable the client before syprepping and restart the computer when sysprep is complete though (as described in the updated FOG Client wiki article).

                        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 2
                        • D
                          dolf
                          last edited by Aug 10, 2016, 2:58 PM

                          In @Joe-Schmitt’s second last message, the plan was to require no modification to setupcomplete.cmd. But the wiki still says I have to modify it. Which instructions should I follow?

                          W 1 Reply Last reply Aug 10, 2016, 3:01 PM Reply Quote 0
                          • W
                            Wayne Workman @dolf
                            last edited by Aug 10, 2016, 3:01 PM

                            @dolf The one marked as the answer. We keep the FOG Client article updated, because it’s important.

                            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/

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

                            151

                            Online

                            12.3k

                            Users

                            17.4k

                            Topics

                            155.7k

                            Posts
                            Copyright © 2012-2025 FOG Project