I saw both of those requirements. This doesn’t look promising. I guess now it is less about the price and more about the ridiculous hoops to jump through. Also the GPLv3 thing is killer for us.

@koni said in Can't pxe boot UEFI:

But I didn’t find the pxelinux.cfg

That is correct you should not find pxelinux.cfg because that is for the syslinux boot loader not iPXE. To add items to the iPXE menu you do that via the web ui in FOG Configuration -> iPXE Menu, menus. There is no need to hand edit the boot menus.

Just for reference: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images

@iamvincepr0 Look to see in the target computer firmware that mac address pass through is enabled. The issue is that ipxe is seeing the built in mac address of the computer, but FOS linux (that does the inventory) is only seeing the mac address of the usb dongle.

Also you will probably want to upgrade your FOS Linux kernel to 5.15.x version (FOG WebUI -> FOG Configuration -> Kernel update This will give you the latest hardware drivers for newly released computer hardware.

@john-l-clark said in Lenovo L13W Yoga not booting to FOG:

Ok I have found with the MAC passthrough in the Bios turned on we are not able to boot to FOG unless we were on the same subnet.

This is interesting. My intuition is telling me it might be an MTU issue. We have seen that with tftp, Where (typically) on the other side of a VPN WAN link the MTU of the data packet is less than the block size of tftp. The block size of 1468 comes to mind for tftp. When the network MTU dips below that level it causes fragmentation of the tftp packet, then the transfer fails.

Using the instructions I provided before for collecting a pcap on the fog server, you are interested in udp port 69. Start the packet capture and then pxe boot the target computer on the remote subnet. See if it attempts to contact the fog server. The tftp query will be 2 times before data is transferred, the first time the client queries the tftp server on the size of the file and the second time it asks for the file. My bet is that it will ask for the file size, but then the file is never sent.

@sebastian-roth Where do I “use –recreate-CA and –recreate-keys keys” switches? Like this?
.\installfog.sh --recreate-CA --recreate-keys?

@george1421 said in Error capturing Win 10 image after updating to the latest dev version - Resize Test fails:

Would it just create a larger disk image?

Yes exactly.

If yes then 7 or 8 might be a good start if size is the only penalty.

Ok, will 7 do for now.

@x23piracy Sorry for the long delay! This is a known issue in an older version of FOG and fixed in 1.5.9 and later.

@Mightmar Sorry for the long delay. Have been pretty busy.

I suggest you try to figure out what hash sums should be correct. Grab a copy of the file on the host machine, e.g. C:\Program Files (x86)\FOG\tmp\run_wpkg.bat and calculate the SHA256 hash sum for it. Also check the contents of the file on the host.

@ksrvpvl Hostname is allowed in the latest dev-branch version (1.5.9.140).

@mrp Added to the official FOS inits now. Can’t wait any longer for you to test.

@dpullin said in FOG service invalid host:

The issue seems to be when the name in FOG UI doesn’t match the hostname of the machine (because I changed it in the UI after the fact) - this has started to crop up on other machines due to user error (techs giving machines the wrong names before sending them out the door) - then we try to fix it by changing the name in the UI, then it gives the “invalid host” error as described above.

I can’t seem to replicate the issue as described using the following steps - please verify if you do things a different way:

Check fog.log to see communication works fine Make sure AD credentials are set and correct for the test host in the FOG web UI Change Host Name in FOG web UI Wait for machine to reboot Check hostname (Windows GUI as well as CMD -> hostname) and fog.log (see below). ------------------------------------------------------------------------------ --------------------------------HostnameChanger------------------------------- ------------------------------------------------------------------------------ 4/16/2022 7:06:09 AM Client-Info Client Version: 0.12.0 4/16/2022 7:06:09 AM Client-Info Client OS: Windows 4/16/2022 7:06:09 AM Client-Info Server Version: 1.5.9.139 4/16/2022 7:06:09 AM Middleware::Response Success 4/16/2022 7:06:09 AM HostnameChanger Checking Hostname 4/16/2022 7:06:09 AM HostnameChanger Renaming host to Newhostname 4/16/2022 7:06:09 AM HostnameChanger Renaming host inside existing domain binding 4/16/2022 7:06:09 AM HostnameChanger Success, code = 0 4/16/2022 7:06:09 AM Power Creating shutdown command in 60 seconds 4/16/2022 7:06:09 AM Bus Emmiting message on channel: Power ------------------------------------------------------------------------------

Works fine in my test setup. Do you use plugins or other special things in your FOG setup? Other than that I con only imagine is has to do with the wireless MAC you seem to be using. Is this the primary MAC?

That work now, thank you !

hello

we have dell 3540 using UEFI boot ( legacy boot disabled everywhere)

secure boot has to be disabled dhcp is made via pfsense with ipxe.efi master has been made with UEFI ( fog service has to be stopped before sysprep , otherwise bootloop after deploy / don’t know why) STP disabled on every switch

Works fine here (single or multicast)

@george1421 Yes i already try this. Works fine but already my problem with Bitlocker.
Actually my problem is our computers are configure to boot on pxe when receive wake on lan.
And Bitlocker ask recovery key if order boot has changed.
But i notice if i reboot “normally” even after that, Bitlocker don’t ask recovery key Bitlocker.
My problem is for our computers “Refind EFI” is the only mode who work with pxe. If i use other option, i have an error like “Chainloading failed”.
This is why i was thinking to have a “reboot” mode, because i don’t find how to make it work the “Exit” mode

@george1421 the good thing is, you only need to do the reg hack and app removal on the GI, once you sysprep the GI and capture it, when you deploy it, you have to do nothing and you can deploy to multiple laptops, vms etc

the pic i shows you shows a laptop with TPM enabled, using the deployed image

@joanmarzo ?? OK but I don’t think the problem is FOG but if you want to reinstall that is your choice. We will be here to help if you need it.

I’ve never run into this specific problem until today. Generally, issues with resizing can be fixed by increasing the CAPTURERESIZEPCT in Fog Settings > General Settings. I agree with what @Quazz said about certain kinds of fragmentations causing issues with the theoretical minimum partition size. I’ve found that the more used (fragmented?) a drive is, the more likely it is to fail during resize. I was able to get past the no space left on device and numerical result out of range errors by increasing the CAPTURERESIZEPCT to 15%.

@jape You can use the api (See the powershell api module links in my signature). You can use it to create the scheduled task. i.e. (provided you got the module all setup prior) the following would create a scheduled deploy task for host with id ‘1234’
at 8 pm tonight. The following is all powershell that can be run from your admin workstation.

#define the schedule time in the linux format $startAtTime = (get-date 8pm) $EpochDiff = New-TimeSpan "01 January 1970 00:00:00" $($startAtTime) $scheduleTime = [INT] $EpochDiff.TotalSeconds - [timezone]::CurrentTimeZone.GetUtcOffset($(get-date)).totalseconds #define the schedule time in human readable format $runTime = get-date $StartAtTime -Format "yyyy-M-d HH:MM" $jsonData = @" { "name":"Deploy Task", "type":"S", "taskTypeID":"1", "runTime":"$runTime", "scheduleTime":"$scheduleTime", "isGroupTask":"0", "hostID":"1234", "shutdown":"0", "other2":"0", "other4":"1", "isActive":"1" } "@ #create the scheduled deploy task with the defined json New-FogObject -type object -coreObject scheduledtask -jsonData $jsonData

@george1421 IT’S WORK!!! THANKS A LOT!

The fog kernel version is 5.15.19,

I have created the Linux os image from laptop model hp probook440G8 in the fog server.

while I am trying to deploy the image with the same laptop model, it’s showing me the options as I have shared the previous image.