Installing Bluetooth drivers with DPINST
Hi everyone!
I've been struggeling with trying to pre-install the "Bluetooth by HP" (Widcomm) drivers for my Laptop-users for a while.
The original problem is that the Bluetooth interface isn't detected/installed during deployment of the ÔS on the computer, the hardware appears when the user pushes the Wireless button or starts the preinstalled Bluetooth-software for the first time.
Since this is a locked down environment, the users does not have the administrative rights needed to install the device at this time.
The drivers are unsigned, (BTWUSB.SYS, BTWUSB.INF and BTWUSB.CAT), hence the catalogfile just contains the note "This catalog file should be replace with a real digital signature from Microsoft".
So, I tried to pre-install the driver with DPINST 2.01, using the legacy (LM-switch). After commenting out the reference to the catalogfile from the INF, it seemed to succeed.
But when I log on as a user and active the bluetooth-interface for the first time, I still get faced with the message;
"You must be a member of the admin group on this computer to install this hardware; Bluetooth by HP".
The Unsigned driver installation behaviour policy is set to "silently succeed" on the machines, but this does not seem to do any difference here.
Is there anything I could do, or am I completely of the track here?
/Andreas
I've been struggeling with trying to pre-install the "Bluetooth by HP" (Widcomm) drivers for my Laptop-users for a while.
The original problem is that the Bluetooth interface isn't detected/installed during deployment of the ÔS on the computer, the hardware appears when the user pushes the Wireless button or starts the preinstalled Bluetooth-software for the first time.
Since this is a locked down environment, the users does not have the administrative rights needed to install the device at this time.
The drivers are unsigned, (BTWUSB.SYS, BTWUSB.INF and BTWUSB.CAT), hence the catalogfile just contains the note "This catalog file should be replace with a real digital signature from Microsoft".
So, I tried to pre-install the driver with DPINST 2.01, using the legacy (LM-switch). After commenting out the reference to the catalogfile from the INF, it seemed to succeed.
But when I log on as a user and active the bluetooth-interface for the first time, I still get faced with the message;
"You must be a member of the admin group on this computer to install this hardware; Bluetooth by HP".
The Unsigned driver installation behaviour policy is set to "silently succeed" on the machines, but this does not seem to do any difference here.
Is there anything I could do, or am I completely of the track here?
/Andreas
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
AngelD
17 years ago
The driver must be signed otherwise will the user need to have administrative privileges.
Try use signability tool to create a CAT file for the driver
Try use signability tool to create a CAT file for the driver
Posted by:
beekey
17 years ago
I see, but then I really don't understand the point in pre-installing unsigned drivers in legacy mode at all?
Why did they implement this option?
/Andreas
Why did they implement this option?
/Andreas
Posted by:
AngelD
17 years ago
I don't know, maybe for local administrators
DpInst was in the beginning a tool for developers to test their drivers.
DpInst was in the beginning a tool for developers to test their drivers.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.