When pushing down the Xp Sp2 image through MDT, It goes through the loading of the O.S. and runs sysprep with no error, the computer reboots, boots normally, gets to the Xp Splash screen, I get a quick bluescreen then the computer reboots, I then boot into safemode and stops at the agpCPQ.sys file. I have researched and this is tied to a video driver "CPU to AGP controller (Agpcpq.sys) driver."

Maybe I am viewing the MDT process wrong and need to rethink the driver strategy. Or need to re-examine the concept of building one image to accommodate our current inventory. Which ranges from Dell GX620's, D610's all the to HP DC7700, 7800,  6710 and 6720 models of computers. I know I am so darn close to having the ability of pushing this image.  Starting to get fustrated!

Again, Thanks to everyone who has helped me in the area!!!! Thank you!, Thank you!

One word.

Sata.

Don’t worry though, it’s an easy fix.

If you were to image onto a DC7100 then you would be just fine, but all the machines there have sata controllers which is where the problem is coming in. You can apply the image fine because WinPE has mass storage pre-built in.

Go onto the Intel website and download the Matrix storage drivers and add them to MDT

Here’s a link to get you started

http://www.intel.com/design/chipsets/matrixstorage_sb.htm

When you’ve done that use the “ZTIInjectMassStorage.WSF” - I might be wrong with the filename there, I’m not in front of my build PC at the moment, but it’ll be something obvious though.

MDT doesn’t support the injection of drivers to an offline WIM, you will have to run this after applying a sysprepped image onto a PC and before rebooting into XP.

You'd have this exact same problem making a build manually rather than through MDT, it's just that MDT makes it so much easier to fix user error issues

This is where MDT really shines, you don’t have to rebuild your base image to be able to add drivers for a new PC " align="absmiddle" border="0">

2 minutes work and you should have the build working on all the hardware you mention above.

Also, something else to think about that often causes blue screens at that stage, when you load up safe mode it stops at mup.sys

This is caused by the wrong HAL type.  If you don’t have this problem at the moment then great, just mentioning it since you had BSOD problems anyway.

If all of your hardware is MultiProcessor then it’s not an issue.