Before upgrading to 3.5 on the K2000, I was able to store Wim images to a separate server by using the Kmanipulator and remapping the T: and W: drives.  Since the upgrade, Wims are no longer saved to the shared drive using the remap.  They are stored on //k2000/peinst/wim.  Repointing the Y: drive to the windows share causes the KBE to fail.  

Any idea how to tell the K2000 to save Wims to another server/file share?

This is the script that I am using to remap the drives.

echo off
net use t: /delete
net use t: \\server\share Password /user:UserWithRightsToShare
net use w: \\server\share Password /user:UserWithRightsToShare
echo on

I have installed the latest Media manager (3.5.7324.0) and the latest K Manipulator ( on a fresh computer.

Answer Summary:
0 Comments   [ - ] Hide Comments


Please log in to comment

Community Chosen Answer



You don't have to map the W drive unless you're altering the apply-wim.vbs to match.

You can't repoint Y because you'll lose everything in peinst.  We use the gimagex tool to capture wims rather than the built in method.  This lets you capture them to whatever location you map to a drive with the KBE Manipulator.

Answered 04/13/2013 by: nheyne
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity


This content is currently hidden from public view.
Reason: Removed by member request
For more information, visit our FAQ's.