Switching to use the x64 boot media seems to have fixed it. Not sure why, but there ya go.
MDT Image Build and Capture Task sequence failing
I had a task sequence that had been successfully creating and capturing a Server 2019 image using HyperV as the build host. Now, all of a sudden, it's failing to complete. It always fails during the "Install Operating System" step with DISM errors (see screenshot). I've tried creating a new task sequence, deleting and reimporting OS install files, uninstalling AV, etc., but I just can't seem to figure out what's wrong. Anyone have any ideas?
My setup:
MDT 8456 w/ hotfix
ADK 2004
MDT host - Server 2019 Datacenter with Hyper-V role, Dual Hexcore with Hyperthread, 48GB RAM
VM specs during build - 8CPU, 16GB RAM (dynamic memory disabled), 80GB HDD
1 additional answer
Sort by: Most helpful
-
Anonymous
2021-02-02T08:17:36.797+00:00 Hi,
Thanks for posting in Microsoft MECM Q&A forum.
A couple of things:
- The error you're getting is "Not enough memory resources are available to process this command". This can sometimes be a memory issue, but is typically a hard drive space or scratch space issue.
- Not sure how large your uncompressed image is, but try increasing HDD space to something larger than 80GB.
- Try increasing RAM.
- In your deployment share's properties, Windows PE tab, try increasing scratch space size. There is a Platform dropdown which will allow you to change which boot image you're modifying the rules for. Be sure to update your deployment share afterward.
Similar thread for your reference: MDT for W10 v1809, fail to install OS
Best regards,
Simon============================================================
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.