@wmw509 Disabling CSM makes sense. I’ve seen a lot of bioses that if CSM is enabled it only lets you use the legacy/bios pxe boot. I’ve had that disabled on all my hardware for so long I forgot it was a thing.
@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:
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.
I have solved this thread because as @Junkhacker stated, this is fixed in the dev builds as I am not using gzip compression on the page at all any more. If you are worried about the display, please update to Dev.