Hi,

On our domain (loaded with students), users have offcourse no admin rights.
This gives problems with USB memory sticks. WHen a user plugs his/her stick
into the USB port, Windows starts to install a lot of drivers. Sometimes
this works, sometimes Windows gets angry about it and refuses any further
actions.

Is there a way to allow users to install the drivers anyway? I think it's a
problem with unsigned drivers (and even some drivers from Windows appear as
unsigned, weird).

Thanx.
--
Toni Van Remortel

You should be able to set Windows 2000 to default to accepting unsigned
drivers:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/gp/596.asp

--
Richard G. Harper [MVP Shell/User] rgharper@gmail.com
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"Toni Van Remortel" <t.vanremortel@ha.be> wrote in message
news:eerjeg$ee2$2@ikaria.belnet.be...
> Hi,
>
> On our domain (loaded with students), users have offcourse no admin
> rights.
> This gives problems with USB memory sticks. WHen a user plugs his/her
> stick
> into the USB port, Windows starts to install a lot of drivers. Sometimes
> this works, sometimes Windows gets angry about it and refuses any further
> actions.
>
> Is there a way to allow users to install the drivers anyway? I think it's
> a
> problem with unsigned drivers (and even some drivers from Windows appear
> as
> unsigned, weird).
>
> Thanx.
> --
> Toni Van Remortel

Richard G. Harper wrote:

> You should be able to set Windows 2000 to default to accepting unsigned
> drivers:
>
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/gp/596.asp


Well, I did enable this, and now _every_ workstation refuses to install any
driver for the user, while before it only happend with a few.
It seems that everything in AD is inverted here (almost all settings I apply
through a GPO, don't do what they should).

*sigh* Getting sick of AD here :-(
--
Toni Van Remortel

I wish I had some sage advice, but all I can offer is that the policies work
on my AD network exactly as they should.

--
Richard G. Harper [MVP Shell/User] rgharper@gmail.com
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"Toni Van Remortel" <t.vanremortel@ha.be> wrote in message
news:efvka9$ntf$1@ikaria.belnet.be...
> Richard G. Harper wrote:
>
>> You should be able to set Windows 2000 to default to accepting unsigned
>> drivers:
>>
>>
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/gp/596.asp
>
>
> Well, I did enable this, and now _every_ workstation refuses to install
> any
> driver for the user, while before it only happend with a few.
> It seems that everything in AD is inverted here (almost all settings I
> apply
> through a GPO, don't do what they should).
>
> *sigh* Getting sick of AD here :-(
> --
> Toni Van Remortel

Richard G. Harper wrote:

> I wish I had some sage advice, but all I can offer is that the policies
> work on my AD network exactly as they should.

I'm afraid that the previous sysadmin did too much "registry hacking
sessions" on the domain controller.
I'll try to manage it through low level workstation registry hacks.

Tnx anyway.
--
Toni Van Remortel

The only thing to keep in mind is that most "workstation registry hacks" are
liable to be overridden by Group Policy when it pushes out. The workstation
settings are the basis for the settings that will apply after GPO comes
down - so you may enable it on the workstation only to have your rogue GPO
turn it right back off again.

I'd really start thinking about using something like the RSOP (Resultant Set
of Policies) tool on Windows XP, or the Windows Server 2003 DCs, to analyze
what's going on with GPO. If that's not possible (all your workstations are
Windows 2000) then it might just pay to start up a new GPO with the settings
you want and then nuke all the existing GPOs that you can't figure out.

Just a thought.

--
Richard G. Harper [MVP Shell/User] rgharper@gmail.com
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"Toni Van Remortel" <t.vanremortel@ha.be> wrote in message
news:eg2sra$88s$1@ikaria.belnet.be...
> Richard G. Harper wrote:
>
>> I wish I had some sage advice, but all I can offer is that the policies
>> work on my AD network exactly as they should.
>
> I'm afraid that the previous sysadmin did too much "registry hacking
> sessions" on the domain controller.
> I'll try to manage it through low level workstation registry hacks.
>
> Tnx anyway.
> --
> Toni Van Remortel