auto join. AD



  • I use the new fog 1.5.0. Got the imaging issues solved but I can not get the machines to auto join AD. Using the new client install I used the first line in fog settings / active directory settings/ and did not encrypt the password … also try to encrypt the password even tried the lagacy option using the encrypted password. None of these work. Is there another place to input this info besides fog settings/ active directory settings. Thanks



  • @joe-schmitt That fixed it. Thank you… Sometimes the most obvious gets overlooked.

    James P…



  • @joe-schmitt I was wandering about that. The ou was blank when I started the conversion to a new fog but I added it thinking I needed like the old version of fog.

    I will give you the results. when I try it again with the ou blank.


  • Senior Developer

    @jpaul Can you start back up the service (or restart the computer) and try clearing the OU field in the FOG interface? {yourdomain}.local as the OU could be causing some issues.



  • @joe-schmitt ran it again because I found the reset data encryption. This is the test it generated. The user name and password is correct.

    [mod note: removed log]


  • Senior Developer

    @jpaul when you ran middleware authentication handshake did it give you an error in the Debugger?



  • @joe-schmitt I went through the steps and there was no place to press reset Encryption Data. Ran the debugger and the text file only gave me this. Obviously it was encryted…

    0_1523550041181_FOGCycle.txt


  • Senior Developer

    @jpaul ok good, just wanted to make sure before we look at other things. So the next thing I want to make sure of is that the client is getting the right information from the server.

    Can you try the following steps on this problematic machine?

    • Open an administrative CMD, and run net stop fogservice
    • Navigate to your FOG server’s web portal, select the host you are working on and perform these steps:
      • Press Reset Encryption Data if its an option
    • Download our Debugger.exe and run it
    • The Debugger will open a console that has a fog: prompt, please enter these commands, pressing enter after each one:
      • middleware configuration server http://10.1.13.50/fog
      • middleware authentication handshake
      • dump cycle save

    The debugger should point you to a FOGCycle.txt file. This contains all the information the server tells the client, completely decrypted. Can you make sure the hostnamechanger section has the correct active directory login/OU information?

    To clean up:

    • Close the debugger
    • click Reset Encryption Data again on the host in the gui
    • start back up the fog service if you want


  • @joe-schmitt No the image was not joined to active directory ever… It was a clean image.


  • Senior Developer

    @jpaul was this machine imaged? If so, was the image itself joined to active directory?



  • @joe-schmitt The last line in the log under name changer section says the parameter is incorrect , code =87

    0_1523548195625_fog.log


  • Senior Developer

    @jpaul said in auto join. AD:

    sed the first line in fog settings / active directory settings/ and did not encrypt the password … also try to encrypt the password even tried the lagacy option using the encrypted password. None of these work. Is there another place to input this info besides fog settings/ active directory settings. Thanks

    The first place to look for debugging client issues is C:\fog.log on a computer with the issue. In the HostnameChanger section it should point to a reason why its not being added to active directory (feel free to attach your log file if you are having issues finding out why).


 

387
Online

41.2k
Users

11.6k
Topics

110.7k
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.