Hosts Unable to Join Domain

[herrpommesfrite]

I am running Fog Trunk 6677 on Ubuntu 14.??(sorry i can’t recall what release)

I just updated the client to the most recent release from the server and when it gets to the part to join the domain this is what the log says:

4/8/2016 11:50 AM Middleware::Communication Response: Success
4/8/2016 11:50 AM HostnameChanger Checking Hostname
4/8/2016 11:50 AM HostnameChanger Hostname is correct
4/8/2016 11:50 AM HostnameChanger Registering host with active directory
4/8/2016 11:50 AM HostnameChanger The system cannot open the specified object, code = 110

Previously i got a different error (1326)

Joining Active Directory has never worked for us and I’m trying to figure out why.
Thanks for any and all assistance

0_1460135941986_fog.log

[ITSolutions]

Can you join the machines manually using the AD username and password that you use have in FOG configuration? It looks to me that the 1326 was the username/password was wrong, now it looks like the account doesn’t have access to AD or at least the OU that use are trying to join to.

I would try manually add them with the account you use in FOG AD settings
Try a different AD account
Try a different OU setting in FOG or leave OU blank to just join to Computer OU

Also are you using the new client or old?

[herrpommesfrite]

@ITSolutions I was using the old client with the 1326 error the new client is giving the code = 100.
I have tried three different AD accounts, all of which will add hosts manually.
I have tried different OU settings as well.
Thank you for your suggestions.

[ITSolutions]

@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?

[herrpommesfrite]

@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.

[herrpommesfrite]

@ITSolutions I Have Upgraded to 7116 checked and double checked and changed the AD data and it still is not working.

[Tom Elliott]

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?

[herrpommesfrite]

I uninstalled the legacy client

[Tom Elliott]

Are you using OU’s?

[herrpommesfrite]

@Tom-Elliott Not in fog, I have left that blank.
More recent log file:
0_1460139473191_fog.log

[ITSolutions]

@herrpommesfrite Does the computer account exist in AD already? If so can you delete it and see if it joins then?

[herrpommesfrite]

@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.

[ITSolutions]

@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.

[herrpommesfrite]

This post is deleted!

[ITSolutions]

@herrpommesfrite Yes, it should be the same thing. Is there anything else installed on your image or is a clean win 7 image?

[herrpommesfrite]

@ITSolutions our usual programs nothing special

[Tom Elliott]

@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?

[herrpommesfrite]

@Tom-Elliott it is! it’s the same one i use everytime.

[Tom Elliott]

@herrpommesfrite what does it look like on the host?

[Tom Elliott]

@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.