If anyone else here is dealing with HP computers you know what I mean. They offer their drivers in the form of these little .EXE-based files called SoftPaqs. They tend to be named something like ""SPxxxxx.exe". I have been setting these up in the MDT as APPLICATIONS and I'm running a set of silent install commands on each one to get them installed. If anyone wants to know here's the supported command syntax:
My question is this:
Is anyone else doing this differently (specifically for HP SoftPaqs)?
I've read a few other posts and I've noticed that many people tend to go for a process that involves extracting drivers from vendors and getting them integrated into Out-Of-Box drivers. I'm just wondering if my method is the best. mainly because I need to associate a specific set of these drivers with specific task sequences and that is probing difficult when they are set up as Applications. Any thoughts/advice?
- "SPxxxxx.exe is the SoftPaq to unpack
- "-pdf" is a runtime switch that overrides the build parameters
- "-f" is a runtime switch that overrides the default path set at build time
- "-s" instructs the package to unpack in silent mode, skipping the Welcome, License, and Directory screens
- "-e" instructs the package to extract only, that is, do not run the component installation program.
- -s -a -silent -reboot (Good for silent installs.)
My question is this:
Is anyone else doing this differently (specifically for HP SoftPaqs)?
I've read a few other posts and I've noticed that many people tend to go for a process that involves extracting drivers from vendors and getting them integrated into Out-Of-Box drivers. I'm just wondering if my method is the best. mainly because I need to associate a specific set of these drivers with specific task sequences and that is probing difficult when they are set up as Applications. Any thoughts/advice?