MNHughes Posted February 4, 2010 Posted February 4, 2010 Hi Everyone, This is probably a stupid question and one easily answered, but we've never had the time to really look into it... We are on CC3, soon to be migrating to CC4... Students often remove USB mice from the workstation and put them into another port or steal them from another PC. However students don't have admin rights to reinstall/install the mice again; so someone with admin rights e.g. me has to go and logon and reinstall the drivers. It does sometimes work if a student sees the username password prompt (asking for perms to install driver) and clicks cancel. I was wondering if anyone else has this issue and if they know a solution. Also is this issue still in CC4 if so is there also a solution to that as well? Many Thanks, Martin
Edu-IT Posted February 4, 2010 Posted February 4, 2010 On CC4 I can remove and connect USB devices without any prompts for drivers.
enjay Posted February 4, 2010 Posted February 4, 2010 People can connect USB mice here (CC3) without issue, even cordless keyboards, gyro mice and some tablets - the drivers for these are all installed as part of the build process (or rather, I thought they were standard to Windows itself). Are you using particularly funky USB mice or just regular ones?
MNHughes Posted February 4, 2010 Author Posted February 4, 2010 We've used a number of USB mice from a number of brands e.g. Microsoft, IBM, DELL, Genius and RM. On CC4 I can remove and connect USB devices without any prompts for drivers. Is that with a student account?
synaesthesia Posted February 4, 2010 Posted February 4, 2010 Also not a problem had here - sounds like permissions have gone up the spout somewhere :\
Jamo Posted February 4, 2010 Posted February 4, 2010 Strange, you are not installing custom drivers are you for the mice? the default Windows ones shouldn't require you to do that we have not come across that problem at all before.
meastaugh1 Posted February 4, 2010 Posted February 4, 2010 It is very likely that you have an MSI package that contains and is corrupting the catroot2 folder thereby preventing signed drivers to be loaded/installed by standard users. This is a fairly old issue; RM have produxed a fix to reset catroot2: Log In
MNHughes Posted February 5, 2010 Author Posted February 5, 2010 Thanks everyone for the quick responses. I'm glad this is just on CC3 then; since we're migrating in a couple of weeks it's not that much of a problem. Cheers. Martin
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now