@zbe So from your picture it appears the wait time is coming from iPXE getting an IP address?

Yes.

What version of FOG are you using?

1.5.10

Could you grab a new pcap of the failing pxe boot sequence

Well, technically it’s not failing, it just takes 180 seconds for yet unknown reason.

–

I PM-ed you 6 captures. 3 are done booting UEFI and other 3 BIOS.

I used 3 different network devices:

VirtIO paravirtualized Intel E1000 Realtek RTL8139

As you’ll see almost every configuration behaves somewhat unique. It makes no sense to me. 😛

I can do captures of physical PCs sometime next week, hopefully.

@alexamore90 said in Post download install script:

it start ms-settings:activation

I don’t know that command. I have not used it before.

I;ve used the command line scripts

cscript //nologo c:\windows\system32\slmgr.vbs /ipk <activation_key> cscript //nologo c:\windows\system32\slmgr.vbs /ato

The setupcomplete.cmd will only run if you use sysprep. Do you sysprep your images before you capture with FOG?

@Sebastian-Roth
I think to know what is blocking.
I have to change vlan and fog IP adress to make updates but it use IP parameter in the updateDB() function :

wget --no-check-certificate -qO - --post-data="confirm&fogverified" --no-proxy ${httpproto}://${ipaddress}${webroot}management/index.php?node=schema >>$error_log 2>&1

I think -X with help to finish install.

@jblomquist said in Is there a way to restrict FOG menu access to specific users?:

I’d like to allow a particular user to be able to deploy an image, but not quick delete a host through the PXE menu.

Which version of FOG do you use?

The quick delete option is secured in the iPXE menu in FOG 1.5.10 (github commit).

@AlexPDX said:

i see u did not find the time to fix the M.2 NVMe problem 😐 …and the Storage Nodes being Unauthorized 😐

No, we haven’t yet. You are very welcome to get involved and help fix this stuff.

@Sebastian-Roth Challenge accepted!😁

As a side note:
The image type description in the wiki (I got there from the balloon help: https://wiki.fogproject.org/wiki/index.php?title=Managing_FOG#Images) points to a non-existing page (404): https://docs.fogproject.org/en/latest/management/image-management.html

Thanks! @JJ-Fullmer would you find the time to fix that quickly?

Fixed!
@medchemii thanks for letting us know. We changed the structure of the new docs page a bit and it affected the links. We’re working on getting redirection working for old links still

@Sebastian-Roth We are up and going again. Thank you so much for your help I really appreciate it.

@george1421 Great stuff. Thanks!

@Sebastian-Roth Sorry for the late response. I ended up re-installing everything and its good now. I also changed the permission of the images to executables on the storage nodes, not sure if that helps but its all working now.

Thank you for your help.

@Sebastian-Roth
Capture.PNG
Yes with EFI exit type = REFIND_EFI
it works perfectly
Thxs

@brakcounty said in ipxe boot slow after changing to HTTPS:

Even when using the Paravirtualized Network Adapter in VBox?

Learning something new every day! Wow, didn’t know this and never tried it before. Thanks!!!

@dashwell said in Problem with INIT.xz @ 74%:

new series of laptops

Beside the excellent hints George already gave I might ask which make and model exactly are we talking about?

@sgoodman Reviving this topic as I think this would be good to get done for the next 1.5.x release.

@TBCS OK Just so I understand. Now the error printed on the screen no longer appears. It was fixed by the kernel update to 5.15.x.

Now when you capture the image capture just freezes at 30% and no visible error is displayed.

Do you have another one of this model you can try to capture? So the question is, is the problem related to this specific computer or this computer model. I’m suspecting there is something strange with the source computer’s storage media. As of now there is no difference in disk structure between windows 10 and 11. So selecting win 11 in the fog ui should work well.

@norbo80 this post looks interesting. What seems to be important is the port groups being forwarded to the container: https://forums.fogproject.org/topic/5546/installing-fog-in-a-docker-container

There is a free utility called ShowKeyPlus, which is in the Microsoft Store. This will show you your product key. It will show you the original Win 7/8 key you used to upgrade if you went that route as well.

Once installed via the store you can dig around and locate the ShowKeyPlus.exe file in the hidden folder for Appx apps. It will run on its own as a standalone utility. I put it on the desktop of my golden image so I can easily check.

Of course you want to run ShowKeyPlus BEFORE you image, and save the key to add to the Fog database when you register the host (you must add manually).

@wass This is 100% supported and the recommended way to use fog. One thing you need to do for sure is disable secure boot on the machine as the ipxe bootfile isn’t a signed boot file (it hopefully will be in the not too distant future).

The other important step is setting up your dhcp server to point to fog by setting option 66/67 on your dhcp server, see also https://docs.fogproject.org/en/latest/installation/network-setup/

If there’s a more specific part of the setup you need help with we’ll happily guide you through it

@Sebastian-Roth with all the machines, but different error.

Some of the machines boot to the fog project and when you try to deploy image it have the error “Chainloading failed, hit sfor the iPXE”

other machines dont even go to the fog project and gives the error DHCP failed after getting IP from the DHCP and trying to get ip for the iPXE

@Sebastian-Roth Thanks!