When capturing an image with WIM, all files are compressed into a single WIM file per volume. This is captured locally, then uploaded to the K2000. This means that when planning a WIM image capture, one must be careful of how much space remains on the volume, the rules being to have at least 50% of free space for the compression. The reverse happens when deploying, the full WIM file is copied to the target then the WIM is extracted locally.
K-Image is proprietary to KACE
Files are captured and deployed one-by-one to and from the K2000 and use a de-duplication algorithm. This means that image are generally slower to be created and deployed than WIM. Image creation speed is lower at first but as more de-duplication is done, the Image Creation will be faster. The more files the systems captured have in common, the lower the amount of space required.
WIM and K-Image are managed in the same manner on the K2000.
WIM is a great solution when trying to deploy a high number of systems in a short amount of time via Multicast. Even on a one-by-one basis, WIM can be several times faster than K-Image deployments
K-Image is the superior solution if the goal is to capture a large amount of System Images, as the de-duplication will prove invaluable where WIM would rapidly eat all available space.
K-Image can be used to perform a very useful delta deployment. To do this, you would not format or partition the hard drive and leverage the "Remove files not in image" option to 'refresh' the system.
This can make the process much faster and more efficient than re-deploying from WIM, especially for large image deployments.
System Images captured with K-Image can be configured and customized, later on, allowing more flexibility.