Windows PE 2.0 - XP Disk partitioning issues

Windows PE 2.0 - XP Disk partitioning issues

Many people have been having "Fun and Games" when using Windows Preinstallation Environment (Windows PE) 2.0 to create partitions on a hard disk.

They use Windows PE to create a partition which XP is then installed onto, this then results in a "Blue Screen" at first reboot. This issue only occurs with some BIOS's but can be extremely frustrating.

This patch needs to slimstreamed into your XP source files, and your done!

There is also a workaround for this issue which is detailed in the KB article or if you are using BDD 2007 then take a look at Johan Arwidmark's blog.

Disclaimer: The information on this site is provided "AS IS" with no warranties, confers no rights, and is not supported by the authors or Microsoft Corporation. Use of included script samples are subject to the terms specified in the Terms of Use.

I see the same issues coming up over and over again with BDD 2007. So, I decided it was time for my own

Anonymous

18 May 2007 4:03 PM

What do you mean you still don&#39;t read Ben&#39;s blog? It is non-stop information all around BDD,

Jens

31 Oct 2007 6:46 AM

I'm pretty much at my wits' end. I installed bdd and wds, everything according to MS installation instructions. Goal is to do a scripted install. I manage to PXE-boot into PE but as soon as I am at the prompt diskpart tells me that there are no fixed disks present. The machine is an old Dell PE2450, the mass storage drivers should be present by default, I included them nonetheless in the out-of-box drivers directory. Still the same result.. "there are no fixed disks to show". Can anyone point me into the right direction? Thank you, thank you, thank you,

In our environment, regardless of what is on the hard drive (SMSTasksequencer, minint folder) we need it to format the drive and always do the OSD. As it is, if the minint or smstasksequencer folders are present, it does a refresh. Can I configure my task sequence to always do a new clean install?

Not often, but at times, the image deployment gets interrupted and we have to start over with the image deployment. When this happens, we have to manually format the drive before it will successfully image. Is there a way to configure the task sequence to always format and partition disk, regardless of the gather deciding to do a refresh?