Hello IT community! This is my first post on IT Ninja, I apologize if I am not posting in the correct section. I am having an issue with installing drivers for the Dell Latitude E5530 non-vPro models. The college I work for has many different Dell model desktop and laptops, I am only having the driver issue with this model. Our KBox 2200 is running 3.5.7. I have spoke with Kace Tech support several times, we have tried several different methods to get the drivers loaded. Nothing is working so far. I just wanted to check to see if anyone else is having this issue. I am imaging off a RSA and all the drivers have been synced to the petemp\drivers_postinstall\windows_7_x64\feed\dell folder. I can run the driver discovery tool manually from the KBE and it will install the drivers. However, it is not running properly as part of the WIM image on postinstall. The drivers are installing properly on all the other Dell models.

Any advise or suggestions, would be greatly appreciated!


1 Comment   [ - ] Hide Comment


  • Im having issues with the driver feed. Ive down loaded the drivers from the driver feed into the K2000 but they are not installing on a scripted install. Im not sure if its something to do with the model being non-vpro??

    Any help would be great.
Please log in to comment

Answer this question or Comment on this question for clarity



Did you check the box to use driverfeed with your image (it's under the system image detail page).  Also, your image must be sysprepped?

Lead L3 Enterprise Solutions Engineer, K2000
If my response was helpful, please rate it!

Answered 07/08/2013 by: cserrins
Red Belt

  • i'm having the same issue with the Dell Latitude e5530 non vpro (and only with this modell !) but only after the update to the SP1.

    Did you have any response from the support ?
    • That Series is the worst from Dell, to use the driver feed rename the folder of the E5530 Series to "non-vPro" without of any model name, that works.
      • Using just "non-vPro" issue should have been resolved in an update. Make sure you are using the latest version of the K2000.
Please log in to comment