@raymond-bell said in Lenovo M70a Pxe boot:

And i have never used the FOS Linux

You have, but you’ve never directly interacted with it.

The concepts are here: https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image Understand your caveats and why this isn’t the first choice.

The concept here is that you will boot bzImage and init.xz from the USB stick and bypass iPXE and its interaction with your hardware. Look at the chat bubble in the upper right corner of this page for a few more hints.

@asheroto Did you actually read my question? Which version of FOG do you use?

From the logs it looks like you use 1.5.9 which is the last official version. Yes, this version does not work with Debian 11 because it was released months befor Debian 11 came out! We have fixed this issue in the so called dev-branch version weeks ago. For further details read these topics:

https://forums.fogproject.org/topic/15370/dev-branch-1-5-9-79-installing-package-php-gettext-failed-has-to-use-x-switch-to-get-it-to-work https://github.com/FOGProject/fogproject/issues/433 https://github.com/FOGProject/fogproject/pull/428 https://github.com/FOGProject/fogproject/issues/429

@george1421 said in IPXE Error 2e008081:

This will display the text script that creates the ipxe menu. Lets see exactly what is going wrong here. That “Windows…” still bugs me because I think it should not be in the ipxe menu.

You are correct here I am sure. From what I see in that picture I would assume the string “Windows” is set as Kernel either in the host’s settings or even in the global FOG settings.

My solution for this problem has been to use the api the remove usb macs when my provisioning script is done. I have it working by using the client.
The basics are

Computer gets registered with usb adapter My custom provisioning starts and the fog service is started which will add pending macs I leave the usb adapter plugged in until my provisioning is complete (so software install and whatnot happens over ethernet not wifi) Last step of provisioning uses a powershell api function to remove any existing usb macs (I have a saved list in the powershell of macs in my code) Adapter can then be removed and used on the next device

My custom functions uses my published fogapi powershell module, particularly this function https://fogapi.readthedocs.io/en/latest/commands/Remove-UsbMac/
Here’s a link to the code on github https://github.com/darksidemilk/FogApi/blob/master/FogApi/Public/Remove-UsbMac.ps1
The function also handles making a new mac the client found be the primary mac if the usb mac is the current primary.
If you’re not using the client, you could also create a custom automation to find the mac addresses of the machine during a postscript/firstlogon/provisioning step and have it use https://github.com/darksidemilk/FogApi/blob/master/FogApi/Public/Add-FogHostMac.ps1 to add a new unique mac then use the remove-usbmac function to remove specified usb macs.

If you’d like more info or examples I’d be happy to help, just wanted to offer a quick overview of a possible solution.

@sebastian-roth Wow, it looks like I was mistaken about how groups work. I see now that I need to use the plugin to get what I want. Now that I have enabled that plugin for persistent groups. Is there anywhere that says how to use it the correct way?

From what I understand, the plugin is basically a hack that will request all groups settings on a host when imaged. So do I predefine my group settings then image a machine, or am I missing steps?

Ok so as I posted there is a work around and I suspected something in iPXE but I wanted to be sure I wasn’t being a bonehead here. Thanks!

@utpalgiri143 You can tell FOG to just deploy a single partition. But FOG only knows about the partitions but not the drive letters assigned by Windows. So you need to figure out the correct partition number first.

The second thing you need to keep in mind is that the partition layout is not being deployed if you select a single partition. So a deploy task will fail if the partition layout is not correct. If you deploy the full disk once you can deploy a single partition afterwards as often as you want and as long as the partition layout is not changed.

So for deploying a single partition I suggest you create a new image definition in the FOG web UI. Set the right partition in the image configuration and capture that image. Then set this image to the host you want to deploy and let it do it’s task.

@lee-rowlett said in Secureboot issues:

LockDown.efi

a lot of thanks, that help me a lot…

@dmcadams said in Multicast session is not starting:

These client machines also have NVMe drives, so on the receiver side, instead of “/dev/sda1” should we use “/dev/nvme0”?

Yes, for the first partition use /dev/nvme0n1p1

@bacelo-0 Well there is more details we need about your isolated network.

What device is your dhcp server for this network? (the error you provided is not complete)

But guessing either the dhcp server did not send the IP address of the FOG server or there is no dhcp server on your isolated network.

@dashwell said in FOG bzImage not downloading:

use a Microtik router as our DHCP server and router and it only supports one image file call routine

Once you get past your current issue, If you need dynamic pxe booting (bios/uefi) we have a solution for that even if your dhcp server doesn’t support it. But for now one issue at a time.

@sebastian-roth Fog server is 1.5.9

I try to reproducing error and i put here picture.

@jmeyer said in Fresh install debian 11:

Yes. I’m an running Debian on a Qnap with Container Station.

Have you ever had FOG running on that before? NFS can be an issue in container virtualization. It definitely is on Proxmox when you use the default settings. I don’t know about Qnap.

@sebastian-roth OK thanks, we’re on Latest from 25.07.2021, so we’ll update and try. Thank you for your time. Fog really is amazing software and saved us big time!!

@robertkwild scrap this it works and when it runs the setup eventually its quick like a normal install

@george1421🤝 🤝 Thank you very much !

This is the great solution ever.

reg
utpal

Ha . I see that this was just recently addressed 18 days ago. Please delete. I’ll comment there.

@sebastian-roth Thank you. That fixed it.

@linshiyouxiang-net You need to extract the ZIP file before running the installer. Files bzImage, bzImage32, init.xz, init_32.xz, FOGService.exe and SmartInstaller.exe need to be in /root/fogproject/tmp.

By the way: That binary1.5.9.zip is still available on our server but the installer was changed to pull the mentioned files from github (URL for 1.5.9) some about a year ago. See the change we made in September 2020. No matter where you download the files from, they need to be in the mentioned tmp directory extracted (not as ZIP archive).

The installer will always ignore existing sha256 checksum files and re-download those but it does use bzImage/init files if they exist already and match the freshly downloaded sha256 checksums.