So the captured WIM's are stored in the peinst\wim folder but it's read only. Anyone tried to change permissions for these files so you can replace them?

1 Comment   [ - ] Hide Comment


  • What I am wanting to do is update the Unattend.xml for a system image I uploaded. I want to be able to mount the WIM with DISM and then commit those changes so I can move on with life. It looks as if my arm is being twisted to use the K-Image method. I like using WIM's because I can use VM's to build and maintain my base images. Anyone know if you can capture a VM with the K2000?
Please log in to comment

Answer this question or Comment on this question for clarity



I have created entries in the LockPermissions table in Installshield or Wise that have worked just fine for that.

There have been other instances out of packaging where I have used cacls.exe or Xcacls.exe to modify file/folder perms.


I hope this helps.



Answered 10/03/2013 by: T5_Driver
White Belt

  • the peinst share he is referring to is on the k2000 which is open BSD
    • Ah...ok. Learn something new every day!
Please log in to comment

I don't believe you can change permissions to peinst, although I would love to have access to it.

Answered 10/03/2013 by: nheyne
Red Belt

Please log in to comment

you need to copy the wim from the share to a windows share and edit it there.  Then you can run a map preinstall command to access that share for the wim file.

Answered 10/03/2013 by: SMal.tmcc
Red Belt

  • are you talking about using the old petemp directory? Because thats the old way of mapping the wim directory deploying.
    • no the kbox stores them here. \\ikbox\peinst\wim\XX and I was referring to using external mapping to store and deploy from as in a windows server share. see http://www.itninja.com/blog/view/wim-storage-freeing-up-space-on-your-k2000-if-you-are-using-wims-k2000-version-3-6
Please log in to comment