[fog] netdom driving me insane

[Chad]

Code 87 is a very unhelpful "The parameter is incorrect".

 

Is your OU field blank?

Make sure there are no trailing spaces at the end of any of the AD fields in FOG, I've seen that catch folk out before.

[sven]

I have been leaving the OU fields blank until I can actually get it to join the domain. I don't have any trailing spaces on any of the credentials. Really starting to bamboozle me now. I'm going to go home and relax before I throw something out a window. I appreciate your help on this.

 

Oh, if I take out the double slashes in the AD credentials in the FOG settings and the host settings, I get a different error:

 

24/05/2011 16:28 FOG::HostnameChanger AD mode requested, confirming settings.

24/05/2011 16:28 FOG::HostnameChanger Hostname is up to date

24/05/2011 16:28 FOG::HostnameChanger Attempting to join domain if not already a member....

24/05/2011 16:28 FOG::HostnameChanger Domain Error! ('Bad Netpath' Code: 53)

Edited May 24, 2011 by sven

[Chad]

The hostname settings should be copied from the default ones when you tick the "jojn AD" box but I've seen FOG "remember" the old host settings before (they're actually stored against each host in one of the tables). Try blanking all the domain boxes against the host, then unticking thejoin domain, then save. Then if you tick join domain again it should pull through the global settings.

 

I'd leave the username as domain\username (with domain in short name-only format) and make sure magic quotes is off in the php.ini file (restart apache if you make a change, assuming you're on a Linux box - don't know about the windows server setup)

[Chad]

btw, FOG doesn't give friendly test for some of the error codes, here's a few return values and what they mean:

 

5 = "Access is denied"

87 = "The parameter is incorrect"

110 = "The system cannot open the specified object"

1323 = "Unable to update the password"

1326 = "Logon failure: unknown username or bad password"

1355 = "The specified domain either does not exist or could not be contacted"

2224 = "The account already exists"

2691 = "The machine is already joined to the domain"

2692 = "The machine is not currently joined to a domain"

[sven]

Right, I've come in freshed face this morning, and looked at this from top to bottom. RESULT!

 

The "unknown parameter" error was because cause by the client being pointed to the wrong gateway. Once I changed the client back to DHCP, it worked straight away. No idea how I overlooked it, but I did. Thankyou so much for your help and suggestions. I'm only testing this at the moment, as I'll be putting together a new server and implementing this over summer in the IT rooms. This has been invaluable!