Installing USB drivers
I have a problem deploying software that contains usb drivers on a strict client computer.
After creating and deploying my new package and plugging in the hardware, the Plug and Play wizzard starts and asks for a admin account to install the drivers.
I have searched the forums and found some info on driver signing, but im not sure if this is the same case.
The software we use is Wininstall.
If this problem sounds familiar, please point me in the right direction.
Thank you.
After creating and deploying my new package and plugging in the hardware, the Plug and Play wizzard starts and asks for a admin account to install the drivers.
I have searched the forums and found some info on driver signing, but im not sure if this is the same case.
The software we use is Wininstall.
If this problem sounds familiar, please point me in the right direction.
Thank you.
0 Comments
[ + ] Show comments
Answers (10)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
You need to either get signed drivers or sign them yourself. How anyone is sending out unsigned drivers in 2009 escapes me...
Posted by:
Scazy
14 years ago
HI I faced quite the same problem with PC Suite Sony Ericcson . the problem was that drivers have not been included into the package they were created during the installation by CA. So found a folder to which they install and added to the package dpinst.exe and dpinst.xml file in the the same folder as drivers. then created a CA that just launches dpinst.exe in the deffered execution. that`s it.
the content of the dpinst.xml is following :
http://msdn.microsoft.com/en-us/library/ms790308.aspx
the content of the dpinst.xml is following :
<?xml version="1.0" ?>
<dpinst>
<suppressAddRemovePrograms/>
<!-- The following search and subDirectory elements direct
DPInst to search all subdirectories (under the DPInst working directory) to locate driver
packages. -->
<search>
<subDirectory>*</subDirectory>
</search>
<!-- The following language element localizes its child elements
for the English (Standard) language. The child elements
customize the text that appears on the DPInst wizard pages. -->
<language code="0x0409">
<dpinstTitle>Device Driver Updater</dpinstTitle>
<welcomeTitle>Welcome to the Device Installer!</welcomeTitle>
<welcomeIntro>This wizard will walk you through updating the drivers for your device.</welcomeIntro>
<installHeaderTitle>Installing the software for your device...</installHeaderTitle>
<finishTitle>Congratulations! You finished installing your device drivers.</finishTitle>
</language>
<legacyMode>
<suppressWizard>
<suppressAddRemovePrograms/>
<quietInstall>
</dpinst>
http://msdn.microsoft.com/en-us/library/ms790308.aspx
Posted by:
captain_planet
14 years ago
Scazy - i think you're missing the point. The drivers need to be signed. DPInst wont sign the drivers. It will just install them. The OP looks like he can install the drivers ok. The reason why the OP gets the admin prompt is because the drivers are not signed.
Posted by:
Scazy
14 years ago
I assume that if an unsigned driver will be installed then it wont ask for admin rights anymore. Dpinst.xml is adjusted to install unsigned drivers. Anyway that was just a solution how it worked to me. Used SCCM to deploy it in the System Context( if it makes sense)
Posted by:
captain_planet
14 years ago
I assume that if an unsigned driver will be installed then it wont ask for admin rights anymore.- signed, you mean? [;)]
Dpinst.xml is adjusted to install unsigned drivers.- I'm sure it is, but installing unsigned drivers will still cause the admin prompt mentioned by the OP.
Posted by:
Daggett
14 years ago
Thanks for the reply's!
I am a bit confused about driver signing.
Do I need to sign a driver, so windows automaticly installs them as a trusted (common) driver after plugging in the hardware? (for example: a standard usb storage device)
or is driver signing only for "unsigned" drivers as VBScab mentioned?
I am a bit confused about driver signing.
Do I need to sign a driver, so windows automaticly installs them as a trusted (common) driver after plugging in the hardware? (for example: a standard usb storage device)
or is driver signing only for "unsigned" drivers as VBScab mentioned?
Posted by:
captain_planet
14 years ago
Signed drivers come with a signed catalog file (.cat). In your INF file (under the [version] section) there will be a line saying something simmilar to:
CatalogFile.NTx86=driverCatalogName.cat
If your driver doesn't come with a .cat, then it is not signed and you need to sign it. Search these forums - AngelD has made a good few posts on this subject.....
CatalogFile.NTx86=driverCatalogName.cat
If your driver doesn't come with a .cat, then it is not signed and you need to sign it. Search these forums - AngelD has made a good few posts on this subject.....
Posted by:
AngelD
14 years ago
I wouldn't want to perform these steps for each computer the driver should be installed on.
Posted by:
joedown
14 years ago
Even if the drivers are signed and installed won't members of the Users group still get prompted when plugging in some devices?
Posted by:
AngelD
14 years ago
When we for example use dpinst it will install the driver(s) to the "driver store" and be "disguised" as a driver installed through the OS installation.
So when a user plug-in the device the hardware wizard will find the driver as a legit "pre-installed" driver.
Maybe not the best description but the scenario still applies.
So when a user plug-in the device the hardware wizard will find the driver as a legit "pre-installed" driver.
Maybe not the best description but the scenario still applies.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.