[fog] netdom driving me insane

[stevehp]

Hello all,

 

Have a bit of a issue with netdom and Fog. I've entered all of the details in the settings for Active Directory in Fog as well as encrypting the password with fogcrypt(multiple times). The issue is that the hostname will change, but it will not join the domain. The log file for Fog says "netdom output: Dns name contains an invalid character." So I'm a bit stumped. Which dns name is netdom referring to? If it's the computer name I've already tried a simple name of "test" and it failed. The regular host name was fourteen characters with characters that aren't invalid at all, so I'm at a loss as to what the issue could be. After futzing with this for over an hour and a half I'm just going to leave off the auto domain join stuff and do it manually as it's already been too much of a time waster.

 

If anyone has any suggestions I'd be more than glad to hear them.

 

Cheers

[maniac]

Check you're using the FQDN when specifying the domain for FOG to join clients to, e.g 'school.local' and not just 'school'.

 

Also make sure you haven't accidently typed a space at the end of the domain name in FOG, this caused an issue for me when I first set it up.

 

Mike.

[stevehp]

Check you're using the FQDN when specifying the domain for FOG to join clients to, e.g 'school.local' and not just 'school'.

 

Also make sure you haven't accidently typed a space at the end of the domain name in FOG, this caused an issue for me when I first set it up.

 

Mike.

 

I finally cracked it. The documentation led me to believe that the Active Directory settings in FOG needed to be LDAP formatted. I come to figure out it's not. I either misread the wiki or it needs to be combed over for more errors and or mistakes.

 

Thanks for the suggestions Mike I appreciate it.

Edited February 3, 2010 by stevehp

[maniac]

I finally cracked it. The documentation led me to believe that the settings in Active Directory section in the Fog Settings needed to be ldap formatted. I come to figure out it's not. I either misread the wiki or it needs to be combed over for more errors and or mistakes.

 

Thanks for the suggestions Mike I appreciate it.

 

No worries, there's a little thanks button at the bottom of my post, feel free to press it

 

Mike.

[7andY]

I finally cracked it. The documentation led me to believe that the Active Directory settings in FOG needed to be LDAP formatted. I come to figure out it's not. I either misread the wiki or it needs to be combed over for more errors and or mistakes.

 

Thanks for the suggestions Mike I appreciate it.

 

Just starting with FOG. Set up the AD bit OU=nnn,DC=nnn,DC=nnn etc. Is this not right? And, if it ain't, what should it be??

 

Cheers, Andy E.

[katie.lawe]

We are just starting with Fog and are having similar issues with the machines not joining the domain. Does anyone have any examples of what they put into their AD settings?

 

We have tried encrypted and un-encrypted passwords and am just not getting anywhere. It would save so much time if we could get this working.

 

Thanks

Kate

[morganw]

On the 'Fog Settings' page I've entered

 

FOG_AD_DEFAULT_DOMAINNAME: school.internal

FOG_AD_DEFAULT_OU: -I leave this blank-

FOG_AD_DEFAULT_USER: school\FogADUserAccount

FOG_AD_DEFAULT_PASSWORD: -here you paste in the output from the fog password encryptor-

 

Now when registering the client either check the box in the user interface next to 'Join Domain after image task', the other boxes will populate with the default values, or the same thing will happen if you register the computer through the PXE boot menu, just answer 'y' at the appropriate point.

 

I thought the active directory join was broken on my system but in actual fact I had just forgotten to check the box in the user interface. For debugging check the output of the log file in C:\fog.log.

Edited August 5, 2010 by morganw

[morganw]

...and, you have to delegated the management of computer objects to the fog AD account so that computers can join, you could always test with the domain administrator account and password just to see if that is the problem.

[oxide54]

...and, you have to delegated the management of computer objects to the fog AD account so that computers can join, you could always test with the domain administrator account and password just to see if that is the problem.

 

yes definitely check that, we don't use FOG (yet!) but we found with ghost/sysprep that the delegated account didn't always work. we also found this worked better with the FQDN of the domain instead of the netbios name.

[dhicks]

FOG_AD_DEFAULT_DOMAINNAME: school.internal

FOG_AD_DEFAULT_OU: -I leave this blank-

FOG_AD_DEFAULT_USER: school\FogADUserAccount

FOG_AD_DEFAULT_PASSWORD: -here you paste in the output from the fog password encryptor-

 

Just to add: don't forget to turn off PHP's magic quotes feature, as described here:

 

SourceForge.net: FOG - A Free Cloning Solution: Topic: fog 0.29 join domain error wrong password

 

If you don't, the DOMAIN\username string gets converted to DOMAIN\\username when you save it, causing much confusion and general flumoxisation (you can tell what I've been doing for several hours now...).

 

--

David Hicks

[maniac]

My username for Active Directory operations in FOG doesn't have the domain before it, it's never needed it - works quite happily with just the username in the box.

[morganw]

Just to add: don't forget to turn off PHP's magic quotes feature, as described here:

 

SourceForge.net: FOG - A Free Cloning Solution: Topic: fog 0.29 join domain error wrong password

 

If you don't, the DOMAIN\username string gets converted to DOMAIN\\username when you save it, causing much confusion and general flumoxisation (you can tell what I've been doing for several hours now...).

 

--

David Hicks

 

...and interesting there is bug if you populate the AD settings through a FOG group which will remove the backslash, so DOMAIN\username becomes DOMAINusername.

[Homer]

Seconded on that bug!

[obijon]

Workaround for that bug is to use DOMAIN\\user in group settings (double-backslash).

[oxide54]

Workaround for that bug is to use DOMAIN\\user in group settings (double-backslash).

 

