/build/static/layout/Breadcrumb_cap_w.png

i386 folder as post install task

Does anyone have any ideas on how to best to include the i386 folder to a Windows XP scripted installation?

0 Comments   [ + ] Show comments

Answers (9)

Posted by: dyehardfan 13 years ago
Second Degree Blue Belt
0
use a batch file to copy it from a network share?
Posted by: dchristian 13 years ago
Red Belt
0
sdillane,

You can copy it right from the kbox.

It'll be in \\ikbox\\peinst\source_cds\{xp cd number}\i386
Posted by: cserrins 13 years ago
Red Belt
0
To followup on dchristian, you should do this as a mid-level tast (a post installation task with KBE as the selected environment). xcopy would work well. This would minimize the space on the K2.
Posted by: dyehardfan 13 years ago
Second Degree Blue Belt
0
Nice trick, didn't realize that could be done.


ORIGINAL: dchristian

sdillane,

You can copy it right from the kbox.

It'll be in \\ikbox\\peinst\source_cds\{xp cd number}\i386



ORIGINAL: cserrins

To followup on dchristian, you should do this as a mid-level tast (a post installation task with KBE as the selected environment). xcopy would work well. This would minimize the space on the K2.



And to get rid of a little more of my k2000 ignorance, how does this save space on the appliance?
Posted by: cserrins 13 years ago
Red Belt
0
the files are already on the K2, so by copying them from where dchristian stated works without uploading anything new to the K2000. Some may take the i386 folder, zip it up and upload it as a mid or post installation task, but that would take up more space.
Posted by: dyehardfan 13 years ago
Second Degree Blue Belt
0
I gotcha. Misunderstood what you were saying. I thought you were saying doing it as a mid-level task would free up space, but you were actually saying that copying the files from the kbox is what saves the space. Good to know. New trick for my server installs.


ORIGINAL: cserrins

the files are already on the K2, so by copying them from where dchristian stated works without uploading anything new to the K2000.  Some may take the i386 folder, zip it up and upload it as a mid or post installation task, but that would take up more space.


Posted by: sdillane 13 years ago
Senior Yellow Belt
0
David thanks for the information, this helped out a lot. I was not aware that the source files were copied to the peinst folder. Once I took a closer look I also noticed that during the install I was already mapped to the location. This is what worked for me:
xcopy y:\source_cds\1\i386 c:\i386 /y /i /s /e /h
Posted by: dchristian 13 years ago
Red Belt
0
Glad it helped!

Just kinda curious, what do you need the i386 folder for?

If your computers are going to be staying in a network that has communication with the KBOX you can map peinst as the default location for i386.

Take a look at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup.

There are a couple of registry keys (installation sources, servicepacksource patch, and sourcepath) in here that set the location of i386 when adding or removing windows components.

If this works for you maybe all you'll need is to set these to point to peinst.

Example bat script:
reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup /v ServicePackSourcePath /t REG_SZ /d \\{your kbox here}\peinst\source_cds\{source cd number here} /f
Posted by: sdillane 13 years ago
Senior Yellow Belt
0
now that is an interesting idea. I've always kept a copy of the source files on each computer. Something to think about.

Thanks
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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