@ProfDrSir said in Imaging Windows 10 v2004 with UEFI - GPT Partitions onto 31GB or smaller drive. (and failing):
which fat standard are you using?
There are two methodologies here. The first is a thin image in that only the windows OS and updates are added to the reference image. All other applications like office, SAP, acrobat reader are added into the image on the target computer. The advantage to this is that when updated versions of acrobat reader or other applications come out you don’t need to rebuild your reference image (because it only contains windows + updates). You just change your post deployment tasks (snapins, or what every deployment tool you are using to deploy the later application)
The second is a fat image, in that you load all applications onto your reference image before you capture it with FOG (understand if you have applications that are based on a unique guid, like enterprise antivirus you must install those post imaging anyway). All of the time of loading these applications goes into the reference image and not post deployment. With MDT it takes about 1.5 hours to create and configure the reference image. When I capture it with fog the reference image is about 98% of the completed image. With a fat client I can take a workstation and go from bare metal to ready to move to the user’s worksite in 15 minutes. The system is fully configured and ready to roll. I don’t have to do much post install configuration.
To recap a thin install gives you the flexibility to modify the deployment with different applications or configurations at deployment time. A fat image you put all of your work in to the reference image up front and then enjoy rapid deployment on the back end.
Before win10 our methodology was to use the thin image approach because we could create a standard OS reference image and use it for a year or so. Basically the applications would update version more often than the OS. Now with Win10 we have to build a new OS every 18 months so the OS updates more frequently than the applications. That makes the fat image approach more beneficial.
As I mentioned a few times previously we use MDT and the lite touch approach to build our reference image. That way we can get a consistent build each time we rebuild our reference image. When we go between 1903 and 1909 we just copy our task sequences between builds and we get the same results (hopefully) when we build a new base image on the next release of windows 10 (the last OS you will ever have/need).