I have a blog about storing wims externally with the 3.4 kbox.
http://www.itninja.com/blog/view/wim-storage-freeing-up-space-on-your-k2000-if-you-are-using-wim-s
I have been reapplyed the patch 3.4 wim package to my 3.5 box and it worked fine till I informed Kace I was doing this. Mysteriously now the capture wim button keeps disappearing from the imaging menu overnight every couple of days ever since I told the Kace Engineers about my by pass. Well I got tired of having to reapply the .bin file so I found a new method.
I found the easy solution for this. If you installed the native imaging kits to your 3.4 box the .hta file to do the work is still there it just does not show on the imaging window.
If you want to use the external method:
Confirm the k2000 still has the needed file. Go to \\ikbox\peinst\hta and see if you still have the file capture_wim.hta.
If that exists:
boot with your external net use mappings like in the old blog
from the main menu choose recovery and then choose command prompt
enter y:\hta\capture_wim.hta and the capture box will pop up. Fill it in like you did in 3.4 and go for it.
Let us capture natively to the RSAs please, KACE! - nheyne 11 years ago
I know of one person who had this file removed when they were tethered to it. They had to flush his peinst files and reapply the update so his file went away. He did not want to reapply the knit to version3.5 k2000 fearing it would create a problem. - SMal.tmcc 11 years ago
A workaround would be to grab that file when it is there and copy it to petemp. Then in kbe, you can run the file by accessing T:
However, I do not recommend that you apply the update to 3.5, this does overwrite the built in ability to capture a wim integrated into the k2.
Corey
Lead L3 Enterprise Solutions Consultant, K2000
If my response was helpful, please rate it! - cserrins 11 years ago