Welcome to Sign in | Join | Help
in
Home Blog Forums

The Lazy Admin

Building a Windows XP Image in BDD 2007 Part 1

Sponsor


Many people are interested in the utilities and features offered in Windows Vista deployment tools. They are also very interested in the new BDD framework. What many people don't realize is that you can use many of the Vista deployment tools to manage and configure Windows XP images.

The following guide will get you on your way to automated greatness of BDD.

The first thing you need to do is copy the OS files into the BDD infrastructure.

To do this open the BDD workbench MMC.

Next click on "Operating Systems" and click "New" in the Actions Pane.

In the wizard choose "Full set of source Files" and Click next.

Insert the Windows XP SP2 CD or mount an ISO image on your BDD server. Browse to the appropriate drive and select it. Click Next

Type in the name you wish to use for the directory and click copy.

The operation to copy all the files will take a few minutes you'll see a progress bar similar to the following:

This is actually just copying the source files into a directory in your distribution share. You can see the folder if you open your distribution share and browse to the Operating System folder. Note: The distribution share would have been created when you installed BDD. By default it will be on c:\distribution.

Now that we have the source files we want to create a build. The build is the part where we specify custom options we want to automate.

  • Click on the "Builds" branch in the BDD MMC. In the Actions pane click "New"
  • Type in the Build ID, Build Name, and if needed Build Comments. click "Next"

  • Select the Windows XP source files you wish to use to build your install, click "Next":

  • Type in your VLK license key from your Microsoft Volume License Agreement. click "Next".
  • In the next screen you need to provide a Full Name, Organization, and an IE home page. Then click Next. (don't forget to use "http://" when entering in the web URL)
  • Specify a local Administrator Password and click Create.

Now you should see your build in the Builds details pane (middle pane). If you double click on the build you will see some options that can be adjusted.

In the General Tab you can adjust the operating system Source, Build names and Version number. You can also adjust comments.

The Setting Tab allows you to fix any mistakes or allows for adjustments in the information you entered during the wizard. It also allows you to access the Sysprep.inf and Unattend.txt files.

We are still dealing with Windows XP so we still have to sometimes manipulate these files manually. A good example is the case where we need to add SATA drivers to a build. The majority of SATA drivers were released after Windows XP. So even in the SP2 release many new hard disk controllers are not in the Windows XP source files by default. (We deal with this manually by pressing F6 during the text mode setup)

To lay down some context here is the usual startup process for Windows XP install:

Boot Computer -> Start Windows XP install from CD or network -> Start Text Based install -> Load Mass Storage Drivers -> Detect Hard Drives ->Select install Options-> Reboot in the GUI Install Mode.

If there is a problem with the Mass storage Driver you will often get a blue screen when loading the XP GUI installer.

We will cover integrating mass storage drivers into the Sysprep.inf files and Unattend.txt files in a future article.

Finally there is the Task Sequence Tab. The tasks that you find on this tab are all the steps BDD takes to build the image. This is an extremely flexible and easy way to customize your build.

This brings us to another issue with Windows XP and BDD 2007. Due to the way BDD 2007 partitions drives it causes that partition to not be compatible with Windows XP. This has been called the BDD Uber bug in some circles. Thanks to the fellows at www.deployvista.com there is a workaround to patch this bug.

First you need to create a text file with a .reg file extension. next past the following line of text (without the dashed line):

-------------------------------------------------------------------------------------------------------------------

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICES\VDS\ALIGNMENT]

"LessThan4GB"=dword:00000000
"Between4_8GB"=dword:00000000
"Between8_32GB"=dword:00000000
"GreaterThan32GB"=dword:00000000

--------------------------------------------------------------------------------------------------------------------

Save the file to the Distributions\Scripts folder.

Next in the Task Sequence dialog box seen above Click "Preinstall" Then click Add.

You will see a "New task" appear in the list. Use the "UP" Arrow button to move the custom task to the beginning of the list.

Name the task: Fix WinPE 2.0  Bug.

Then enter the following in the command line: reg import %SCRIPTROOT%\YOUR_REG_FILE.reg

This fix will make sure that Windows PE uses the correct settings when setting up the Windows XP partition.

Finally you're ready to build your deployment point, and kick off your XP install. In the Deploy->Deployment Points branch in the BDD workbench click "New" Choos a lab deployment point. Accept the default options in the Deployment Point wizard. At the the end click "Create". Once your Lab deployment point has been created, click on it in the Information pane, and then in the actions pane click Update. This will build a new deployment point and create the necessary files you need to boot up Windows PE.

Using the WDS server or the LiteTouchPE_x86.iso file found in [Drive]\Distribution\Boot. start WinPE 2.0 (See how to configure WDS For information on booting up over a network)

