K2000: Any way to go back to the "old" WIM imaging method?
We're on the latest K2 version, and WIM imaging is great - but I think it was better for us in the previous "workaround" method. Let me explain:
I have 20 locations, all with the same base image - but separate post install tasks - therefore, I could point them all with the old workaround to that single WIM file. With the built in WIM support on the latest K2 version though, if I duplicate an image for all 20 locations, the WIM is copied over 20x, taking up 20x more space.
Is it possible for me to somehow go back to the old WIM imaging method?
Answers (4)
I posted a blog yesterday on this.
http://www.itninja.com/blog/view/do-you-want-to-store-your-wim-s-externally-with-k2000-v3-5-like-we-did-with-3-4
Comments:
Yes in fact we still use the "old" method rather than the new one for that exact reason. You can still use the placeholder images that came with the 3.4 KNIT. For our base image, I have a redirect bath file as a preinstall task that maps T: to where I store the image file, so no matter where I mapped their T: drive with the KBEM, they will always grab that particular image from the same place.
Although it may appear like a new .wim is created, on the backend, its just a link to the original. This is not evident when looking at \peinst\wim, but on the backend my duplicate wim was 2k.
Corey
Lead L3 Enterprise Solutions Engineer, K2000
If my response was helpful, please rate it!
I used 3.5 to create the WIM in the \peinst\wim folder and just copied that WIM file into the \petemp\imagestore folder and just rename it to whatever the old WIM file was with this updated file and it keeps all the old 3.4 images working, since all my images pointed to the same WIM
