If you're applying an optimized FFU, you have to use WinPE, version 1903, or later.Ĭonnect a storage drive or map the network location that has your FFU file and note the drive letter, for example, N. You can't run /optimize-ffu on the same disk as the captured FFU. The /Optimize-FFU DISM option allows you to choose a partition that will automatically expand or shrink after the FFU is applied to a disk:Ĭopy the FFU file to a technician PC running Windows 10, version 1903 or later. This command also gives a name and description to the FFU image. DISM.exe /capture-ffu /imagefile=e:\WinOEM.ffu /capturedrive=\\.\PhysicalDrive0 /name:disk0 /description:"Windows 10 FFU" name is required, /description is optional. This information is displayed when you use dism /get-imageinfo. The /name and /description arguments allow you to set information about your image. The following command captures an FFU image of PhysicalDrive0 called WinOEM.ffu. Note that you shouldn't have to specify a PlatformID when capturing a desktop image. To see command line options for capturing FFUs, run dism /capture-ffu /? or see DISM Image Management Command-Line Options. For example, to capture Disk 0, you'd use /CaptureDrive:\\.\PhysicalDrive0.įor more information about PhysicalDrive X, see CreateFile function. For disk X:, the string used with /capturedrive will look like this: \\.\PhysicalDriveX, where X is the disk number that diskpart provides. Use DISM to capture an image of all the partitions on the physical drive. This is the value that you'll use when capturing your image. Make a note of the disk number in the Disk # column. You can use diskpart, or add Windows PowerShell support to WinPE and use Get-Disk for scriptability and more complex setups such as a server with multiple disks. Identify the drive to which you'll be capturing the image from. For optimal performance, use a 1 Gb or faster network.īoot the reference PC using WinPE bootable media. Network storage where you can keep your FFU image. For best performance use a USB 3.0 drive to store the image, and an internal SSD for the destination device. For best performance, you want to maximize I/O between where your FFU is stored and the destination PC. You can use the same USB drive for WinPE and storage if you follow the instructions for creating a multipartiton USB drive. 16 GB is enough space to store an FFU of a basic Windows image. USB storage, formatted as NTFS with enough space to save the FFU. The latest version of the ADK, from Download the Windows ADK. The hard drive on this PC will be overwritten, so make sure you're using a PC that doesn't have any information you want to keep. We'll refer to this as the destination PC. For a walkthrough on how to create an image that's ready for deployment, see the OEM Windows deployment lab. A Windows PC that has been generalized with Sysprep.To capture and deploy FFUs using the instructions below, you'll also need: To deploy portable FFUs, you'll need WinPE for Windows 10, version 1903 or later. To capture, deploy, and mount FFU images with DISM, you'll need to work in a Windows 10, version 1709 or later or WinPE for Windows 10, version 1709 or later environment. What you need to work with FFUs in Windows You can't capture an FFU of a hard drive that uses MBR-based hard partitions.Capturing an FFU captures and entire disk, with no mechanism to exclude specific files.Splitting compressed FFUs is not supported.Captures of disks that have Volume Shadow Copy Service (VSS) enabled are not supported.FFU captures of encrypted disks are not supported.If you don't optimize your FFU, the drive that an FFU is applied to has to be the same or larger than the drive it is captured from.Applying an optimized FFU requires Windows 10, version 1903 WinPE version 1903 or later.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |