KACE Product Support Question

Deploying a sysprepped image results in a blue screen during sysprep

02/03/2016 2781 views
The sequence seems to be this:

Image is deployed
System is rebooted
Sysprep starts and reaches approx 70%
BSOD ndis.sys 0x000007E
It then reboots to the OS repair screen
Start either normally or in safe mode and it will come up with this windows install error:


Another reboot will give the same result over and over again.

This is an image we have deployed before to the same hardware without issue. The only thing that has changed is we have moved from KACE 3.5 to KACE 3.7.113224. Does anyone have any ideas? Has anyone come across this before? Our other images, the ones we have tested anyway, all seem to deploy as they did with KACE 3.5, this is the only one with a problem.


Answer Summary:
0 Comments   [ + ] Show comments


Answer Chosen by the Author

Ok lets see what the kbox thinks this model is.

Boot to your kbe on the e5550 and go to the recovery menu open a command window
go to Y:
change directory to \\ikbox\peinst\drivers_postinstall\feed_tools
csript driver_feed_discovery_tool.vbs

it will tell you it cannot write the log file but look at the screen and what do you get back for model expected and path

Answered 02/04/2016 by: SMal.tmcc
Red Belt

All Answers

that is a sign of missing drivers.  If the image was using the driver feed with 3.5, check the setup in 3.7 and make sure you have it configured properly
Answered 02/03/2016 by: SMal.tmcc
Red Belt

  • Thanks...I will doublecheck the driver settings. We did simply deploy the image exactly as we had before but perhaps the upgrade to 3.7 has messed something up.
    All searches I have done so far do point to a driver issue though.
    • the driver feed changed between versions so I would lean towards that. you can manually inject the drivers as a mid term to test if needed
      • Do you mean the 'Copy feed files to workstation' task? If so, that was used during the initial attempt.
  • I can confirm that it was set to use the driver feed initially. We tried it again having changed that setting and it still failed.
    We are going to try deploying the same image to another hardware type, putting image on a USB and deploying from there, moving up to the latest version of KACE. Maybe one of those options will help.
    • you need to setup the driver feed before you can use it
      • Thanks for the screenshot. I have checked and it says for Model Latitude E5550_5550 the package status is: Installed into share
        Location is \drivers_postinstall\dell\windows_7_x64\e5550\x64

        On my K2000, I have a folder called 'drivers_postinstall' but also another simply called 'drivers' - if the postinstall ones are for drivers installed after the OS, then what is the one simply called 'drivers' for? Any driver required before the OS surely go into the KBE?

        Thank you...
      • make sure you recached your drivers under appliance maintenance

        if you still have problems look at updating to the newer 3.7 version.

        my current version is 3.7.120251. there were driver feed problems with earlier 3.7 versions that were corrected in the updates


      • the drivers dir was for older versions of kace but the kbe files are still kept here. all your files should be found under \\ikbox\drivers_postinstall\dell
      • Thanks for the continuing advice. The link for the KB about drivers not being recognised states this "Updating to 3.7.113224 will solve this limitation" ...and we are at that version. I may try upgrading again. All drivers are in the \drivers_postinstall\dell folder.
      • OK...so I have checked everything and all looks like it is in the right place, right folder path, right name etc...but it still will not install drivers.

        I ran the driver copy tool and it didn't give an error, but didn't do anything either. After running it, a small cmd window popped up for a second with no visible text then disappeared. It did that again a moment later and then nothing. No error shown, no drivers copied.

        I then deployed an image and watched it get to the 'copy drivers' section. It seemed to skip over that and do nothing.

        I have a folder called e5550_5550 (which is what the driver discovery tool reported: \dell\x64\e5550_5550) in the following places:


        ...and all drivers have been recached.

        Do I have the correct location for the driver folders?

        UPDATE: After copying the driver files to \k200\drivers_postinstall\dell\windows_7_x64\e5550_5550 it worked!

        So...why does the driver feed tool report back the path is:
        when is actual fact, it seems to be:


        Given all the importance of getting the pathway exactly right it seems ridiculous that the tool would report back an incorrect location. It has simply missed out the "windows_7_" prefix of the x64 folder. Bizarre.

        ...or have I missed something here...?
to see if the drivers are in the feed go to Library-Driver feed, search for your model and check the status

Answered 02/03/2016 by: SMal.tmcc
Red Belt

Answered 02/04/2016 by: SMal.tmcc
Red Belt

I just ran the tool and it returned this value:

It's a bit blurry, but it says \dell\_x64\e5550_5550 whereas I had to put the drivers in \dell\windows_7_x64\e5550_5550 before it would see them.

Is the driver feed tool broken?

I have resolved the issue now so thanks for all your assistance. Also appreciate the article you linked to.


Answered 02/05/2016 by: Duncan_H
Senior Yellow Belt

  • even if I could not give you the exact answer hopefully I was able to point you in the right direction (;-))

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