@Joseph-Hales Thank you sir, yes, it would appear that may be a best practice that has to be instated. Even though I regularly update images, at no more than 2 month cycle, it shouldn’t add much extra work to the process in total.
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.
Thanks for your reply, I have installed the IGMP protocol on my routing server under windows server 2008 but I do not know how to configure it and I do not find much about this on the internet, could you explain to me How to setup this?
@wanderbread Ah yes ISA cards. Glad I left them behind back in the 1990’s…
Watch the IRQ number, make sure its not shared with another device in the computer. The ISA cards had a jumper to select the irq port. irq 3 and 4 were for the serial ports. irq 2 was for the printer (I think). That left irq 5 and 7 open for add in cards (confirm with ancient text documents to be sure). Could the on board nic be interfering with the add in one?
@jamcdonald120 Well what I wanted a bit of clarity on is this. Tom saw as well as I saw in your files that you were / are sending the wrong boot file to this computer.
There are two types of boot files and its important to configure the right one to be sent to the right type of hardware.
There is the undionly.kpxe boot file, that is for bios (legacy) computers. And there is ipxe.efi that is for uefi based computers (as in the one from the pictures). If you have a mix of computers (bios and uefi) in your environment you will have some difficultly with imaging. There are ways to work around this but knowing what you are deploying to is the first step.