Once PE is booted up and initialized you will be presented with the Windows Deployment Wizard:

  • Choose the correct Keyboard layout for your needs, and click "Next"
  • You will be presented with a screen asking for an account with permissions to access the Distribution share you set up on your BDD server.
  • Next you will be asked for a computer name.
  • Next you will be asked for a domain name. If you want to capture this install to a base Wim Image you must leave the setting to the default "Join A workgroup" Click "Next".
  • The following screen prompts you to specify where your user settings are being stored. As are preparing a base image, leave the default setting as is and click "Next".
  • Choose the Windows XP SP2 Build Files, Click "Next".
  • Choose your Time Zone Click "Next".
  • Choose any applications you added. (For base images, and first time installs it's fine if you haven't added any applications yet) click "Next".
  • accept the default setting for capturing the image. (Rename the image file should you want another name) Click "Next".
  • In the final screen you may review details about the install. When you are satisfied with the results click "Begin".

This Window will pop up and detail the installation progress. If all went well WindowsXP should be installed in a fully automated fashion. The end product will be a Windows XP Wim image in your Distributions\Capture directory.

This concludes part one. In Part 2 we will pickup where we left off here, and will explain how to use the Wim image to quickly deploy Windows XP desktops.





Published Thursday, May 24, 2007 8:30 AM by daniel.nerenberg

Comments

 

4sysops -- Update rollup for the BDD 2007 said:

June 18, 2007 2:34 PM
 

igor said:

Is there a way to automate the winPE portion of the XP deployment?  to make it zero touch.

thanks

June 21, 2007 4:40 PM
 

The Lazy Admin said:

Microsoft has released a patch 1 for BDD 2007. This patch fixes a bunch of bugs. (I'm not sure if it

July 9, 2007 4:00 PM
 

jsharp said:

This is what i've done

Server 2003 with WDS installed

BDD 2007 Installed

Followed part 1 of this article

I PXE boot into WinPE and then...nothing

I can't figure out how to get the install to start for XP

I've added my WinPE image into WDS as a boot image...is there anything else i need to do.  

Any advice would be great!

July 18, 2007 6:54 PM
 

jsharp said:

**For those having problems getting the sysprep to run to capture an image**

When initially doing the install for Windows XP do NOT select the option to join a computer to a domain.  

It is only if you join a computer to a Workgroup will you get the option of where to capture your WIM file to.  

Otherwise Sysprep will not run and no WIM will be created

July 24, 2007 4:26 PM
 

fire_starter66 said:

jsharp...I am having the same issue.  I also PXE boot and then get nothing...just the command prompt sitting with:

X:\WINDOWS\system32>

What did you do to make it work.  I have configured everything as per this guide and the WDS guide (installing the boot image).  the only difference is that my client PC is a VM (VM-Ware server on CentOS) since the office doesn't have any spare PXE-capable machines kicking around.

Any help would be great.

Cheers

August 8, 2007 4:56 PM
 

dcarter_home said:

If you are having problems with PXE boot sitting at a CMD Prompt you may need to increase the RAM in the machine so that it is higher than 256.

This worked for me.

August 14, 2007 10:30 AM
 

Mick_RW said:

Hi, Firstly would like to say thanks for an excellent Blog. Am having a problem with BDD2007 / XP / VMWare. When deploying XP as per your blog it works fine, until the first rebbot, it then goes thru the actions you would expect then when it displays "Starting Windows..." it blue screns on me. The error message it comes up with points to it being a hard drive problem. Have tried everything I can think of with no luck. Has anybody else seen this prblem and if so how did you resolve it. TIA Mick.

August 15, 2007 9:11 AM
 

Mick_RW said:

When I first followed the blog I found the problem with stopping at the X: prompt. I am using VMWare Workstation 5. When creating a new virtual machine and selecting Windows XP Pro as the virtual machine it would fail everytime. I have found that selecting Vista (Experimental) as my virtual machine did not cause any problems until the first reboot.

August 15, 2007 9:20 AM
 

steven.van.looy said:

Excellent blog Daniel. I followed your guide to deploy XP at a customer with BDD2007/OSD and had no problems whatsoever, except for losing half a day trying to build a Lenovo X61s, which gave me a TRAP - 00000006 Exception booting PE.

Appeared to be that the weasel who delivered the reference machine forgot putting a harddisk in it, go figure...

September 12, 2007 6:51 AM
 

steven.van.looy said:

Excellent Blog! Saved me a lot of time while deploying XP at a customer with BDD2007 & OSD2003.

September 14, 2007 4:16 AM
 

masana said:

Ok, guys. I tried to do exactly what this guide shows, but I'm stucked at the "System Management Server - Running: Apply Image" screen (The last one showed here in this guide). What Did I do wrong? Or How long does it take for the Windows XP installing screen pops up?

Thanks.

September 29, 2007 6:23 PM
 

eror said:

Hi,

I used this manual to create deployment server for XP Pro. Everything worked great, I boot clean computer with my deployement server and boot with litetouch_x86.wim, but  after asking me for account which will access deployement share I get error saying that depl share could not be conntacted. I tried to ping server where deployement share is and ipconfig /all from cmd on machine but I dont see any network adapters. Can you help me?

--------------------------------

Most likely the problem is that WinPE does not have a driver for the network card you are using. You may need to inject the driver into your PE build.

October 4, 2007 9:03 AM
 

junknav said:

Hi,

  What is the use of capturing the fresh install as a wim image. Is it faster to deploy using wim images. Will it act as a generic image which i can use to deploy on different HALs. If that is the case i wish it would give me an oppurtunity to install all other apps and updates before the sysprep execution and capture.

Thanks,

Nav

November 26, 2007 9:24 AM
 

ProfessionalMan said:

Hi, i'm in the process of learning this whole toolset, with the end result being that I have an image of an already configured workstation being installable on other machines. Before I go ImageX the workstation that I have configured, I'm testing my knowledge with a basic WinXP installation. I've applied the WinPE bug fix, no applications going with the build, straight basics. My operations have varied slightly, though. I chose 'removable media' from the list, and I am asking for a product key. Well, i've built the ISO and I'm attempting to perform my created base install on a Virtual PC.... I get to the point where the command prompt is running 'wpeinit' .... and after that, I don't get a Welcome Windows Deployment window. The command prompt goes back to a working prompt... and just flashes. Any ideas?

November 28, 2007 6:16 PM
 

BigMazi said:

Hi everyone

i've got couple lame questions and i'm hoping someone went through that before and can advise on what i'm missing here, i've been working with it for couple weeks and some issues are very persistent - i'm using stand alone BDD and basically testing configurations with either usb flash oir dvd:

XP - imported wim image to bdd does not take any additional folders ($1,$$ etc) whichever way implemented (image folder, distribution folder), only updating mounted wim does work. the image has been syspreped so additional tasks like cleanup in sequencer don't make sense but adding folders should be ok...

Vista - imported wim image - I need some light on Syntax and proper location for setupcomplete.cmd file - i had bunch of simple scripts i listed in the file but they don't execute (& doesn't help). there is not much info out there about the file so anything would be great. by the way i put the file in "Distribution\Operating Systems\Windows Vista\sources\$oem$\$$\Setup\Scripts"

