/build/static/layout/Breadcrumb_cap_w.png

Wim imaging to windows file server not working after 3.5 upgrade

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 (3.4.9.3) on a fresh computer.


0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: nheyne 11 years ago
Red Belt
2

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.

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