XP SP2 image with BDD

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm attempting to deploy WSD/WAIK and BDD2007. Unfortunately, Vista is not
in our immediate future so I need to continue deploying XP. I have
successfully captured and deployed a basic XP image using the standard LTI
processes supplied with BDD 2007. The standard process wipes the disk,
deploys an new OS and apps, then captures the image all in one continuous
stream.

I need help with two things:
1) How do I interrupt this BDD LTI standard process allowing for manual
modifications then perform the image creation and capture?
2) How do I capture an image of an already existing XP SP2 installation?

Any help or pointers to articles I have missed will be greatly appreciated.

Todd
 
Hi Todd
Do the Following:
1. Deploy Your XP OS
2. Install all the app, drivers, fixes etc.
3. Extract and run SYSPREP
-- c:\sysprep.exe -mini -quiet -reseal
4. After the shutdown, boot with Windows PE 2.0
5. Create a connection with your BDD server
-- net use f: \\BDD_server\distribution_share
6. Go to f:\tools\x86 (32bit)
7. Run "imagex /capture /compress maximum c:\ f:\Captures\file_name.wim "XP
Image Name"
8. Import your wim file into WDS using the "Add Boot Image" not "Add Install
Image"
9. Use the customsetting.ini file on the Control folder of your BDD
distribution share to control the level of unattendet setup that you want.
(Use BDD Configuration Reference guide)

Regards
Johan
 
Thanks Johan. I'll give this a shot as my next step in deploying BDD2007.

I'm deploying this to a lab environment so this addresses my need for
capturing an existing base XP configuration. However, I also need something
very simple which I can hand over to testers, which is why I was trying to
temporarily interrupt the LTI process. The LTI process is very simple, works
well, and is easy for them to use. The only issue I run into is the
inablility to insert a step allowing manual changes prior to the capture.
Any suggestions that will help with this requirement?

Thanks again,
Todd
 
Tod,

Can you tell me how you automated reg entries, group policy edits, software installs? Did you create MSI'S? How did you patch SP2 with 70 something patches to get it up to date? Have you had any luck DEPLOYING this image?

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com
 
Ken,
On the LTI side of my original question...
- all the apps I deployed are MSI based worked fairly easily once I realized
the working directory must the same location as my MSI and not some other
temporary working location.
- patches are deployed after the install via WSUS which probably doesn't
help you
- I'm not trying to modify reg entries or GP edits since these are all
controlled via my Domain group policies.
- After several trial and error cycles of capture and deployment I did
finally get the process down and now it works well. I just followed the
BDD2007 documentation for the Image Capture and LTI.

I suspect your question really leads to the same question I'm still trying
to get answered. The LTI process works well and easy to use. However, for
my more complex and/or non-scripted installations and modifications I need a
way to interrupt the standard LTI process to allow the manual intervention,
then continue with the LTI capture.

Hope this helps at least clarify what I have been successful at so far...
Todd
 
Back
Top