XP and Vista - I’m looking at scenario where wim image is imported into BDD, modified and “content” folder & ISO created. The goal is to make the Content folder in such way that it can be copied over to C: drive and once machine is rebooted it boots to it (C:) and restores it to the same location (C:) – there was something about advertising task sequence but i can't simply find it - i hope it can be done by modyfying local scripts as i do not have WDC server set up.

Any info would be greatly appreciated.

November 29, 2007 2:03 PM
 

Darren said:

Hi,

I did as you said above but when I add it to WDS it comes Vista PE image as the description.  I change this to Windows XP Pro but when it PX Boots it has the vista bar scrolling across and then I get a stop error.  Any idea what I'm doing wrong.  I used a win xppro cd to create the distribtuion etc and it picks that up in the build.  Any help would be great

November 29, 2007 8:20 PM
 

Casper42 said:

In regards to the section about F6 and SATA Drivers, I have built several custom Windows XP Install CDs using a free tool called nLite.

One of the major advantages is you can integrate new drivers into the image.

Wouldnt it therefore be possible to use this tool to add the extra Mass Storage drivers to the CD and then use the modified XP CD as your source for the Source Files and then not even need to F6?

Just a thought.

I ripped Vista off my Wife's Dell Inspiron 1520 and found that when I hit F6 and showed it the Intel Matrix Storage drivers it would NOT let me install to the disk.

I used nLite and integrated the drivers and made a custom CD that I labeled "XP Santa Rosa" and that Custom CD installed without a hitch.

February 29, 2008 7:10 PM
 

program pro game rip said:

For those of you fine people who were listening last night, you may remember that I opened with Orson- No Tomorrow. The reason for that is because it\'s awesome! The tune, the style, the lyrics and the whole story that it tells. If all songs were this

June 21, 2008 12:07 PM
 

dvd coping said:

Recent News OS X Curmudgeon? Me? Not By Design Or Intent Test Driving The Firefox 3 Beta 4 Browser Applelinks Tech Web Reader- Friday, March 14, 2008 Applelinks iPhone News Reader- Friday, March 14, 2008 First Updates of the Year: DEVONthink Pro 1. 5.

June 22, 2008 11:01 AM
Anonymous comments are disabled

About daniel.nerenberg

I am an MCT, Consultant based out of Montreal Quebec Canada. As the "new" Lazy Admin on the block I am working to make TheLazyAdmin.com the best website for MS Software tips and tricks out there!

This Blog

Powered By

 

Syndication

Sponsors

 
 
Get a free 5GB e-mail account @isalazyadmin.com

Certifications & Awards




All postings are provided "AS IS" with no warranties, and confer no rights.
Microsoft product screen shot(s) reprinted with permission from Microsoft Corporation.