@Clebboii Thank you for your comments. I’m following up on your responses below.

It looks like MAC Passthrough is only a thing on Latitude, Precision, and XPS laptops. We utilize Latitudes. We do disable Secure Boot when trying to go into PXE boot. We’re going to try to set up a USB with WinPE to disable bitlocker. What confuses me is that the XPS had bitlocker get triggered when secure boot was off but still made it through PXE. It makes me think Bitlocker isn’t the issue here. The Dell USB-C to Ethernet does not support our Dell Inspirons. We tried an Anker USB-C hub with Ethernet and a usb-Ethernet TP-Link adapter on the Inspirons which didn’t give us the option to PXE boot. 66 and 67 weren’t set up when it worked on the ThinkPads or XPS. We set it up on our Firewall not our Router. It also worked after enabling. Going to look into this once our ThinkPad returns from being issued out as a loaner laptop.

Nevermind, looks like it was an error in the script itself.

@Itay1787 I just pushed a change to the dev-branch. Please try installing it again from there and let me know how it goes.

I just want to know if it is possible. Seems like it should be, but I am having difficulty finding any information online regarding how to actually do it.

@rodluz

Alright it works thank you.

@JeremyL Hi, yes I am sure I have run Fog under Proxmox as well successfully but this time it didn’t want to work. Anyway once I switched to using Fog running under a Container, it uses much fewer resources and runs just as well.
So I would recommend switching to running it under a container when possible.

@rodluz

ok scrap the local GPO done this and it works

reg add HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce /v firstlogon /t REG_SZ /d powershell -noexit -ep bypass c:\users\admin\sysprep\firstlogon.ps1 /f

@george1421 thanks for continuing to provide such detailed information.

I believe the best way to learn is to do, so i am going to go shopping for an SSD (and perhaps some RAM to be safe). Once I have everything in place, I am going to do a test run on our machines as well as those of an associate just to see what happens when the network changes. Following this, I will check back with you if you don’t mind to go through the results.

Hello,
In my attempt to switch to HTTPS for the Fog server, I encountered the same issue of the keyboard being disabled in the iPXE menu. After several unsuccessful tests, I consulted Copilot. After reviewing all the scripts and .h files, it indicated that the issue stemmed from the size of the iPXE.efi file I was using. It was too large due to all the necessary modules for HTTPS, causing iPXE to deactivate the USB keyboard functionality during loading. Consequently, I opted for snponly.efi instead, and now the keyboard works perfectly.

I modified the script buildipxe.sh :

sed -i ‘s+#define USB_HCD_USBIO+//#define USB_HCD_USBIO+g’ config/usb.h
sed -i ‘s+#define USB_KEYBOARD+//#define USB_KEYBOARD+g’ config/usb.h
sed -i ‘s+//#define USB_EFI+#define USB_EFI+g’ config/usb.h

May I propose a change in the console.h : Could you set the keyboard map to “dynamic” instead of “us” ? That way we can easily set our language in default.ipxe

//#define KEYBOARD_MAP us // Default US keyboard map
#define KEYBOARD_MAP dynamic // Runtime selectable keyboard map

@Tom-Elliott is there a way to find out where its failing

i have the PCAP file if interested?