Like others here, Im looking to upload modified wim images to the kbox, without having to create a new scripted install and add all the tasks to it every time.

With Win10 and rollup updates coming out frequently, Ive gone from making system images to scripted installs, and using scripts to customise the look and feel. This allows me to keep the deployment up to date.

But having to upload the install media each time i make an update to the install.wim, and then adding all the tasks / processes to a new scripted install is a pain. It would be much better/easier if i could just upload the modified/updated install.wim file to the kbox, replacing the existing install.wim.

This way, i wouldnt need to re-create a scripted install each time.

Reposting this comment from Will Green in 2013:
"At a minimum, allow read/write access to the PeInst\WIM folder, so we can copy down WIM images and do offline editing of them using DISM. As it stands, making even minor changes to an image requires applying, booting, unsealing, then resealing and recapturing the image on a VM or PC. Exceptionally time consuming when I can do the same thing in DISM with two commands inside 10 minutes."

Please allow us to have read/write access to the wim images as Will requests. We can do many image manipulations with DISM, like adding drivers, much faster with this type of direct access. If this isn't possible and explanation of why would be in order. Thank you!

I understand the need, believe me...
But why not a midlevel task, there isn't anything you can't do that I can image!!

A request like this is highly needed we need to go thru more extra steps and rework in order to test quick changes.

The next step in a future release will be to enable WIM manipulation in the same manner as we allow KImages to be manipulated.

Since updating to the latest version and loosing the ability to manually manage/copy WIMs to the Kbox its impacted our productivity negatively. Was easy to run test in a lab environment and then just quickly copy that WIM to the production system now using the import/export function just takes too long plus you basically need double the storage space.

I would second this...would be really useful to be able to upload WIM images back to KACE, especially if it's just one or two small updates that need to be injected. Far less hassle than a redeploy and subsequent recapture.

Thanks

Scope for most users is to edit the WIM on their machine and upload it back into this folder (for editing the unattend.xml or driver injection). My scope is so that we can remove unneeded images from the K2 and have them housed on a particular RSA (where they are needed) and save room on the K2 (since someone thought 500GB was all that was needed - yes I know we can offload, but NFS drives are hard to make on compellant when you don't buy the module).

There used to be read/write access. That's how we saved room on our K2 was by copying the WIMs to a RSA and then deleting the original WIM from the K2. Since they've revoked rights to most of these folders, I cannot customize the boot images to reflect our company anymore either. I was in the middle of building a kbe that booted to a clonezilla server, and then they revoked rights to these folders. I can't change anything anymore. Seems as if they want to regulate end users like Apple.

At a minimum, allow read/write access to the PeInst\WIM folder, so we can copy down WIM images and do offline editing of them using DISM. As it stands, making even minor changes to an image requires applying, booting, unsealing, then resealing and recapturing the image on a VM or PC. Exceptionally time consuming when I can do the same thing in DISM with two commands inside 10 minutes.

I just need read/write access to the peinst\wim directory. If I can mount these images with DISM and commit the changes I would be satisfied with this product. I manage my images virtually and capture them with Image-X. Please, someone just let me access these files and I will be on my way.

Currently there is no way to edit wim images that has been captured by the kbox. the only way to do it is to use Post installation tasks. i'd like to directly mount it from the folder where the wim resides.

WIM (and DMG) are essentially compressed disk images (in many ways similar to a ZIP file). We would have to spawn a local instance 'disk', extract the WIM to it, allow you to change the file, then somehow re-package the WIM. With possible image sizes for WIM hitting multiple gigabytes, you can see how this process would take quite a while, even if implemented. Our suggestion is that if you need to make changes often, you might look into K-Image as your gold master, and then when ready to commit a deployment, recapture with WIM.

With the new intergration of .WIM we should be able to have an option to browse the .WIM as we do with the K-Image from the web portal.

For example, if we backup a machine that we're redeploying using the .WIM functionality and in 4 weeks time we need to grab data off a users profiles desktop then we need to manually mount the image and then grab the data. Where with the integrated browser from the web portal we could instantly browse it.

Thanks.

You can update your own .wim using DISM on a windows machine at this time.

Looking forward to the Native Imaging capabilities in the K2 3.4 update, but my understanding of it is that if we wished to update the WIMs we would have to just upload a new, updated WIM.

Could we have K2000 automatically update the WIM on its own?