New
#600
Thanks for the write up - that definitely helps.
Based upon your first 2 answers, as soon as we use a custom file for Pass 1, all of that goes out the window, then, and we're forced to make all of these partitions manually. Correct?
Reason I ask is that when using a regular Windows 10 install tool, there is some sort scheme being used to set up everything - the computer I just built and used an MCT generated install USB created the following with 0 customization to the USB - I didn't even do my traditional Moving of \Users tree to a separate HD (see this tutorial: Move Users Folder Location in Windows 10) because this is all a temporary install until I get a true HyperVisor installed on the machine and make VMs for all the different OSs I want to use as guests in that. But this is the partition scheme that it created:
So, my (apparently incorrect) rationale was that if you don't specify the information in the answerfile under Pass1, then it just makes what it would normally make. Oh well.
So, now I need to collate all of this info together, from the original tut, my modifications to my own answer file, and our subsequent discussion over the last couple of days to get this all into a working single package, that I can then image into a few USB drives and do some mad installs (versus using a PXE boot and image through something like CloneZilla, as these machines are not isolated from the live testing computers, and the last thing I want is to accidentally cause issues like IP address conflicts on reboot that take down someone taking a live test.
I was hoping this would be an easy fix to get all the little things like partitions, UWP app removal and the little Customization all fixed in one go. But since I'm using VMs now, I can play and experiment and see what happens. So that is exactly what I am going to do.