![]() Capturing and deploying FFU images is fast, in fact much faster than using any third party software. FFU images are 100% exact copies of the disk, sector by sector. ![]() The smaller the disk on your reference machine therefore, the better images will be smaller and can be deployed to more destination machines.ĭISM with FFU is also practical if you have to replace an HDD or SSD just capture an FFU image, replace the disk, and apply image to new disk. This is the only con I can think of if your reference machine you used to build an image has a 512 GB disk, that captured FFU image can only be applied to destination machines with 512 GB or larger disks. How much storage capacity is used or free on that disk is irrelevant, only affecting the size of the captured FFU image file. This means that whereas a WIM file can be applied to any size HDD or SSD, an FFU image may only be applied (deployed) to disk which is the same size or larger than the captured disk. FFU captures a disk sector by sector to a file container that holds an exact image of the disk. ![]() Since Windows 10 version 1709, you can use DISM to capture and deploy FFU (Full Flash Update) images.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |