Fog expanding image

[chris_unit]

Hi there,

We’ve intenntially shrunk our partiton size of windows so that it can fit on a variety of systems we have here, but we’re finding after we’ve put the image back on systems, it’s expanding into all the unused space on the disk.

is there a way to prevent this?

Its either that or windows on first boot is expanding the system partition to use all the unused space.

Thanks

[Sebastian Roth]

@chris_unit What image type is it set to? Resizable or non-resizable?

[chris_unit]

@sebastian-roth That’s right, it’s about 40gb of data on a partition that’s 250gb.

ideally it would shrink the partition down to 40gb to take the image as then repliccate the partition table when it’s deployed back to 250gb

[Sebastian Roth]

@chris_unit Sorry, I don’t get what you mean.

but we’re finding after we’ve put the image back on systems, it’s expanding into all the unused space on the disk.

To me this sounds like you don’t want it to expand on deploy, right?

ideally it would shrink the partition down to 40gb to take the image as then repliccate the partition table when it’s deployed back to 250gb

Now this sounds as if you want it to shrink/expand?!

Need more information to be able to help you with this.

[chris_unit]

@sebastian-roth

hi there

here’s an example:

we have two types of systems
system a
system b

ssd in system a is 400gb
ssd in system b is 280gb

data to be captured on image 180gb

we want the image to be the size of the data used (180gb)

we can’t have any expanding, becuase if we take the image again, it will be too large

so we’d like fog to, shrink image during capture, then ONLY expand to the original partition size of 180gb.

[Sebastian Roth]

@chris_unit said in Fog expanding image:

we can’t have any expanding, becuase if we take the image again, it will be too large

I think this part was missing in my understanding. From what I get you follow this procedure: System A is captured to have an image in the FOG server. This image is deployed to system B. Now system A is given to a user and if you need to capture the image again you would just capture from system B (or C) and deploy that image to system D. Right?

While you can do this it’s not really great practice. In “my” world of imaging I always advice people to have one master machine (be it a physical PC or even a virtual machine) that is used to prepare the perfect golden installation on. This master is always used for capturing and not given to any user no matter what.

On the other hand I have to say that your cycle of capturing from different hosts does not necessarily have to cause a disk size problem. What you describe (image to big to be deployed to a smaller size disk) is an issue with FOG 1.5.9 and earlier version as Microsoft changed WIndows partition layouts with build update 2004 or maybe even 1907. This issue is fixed in the latest inits. So you might just download and use those new inits from github to get around this restriction.

so we’d like fog to, shrink image during capture, then ONLY expand to the original partition size of 180gb.

This is not supported by FOG as of now and I don’t see why we should add this. 99.9999 % of users want us to expand to full disk size and they blame us if it doesn’t work as expected.

[chris_unit]

@sebastian-roth Hi there
we’ve done some testing and found that non resizeable seems to move between different size disks and puts the partition size back to 200gb

i think this should do the trick