MDT and Windows 11 - MDT capture fails that there is not enough space

Question

I built my golden image in hyper-v as I have been doing for years. Logged into the VM, went to the deploymentshare\scripts\litescript.vbs. It runs and reboots and starts to capture and then fails that there is not enough space. There is 500GB of space on the server it's being captured to and there is 120GB of hard drive space on the VM image.

MDT: 6.3.8456.1000
ADK: 10.1.22000.1

Any Ideas?

Answer 1

Hello,

I had the same problem. I ran Litetouch script from windows environment (not from iso or pxe) and it solved this issue for me. It caused that script ran under C drive and it had enough space for this capturing.

Best regards,

Jan

Answer 2

Hi guys

I had the same issue and tried everything that was suggested on the trusted forums. However, after trying all the suggestions, my capture would still failed.

I then did the following:

• Allocated an additional 10GB to my VM.
• Using Hiren, I resized the first partition {Healthy (EFI System)}, allocating the 10GB to it (may be too much, but this is how much I allocated)
• I logged back into my VM and started the capture process again and it WORKED!!

My diagnosis:

When the deployment starts, it looks at the first partition to dump any temp files on it and if the partition is too small, it fails the process.

@Ray, Rick please give this a go and let me know if I was able to help.

Answer 3

I also just created a new VM with windows 11 and no modifications. Full, 127GB hard drive space and same exact issue.. But still, the windows 10 image captures with the exact same settings.

The only other weird thing I notice is that when I run litetouch.vbs, it asks the questions about picking a task sequence, giving it a name, etc but then it reboots and asks all the questions again. This happens on both windows 11 images. That has never happened on my previous captures of previous windows versions

Answer 4

That is a screenshot of disk mgmt in the Windows 11 image.

Here is the screenshot of the capture server. It captures to the C drive:

I would also point out that I have a windows 10 image on the same server in hyper-V that I can capture without issues, doing it the exact same way I am trying to capture the windows 11 image.

Answer 5

Any other ideas?