@sebastian-roth I have not, it seems to have just been that one time.

That error says that partition 4 is too small. So it seems to think that the image is bigger than the spin 5’s drive.
Looking at your image settings I’d recommend recapturing using partclone zstd at compression level 19. Probably won’t fix this problem, but might speed up your imaging while saving space on the server.

I believe the when fog captures the image it shrinks it down to only what is actually in use, so your scenario should work. Personally, as a fail safe, I use a 80 GB virtual disk size for my images which never had an issue deploying to 120 GB drives. Granted after a while we found that users with 120 GB drives ran out of space just from windows maintenance (updates, caches, etc.), well that and the users never deleting an email in outlook.

So if it’s feasible, maybe try recapturing the image with the virtual drive being smaller than anything in your environment. (80-120 GB perhaps).

@brakcounty To get some more information, can you please schedule a debug deploy task (same as you would do a normal deploy task but just before you hit the last button in the web UI there is a check box for debug). Boot up the client as usual and let it boot up. Then you need to hit ENTER twice to get to the shell. Now type fog and ENTER again to start and step through all the process till you hit the error. It will throw you back to the shell. Now type:

sgdisk -gl /images/Win10Standard_GPT_EFI/d1.mbr /dev/sda

It surely will fail. Take a picture of the screen and post that here.

@jjsplitter Since you still had firewalld enabled, did you remember to set selinux to permissive? If not you will have a sad time when you try to capture an image.

@JJ-Fullmer this is awesome thank you for sharing your knowledge and scripts.

The OP’s problem can be solved with the location plugin in FOG 1.2.0, and FOG 1.3.0. Documentation on the plugin are linked below. Marking this thread as solved.
https://wiki.fogproject.org/wiki/index.php?title=Location_Plugin

@Wayne-Workman

I think so, if any new info or issues related comes up I’ll post.

An image defined as “All disks” will upload from all disks and deploy to all disks… So, yes. You need to (re-)upload.