I also get prompted using the test user when I plug in and out the MS Keyboard.
I've removed all computer and user policies and still the UAC prompts when I plug in and out both the k/b and mouse :(
Printable View
I also get prompted using the test user when I plug in and out the MS Keyboard.
I've removed all computer and user policies and still the UAC prompts when I plug in and out both the k/b and mouse :(
So to recap:
I have in my office for testing this:
PC1 - which was imaged with windows 7 64bit in the summer - each time I plug the mouse or keyboard in and out I get the UAC warning as a std user.
PC2 - which was imaged with windows 7 64bit this week - where each time I plug the mouse or keyboard in and out I DO NOT get the UAC warning as a std user.
id say pc1 has some corrupt drivers so ith thinks standard items drivers are unsigned and need admin approval
We are going to re-image a PC and before installing any additional software or doing any MS updates see if the problem appears.
:)
Try this option for drivers in general. You'll have to find out the class for the type of drivers you want to allow.
Attachment 16008
Otherwise just for printers try this option. (as previously mentioned)
Attachment 16009
Thanks - I tried that sadly it did nt work.
I created a new GPO - the only one that was applied and allowed the following classes :
{4d36e96f-e325-11ce-bfc1-08002be10318}
{4d36e96b-e325-11ce-bfc1-08002be10318}
I believe one to be the mouse and one the keyboard.
I wonder if this could be a clue:
darkoshi | automatic updates device driver problem
This is the sequence of events on the affected PC's when a non-admin user logs on or removes and re-inserts the mouse.
I entered admin details to the UAC prompt.
Attachment 16010
Attachment 16011
Attachment 16012
looks like you have some strange ms keyboard/mouse software rather than std windows drivers perhaps its installing software as well as drivers which would nesesciate the uac prompt
Progress.
After reading this:
Christjan's IT Minutes » Annoying Lenovo device initialization at first logon
Specifically this part:
To instruct a device NOT to do additional initialization, the registry value “ConfigFlags” must be set to 0 in key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Enum” followed by the enum path (the device ID captured above). So full registry path to the device would be like: “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ usb\vid_0a5c&pid_217f\00271396b088”.
It seems “ConfigFlags” value 0×00020000 (131072) causes the extra initialization, so change it to 0.
I logged on to one of the affected PC's and looked in :
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USB and searched for all ConfigFlags that = 0x000200 (131072)
From this I could ascertain the ClassGUID for any that were 0x000200 (131072)
I found one which was {745a17a0-74d3-11d0-b6fe-00a0c90f57da}
I've added this to a GPO :
Policies
Administrative Templates
Policy definitions (ADMX files) retrieved from the central store.System/Driver Installation
Policy Setting Comment
Allow non-administrators to install drivers for these device setup classes Enabled
Allow Users to install device drivers for these classes:
{4d36e96f-e325-11ce-bfc1-08002be10318}
{4d36e96b-e325-11ce-bfc1-08002be10318}
{745a17a0-74d3-11d0-b6fe-00a0c90f57da}
Initial testing seems to suggest this suppresses the UAC prompt....
Annoyingly I've pulled another random machine in for testing this and the problem still remains...
The only items in the registry that have the “ConfigFlags” value 0×00020000 (131072) are those that are also :
ClassGUID = {745a17a0-74d3-11d0-b6fe-00a0c90f57da}
Which is covered by my existing GPO as detailed above.
I've run Group Policy Results Wizard and this policy IS being applied.
Stumped again...
Going to re-image with windows 7 64bit as part of an ongoing upgrade to see if that clears the issue....