Barry

We're having the same problem on 40 of our machines which have Pro Tools installed, and I've been pulling my hair out for days trying to solve it. Things I've tried include : Putting Domain Users into Power Users group Settings the correct permissions/rights through group policy, and running gpudate Giving Domain Users permissions to the USBSTOR and USB registry keys Giving Domain Users permissions to the USBSTOR driver files Unfortunately giving our students admin access is a complete no-no. Any ideas? We have the same problems, caused by installing the protools drivers for the mbox2.

It might not be a one click thing, but JFileSync might be worth looking into. One of the guys here has been playing about with it as a method of doing laptop back ups. I believe it works in a similar fashion to rsync so it should speed up the backup and save bandwidth by only copying changed files.

Anything that relies on the Protools audio drivers causes this problem and there is no work around. Source: Digidesign website

I've figured out what was causing the problem (for me at least) at last It seems that any machine that has protools related kit or drivers installed suffers from the problem. According to their site, they are aware of it and there is no fix yet. That sorts out the majority of my machines but leaves me with one user who's laptop is affected and he doesn't use protools. Barry

You could always remove the audio cable that runs between the cdrom and motherboard/soundcard. A bit of a pain if you've got a lot of machines but that would do the job. Barry

I'm also having a similar problem and hours on google is no help at all. It's rather confusing as it works as intended on some machines but refuses on others. They're all set up exactly the same using the same RIS build and have the same software and policies. I've went to the extent of upping the permissions of my test user account to have full filesystem and registry access which makes no difference. I've also checked that we have all of the correct settings in the GPO's we apply to the machines. Has anyone figured this out yet?