Active Directory Joining

[tri_94]

Having been using fog for a while and it seems to be really hit and miss for AD joining after image. I can get it to join if I wait till the machines are imaged and then un-tick and re-tick the box to send the command again.

Is there something I can do to solve this so it will image and join without the manual intervention afterwards.

Thanks

[EagleEnergy]

Hello,

I had the same problem.

this the solution for me:

Delete the target computer from the AD

In fog AD default settings:
FOG_AD_DEFAULT_DOMAINNAME: mydomain.local
FOG_AD_DEFAULT_USER: administrator
FOG_AD_DEFAULT_PASSWORD: passwordforadministrator
FOG_ENFORCE_HOST_CHANGES: checked

FOG_AD_DEFAULT_PASSWORD_LEGACY: blank
FOG_AD_DEFAULT_OU:blank

In host AD settings :
Join Domain after image task: checked

The rest will be filled automaticelly

Make changes even when users are logged on?: checked

And now deploy

[Avaryan]

@tri_94 said in Active Directory Joining:

Having been using fog for a while and it seems to be really hit and miss for AD joining after image. I can get it to join if I wait till the machines are imaged and then un-tick and re-tick the box to send the command again.

Is there something I can do to solve this so it will image and join without the manual intervention afterwards.

Thanks

Which version of FOG are you running? The FOG Client included in 1.4.0 is supposed to increase the speed at which it renames and joins computers to the domain. I’d suggest updating to the latest stable build.

[Wayne Workman]

@tri_94 said in Active Directory Joining:

I can get it to join if I wait till the machines are imaged and then un-tick and re-tick the box to send the command again.

This doesn’t send the command again. The FOG Client gets it’s information via polling the server every x amount of seconds, default is five minutes. The server doesn’t initiate a send, the client does. On every single pole, the FOG Client is given all configuration the host should have from the server - similar to how Puppet works in a way. It sounds to me like you’re probably experiencing a server bug in what is probably an older version of FOG - The latest is 1.4, I strongly suggest you upgrade to it.

The only things the FOG Server initiates a send of are WOL and Multicast and pings, replication, maybe a couple other minor things. Most client side activities is completely controlled either by the FOG Client or network booting via some method at the client.