Captured Image is about the size of the Hard Drive

[KevFlwrs]

Greetings,

I am currently working on capturing an image to a fog server. I’ve registered the client and added the Image. I’ve set up the task, and ran sysprep. Once it reboots, it begins the capture. First, it captures the 100 mb system reserved. Then it moves on to the next partition. This image is only taking about 22 GB of space up, looking at the image management, I shows as 232 GB under “image on client”

Has anyone had a similar issue? Any ideas on why this is happening?

I’m using version 1.3.3 of Fog Server. The image I’m attempting to capture is Windows 10 version 1809. I’ve attached a couple screenshots.

[Junkhacker]

the images didn’t attach to your post, it seems we’ve had a problem with that on the forums lately. i don’t understand what the issue is. what settings did you use for your image?

[KevFlwrs]

[IMG] http://i68.tinypic.com/2llezwk.jpg [/IMG]
[IMG] http://i67.tinypic.com/1zya5on.jpg [/IMG]

[KevFlwrs]

The two links I posted are my images I attempted to attach.

[Junkhacker]

@KevFlwrs again, what settings did you use for your image? what you’re seeing would be perfectly normal if you are using a nonresizable image type.

[KevFlwrs]

@Junkhacker the image type is set to “single disk - resizable”. Partition set to “Everything”

[Junkhacker]

@KevFlwrs the “size on disk” is the partition size that partclone is trying to capture. fog tries to resize the partition down before capturing it, but it can only shrink down to the last used block on the partition. you might be able to get it to shrink down if you defrag the drive before you attempt to capture the image.

[Tom Elliott]

Don’t forget to ensure bitlocker is disabled. In the past even if you didn’t enable it specifically, bitlocker would encrypt the free space which could cause this type of issue as well.

[KevFlwrs]

Thanks to @Tom-Elliott and @Junkhacker. I’ll give both of these suggestions a shot.

[george1421]

@KevFlwrs Just to confirm what Tom said, check out this thread that discusses the same issue and the commands needed to disable it: https://forums.fogproject.org/post/102522

Review the posts by @THEMCV they are enlightening to what may be causing this issue.

[rogalskij]

I realize this post is a bit old, but I wanted to thank everyone for their suggestions and give our experience to back up what has been said in this topic already. We experienced an image that should have been about 120gb, but was showing in FOG as the full 500GB hard drive. After referencing this thread, it fixed the issue. The steps we took are below in order:

Verified that the PC didn’t have a second drive or second large partition it was capturing
Verified that bitlocker encryption was OFF using the command prompt command “manage-bde -off C:”
Ran Disk Cleanup (to get rid of old unused files)
Ran Tools > Check to scan for hard drive errors (may require reboot to fix)
Ran Tools > Tools > Optimize and defagment
Capture Image again

Once we did those steps, the newly captured image only takes up the actual amount used on the hard drive.