MDT 2008 and Windows XP SP2

[slemelin]

I'm trying to build and capture a vanilla lab image using MDT on an AMD
desktop.

My issue is with using the MDT build process (Task Sequence)... From the
task sequence, it's creating the partition and quick formats the drive fine.
Then it copies over the Windows XP SP2 file (the blue screen with the yellow
process bar). Once the files are copied, the pc reboots and comes up saying
Unable to load operating system.

I've verified the bdd.log file and all the drivers are correctly injected.

I don't know what's causing this issue since I don't have it using BDD 2.5.
I have another Lenovo M55 (Intel CPU) where the process is working perfectly
fine (SATA drive as well). The only difference with this model (Lenovo A61)
is that it's an AMD.

Since I can't use an Intel image on an AMD I would very like to be able to
build this PC and capture a wim file.

 

[BigDaddyJim]

I'm trying to build and capture a vanilla lab image using MDT on an AMD
desktop.

My issue is with using the MDT build process (Task Sequence)...  From the
task sequence, it's creating the partition and quick formats the drive fine.  
Then it copies over the Windows XP SP2 file (the blue screen with the yellow
process bar).  Once the files are copied, the pc reboots and comes up saying
Unable to load operating system.

I've verified the bdd.log file and all the drivers are correctly injected..

I don't know what's causing this issue since I don't have it using BDD 2.5.  
I have another Lenovo M55 (Intel CPU) where the process is working perfectly
fine (SATA drive as well).  The only difference with this model (LenovoA61)
is that it's an AMD.

Since I can't use an Intel image on an AMD I would very like to be able to
build this PC and capture a wim file.

One of the things that you did not mention is if the drive that was
used to create the original image is larger than the drive being used
to deploy the OS via BDD. If the drive is smaller, it may not work.

Jim

 

[slemelin]

Tim Mintner from The Deployment Guys Blog responded to my post and fixed my
issue with this statement...

Have you enabled the Diskpart BIOS Compatibility Mode task in the task
sequence? That fixes a bug in Windows PE 2.x that can cause issues like this
when deploying XP