Scripting driver installation for a USB device
We have some USB hardware to install. When we plug the device the PnP is asking to install the device and as our users are locked down they cannot. If I launch the batch with SMS (SMS is using an admin account) then the batch will pause until someone will cancel the PnP window.
If noone is in front of the computer then noone will be able to click cancel and the batch will be pending indefinitely.
Is it a way from the batch file to bypass that PnP window or to make the batch running or...
Any idea would be appreciate.
If noone is in front of the computer then noone will be able to click cancel and the batch will be pending indefinitely.
Is it a way from the batch file to bypass that PnP window or to make the batch running or...
Any idea would be appreciate.
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
nmi
19 years ago
If it helps, I recently packaged an HP Scanjet scanner. This device needed drivers installed as an Admin. If the software was deployed and then a normal user came along and plugged it in, the "Found new Hardware" wizard would come up and ask for a username/password to install the drivers.
The solution we found (which worked PERFECTLY), was to use a feature of Adminstudio 6, this was the "Device Driver Wizard". This took the inf file and the drivers and gave us an MSI that we installed as part of the deployment. Once this was done, when a normal user came along, they would plug in the scanner and all the drivers would install without further prompts.
It is definitely worth checking if you can use this to fix your current issues.
HTH
nmi
The solution we found (which worked PERFECTLY), was to use a feature of Adminstudio 6, this was the "Device Driver Wizard". This took the inf file and the drivers and gave us an MSI that we installed as part of the deployment. Once this was done, when a normal user came along, they would plug in the scanner and all the drivers would install without further prompts.
It is definitely worth checking if you can use this to fix your current issues.
HTH
nmi
Posted by:
WiseUser
19 years ago
If your driver is correctly preinstalled, the user's shouldn't get the message you're talking about. The message you're referring to is most probably due to your "Driver Signing" policy being set to warn.
See this post for information about preinstalling drivers:
http://itninja.com/question/gnu,-freeware-and-shareware-programs-to-cloning596
See this post for information about preinstalling drivers:
http://itninja.com/question/gnu,-freeware-and-shareware-programs-to-cloning596
Posted by:
Francoisracine
19 years ago
Yes we are set to warn.
The document is unclear.
This link is dead: http://home.att.net/~wshvbs/wshAPIToolkitObjectPage.htm
We are not creating MSI so it is more important to do so with a VBS.
I would like more details.
All installation are done here by using a Batch file.
So,
1. Copy the driver locally on the computer
2. Copy the driver.inf to windows\inf and compile the pnf. What does mean this last part.
The document is unclear.
This link is dead: http://home.att.net/~wshvbs/wshAPIToolkitObjectPage.htm
We are not creating MSI so it is more important to do so with a VBS.
I would like more details.
All installation are done here by using a Batch file.
So,
1. Copy the driver locally on the computer
2. Copy the driver.inf to windows\inf and compile the pnf. What does mean this last part.
Posted by:
WiseUser
19 years ago
Is your driver a signed driver (with "cat" file)? If so, these links (not dead) might help:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/setupapi/setup/setupcopyoeminf.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/install/hh/install/custom-install_882a44b1-2b4f-44cd-8215-e118866e3a94.xml.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/setupapi/setup/setupcopyoeminf.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/install/hh/install/custom-install_882a44b1-2b4f-44cd-8215-e118866e3a94.xml.asp
Posted by:
kkaminsk
19 years ago
Also watch out for USB drivers because they like to reconfigure if the user sticks the device into another port. With hardware protection drivers we use a manual process because the key is litterally installed onto every USB port on the computer one by one. This allows a locked down user to plug the device back in without having to remember which port it was installed on. Your device might not behave the same way but be sure to test this.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.