FOG Won't Join Imaged PC to Domain
- FOG Version: 5962
- OS: Ubuntu 14.04
- Service Version:
I’m currently having an issue where FOG won’t join a newly imaged system to the domain. I’ve gone into FOG Configuration - FOG Settings - Active Directory Defaults and have entered the correct credentials, etc. I then set-up a VM, performed a full host registration and inventory, and then imaged it (whilst selecting ‘yes’ to the question of joining it to the domain with the default settings). Upon logging in to the VM, I can see it’s still part of a workgroup.
The image was taken when a previous VM was set-up and was never joined to the domain. It was my understanding that FOG would join the system to the domain automatically using the default settings, regardless if the image was set-up as being on the domain or not.
Have I missed a set-up step somewhere?
@Wayne-Workman Yep, I already learnt that one the hard way :p
@RobTitian16 Another thing to keep in mind - don’t capture an image that is joined to the domain. It will absolutely not work and you’ll find this out when it’s too late. The FOG Client enforces the settings that are set on hosts in the web interface. So before capturing, you want the reference-host to be set to not join the domain, and then make sure it’s not joined to the domain as well.
@Wayne-Workman Doh, many thanks for your help!
I suppose that’s the reason this is failing?
The FOG Client is the software that the FOG Server communicates with to do things on hosts post-imaging. The FOG Client also allows for full life-cycle management of your hosts. You would need to update all of your images to have the FOG Client installed and working, and then re-capture your images. If you sysprep, there are special steps to follow linked below. The below link also in general is the go-to place for information about the FOG Client.
If you have further problems, please create a new thread, include details, and the FOG Client log file if relevant.
@Wayne-Workman No, it’s not there. I haven’t done anything with the FOG client on the images, so I suppose that’s the reason this is failing? I had a thought I was missing a vital step somewhere…
On another note, going to: http://[serverip]/fog/client/ doesn’t actually let me download the FOG client.
@RobTitian16 First check to see if it’s in
C:\Program Files (x86)\FOG\fog.log
Another good question - have you installed the FOG Client on your images?
Ah, I don’t have that. Is this configured on the web gui somewhere?
@RobTitian16 On the problematic hosts that you’re working with, it’s normally located at
@Tom-Elliott Where would I normally find this? I saw on another forum post it’s meant to be on the client machine, but I can’t see it anywhere.
@RobTitian16 correct can you provide the client fog.log?
@Tom-Elliott Yep, I can see the AD settings are there.
It shouldn’t make a difference if the username is “domain\user”, right?
@RobTitian16 please check that the ad settings made it to the host.
@Tom-Elliott Updating hasn’t helped this issue, unfortunately.
Please update to RC 14.