We are having a (7E Error Stop) BSoD issue when attempting to deploy a sysprepped Windows 7 64-bit WIM image from an OptiPlex 9020 to some 9010's. We can deploy the same image to both 990's and 980's, as well as 9020's, but the 9010's fail on Windows deploy/setup "installing drivers" around 62-79% completion. We have tried downloading and infusing the latest drivers to the post-install drivers share on the K2200, and installing the latest BIOS, but to no avail. Formerly, with Ghost, we found that you can go up to a 9020 from a 9010, or up to a 9010 or 9020 from a 990 or 980, but not down to a 990 or 980 from a 9010, and not down to a 9010 from a 9020. (We didn't try going from a 9020 down to a 990 or 980, though, with Ghost.) Can anyone shed some light on what we may be missing?
0 Comments   [ + ] Show Comments


Please log in to comment


Step one..  build one Gold image x64. I build my Gold image by doing scripted image then add every thing for that image, also set all settings that need set.
Step two.. I back it up.
Step three.. I sysprep  and Immediately pull it into the k2
Step four..  Every time we have a new model then I go to driver feed and add them, if for some reason it does not show in the drive feed as the correct model  then go to the driver share and  in the feed tools use "Get_Manufacturer_Model_OS.vbs" run that on the computer to get the correct model name, try that name in the driver feed. If driver feed does not see that one to install then you can use Double Driver to pull in the drivers to the Feed or you can manually build the driver folder you need in the share.
Step five.. I send out the new gold image to "any model" and that one image works, the drivers install after the computer is imaged as one of the task.

K2 is a great tool.  I do use more images with different purposes.

Answered 03/17/2015 by: TimHR
Orange Belt

  • I will take your advice, provided I can figure out some of the specifics you stated in Step 4, if our current resolution attempt fails. At current, we are trying the individual drivers, one at a time until one fails, then replacing it with a newer or older driver posted on Dell's site. Alternatively, we may decide to build our images on a 980 or 990, and let the drivers upgrade from there up, as the image gets dropped to a 9010 or 9020 and pulls from the feed. Technically, we are doing this backward at current, which the latter idea would correct - even building on a 9010 and dropping to a 9020 should work. Thank you for your interest in and consideration of our issue, it's greatly appreciated. Two heads are better than one, anytime.
    • This may help with some of it.
      I would suggest when the image fails on the task and you see the task failed that you chose RECOVERY> Edit a file with Notepad> Windows> Panther> setupact this is the log to look at to see what might be going on.
      Could be you have added in some drivers in the driver folder that are messing your image up in the driver share.
      Look for errors loading drivers in the log file just look at the address and delete or remove those drivers out of the driver share. Does not need to be the whole folder.
      • Also every time you make changes to the driver feed you have to recache If you made changes to only one of the driver directories, you can recache only those drivers. You might also need to rebuild the KBE.
Please log in to comment
> Formerly, with Ghost, we found that you can go up to a 9020 from a 9010, <snip> but not down to a 9010 from a 9020

Why would that magically have changed using a different deployment system? Trying to debug this will take you longer than it would to create a proper image for the 9010, surely?
Answered 03/03/2015 by: VBScab
Red Belt

  • The only catch is that the Dell KACE promises to handle drivers for any of Dell's models with only one image. Now it looks like we will be forced to make multiple images, or try using a virtual machine to build the images out, perhaps. We were just hoping to get away from trying to do virtual images if we could only solve the 9010 driver issue.
    • One image really does work. Make sure you recache after you make changes to driver feed and also you might need to rebuild your KBE.
Please log in to comment
Answer this question or Comment on this question for clarity