The issue looks to be fixed since I changed the boot file name. This thread can be marked as closed/solved. Thanks again for everyone’s help.
Best posts made by Donutsrule5
Latest posts made by Donutsrule5
RE: PXE Boot Issues
@george1421 Thank you for your help and insight. I confirmed with the models that don’t work (as well as the models that do to compare BIOS’s) that they are using legacy mode and not using secure boot etc. I am using the built in Ethernet port into the laptop or desktop, no kind of docking station. In response to @Sebastian-Roth post, I changed my bootfile name from undionly.kpxe to ipxe.pxe and got at least the E6440 model to boot into the Fog menu. So i’m off to try the others.
RE: PXE Boot Issues
@sebastian-roth You are THE man. I changed my DHCP option from undionly.kpxe to ipxe.pxe and my E6440 booted right into the FOG menu. I’m going to try the other models later this morning to see if they are working as well. I’ll reply back to this thread if it gets everything working. This is a promising start!
PXE Boot Issues
- FOG Version: 1.5.0-RC-6
- OS: Ubuntu
- Service Version: ?
- OS: Windows 7
I’m having issues booting some of my machines into Fog. But some work. For instance, I have a ThinkPad L440 model that boots into the Fog menu fine. My VM’s I use for creating images still boot into Fog fine. But I have a Dell Latitude E6440 and another model that do not boot.
For troubleshooting, I updated my Fog environment to 1.4.4 (latest stable release) and that did not help. So I went ahead and upgraded it to 1.5.0-RC-6 (latest trunk version) and that did not help either. I also tried upgrading the BIOS on the Latitude E6440 to the latest and that didn’t help either. I’ve tried different cables, different networks, different computers with the same model etc.
Posting here is my last resort. I’m not sure if there are logs on the Fog/Ubuntu server that will tell me why it won’t boot into the Fog menu or if there is something else with legacy/UEFI boot modes. Or if the iPXE boot menu or boot exit settings need to be something different. I need help. Picture attached is what my machines get when trying to PXE boot into Fog.
RE: FOG Snapin Task Queued
Good morning, Tom. The .msi file for Google Chrome is roughly 43 MB. Although I did follow the wiki on editing the php.ini file and increasing the “memory_limit”, “post_max_size”, and “upload_max_file_size” to 1900 M.
Could I have screwed up the php.ini file and it’s causing this issue somehow? I (of course) didn’t make a backup before editing it, but i’m sure I can find a default, out-of-the-box php.ini to replace it with.
FOG Snapin Task Queued
First time poster and user of this great product. I tried searching on the forums and on Google, but none of the threads could help me.
I’m running the latest version of Unbuntu and running FOG 1.2.0. I created a simple snapin for Google Chrome installation. For the “Snapin Run With” field i’m using “C:\Windows\system32\msiexec.exe”. For the “Snapin Run with Argument” field i’m using “/i”. I’ve uploaded my .msi file I downloaded for Chrome. For the “Snapin Arguements” field i’m using “/quiet” and i’m not checking the option to reboot. It creates the Snapin fine. I can go to the host and put it in the snap in group. Then I navigate back to the host, go to “Basic Tasks” and go to “Advanced”. Then select on “Single Snapin”. I select my software and tell it to “Schedule Instant Deployment” and create the task. From there I can go to “Task Management” at the top and see the task there, but it sits at queued. I’ve waited around 30 minutes and it never progresses. The fog.log file under the C:\ doesn’t show anything. I’ve tried restarting the FOG service and rebooting the entire computer, but it never goes beyond queued.
I did find one thread that wanted you to run the MySQL commands “truncate table snapinJobs;” and “truncate table snapinTasks;”. I ran that once and the job did go through and completed. But as soon as uninstalled Chrome, restarted the computer and re-ran the task again, it would sit at queued. I then tried the MySQL commands again and those don’t work anymore.
Any help is greatly appreciated.