The boot.wim on regular Windows boot media is in the /sources folder. If you are talking about the Dell recovery media then that's something different. I believe they use a custom OEM WinPE image
I'm actually in the middle of a project doing this myself but used the excellent WimWitch (https://www.powershellgallery.com/packages/WIMWitch/2.3.3) along with MDT to create the initial USB. Very lightweight install and contains a couple of our corporate apps. Initial build done by IT then send a Sysprepped device to the user for them to go through OOBE/Autopilot.
WimWitch is an amazing effort by Donna Ryan. I've used it myself on occasions. Using MDT for image base creation is also a valid solution. Especially if Whiteglove bit you in the backside.
The main issue I have with MDT is the overhead of maintaining the solution. It's fine if you have a high skill department with loads of expertise, but if you don't have a dedicated person or team to work on the MDT image then it falls in disrepair quickly. I tend to work as a consultant for organisations that don't have a deep bench of talent, so I focus on solutions that will work for them in the long term.
FYI, you will need this article if your install.wim file is larger than 4 GB, due to the limits in the FAT32 file structure: https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/install-windows-from-a-usb-flash-drive?view=windows-11#if-your-windows-image-is-larger-than-4gb
Thank you so much for this guide, incredibly helpful!
Hi, anybody know where is the boot.wim located on Dell laptops, i just want to add hard disk drivers to the default boot.wim .
The boot.wim on regular Windows boot media is in the /sources folder. If you are talking about the Dell recovery media then that's something different. I believe they use a custom OEM WinPE image
I'm actually in the middle of a project doing this myself but used the excellent WimWitch (https://www.powershellgallery.com/packages/WIMWitch/2.3.3) along with MDT to create the initial USB. Very lightweight install and contains a couple of our corporate apps. Initial build done by IT then send a Sysprepped device to the user for them to go through OOBE/Autopilot.
WimWitch is an amazing effort by Donna Ryan. I've used it myself on occasions. Using MDT for image base creation is also a valid solution. Especially if Whiteglove bit you in the backside.
The main issue I have with MDT is the overhead of maintaining the solution. It's fine if you have a high skill department with loads of expertise, but if you don't have a dedicated person or team to work on the MDT image then it falls in disrepair quickly. I tend to work as a consultant for organisations that don't have a deep bench of talent, so I focus on solutions that will work for them in the long term.