Import single Driver of .EXE extension in SCCM task sequence

Question

Hi Everyone,

Hope everyone is doing great and being safe!

Need your assistance and experience with one of the scenarios we are facing with the driver installation in the task sequence.

Normally while introducing driver within a task sequence we download a driver package file from the vendor website which consist of .INI file extension and after importing the driver into the driver node and creating the package we use the driver package for the drivers’ installation based on the WMI query for specific models or vendors.

We have a situation where our client wants to install a specific driver which is not for vendor-specific like Dell, HP but it is a driver with .EXE extension that is for a  specific APPlication and some mouse drivers now here is my question:

Can we install a single driver .EXE extension in task sequence and would that be a slient install.

Can any driver of.exe extension be be included in task sequence as silent install and if yes can someone help me with the complete step of how to do that?

Thanking in advance.

Regards,

Arvind Dubey

solved 0
Arvind Dubey 1 month 3 Answers 39 views Beginner 0

Answers ( 3 )

  1. Hello Aravind, If you able to extract the executable files then you can import as driver package as suggested by Ankit.

    You have any difficulty, you can try to create package with command line options and execute.

    For Example : “DriverpackName.exe” /S [Try to check silent command line with /? or .. and install it manually ]

    Best answer
  2. Have you tried to extract that exe file and then tried to import it with same procedure as done for driver package?

    • HI Ankit/Jitesh,

      First of all thanks a lot for your time and expertise on this :).

      Yeah I did try to execute the .EXE but I guess wasn’t getting the executable i could use for the same purpose.

      However, as you both mentioned above that it could be used as a normal package or application that I wasn’t so sure of 🙂 but after your clarification now it’s clear that how I could I take this forward to be used in the task sequence as a normal package or application as command line :).

      Thanks a bunch, guys for your time hope to have your expertise and assistance going ahead too.

      Stay safe

      Regards,
      Arvind Dubey

Leave an answer

Sorry, you do not have a permission to answer to this question .