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

Host does not join AD Domain

Scheduled Pinned Locked Moved Solved
FOG Problems
2
3
493
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.
  • B
    BiologyBen
    last edited by Feb 19, 2018, 7:37 PM

    I’m certain there is some silly issue that is causing this - I’ve fixed our BIOS / NIC Boot issues, the Windows 2012 server DHCP options for UEFI, the Fog Service installation options and everything else seems to be running well - including installing a snap-in to the PC. I appreciate any help you can provide in solving this last issue!

    On a Dell OptiPlex 3050 micro running Windows 10, the Fog Service is installed and operational. It has changed the host name, installed a snapin, reboots on command, etc but does join PC to domain.

    I’ve checked that the ‘FogServer’ user & password will allow adding to domain manually, but does not join automatically.

    How do I verify that Fog is set-up correctly vs the possibility that some Group Policy or something on the server is preventing the join? Any suggestions would be appreciated - about to install 20 of these in our youth STEAM lab and this is the last hiccup!

    Thanks!

    SERVER

    FOG Version: 1.4.0
    OS: Ubuntu 16.04 as a VM on a Windows 2012r2 Server
    2012r2 server functions as DC, AD DS, DNS, DHCP

    CLIENT

    Service Version: 0.11.12 (Smart Installer)
    OS: Windows 7

    W 1 Reply Last reply Feb 19, 2018, 7:45 PM Reply Quote 0
    • W
      Wayne Workman @BiologyBen
      last edited by Wayne Workman Feb 19, 2018, 1:46 PM Feb 19, 2018, 7:45 PM

      @biologyben Whenever you have any issue with the FOG Client - the first step in troubleshooting is always to look at the fog log. Generally, it’s here: C:\fog.log If you can’t make sense of it, please post the last 200 or so lines here in a code-block so we can help. Of note: Any error codes that you find in the fog.log file are the actual error codes from what the FOG Client was doing - I.E. error codes from snapins are the error codes from the snapin, not the client. error codes from domain joining are from Windows, not the client. So you can Google these error codes yourself (it’s what we will do) to figure out what’s happening.

      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
      • B
        BiologyBen
        last edited by Feb 19, 2018, 9:35 PM

        Of course - checked the logs and I had the user name or password in wrong in fog. Had to be easy. Thanks!

        SERVER

        FOG Version: 1.4.0
        OS: Ubuntu 16.04 as a VM on a Windows 2012r2 Server
        2012r2 server functions as DC, AD DS, DNS, DHCP

        CLIENT

        Service Version: 0.11.12 (Smart Installer)
        OS: Windows 7

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

        178

        Online

        12.0k

        Users

        17.3k

        Topics

        155.2k

        Posts
        Copyright © 2012-2024 FOG Project