its the first thing i would of tried, its pretty standard for c based programming languages and a lot of script languages.

 

\n = newline

\\ = \

\" = "

 

etc etc

[armadillo]

Sorry to change the direction slightly-

I am new to FOG and I just wanted to ask for your opinion- how does it compare to MS WDS MTD when it comes to using it with win7. I am currently using symantec ghost and We will be deploying win7 in a couple of months time.

 

Thanks in advance for your help.

[morganw]

At the moment the FOG service doesn't work 100% with Windows 7, it is apparently getting update within the next couple of releases to add better support for this OS. In it's current state with the extra features it offers using the service I would say it's the best way to deploy Windows XP. If you are looking to go to Windows 7 in a couple of months it will do the imaging, but you'll have to sort getting a universal image together that will work on all your hardware - something like this may be easier to create and update with WDS / MDT2010.

 

Personally I've ended up using using a lot of extra features in FOG like printer managment, screen resolution changing, inventory, and using snapins it does all of our software installation. Moving from FOG means replacing all of this functionality and somewhat de-centralising the management tools so even if Windows 7 with FOG is more work in terms of the actual imaging it might be worth sticking with it.

 

You could try both at once and see which fits best, if you run DHCP client groups and enter the MAC addresses of some PCs you can set PXE boot options to force a boot from the FOG server rather than WDS.

[marsdenprimary]

On the 'Fog Settings' page I've entered

 

FOG_AD_DEFAULT_DOMAINNAME: school.internal

FOG_AD_DEFAULT_OU: -I leave this blank-

FOG_AD_DEFAULT_USER: school\FogADUserAccount

FOG_AD_DEFAULT_PASSWORD: -here you paste in the output from the fog password encryptor-

 

Now when registering the client either check the box in the user interface next to 'Join Domain after image task', the other boxes will populate with the default values, or the same thing will happen if you register the computer through the PXE boot menu, just answer 'y' at the appropriate point.

 

I thought the active directory join was broken on my system but in actual fact I had just forgotten to check the box in the user interface. For debugging check the output of the log file in C:\fog.log.

 

How do you use the FOG Encryptor??

[morganw]

It's in the tar file that you download and you run it on a windows computer to convert your password to an encrypyted one. There are instructions here along with notes on making the encyption more secure.

[armadillo]

At the moment the FOG service doesn't work 100% with Windows 7, it is apparently getting update within the next couple of releases to add better support for this OS. In it's current state with the extra features it offers using the service I would say it's the best way to deploy Windows XP. If you are looking to go to Windows 7 in a couple of months it will do the imaging, but you'll have to sort getting a universal image together that will work on all your hardware - something like this may be easier to create and update with WDS / MDT2010.

 

Personally I've ended up using using a lot of extra features in FOG like printer managment, screen resolution changing, inventory, and using snapins it does all of our software installation. Moving from FOG means replacing all of this functionality and somewhat de-centralising the management tools so even if Windows 7 with FOG is more work in terms of the actual imaging it might be worth sticking with it.

 

You could try both at once and see which fits best, if you run DHCP client groups and enter the MAC addresses of some PCs you can set PXE boot options to force a boot from the FOG server rather than WDS.

 

Hi morganw, thanks for your input on this and it definetly sounds like Fog is worth a shot. I will keep posted soon. Thanks.

[sven]

This thread is a bit old, but I'll give this a bash....

 

I have FOG changing the hostname no problem, but it doesn't seem to want to add the host to the domain. I'm not sure WHEN FOG actually tries to do this. Is there anything you would suggest looking at? I'm using the encrypted password and the FQDN.

[obijon]

This thread is a bit old, but I'll give this a bash....

 

I have FOG changing the hostname no problem, but it doesn't seem to want to add the host to the domain. I'm not sure WHEN FOG actually tries to do this. Is there anything you would suggest looking at? I'm using the encrypted password and the FQDN.

The FOG Service (you did include it in your image didn't you?) will make the change after imaging a computer, generally within a minute or two after the client boots. It only does this once, it won't keep trying to join. Before you uploaded the image the FOG Service should have been installed and the FOG server IP entered into the client. You don't need netdom with newer versions of FOG. Make sure you have followed the FOGCrypt instructions to set up the AD section on the server with hashed password. Some people (myself included) ran into trouble with the backslash in "domain\user" being stripped out. To fix this I had to use "domain\\user". I think this was fixed in a recent version IIRC.

 

Hope some of these random thoughts help.

[sven]

The FOG Service (you did include it in your image didn't you?) will make the change after imaging a computer, generally within a minute or two after the client boots. It only does this once, it won't keep trying to join. Before you uploaded the image the FOG Service should have been installed and the FOG server IP entered into the client. You don't need netdom with newer versions of FOG. Make sure you have followed the FOGCrypt instructions to set up the AD section on the server with hashed password. Some people (myself included) ran into trouble with the backslash in "domain\user" being stripped out. To fix this I had to use "domain\\user". I think this was fixed in a recent version IIRC.

 

Hope some of these random thoughts help.

 

I can put a big tick next to all of those points, apart from the double slashes. How will I know if this is causing an issue?

[Chad]

I can put a big tick next to all of those points, apart from the double slashes. How will I know if this is causing an issue?

 

Check that magic_quotes is set to off in your php.ini file

 

for Ubuntu, this file is found at /etc/php/apache2/php.ini

 

Look in the fog.log on the PC and see what errors are reported by the hostnamechanger module. You may need to increase the size of the log file which you can do by tweaking the ini file in (from memory) program files\fog\etc\

[sven]

I found the following in the fog.log:

 

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

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

24/05/2011 16:09 FOG::HostnameChanger Domain Error! ('Unknown Error' Code: 87)