Open HedgeComp opened 3 weeks ago
rbalsleyMSFT
commented
3 weeks ago Thanks. I think what I'll do is change the code in 2410 to not be reliant on the location of where the ComputerName setting is. The original intent was for just being able to set the Name, but now that folks are using other components, it's probably best to not care where that component is.
HedgeComp
commented
3 weeks ago Sounds like a good idea, I was going suggest that or look at the code myself.
FYI I've had a few colleagues who've been using your FFU now and the common troubleshooting issue seems to be with Unattend.xml s so I thought samples would help everyone. Helpful for all those who are coming over from Using MDT deployments. Used to take hours some times to prep a machine.
So one a side note, I know this all started as EDU sector, but your FFU is really saving all of us in the field a ton of time. With FFUs on a Gen2 USB , I've been deploying Fully Loaded Workstation PCs for Drafting environment, in less then 4 minutes! So thanks for all work and taking our recommendations on this script!
🥂 Scott
Based on the following issues. Thought it would be helpful for others and cut down on repeated Issues creation
59
adding Comments to XML files to ensure proper placement of the
<ComputerName>in the first Component Element.56
In continuing the Theme of using Sample Files. Created a SampleUnattend.xml file that contains some simple customizations and previous resolutions to Issues for proper placement and parsing of the Unattend_xx.xml file.
@rbalsleyMSFT not sure if you closed the last pull during the commit to Main branch, but I am adding this again just in case it was a timing issue.
Cheeers!