Ah ok I understand now - brilliant this has resolved the issue I wasn’t aware that specifying the default OU would have a knock on effect.

Thanks again for your help

I have previously had fog set up to join different OUs depending on the department the machine will be located. Separated by the | symbol and the default OU being set by the ;

It use to work a treat but I have since removed all this to try and fix the current issue. Still the same message in the log file and it is just not joining the domain. Not sure what it is failing on as it says HostnameChanger Domain Error! (‘Unknown Error’ Code: 2)

Hi,

I am having trouble with getting fog to add machines to the domain. This was working fine and has recently just stopped and I cannot figure out what has changed.

I get as far as the image being deployed and in the fog log it says 20/04/2015 09:51 FOG::HostnameChanger Domain Error! (‘Unknown Error’ Code: 2)

I am not sure what the error code 2 means.

I have tried changing he password and rebuilt the dll and used fog crypt. When I do this it brings up a different error message which I searched for and it states it is something to do with the password. So I am sure that error code 2 is not password related? I have also checked the hostname changer service is running and that the OU directory listed is correct.

Help?

Thanks chad-bisd for the reply.

How do we add a proxydhcp server on fog?

Also after the update to fog 1.1.2 which no longer supports pxelinux.0 we are now using undionly.kpxe or ipxe.pxe.

Thanks
Scott

Already tried a bios update and same issue.

Network card in the machine is as follows: Intel 82578DM Gigabit Network Connection

they are receiving no DHCP offers received or else get to the deploy image stage and freeze on a black screen with cursor flashing. It appears when the machines that aren’t working are trying to PXE boot they are using Intel Boot Agent Version 1.3.24 however the machines that are working and can deploy the image or get to PXE menu without any issues are using a Intel PXE boot agent?

These machines are all on same IP range, under same scope with same boot options applied.

Another update - it appears when the machines that aren’t working are trying to PXE boot they are using Intel Boot Agent Version 1.3.24 however the machines that are working are using a Intel PXE boot agent?

Also as a follow up on this.

Another machine that we have tested that is not working (black screen blinking cursor or reopening network devices or no DHCP offers received) is the Fujitsu ESPRIMO Q530E. So now we have the Fujitsu and Viglen machines not able to deploy image.

However we have Shuttle PCS and Dell OptiPlex machines that we are able to send an image to using same network port and same configurations.

Really not sure of any way around this after changing the boot file from ipxe.pxe, undionly.kpxe and the other options nothing seems to work.

Any one else experienced this?

Have changed the options from Ipxe.pxe and nothing being received at all for the Viglen however the Shuttle and Dell get to Fog menu stage and can image fine. Changed back to Undionly.kpxe and the Viglen then gets to the fog menu and when I select perform full host registration I then get the loading bzimage etc. before screen changes to black with cursor blinking on the screen and that’s as far as it gets.

Do you mean changing the options to boot from IPXE.PXE or UNDIONLY.KPXE etc.?

I have changed this and tried a few different ones (all that came with the install of fog) and same result unfortunately. Last working method was the pxelinux.0 for these machines. Are there some older machines which these files are not compatible?