As alot of applications tend to grow in size both amount of data and amount of files, there is a need for a solution which contains all these files during distribution of the package.

I have created a simple extension which lets you put the installationfiles into a WIM (Windows Imagefile). Please let me know what you think.

EDIT: I just realised i wrote this in the wrong place. Can a mod move it please?

1 Like

Interesting concept. Glad to see I’m not the only one thinking about things like this. I’ve been masticating a similar idea but couldn’t decide on the best route:

  1. Use Zip with little to no compression - Makes it easier for less seasoned techs manage the package.
  2. Use WIMs - I believe there’s a slight performance benefit to using a WIM over ZIP but I could be persuaded otherwise.

Thanks for sharing!

The main reason for going with WIMs are that you dont have to have double the space to use them. Just mount it and get access to all the files then unmount and everything is as it was before.

1 Like

That’s another valid point I think is often overlooked.

Well mounting/unmounting and compressing/decompressing are two different things. For simple tasks, it is not really worth the trouble to create a wim and then write code for using it, in my opinion.

I realised i posted this with my other account :slight_smile:

Well as i stated in the original post, this is only an issue where you distribute the package to alot of clients using a system (MEMCM) which makes one request to the distribution point per file. A package with 40 000 files will be slower to transfer than a package with 5-10 files.

In the organisation where i work, we package alot of applications using PSADT, some weeks its 5-10 applications. And if there are issues i am usually the guy who have to solve them. With that in mind its easier to have every tech package the applications in the same manner even if it adds a little complexity.