Are you using WIM's? Here is a trick to save network bandwidth and K2000 diskspace. Store the Wim's on Windows servers, Wim files are not restricted to K2000 file system.
I had the server crew create storage space on all the sites and I store my Wims at each site. They created a share on the main storage server at each site named images$ and I have a K2000 domain user that has rights to these shares. I created a subdirectory called imagestore in each share (required).
I used the KBE manipulator to create custom pxe boot environements that map the T: and W: drive to each of my storage spaces. When I capture a sysprepped image I choose the proper boot to map the server I want it to go to.
When staff deploys an image, they pxe boot to the K2000, the machine gets it deployment orders from the k2000 and starts. I remap the W drive as my first preinstall task to the needed storage to access the WIM.
net use w: /delete
net use w: \\server\images$ Password /user:domain\user
(note: I do a /delete prior to mapping, stops failures from the drive letter is in use)
The deployment starts on the K2000 and then it switches over to the storage server to copy the wim portion then switches back to the K2000 for the remainder of it's mid level and post tasks.
All the workload of deploying the image files is placed on the storage servers instead of the K2000. I have had 120 images deploying from a single K2000 this way and I am still able to capture an image even when they are deploying.
I have had to image over a T1 when the microwave link went down. Still managed to use the K2000 to do full classrooms by putting the wim file on a local server.
The server crew can easily backup my wims to commvault also.
You don't have to change the t: drive at all. Since you will always have the w: mapped in that kbe, all you have to do is change the apply_wim.vbs script.
Download the vbscript, change all references in it from t:\imagestore to w:\imagestore, then save it and replace the one on the k2.
Also, for those of you not sure what he means about the echo off, when adding a mapped drive with credentials, you don't want users to see it. So when creating the kbe, when it asks you to add custom DOS commands, use @echo off for the 1st command, then map your drive for the 2nd DOS coommand, and then @echo on for the last one.
Corey
Lead L3 Enterprise Solutions Engineer, K2000
If my response was helpful, please rate it! - cserrins 11 years ago
echo off
net use t: /delete
net use t: \\server\share Password /user:UserWithRightsToShare
net use w: \\server\share Password /user:UserWithRightsToShare
echo on
You can then check to see if the mappings are working by pxe booting and from the main menu choose recovery - command prompt. Enter "net use" to verify your mappings go to t or w and cd to imagestore and verify you can see the files.
If this is a preboot task
net use t: /delete
net use w: /delete
net use t: \\server\share Password /user:UserWithRightsToShare
net use w: \\server\share Password /user:UserWithRightsToShare
if you are still stuck post a question or email me I will help you to get setup to do this. I map to our main campus server in the KBE and if I need to reach one of the other storage servers at other sites I remap as a pre task. If you set up multiple areas, use a domain account to authenticate. - SMal.tmcc 11 years ago
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
http://www.itninja.com/blog/view/create-dedicated-kbe-s-to-capture-wim-s-and-store-externally-for-k2000-version-3-5 - SMal.tmcc 10 years ago
echo off
net use t: /delete
net use w: /delete
net use t: \\server\share Password /user:UserWithRightsToShare
net use w: \\server\share Password /user:UserWithRightsToShare
echo on
Since I'm doing this do I have to edit apply_wim.vbs? If so where do I find the file I don't see it in my pre or post installation tasks.
Thanks in advance - knuckle66 9 years ago