Preventing student access to 'Previous Versions'

[maniac]

We run RMCC3 here, and I can't seem to stop the students having access to the previous versions tab in Explorer. I've tried both the user and machine registry key additions from the microsoft support site, they work on a non CC3 machine, but on a CC3 machine there's something stopping them from working! I know the registry keys are applied, as I've remotely accessed the registry on my test machine and checked the key is present, and it is!

 

Anyone got any ideas on preventing the students accessing this on RMCC3, as there's obviously something in CC3 over writing the registry change I've made.

 

(In case you're wondering, they're having great fun restoring MP3 and SWF games at the moment that I keep deleting, I wondered how they were doing it so quickly! )

 

Cheers,

 

Mike.

[bossman]

Do you have the students as restricted or advanced user types?

 

Which version of I.E. are you using?

[maniac]

IE6, as IE7 does something screwy with our wallpaper

 

As far as I know the students are normal CC3 users, although this network has been changed a lot over the 4-5 years it's been here, and nothing is documented so it's hard to tell as it's nothing like the way RM would have configured it I don't think. How do I tell if they are elevated users on CC3 or not??

 

Mike

[maniac]

Actually I've just round a solution to this.

 

Using the REGSVR32 command to un-register the library twext.dll solves the problem, stops anything to do with previous versions appearing on the workstation, fantastic!

 

Mike.

[Michael]

Why not turn off Previous Versions or Shadow Copies altogether?

 

Right click the volume on the server then select the Shadow Copies tab

[sahmeepee]

Why not turn off Previous Versions or Shadow Copies altogether?

 

Right click the volume on the server then select the Shadow Copies tab

 

Presumably because he wants to have access to the feature for administrators but not for users. That's how we have it to reduce the likelihood of them firing their user areas into the bitbucket.