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

    AD Join/Hostname changer not working

    Scheduled Pinned Locked Moved
    FOG Problems
    3
    3
    737
    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.
    • Scott AdamsS
      Scott Adams
      last edited by

      Running Ubuntu 14.04, FOG Trunk 7252.

      Have set Active directory settings in FOG Configuration. I put plain text password into the field for the new client, and the encrypted FOGCrypt password for the legacy client (I do not have any legacy clients out there though).

      After an image, the computer never joins the domain. If I try to rename the computer in FOG, the computer never restarts to change the name.

      Not sure what’s going on, but I have noticed that the new client AD password is different on every host that I look at. I know it is encrypted, but the encrypted password is different for every host. The legacy password is always the same. Is this normal? Doesn’t make sense to me why the password would be different for each host.

      1 Reply Last reply Reply Quote 0
      • J
        Joe Schmitt Senior Developer
        last edited by

        @Scott-Adams each host has its own copy of the AD password, and each one is encrypted with AES, where the same message can have different encrypted outputs (this is because of a unique initialization vector). As for the client not working, I would need to see a log file of one of the hosts which doesn’t work to help further.

        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 3
        • PsycholiquidP
          Psycholiquid Testers
          last edited by Psycholiquid

          A cool little way I track what is going on for the clients when that is happening (That @Tom Elliott showed me )

          Open powershell and type: get-content -wait C:\fog.log (or wherever you have the log stored.)

          this will let you see what it is doing while it is doing it. Depending on the error it can lead you in the right direction.

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

          247

          Online

          12.0k

          Users

          17.3k

          Topics

          155.2k

          Posts
          Copyright © 2012-2024 FOG Project