@george1421 said: There were a couple references to this “with a partition scheme suitable for EFI”. Which makes me wonder if there has to be something done special with the init fs to make it efi suitable?? Interesting. Haven’t thought about this before. Well we do have FOG (FOS) running on several different UEFI machines. So I am certain that it works with those inits Tom is building. AFAIK there is no partition scheme involved. initrd is just a compressed image file - no MBR, no partitions, no GPT …

I’ve removed Arch Linux from the automated tests due to complications within Terraform. These issues were sort of the final straw in my Arch testing efforts. The Arch community doesn’t supply an official AWS AMI. I had been relying on a privately built AMI that isn’t 1:1 with a manual Arch installation. For perhaps the last half year, my Arch tests were failing but the installer worked if you tested it against a manually setup Arch installation. This can only be due to differences between the AMI I was using and a manual installation. The Arch community is vehement about only providing help if you follow their installation instructions on their wiki exactly. Because of this, when I asked for some help sorting out the issues, they were not willing to help. Until someone with some Arch prowess can put some time into helping with this, Arch Linux will not be included in the automated tests.

Well… if we didn’t hear from him this morning, that probably means the FOG server stayed up all week. Thread solved.

@Jbob Hello In first sorry for this long delay I just made the test today with the latest client. Everything seems to work fine !!

Same issue with Dell Precision T7610. Error 040ee119. Tried everything including chainloading[SIZE=2]. Dell T3500s and other 100 machines are good. Any ideas what else I can check ? Fog 1.2.0[/SIZE] [SIZE=2]Thanks.[/SIZE]

@george1421 +1 for a wiki page. This is really useful stuff and I only found out about it when coming onto the forums and talking with George. Without the forums, I wouldn’t have ever found this out/get it working.

@mandrade I was just on a side chat with Tom. He said that the FOS kernels were updated earlier this week to 4.6.2. What is on the usb image is older than those. It would be interesting to see if the newer bzImage allowed that onboard nic to work. You might want to download and refresh these files on the usb stick and try again. https://fogproject.org/inits/init.xz https://fogproject.org/inits/init_32.xz https://fogproject.org/kernels/bzImage https://fogproject.org/kernels/bzImage32

Good luck!

@Tom-Elliott said in UEFI won boot tools via fog menu.: hink I see!! that’s great to know!!!

@Sebastian-Roth I am now, as what I expected is the case.

[quote=“Tom Elliott, post: 23193, member: 7271”]You’re welcome. All is working then I presume?[/quote] I have succesfull created an image of a Windows 7 machine. I have not tried to deploy the image back to the Windows 7 machine, but I assume that this is going to work, otherwise I let it know.

[quote=“Peter Kuykendall, post: 19739, member: 18261”]I’m having the same problem trying to install FOG 0.32 on Ubuntu 12.04.3 LTS server i386 (in a VM for now). Output is in the attached text file (initial stuff was clipped due to the size of my SSH session buffer). Suggestions?[/quote] The UDPCast file within the fog installation is outdated. Follow the solution in this forum: [url]http://fogproject.org/forum/threads/setting-up-and-building-udpcast-failed.4548/[/url] It’s basically downloading a newer version, patching it, and then redirecting the fog installation to look to that version instead of the one that fog provides. Once you do that, run the install again, and it should complete without a problem.

@Wayne-Workman Hi, Ok i understand. Actually majority off our classroom reboot at the same time for software update in night (same time is residual effect with green fog on old version). I will adjust power management (good amelioration in this version) for spread out this reboot. Thanks.

@george1421 what version of MDT are you running btw? I’m on 8450.

just stumbled across this thread, felt i should mention that the latest FOG trunk is still working on Ubuntu 12.04 LTS

@JJ-Fullmer Well it wasn’t actually phpipam that was slowing it down. I had some ssl logs running for a website running on that server. It was tracking access logs for every access of the ssl cert and site. Which was also adding up to over 400 GB of logs. I changed the apache configuration of the site to log much less. That solved the problem. So again, nothing wrong with zstd. Just wanted to have the right answer in case someone else happens to see a constant 5-8 Mbps transmit and receive on a storage node.

@mabarton I briefly went over this thread because it’s been a while. Have you individually tried every EFI exit type?

@Chris-Bosman A new feature has been added to FOG Trunk that allows users to specify the FTP path to the image directory for any storage node. This is exactly what you need in your situation. The relevant thread is here: https://forums.fogproject.org/topic/5333/ftp-path-for-storage-nodes Here is how you would upgrade to FOG Trunk: https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

@Sebastian-Roth thank you for pointing me at the DHCP! I found the problem! All files are fine, but our company DHCP was not! After trying it in a seperated VMware Network it worked like a charm! So all the effort was in vain - i am sorry We have an old fog running 1.4.4 in our DHCP config for managing the PXE Menu because we are running multiple (i)PXE Services in one subnet. I created a new boot menu item to forward the pxe boot to the new fog server. like this: iseq ${net0/mac} a0:36:9f:bd:XX:XX && goto testing || :testing set pxeserver:ipv4 FOG-IP set next-server ${pxeserver} chain tftp://FOG-IP/default.ipxe exit Got it from here in 2017: https://forums.fogproject.org/topic/9648/add-a-second-pxe-boot-option Worked fine, until now … And by now, i understand why no certification cmds were availibe because it got stuck in the old fog enviroment. Need sth. to reload the enviroment i think. I will take a look into it to find a way. Maybe i will open a new topic here! Thank you @Sebastian-Roth for taking the time! Your scrips are fine - it was my fault …