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

    PC rename/Join domain task

    Scheduled Pinned Locked Moved
    Feature Request
    3
    5
    1.9k
    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.
    • netbootdiskN
      netbootdisk
      last edited by

      Hello
      Can I wish for a task button where by a computer can be forced to rename itself & join the domain again?

      Much like the ‘Configuration Task’ (?) back in Ghost Solution Suite.

      This would be handy for any machines that decide not to rename/join domain for whatever reason. Be easier to kick this off rather than an entire reimage.

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

        With the current setup the computer always tries to rename & join itself every boot-up. The only case where renaming doesn’t happen is if the service detects the name is already correct. What situation are you encountering which provides the 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.

        1 Reply Last reply Reply Quote 0
        • netbootdiskN
          netbootdisk
          last edited by

          Imaged a lab of 25, and I had 5 machines fail to rename. Kicking them off again they then decide to work fine. Seems to be happening randomly - i am having to double check that everything has actually finished / domain joined correctly still.

          Logging in to the failed machines locally, they still have the sysprep generated PC name.

          Changing the FOG rename early setting hasn’t made any difference.

          1 Reply Last reply Reply Quote 0
          • JunkhackerJ
            Junkhacker Developer
            last edited by

            do these computers have SSD’s? you may need to set the fog service to delayed start. some systems start the service and it tries to do it’s thing before the rest of the system is able to handle it. or, alternatively, update to the latest SVN where we have a workaround for this implemented on the serverside

            signature:
            Junkhacker
            We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

            1 Reply Last reply Reply Quote 0
            • netbootdiskN
              netbootdisk
              last edited by

              No SSD drives, they are standard Optiplex 3010’s. Will give the delayed started trick a go.

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

              223

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project