@Gary-Kulovics said in Fog Client won't join Domain:

9560

Invalid character in name.

@Wayne-Workman
I feel dumb now, should have tried that yesterday. Simply deleting those folders/doing another git clone and everything is working fine now. Thanks a lot for the help!

@Sebastian-Roth said in USB NIC PXE Boot?:

The PC/notebook/tablet/whatever device you are trying to PXE boot with this USB NIC needs to have specific drivers for this USB NIC chip in the BIOS!!

I suppose now we must record the device that the adapter worked on, too. I didn’t think of this but it makes sense.

#wiki

This is already known about and has already been fixed.

I suppose this is dependent upon how your clients, vs your server, communicate to the internet.

There could be the issue I created, though I’m starting to think your fogserver is not necessarily supposed to be going through the proxy itself?

@Joe-Schmitt Done. Also put links from the FOG Client article and an older article to it as well.
https://wiki.fogproject.org/wiki/index.php?title=Power_Management

I know this thread is quite old, but I wanted to include another possible cause because Google searches seem to bring you back to this thread.

I was experiencing the same issue with my Windows 7 Fog clients, and resetting the encryption data did nothing. It turned out to be the time was quite off on the client, so it was never able to authenticate with the Fog server. Once the time was corrected, the client connected and everything worked fine (hostname, join, etc.).

Just in case someone else runs into this issue, hopefully this can save you some time.

Well… This is embarrassing.

Good news I fixed it, i get into the PXE menu now! 😄

I do have a different question now, when I click boot from hard disk in the pxe menu it doesn’t load the operating system, any ideas for that?

For the issue relating to TFTP this is what happened:

I set up a packet scan on both the DHCP and PXE server and after analyzing the packets i noticed there were two different packets sending a different option 66 and option 67. One was right pointing to the FOG server and Undionly.kpxe the other however pointed to the DHCP server. Apparently an old image deployment software was still working even though the options weren’t configure anymore. I removed these and everything worked great!

@Wayne-Workman Thanks so much for your reply Wayne. I really appeciate the info. Also, we just went ahead just now and updated it to 1.3.0.

@Quazz is correct.

@Wayne-Workman ok xD

When I update an OU of a host/group, after changes the default OU displayed on the host is the first dropdown item, not the value that I’ve applied.

@t1pt0p the problem is that stp IS enabled. You need to enable a fast stp protocol. The quick test is to put an unmanaged switch between your building switch and the target computer.

If you have stp turned on, then look for port fast, fast stp, or rstp and turn it on on the target computer port.

it’s work after re install
thank all for you help

@EAHarvey You might want to check your /images folder contents, though.

The way image capture works is they get placed in /images/dev first and then at the end they get moved to /images and renamed to the proper destination name.

This moving process uses FTP, failure to move them indicates some sort of issue with that, most likely credentials, but if you’ve recently run the (trunk) FOG installer, this should already be corrected in the mean time.

@Quazz okk im creating a new account and reinstalling fog

@george1421 said in Chainloading Failed - Fog Menu - Boot HD:

OK we need a bit more info, and a possible recommendation that you update to the 1.3.0 RC series before we do too much debugging.

What is version 13, is that fog 1.3.0 (something)? Since the svn versions became disconnected from the git version I can’t tell if that is current or not.

More to the point of your question, is this a uefi or bios (legacy) based target computer? Also please include the mfg and model number of the target computer.

My mistake, it is 1.3.0 RC and the host is a Dell 790 BIOS based.

@Quazz
Now it works with 7zip too.
Definitely something went wrong at last time.

@Wayne-Workman Ok ill be sure to look for that in the future. Thanks to everyone who helped! Ill be sure too update frequently now haha

@Wayne-Workman

Yulp. That was it. Re-ran the install and it updated the IP address.

Thanks for the help!