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

    Not Joining to Domain after imaging

    Scheduled Pinned Locked Moved
    FOG Problems
    3
    4
    1.1k
    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.
    • Q
      quinniedid
      last edited by

      Running Version 1.4.0
      SVN Revision: 6069

      After deploying an image (Windows 10), the PC is not joining the domain even though I have it set to at the group and I can see the settings on the individual device as well.

      I have tried the troubleshooting here: https://wiki.fogproject.org/wiki/index.php/Active_Directory_-_FOG_Setting

      Is gives me that netdom does not exist.

      Any ideas? Any other troubleshooting I can try?

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

        That article is aged, it should probably be taken down.

        Look at the fog log - normally it explicitly tells you what the issue is on one of the error lines. This log is located on the target machine you’re working with usually at C:\fog.log Feel free to copy/paste it here - use the code-wrap tool if you do.

        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
        • Q
          quinniedid
          last edited by

          I have figured this out. The client that is on the image is pointing to an old FOG server. Is there a way to change the settings on the machine somewhere to the new IP address? Also do I have to use an IP address or can I use an FQDN?

          AvaryanA 1 Reply Last reply Reply Quote 0
          • AvaryanA
            Avaryan @quinniedid
            last edited by

            @quinniedid There is a .msi version of the client that you could use to install the newer client with the correct address. Unsure if old client would need uninstalled first.

            If you have a way to push out a PowerShell script, something like this might help.

            $FOG = Get-WmiObject -Class Win32_Product | Where-Object -Property Name -EQ 'FOG Service'
            $FOG.Uninstall()
            
            $url = "http://<ip address>/fog/client/download.php?newclient"
            $outfile = "FOGService.msi"
            (New-Object System.Net.WebClient).DownloadFile($url, $outfile)
            
            $ArgumentList = "/i $outfile /quiet USETRAY=""0"" WEBADDRESS=""<ip address>"" WEBROOT=""/fog"" /norestart"
            Start-Process -FilePath MSIEXEC.exe -ArgumentList $ArgumentList -Wait
            
            Start-Service -Name FOGService
            Start-Sleep -Seconds 2
            Restart-Computer -Force
            
            1 Reply Last reply Reply Quote 0
            • 1 / 1
            • First post
              Last post

            156

            Online

            12.0k

            Users

            17.3k

            Topics

            155.2k

            Posts
            Copyright © 2012-2024 FOG Project