/build/static/layout/Breadcrumb_cap_w.png

Setting up post install drivers for systems not in the driver feed in 3.4

In order to setup drivers for systems that are not in the driver feed, you will need to manually add the drivers to the driver share (\\Host_name_or_IP_of_your_K2000\drivers_postinstall)

 

You will have to manually create the folder structure and manually add the drivers to the share.

You will need three pieces of information to create the correct folder structure.

  1. Manufacturer
  2. Operating System
  3. Model

The folder structure for the Driver share is Manufacturer \ Operating system + Architecture \ Model.
Example: Dell\windows_7_x64\E6400

Note: You can run a script on the machine or model type you wish to know the exact manufacturer and model structure.

  1. Open the Driver share
  2. Open the feed_tools folder
  3. Double-click GetManufacturer_Model_OS.vbs.
  4. You will receive a windows message box with Manufacturer, Model and OS information. It will not give you the operating system architecture.

For the operating system folder structure please use the folder names exactly as they are listed below:

  • windows_7_x64
  • windows_7_x86
  • windows_vista_x64
  • windows_vista
  • windows_xp_x64
  • windows_xp

With the correct folder structure in place you can now place the raw driver files (.ini, .sys, .inf, or .cat) into the model folder. You can also have an internal folder structure in the model folder organizing the drivers into their categories. (IE: Audio, Chipset, Network, wireless, etc.)

Once finished your driver folder structure for a network driver will look like this:
Example: \\Hostname_or_IP_of_your_K2\drivers_postinstall\Dell\windows_7_x64\E6400\network\networkdriver.ini

 


Comments

This post is locked
 
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