Allowing Users to Install Hardware Device Drivers
#1
Posted 20 September 2006 - 08:56 AM
secpol.msc > Security Settings > Local Policies > User Rights Assignment > Load and unload device drivers > Add User or Group
However, the Add User of Group option is greyed out. All I have in the Allowed Users is Administrators and Print Operators.
So is there anyway I can allow users to, in theory, add hardware?
Zoom7000
#2
Posted 20 September 2006 - 11:12 AM
#3
Posted 20 September 2006 - 11:24 AM
#4
Posted 20 September 2006 - 12:22 PM
#5
Posted 21 September 2006 - 01:09 AM
Thanks for the help guys, however any more ideas are very welcome!
#6
Posted 21 September 2006 - 12:19 PM
Problem is the way that the corresponding .INF file is structured and the number of different ID's the different sticks have.
Open with a Registry editor or viewer the registry on one of the machines of which the sticks have been mounted, at this key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USBSTOR
or corresponding
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet00x\Enum\USBSTOR
You will see a (LONG) list of all devices that were ever mounted.
This happens because devices have their own identity "coupled" with the driver.
Check this entry also:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}\
It should be possible, but mind you, this is just an idea, to install it in the CriticalDeviceDatabase, then you may not have the need to re-install the same driver again and again each time a new device is connected, as it will already be running.
Some info can be taken from this (LOOONG) thread here:
http://www.911cd.net...showtopic=14181
Particularly these posts from sisal:
http://www.911cd.net/forums//index.php?s=&...ost&p=99087
http://www.911cd.net/forums//index.php?s=&...st&p=101267
but you will need to read a lot more if you want to follow this hint.
jaclaz
#7
Posted 22 September 2006 - 08:21 AM
Another way around the issue is to make the "Domain Users" group a member of the Local "Power Users" group and make sure that you have heavily restricted them from running *.cpl and *.msc via group policy. Again, making Domain Users members of the Local Power Users group would need to be done on EVERY machine!
Is there a script that can be run at logon that would allow me to make any Domain User that logs on to the machine a member of the Local Power Users group?
#8
Posted 22 September 2006 - 11:51 AM
http://setacl.sourceforge.net/
(GPL)
jaclaz
This post has been edited by jaclaz: 22 September 2006 - 11:52 AM
#9
Posted 27 September 2006 - 02:21 AM
#10
Posted 27 September 2006 - 08:08 AM
First create a global group in AD add all users you want to have local power users rights for example name it Powdomainusers.
Create a GPO which will run a startup script in local computer policy.
The script will be :
net localgroup "power users" domainname\powdomainusers /add
#11
Posted 13 October 2006 - 03:07 AM
allen2, on Sep 27 2006, 08:08 AM, said:
First create a global group in AD add all users you want to have local power users rights for example name it Powdomainusers.
Create a GPO which will run a startup script in local computer policy.
The script will be :
net localgroup "power users" domainname\powdomainusers /add
Thanks for that allen2. However, although it answers my question, and I thought it would solve the issue. It doesn't seem to want to fix the problem. The message we are getting, and I didn't realise it at first, is that "You need to be a member of the Administrators group on this computer to install this hardware" It then asks for a password.
There is no way we can add kids to the Administrators group! So, looks like I'm back at square 1.
Any ideas?
Zoom7000
#12
Posted 23 October 2006 - 07:20 AM
http://www.novell.co...ools/16306.html
Quote
Novell Cool Solutions: Cool Tool
In Brief
Grant Users and Power Users the ability to install USB mass storage devices
jaclaz
P.S.: IF it does, you owe me a beer
#13
Posted 07 November 2006 - 05:15 AM
#14
Posted 07 November 2006 - 11:15 AM
http://uranus.it.swi...au/~jn/coke.htm
jaclaz
#15
Posted 14 January 2007 - 02:15 PM
Ctrl-X, on Sep 20 2006, 05:12 PM, said:
I have this problem where after I have made a nlite version of windows 2003 datacenter, i input my usb flash drive (and any other usb drives and so on) and i am subsequently prompted to install 'Generic Volume'. However, when I was using the full installation of windows 2003, I have never had to confirm any driver installation, because i would get a notification balloon in the taskbar saying the drive (or flashdrive) device has been recognised, and it would all install automatically. So therefore, having looked at your post above, i have come to the conclusion that somehow nlite breaks signed drivers or something along those lines. Is there something i could do in nlite to prevent this popup from appearing (which at one time asked me to continue, because the drivers weren't marked as signed!), or is there some other thing i am overlooking? Thanx in advance!
#16
Posted 02 February 2007 - 08:20 AM
jaclaz, on Oct 23 2006, 07:20 AM, said:
http://www.novell.co...ools/16306.html
Quote
Novell Cool Solutions: Cool Tool
In Brief
Grant Users and Power Users the ability to install USB mass storage devices
jaclaz
P.S.: IF it does, you owe me a beer
Unfortunately, this didn't fix the problem, so I'm still searching for a solution...
#17
Posted 02 February 2007 - 09:33 AM
Quote
jaclaz
#18
Posted 02 February 2007 - 09:59 AM
;AllowUSBJumpDrives.au3 ;Created by Jeremy Mlazovsky If IsAdmin ( ) = 0 Then MsgBox ( 0+48+262144, 'Uh oh!', 'You need to have administrator-level access to run this utility!' ) Exit EndIf Dim $file = 'C:\Windows\inf\usbstor.inf' Dim $group $group = 'Power Users' SplashTextOn ( $group, 'Updating permissions for the file' & @CRLF & $file & ' to' & @CRLF & 'Modify, Read and Execute, Read, Write!', 300, 75 ) RunWait ( 'cacls ' & $file & ' /E /G "' & $group & '":R', '',@SW_HIDE ) RunWait ( 'cacls ' & $file & ' /E /G "' & $group & '":W', '',@SW_HIDE ) RunWait ( 'cacls ' & $file & ' /E /G "' & $group & '":C', '',@SW_HIDE ) Sleep ( 2500 ) $group = 'Users' SplashTextOn ( $group, 'Updating permissions for the file' & @CRLF & $file & ' to' & @CRLF & 'Modify, Read and Execute, Read, Write!', 300, 75 ) RunWait ( 'cacls ' & $file & ' /E /G "' & $group & '":R', '', @SW_HIDE ) RunWait ( 'cacls ' & $file & ' /E /G "' & $group & '":W', '', @SW_HIDE ) RunWait ( 'cacls ' & $file & ' /E /G "' & $group & '":C', '', @SW_HIDE ) Sleep ( 2500 ) SplashOff() MsgBox ( 0+262144, @ScriptName, 'Users and Power Users should now be able to install USB Flash drives!', 10 )
Could it be anything to do with Driver Signing? Albeit I have told AD to ignore all instances of Driver Signing.
#19
Posted 02 February 2007 - 11:09 AM
The only thing that should prevent installing the USB device should be if the device is not standard, i.e. it does not comply with either the eplicit vid&pid or the general Class&Subclass declared in usbstor.inf.
Also check permissions on the tree above USBSTOR.INF, maybe something needs to be changed there, as said I am not an expert on this, but maybe some Ownership and Inheritance settings do override the file ones.
A test you could make, if you can make a test install, is to setup XP on a FAT32 partition....
Another idea (again of which I have NO experience) could be using NTRIGHTS:
http://www.ss64.com/nt/ntrights.html
with the "SeLoadDriverPrivilege"
jaclaz
This post has been edited by jaclaz: 02 February 2007 - 11:24 AM
#20
Posted 05 February 2007 - 03:13 AM



Help


Back to top









