Most likely these are partially (or fully captured that were unable to move) capture images hanging out in /images/dev

@irishfoguser Hi, generally speaking you’re better off using Resizable image. If this for some reason doesn’t work (fails to deploy), then trying the other options is recommended.

For your situation, it sounds like Resizable Image will do the trick. So I recommend picking an image, setting it to resizable, recapture, deploy and see if it works for you.

1.3 is able to resize the correct partition for you before Windows even boots for the first time.

@AlexPDX Rule of thumb is to create a new thread, since the OP in this case was using a very old version, and you are likely using FOG 1.5.8

That said, quick fix is:

sed -i 's#/usr/bin/php env #/usr/bin/env php #g' /usr/lib/systemd/system/FOGSnapinReplicator.service
systemctl daemon-reload
systemctl start FOGSnapinReplicator

To be fair, it’s been a longstanding recommendation that the FOG server should be running nothing but the FOG server for a reason.

Apparentally, to prevent Windows search from breaking after copying the profile over, all you have to do is delete

AppData\Local\Microsoft\Windows\UsrClass.dat

Windows will create one on login.

@TomBagley Considering you have to enter tftp server address, it is likely you have another DHCP server on your network (likely your modem), which might be interfering.

I’m guessing you launch a batch script which launches a msiexec and then closes rather than waiting

Adjust accordingly.

It’s /var/www/fog/service/ipxe (singular service)

@lebrun78 You could try a different disk boot command. You can choose these globally, per group or per host I believe. Default is Sanboot if I’m not mistaken.

There’s different options because different hardware handles it differrently, annoyingly enough.

What error are you getting?

set username foglogin
set password foglogin
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme

Try using that, changing the set username and set password parts to your own webgui login info

@peirkern Ok, looks you’re doing this on Windows docker, which means it is using WSL2 as a backend.

https://github.com/libffi/libffi/issues/552

It seems that it doesn’t behave correctly in that environment currently (that specific package that is).

You might run into other problems as well if you’re unlucky.

You can try disabling WSL2 in docker settings and see if that helps.

@peirkern Both the “clock skew” and certificate failures would indicate a problem with your clock/datetime on the docker image, though the echo’d output seems to indicate it’s fine (or close enough anyway).

Still, can’t hurt to doublecheck?

Don’t know if it’s changed since then, but https://forums.fogproject.org/topic/10615/ipxe-booting-possibly-broken-on-os-x-sierra-update/ seems relevant

@fog_newb Some PHP files are already fine as they are, some are not, the database update one is one such that is not fine, hence the error.

@tramirez Try using a different hard drive to deploy to, so we can rule out hardware issues.

@fog_newb Ubuntu 21.10 uses PHP8 by default. PHP 8 has certain breaking changes that FOG isn’t compatible with yet.

So as Wayne said, safer to stick to LTS.

I’ll try and help out the devs with PHP8 support tonight if I find the time, it’s been something on my to do list, but I haven’t gotten around to it yet.

Comment mirrorlist AND uncomment baseurl (and if necessary change the baseurl to the one you want) in /etc/yum.repos.d/remi.repo

@renanrenan While that may be the case, it doesn’t seem related to the image type as this is long before it touches anything related to it.

Presumably you get stuck here: https://github.com/FOGProject/fos/blob/1085652c894e259c88fc069b2a0691099ad18d82/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L431

Are the win7 / win xp machines physical machines different from the w10 machines?

@mightmar RC2 is quite old (even compared to release 1.5.9, never mind the dev branch) Updating might help already.

Other than that, it’s likely an issue with https. Perhaps date/time isn’t configured in BIOS.

Checkout https://forums.fogproject.org/topic/15606/ipxe-boot-issue-boot-php-permission-denied/7 they had a similar issue.

@renanrenan There’s no error in the picture.

Does it hang on the “setting permission” step?