I'm trying to setup an hardware agnostic k-image for windows XP with our K2000 box, unfortunately i'm running into some problems and I hope someone can point me into the right direction here. 

We only use Dell models (Optiplex and Lattitude ) and I'm trying to create a single new image for future installations, currently we use a different Ghost image for every model.  

Steps I've taken:

1. Installed an XP workstation on a Optiplex 790 with everything we need and all updates. Sysprepped it and made an image with Kace following this guide: http://www.kace.com/support/resources/kb/article/kace-and-sysprep-for-windows-xp-image-deployment

2. Installed the following 2 tasks: driver_feed_mid_task & install_drivers.exe according to this blog I found: http://www.itninja.com/blog/view/driverfeed-workaround-for-k2000-v3-4

3. Added the 2 tasks I mentioned earlier to my image ( http://puu.sh/20Qr9 )

4. In the Library -> Driver Feed, I enabled and installed all models we use. 

When I deploy an image to a Optiplex 790 there's no problem because the image was made on a 790. But when deploying it to a different model, it gets deployed without a problem but as soon a the XP startup screen appears, a BSOD happens. So it's probably missing the required drivers. 

Is there a step I'm missing or am I doing something wrong?

Many thanks in advance,


0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity



When you are sysprepping are you using the reseal option? Also, when you created the tasks for the driver feed workaround did you include the quotes in the command line or did you remove them?  (They shouldn't be included.)

Answered 02/13/2013 by: andrew_lubchansky
Black Belt

Please log in to comment

Did you recache the drivers after you added them in the driver feed?

Answered 02/13/2013 by: dugullett
Red Belt

  • Driver feeds automatically recache once the drivers are finished downloading. Dont really need to recache a driver feed however, the only reason it recahces is because it places a network driver in the Driver share.
Please log in to comment

I've recached the drivers and made a new sysprep making sure I selected mini-setup + reseal. Then I deployed the image to a test pc but unfortunately it still gives a BSOD as soon as the windows xp logo appears. 

@Andrew_lubchansky, I didn't include the quotes in the command line. 


Answered 02/14/2013 by: Derovian
White Belt

  • If you go to System Inventory and look into the record for a different model, check the driver compatibility report. Switch the OS to Windows XP. Looking at this report, does the storage controller driver have a red or green symbol? Its possible that you need to provide a few additional drivers for Win XP earlier in the install process.
  • Andrew,

    I've checked the driver compatibility in the System Inventory,
    The Optiplex 7010 is the only model where the SATA driver is shown red, other models like 790, 780 and Lattitude E6530 show the SATA drivers in green.

    But all models fail to boot besides the model where the image was created on.

    Thanks for help so far.
Please log in to comment