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.

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

@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.

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.

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

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

Adjust accordingly.

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

@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.

Fairly certain the problem is that Snapins run under the System account, which cannot interact with the desktop, and thus you can’t “elevate” to administrator.

There is a missing , at https://github.com/FOGProject/fogproject/blob/ddcc96c4ff8158314ab0383f988c9c6666e8686e/packages/web/lib/pages/processlogin.class.php#L260

and

https://github.com/FOGProject/fogproject/blob/ddcc96c4ff8158314ab0383f988c9c6666e8686e/packages/web/lib/pages/processlogin.class.php#L283

@developers can you fix this one?

@enzogislard It doesn’t care about whether or not there is data on it, the structure gets captured and deployed.

@enzogislard I think it is a similar problem here, even if Centos.

If you move the swap partition before the root partition and then capture it again (in resizable mode) it should work I reckon.

Are you capturing in resizable mode already? Other modes will fail since your source disk is much larger than target disks, even if the partitions on it are smaller than the target disks (could be mistaken about this though)

@gfrancesco84 What is the output of list vol in diskpart?

@enzogislard This is a known problem on newer Windows 10 versions.

They put a partition (recovery I think) after the main Windows partition now, which FOG doesn’t handle that well currently. (it expects ‘data’ partitions to be last)

You can use a partition manager program to move the partitions around.

If you capture it after moving the Windows partition to the end of the disk, then it should work as expected.

@Tom-Elliott I kind of like that idea of a fallback mechanism, but I fear that it would kind of nullify what it’s trying to solve in a way.

Few people would know about the NVME naming scheme being essentially random on each boot and thus may presumably fill in the name of the drive. This would then get used and the size (if filled in) would be ignored.

I think if it were to be implemented as such, then the GUI should inform to use size over name for NVME drives.

PS: What happens when you have 2 identical drives?

@Wayne-Workman DATE() returns the date without the timestamp. So it will be assumed to be 00:00:00

Use just NOW() and drop DATE(), so that it is updated more accurately.

@benc Can you do

zstdmt -dc </images/_Windows10Prox641909/d1p4.img | partclone.info -s -

And paste the output here? It will tell us which version the image was made with. (if it works ofc)

You can of course build partclone from source from their github repo.

Let’s start with installing partclone 0.3.13, since FOG has been using that for a while and the image format is different to how it used to be. (it can still restore images made under older versions though)

Next up, you need to check the zstd version. FOG uses a fairly recent version (again backwards compatible, but older versions may fail on newer compressed files) Should be 1.45 I believe.

zstdmt -dc </tmp/pigz1 | partclone.restore -n "Storage Location $storage, Image name $img" -O ${target} -Nf 1

Is what FOS uses to restore an image back to a disk (deployment).

So for this case we can modify to

zstdmt -dc </images/_Windows10Prox641909/d1p4.img | partclone.restore -C -O /d1p4.extracted.img -Nf 1 --restore_raw_file

Tested this on my FOG server and it worked fine. Let me know how it goes.

@x23piracy It’s safe to delete if you don’t need that partition.

Alternatively, you could manually create the partitions in windows setup I suppose.