1

answers of this question is very important to administrators to choose between Microsoft solution or other 3rd Party Tools.

WIM solution is file based and others are sector by sector images like Acronis or other backup and clone tools like Norton Ghost or Cloning in vmware ESXi and etc.

My question about the advantages of WIM to edit or deploy in Enterprise? to get agreements of managers to choose between these alternative decisions.

Are we had any Key Performance Indicators in Change management?

Are there any statistics about compares of these solutions?

What Time is spend in any solotion to get image or change images or revert and apply images?

Is it possible to change and modify images that made in All of these solutions as easy as in WIM file?

2

ISO vs WIM

Sector-based imaging is best used for quickly backing up (similar hardware) machines/disks (a limitation of cloning is that it doesn’t support simple updates to the images; any updates require a new clone image).
File-based imaging is for flexible, fast image deployments and easier updates in a mixed hardware environment. (can be deployed to any hardware resulting in a smaller image library that often leads to more efficient deployments)

ISO files contain WIM file (making it more portable & may be extracted to a single file if deployed in Windows environment) eg. Windows 10 ISO contains WIM file (BOOT.WIM, in Windows installation disks, contains a bootable version of Windows PE). Windows boot loader supports booting Windows from within a WIM file.

WIM images are engineered to perform optimally in Windows systems, but conversion to ISO will render the image more portable.
For operating systems that don't support WIM format, wim images may be converted to the more commonly used ISO image using the Windows Assessment and Deployment Kit (ADK).

Unlike sector-based formats (such as ISO or VHD), WIM is file-based: The fundamental unit of information in a WIM is a file. The primary advantages of being file-based is hardware independence and single-instance storage (prevent data duplication). Since the files are stored inside a single WIM file, the overhead of opening and closing many individual files is reduced. Also the cost of reading or writing files is eliminated by disk caching & sequential data access.

WIM files can contain multiple disk images, which are referenced either by their numerical index or by their unique name.

dism /Get-WimInfo /WimFile:"c:\path\install.wim"

Images may be extracted to a single file:

dism /Export-Image /SourceImageFile:"c:\path\install.wim" /SourceIndex:3 /DestinationImageFile: "c:\temp\install_3.wim"

Due to the use of single-instance storage, the more each successive disk image has in common with previous images added to the WIM file, the less new data will be added. A WIM can also be split (spanned) into multiple parts.

File-based cloning also results in defragmented drives (inherent benefit). Thus a drawback is that only one volume (formatted filesystem) can be cloned at a time, and the initial cloning will be slower, esp. on at/near capacity disks being cloned since file access requires the system to read the filesystem directory, process the location of the file, access the file, and then read it for cloning.

This overhead doesn't apply to sector-based cloning, which just reads & copies bytes on disk, resulting in a faster initial cloning. Another benefit of this method is that files that have been deleted, corrupted, or otherwise lost from the filesystem are also recoverable in the clone.

References:
https://en.wikipedia.org/wiki/Windows_Imaging_Format
https://www.smartdeploy.com/blog/the-difference-between-file-based-and-sector-based-imaging/ https://www.cnet.com/news/differences-between-file-level-and-block-level-cloning/

-1

When our image is editable we can configure it for enterprise goals.

  1. apply new updates on WIM files IMAGES
  2. mount images to system and then commit changes to apply on images when we want.
  3. obtain language packs or drivers or anything else we want on the images
  4. CONVERT WIM files to VHD (WIM2VHD) and create virtual machines in SCVMM or Microsoft Virtual PC. and then convert them to VMHD in vmware
  5. single instance : instead of 10 images for 10 PC we have single instance like TEMPLATEs

Deploy many of OS in various Hardware are not easy for thousand of clients!

so if we have images that based on files , there are configurable

hardware independent images has more flexibility.

we make it once and use them for diffident systems

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.