Windows Client notices task, reboots and boots into PXE but just goes back to windows.
-
[quote=“Tom Elliott, post: 25172, member: 7271”]Is your system setup to boot to network first? If not, all that’s going to happen is what you’re describing. The client recognizes there’s a task to be performed, restart the system, load back to Windows, start again.
Make sure you set the systems needing to be tasked by FOG to boot from the NIC.[/quote]
It does boot to the linux kernel. It connects to the server and that works fine. It however does not connect to the server once it boots into the linux kernel. It just goes through it’s timer and goes back to linux.
-
So forgive me, but I’m a little confused. In the first post you state it keeps rebooting to windows. In this post you state it keeps rebooting to linux? Please elaborate more.
-
When turning on the PC it remote boots from the FOG server. I get the linux kernel that deals with fog.
I have a task set to upload the image, but when booting to FOG it doesn’t do anything.
After the timeout timer runs down it just goes back to normal booting to Windows.
After it boots back into windows it connects to the FOG server and sees that it has a task, and reboots.
This process is an endless loop.
-
Okay,
So PXE Boot is not set, but the “Timer Error” message means that there’s another issue, which forces the system to reboot, but this time it loads back to windows because PXE Boot is not there.
What’s the “Timer Countdown” message referring to?
-
It’s not a timer error, I’m booting to the default FOG kernel that doesn’t have any task with it. It says “Automatic boot in 3 seconds…”.
There’s no timer error, no error occurs. I want it to upload an image to the server but it’s just not doing that. That’s the issue I’m running into. It connects, it boots to FOG, doesn’t do anything but go back to windows after the timer runs down. It’s the menu with the default FOG commands, MemTest, register with the server, etc.
-
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.
