Interesting, we do not need the Domain name in front :-/
Anywho, great that you solved it :D
I noticed the same thing some time ago, but wasnt sure it always happened so never reported it. Didnt try for some time to delete an image though.
I am stuck with an error on one of our clients.
FOG Version: 188.8.131.52
Running on Centos
Deployment works on all clients that I’ve tried it with in the last couple days, nothing has changed that I know of.
I get the error message:
PXE T01 File not found
PXE E3B …
And the client switches to normal HDD Boot.
When I check with Wireshark: The Client requests everything correctly - resulting in undionly.kpxe being requested.
But then Wireshark shows me an error: Error Code, Code: Not defined, Message: TFTP Aborted
I have no idea whats happening.
Undionly.kpxe is in the tftpboot folder on the FOG Server, the DHCP Settings on our Windows server seem to resolve correctly …
Does anybody have an idea what steps I can take next to troubleshoot?
Thanks for the support.
As Sebastian stated, for a domain join to function the Host will have to have the client running.
Information here https://wiki.fogproject.org/wiki/index.php?title=FOG_Client
And for further questions, have a look around the wiki first, it will answer many questions. Anything not listed there people on the forum will be able to help you with. The Developers are VERY active and great :)
Then its not pending :)
What happens when you LAN Boot from the machine? Can you log on and register it?
Can you find the host (Mac Adress: 3C:D9:2B:53:53:BA) in your Pending Hosts list (Under Hosts -> Left side)?
When you PXE Boot the Host via your LAN, can you do a registration from there?
You could try resetting the encryption keys.
That option should be available in the Host Details in your FOG Web-UI.
Not sure if it directly relates to this, but I think what that button does is to make FOG “forget” who is registered to a certain mac / hostname and when the host then contacts the server the next time FOG accepts that connection and establishes a trust relationship … or something like that :)
The settings are rather clear. All you need is to set the FOG Active Directory Settings to the correct OU and use the correct User and Password combination.
The Wiki has an article on this, if that doesnt help feel free to ask more :)