Sorry for my late reply, re: the other thread that I started on this. I don’t manage the hardware-side of the FOG server so i couldn’t get the file specified. I was also furloughed from work for some time, so I’ve missed the earlier updates.

@Tom-Elliott No, I’m not capturing multiple partitions. The issue is, that for years the image size on client reflected a file size that would be normal for an image captured post-compression for storage, as in a 30gb Windows installation stored in an image file below 20gb. Each time that I’d update the image and re-upload it, the file size would stay approximately the same.

But in recent months, without warning, the image size on client in the web interface has been erroneously reporting that the image files were far larger than they actually were, essentially adding the old file size to the new one, resulting in a huge file report, despite not being that big.

@Sebastian-Roth The images are set reizeable, and yes, every time the image is updated, the file size is reported that it’s the sum of the old file size added to the new one.

We’ve verified that the image file is no where near as big as reported, but it’s strange that a file that takes up 8gb on our server is being reported as being over 50gb.

Hi, we’re currently running version: 1.5.7.56 of FOG and in recent months, we’ve been encountering a strange issue. Specifically, the “image size on client” field is coming up incorrect.

Our usual Windows installations are around 30gb in size, with an image file less than 20gb in size. However, now each time we upload a new image file, the “image size on client” fields just adds up the size of the old file and the new one, increasing each time the image is updated.

We verified on the server that the image files are the correct size, but the web interface continues to show the wrong value.

Any ideas?

I’ve been having some issues deleting images and reclaiming used disk space when attempting to remove unneeded system images. Using the option to remove the image definition and data doesn’t result in the image being removed, but selecting the image from “List All Images”, checking the image in question and selecting it for deletion appears to remove the image definition but not the data. When I review the amount of disk space used, it remains unchanged. Is there a “disk cleanup” option to reclaim disk space that I’m overlooking? Any help would be greatly appreciated.