Driver Collection & Management - ManageEngine OS Deployer





Completely Automated Driver Management

Achieving true independence from downloading and distributing the required drivers every time while deploying an OS can be an uphill battle. Specifically when you have a hardware-diverse environment, and need to support a new hardware type. With OS Deployer, you can use one golden image for all the end-points irrespective of the makes and models. The drivers will be handled automatically without you having to step-in.

How automated driver management works?

The bottom line of successfully deploying OS lies in installing the necessary drivers. Missing out on drivers impact the respective functionalities. For instance, if a hard disk/network driver goes missing in the target computer, the system boot up and network connections will be affected. The only solution is to have the required set of drivers ready. You don't have to take-up the endless task of collecting and distributing drivers, OS Deployer has strategized various ways to automate the driver collection by covering every stride of imaging and deployment needs.

Handy and reliable vendor drivers

Instead of you striving to get to the right vendor site to find the drivers you need, OS Deployer comes with a set of pre-added vendor-specific WinPE drivers. You can simply access these WinPE drivers from the web-console. These vendor and model specific drivers can be filtered and downloaded to your repository based on your needs. Besides, you can also download the WinPE drivers from the vendor-specific links provided and have those uploaded to the server. Know more on searching and adding drivers

Primary and Secondary Driver Repositories

OS Deployer has two kinds of driver repositories: primary and secondary driver repositories. All the automatically detected drivers from the imaged system and from the system where Endpoint Central agent is installed, will be stored in the primary driver repository. In addition to the primary driver repository, you can have multiple secondary driver repositories where you can manually add drivers.

You also have the option to designate a new repository as a primary driver repository. From then on, the automatically collected drivers will be stored in the new primary driver repository. However, the drivers in the old repository will still be used for deployment purposes. You can also move the drivers that were already collected to this new repository.

Intelligent driver collection scheme

Right when the image is captured, the image creator component checks for the available third-party drivers in the target computer, fetches them and sends the details to the server. These drivers are then stored in the configured primary driver repository. The applicable drivers will then be injected to the target computer automatically right after the OS is deployed.

If you are using OS Deployer add-on for Endpoint Central, drivers are also collected from the computers where Endpoint Central agent is installed. These drivers are also stored in the configured primary driver repository.

How to manually add drivers?

To ease the driver installation, you can also manually add a set of required drivers to a common network share. The applicable drivers from this repository will automatically be installed to the target computers right after OS deployment.Steps to configure driver repository.

How does driver deployment work?

OS Deployer deploys drivers for both local as well as remote offices. Let us understand the deployment process for both local and remote offices.

  • Local office deployment: For Local office deployment, the required drivers will be installed from the driver repositories located in the local office.
  • Remote office deployment: If all the required drivers are available in the driver repositories present in the remote office, the drivers will be installed from those repositories.

    If the required drivers are not available in the remote office but available in the local office, the replication process will be initiated. The Distribution Server present in the remote office will replicate the drivers from Local Office to Remote Office. The driver installation will then be completed.

How does Driver Repository Scan work?

To keep the driver details updated in your servers, OS Deployer automatically scans your driver repositories present in local and remote offices. The local office repository will be scanned every 4 hours whereas the remote office repositories will be scanned every 24 hours.

OS Deployer also offers the option to manually scan your driver repositories on-demand in two ways:

  • Differential scan: This scan allows you to detect all the drivers that are added and removed in the latest. This can be done using the Scan driver repository available at the top of the console.
  • Full scan: This scan clears all the driver details of that particular repository and updates the complete driver details again. This can be done by using the Initiate full scan option under the Action button.

What if there are missing drivers post deployment?

The aforementioned strategies will come handy in collecting the drivers and storing them in the repository. Post OS deployment, the respective drivers required to boot the computer will automatically be installed. Once the booting is done, the missing set of drivers will be scanned and reported to the central server. These missing drivers if available in the repository, will be injected to the target computer automatically. If there still drivers missing, those will be reported under the "Missing drivers view". You can either search and add the missing drivers from the readily available vendor drivers or to the configured driver repository which can be used for future deployment.

Imaging and Deployment Software trusted by