Hosts Unable to Join Domain
-
@herrpommesfrite I know there has been a few updates with the client and I think one since 6677 that you are on, can you try updating to the latest as of now it looks like 7114. Also you might want to double check your settings in FOG.
- Make sure that the domain name is correct no spaces in front or behind the name “domain.com”
- Usename, for the new client doesn’t like the “domain\username” set up, should be just “username”
- The password needs to be entered in the FOG_AD_DEFAULT_PASSWORD field, best to clear the Legacy field just for sake of not needing it. There is no encrypting the password before entering it like in the old client setup. So enter the password in plain text and it will encrypt on save.
- For Testing purposes I would remove all OU settings, just to be sure that it isn’t an issue with a setting.
According to Microsoft and the error that you receive it is pointing toward a permissions issue with the account.
I know some of those steps seem simple but I have had many times I banged my head against a wall to solve a typo I made that I overlooked a million times.
Oh and a question I forgot to ask, what OS are you using, win7, 10, 8?
-
@ITSolutions I have re entered all relevant data and double checked for spelling. I will update fog in a little bit.
I am on Win7 32b Pro.
-
@ITSolutions I Have Upgraded to 7116 checked and double checked and changed the AD data and it still is not working.
-
The information in the log appears to be from two different instances of the fog client.
Do you still have the “Old client” installed along with the “New client” on the same machine?
-
I uninstalled the legacy client
-
Are you using OU’s?
-
@Tom-Elliott Not in fog, I have left that blank.
More recent log file:
0_1460139473191_fog.log -
@herrpommesfrite Does the computer account exist in AD already? If so can you delete it and see if it joins then?
-
@ITSolutions It does not this is a fresh image made strictly to test domain joining. The new client was installed after the old was removed if that makes any difference.
-
@herrpommesfrite That shouldn’t make a difference. If the old client was uninstalled then it shouldn’t cause any issues with the new client. Can you try changing the host name in FOG to something new, just name it “adtest”. I am just trying to rule out all possibilities.
-
This post is deleted! -
@herrpommesfrite Yes, it should be the same thing. Is there anything else installed on your image or is a clean win 7 image?
-
@ITSolutions our usual programs nothing special
-
@herrpommesfrite the user you have for joining domain should have the proper permissions to join to the domain to begin with. Is this already the case?
-
@Tom-Elliott it is! it’s the same one i use everytime.
-
@herrpommesfrite what does it look like on the host?
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.
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
@Tom-Elliott also please try updating. Maybe there were extra characters passed in older versions? I don’t know but I know of it were broken if have been made well aware of it.
-
@Tom-Elliott What do you mean “what does it look like on the host?” I updated the server to 7116. and am using client v0.9.12.
-
@herrpommesfrite in the GUI. What does one of these hosts ad settings look like?
-
This post is deleted!
