Windows Client notices task, reboots and boots into PXE but just goes back to windows.
-
Okay, that is descriptive then.
Check the host and verify that the LAN’s MAC Address is set as the Primary MAC for that system. Reason being is my guess is the System is set with a valid task, but the task is set for the wrong System MAC.
-
Yes, the MAC address matches within windows, when booting, and on the FOG server.
-
If you are getting the FOG menu on PXE booting, then you do not have the correct 01-[mac-address] file in your tftpboot folder maybe?
-
[quote=“chad-bisd, post: 25773, member: 18”]If you are getting the FOG menu on PXE booting, then you do not have the correct 01-[mac-address] file in your tftpboot folder maybe?[/quote]
That seems to be the case, how would I go about fixing this? It sounds to be a permission issue.
-
Cancel the current task for the host. Create a new task for the host, like a hardware inventory task. Once the task shows as scheduled in the webUI, log onto the FOG server (ssh or terminal access) and look in /tftpboot/pxelinux.cfg for a file 01-[mac-address]. If there is a file, mac sure it matches the primary mac address of the host record in the FOG webUI AND that it matches the mac address of the host as seen from inside the host’s OS.
If there is no file, you have other issues, but we’ll wait on your response.
*edited for proper path,maybe
-
There isn’t anything in the /tftpboot directory with 01-[MAC].
I have a secondary /tftpboot/tftpboot/ in there as well with nothing in it. I tested to see if the web service can connect to the server by downloading a new kernel, it does have write access to the directory /tftpboot and it wrote the kernel file to /fog/kernel.
I’ve also tried your idea of cancelling and restarting the task and still run into the same issue.
-
This post is deleted! -
Ah, he’s using 0.33b
-
[quote=“Tom Elliott, post: 25986, member: 7271”]Ah, he’s using 0.33b[/quote]
It was the most up to date one that I could find while searching the forums at the time.
-
Issue was:
TFTP Server Settings were set incorrectly.
