Our OSD one size fits all layered imaging stopped working for the Optiplex GX620.Worked fine for a year or so and then stopped.It would get all the way through the Windows XP sp3 install and freeze after the final reboot on the starting windows screen. (Could get it to load windows and continue by disabling the CD/DVD drives in the bios.)After reading the forums and a lot of trial and error, I got it to work again.It first started working again when I checked the: "Limit driver matching to only consider drivers in selected categories" and then selected the previously made GX620 from the list of categories.Then in order to continue using our, one task works for all, xp sp3 workstations task. I added an "apply drivers package" with an option- wmi query: Select * From Win32_ComputerSystem Where Model = "OptiPlex GX620 "Then I added the same option to the "Apply Device Drivers" but this time it runs if the model is not a GX620: Select * From Win32_ComputerSystem Where Model <> "OptiPlex GX620 " I'm thinking the reason it stopped working was becaue we added a bunch of newer models and thier newer version of drivers. So the "Apply Device Drivers" loaded the wrong version of the sata driver.

Thanks, we have the same problem. Your suggestion was very useful.

We also had this problem and successfully fixed it with the above change to the Task Sequence. I used a slightly different WMI query - Select * from Win32_ComputerSystemProduct Where NOT Name LIKE "%Optiplex GX620%"

I am having the same issue when trying to deploy xp sp3 to a gx620....the image works fine on all the other machines we deploy it to. I am a little new to using the deployment workbench and tried to following the advice given above but am having a hard time. Please help

if xpsp3 you could change the SATA mode in the bios to ATA My step by step SCCM Guides I'm on Twitter > ncbrady

I actually tried that, it didn't make a difference

I am in the process of upgrading deployment workbench from 2008 to 2010....figured I'd have the latest version. But I am still unclear on how and where exactly to create and modify this wmi filter....anyone?

well if it wasnt the sata mode then it must be the HAL, how did you create this image (on what hardware) ? My step by step SCCM Guides I'm on Twitter > ncbrady

The image was created on a optiplex gx620 ...the only options regarding sata opertaion consist of normal or combo, I tried both didn't seem to make a difference...I'm pretty certain that it has something to do with a driver that is causing the os to freeze up while windows tries to boot up after the image has been successfully been put on the machine.

regarding your earlier question, the wmi filter is set as an option in the task sequence itself, look at the Set Variables action, ar eyou only using MDT or are you also using SCCM ? My step by step SCCM Guides I'm on Twitter > ncbrady

After Upgrading deployment workbench from 2008 to 2010 the issues seems to have been resolved :)

nice :) were you installing xp or 7 ? mdt 2010 is required for windows 7 My step by step SCCM Guides I'm on Twitter > ncbrady

Well i was installing xp...but we are planning on migrating to 7 sometime in the near future so we should be all set when that time comes. Thanks for all your advice and help...it is much appreciated.

Had to try a few different approaches to this one. Here's what we've got so far in our deployment on the Optiplex GX620, which behaves the same way, I suspect. MDT 2010 deployment runs through the file copy and mini setup of the image, then hangs as Windows XP starts to boot. We disable the PATA controller in BIOS, let the task sequence complete, then force the Intel Chipset ICH driver on the IDE/ATA/ATAPI controllers. It seems like the latest release from Dell has a SATA/IDE controller driver that is incompatible with the hardware on this system and XP chokes on it when it boots. Once the two storage controller drivers are updated, you can re-enable the PATA controller in BIOS. Kind of a kludge workaround, but it does work. Think these guys have some hybrid IDE/SATA controller that throws the PNPID bit for a loop.

can anyone walk me through how to modify the task sequence so that I can get this image working on a gx620?

I just ran into this as well and narrrowed it down to the Chipset driver as well. To fix it I Removed the GX620 Chipset driver from Driver Package Create a new Package (not a Driver Package) for the Chipset driver. Add a Run Command Line task to silently install the Chipset driver from the newly created package.

I just ran into this as well and narrrowed it down to the Chipset driver as well. To fix it I Removed the GX620 Chipset driver from Driver Package Create a new Package (not a Driver Package) for the Chipset driver. Add a Run Command Line task to silently install the Chipset driver from the newly created package.

thanks for sharing this info so others may benefit My step by step SCCM Guides I'm on Twitter > ncbrady

What is the exact name of the driver for the chip set that I need to remove?

I tried deleting all the drivers from my gx620 driver folder on the workbench and it is still freezing after the image is put on the machine ...unreal...if anyone could email me some tips im fairly new with this so please bare with me ... tgraci@roe.com is my email address. Thank You

I tried deleting all the drivers from my gx620 driver folder on the workbench and it is still freezing after the image is put on the machine ...unreal...if anyone could email me some tips im fairly new with this so please bare with me ... tgraci@roe.com is my email address. Thank You Create a seperate package with the WMI query like the above suggests and use the original drivers from Dell from the link below. This is why I like to build driver sets based on model specific using WMI. Some drivers may be duplicated on server but it's easier to get it working. http://support.dell.com/support/downloads/download.aspx?c=us&cs=555&l=en&s=biz&releaseid=R96614&SystemID=PLX_GX620&servicetag=&os=WW1&osl=en&deviceid=3268&devlib=0&typecnt=0&vercnt=2&catid=-1&impid=-1&formatcnt=0&libid=27&typeid=-1&dateid=-1&formatid=-1&source=-1&fileid=125390

I tried deleting all the drivers from my gx620 driver folder on the workbench and it is still freezing after the image is put on the machine ...unreal...if anyone could email me some tips im fairly new with this so please bare with me ... tgraci@roe.com is my email address. Thank You Create a seperate package with the WMI query like the above suggests and use the original drivers from Dell from the link below. This is why I like to build driver sets based on model specific using WMI. Some drivers may be duplicated on server but it's easier to get it working. http://support.dell.com/support/downloads/download.aspx?c=us&cs=555&l=en&s=biz&releaseid=R96614&SystemID=PLX_GX620&servicetag=&os=WW1&osl=en&deviceid=3268&devlib=0&typecnt=0&vercnt=2&catid=-1&impid=-1&formatcnt=0&libid=27&typeid=-1&dateid=-1&formatid=-1&source=-1&fileid=125390 Create a seperate package where in MDT? If I create a package in the packages field I am then left with a empty package with options like Import OS packages... is this right?

I had a batch of GX620's, deployed with MDT 2010, that still would not boot after... 1) disabling the pata drive in bios 2) applying the chipset fix 3) re-enabling pata. They were still frozen on bootup. I took the following approach as a work-around (I have a limited number of GX620's to contend with). 1) Disable pata drive in bios 2) Boot windows and let installation complete 3) Search c:\windows\inf\*.inf files for the "intelide" string, and delete the oemX.inf and oemX.pnf files associated with the Intel IDE driver (for me, it was oem42.inf and oem42.pnf). I had borrowed a search string from a website that made searching for this a bit easier. From a command prompt (at the c:\windows\inf directory), type in, "for %a in (oem*.inf) do find /i "intelide" %a >> c:\output.txt". Then just inspect the output.txt file for the oem driver that is identified. 4) Uninstall the Ultra IDE driver from device manager (leaving the SATA driver in tact) 5) Scan for hardware changes, and accept the first Intel driver on the list that is offered by the hardware wizard 6) Reboot, go to BIOS, re-enable pata, boot windows 7) Answer "yes" and "yes" to allow the hardware wizard to install the newly discovered CD/DVD drive. 8) You should be back in business again.