NeilCotton

You don't even need to remove the drum, but it is a very good cost saving hack, as the drum can go another 2 Toner cartridges worth of printing without seing any fusing problems. PS. This is the actual method of reseting the clock on the printer when you really DO replace the drum.

Hi Elsie, That is currently my ownly resort, however, we are sometimes clocking up GBs of tmp files and we are on the limits of our current storage capabilities. Chris, thanks, I'll try this.

Hi Arthur, Thanks for the post. This is essentially what I have already done, and works for the purpose of stopping the deleting of items, however, the bones of the problem I have due to this, is that document temp files, are created when users open files from their home drive, are not deleted when the document is closed or even when the session is logged off. This means that all the users home folders will quickly pile up with tmp files, and I want to try and avoid a mass find/delete scheduled nightly task to remove them and have them cleared when the attributed document is closed, or at least when the user logs off.

Having a bit of a mare, and probably can't see the wood for the trees. But I'm trying to remove delete permissions for users, so that they can't delete any files from their home drives (don't ask). This I can do fine with denying the DELETE priviledge to the STUDENT group in the file system properites of the share, but however this means that every document that they open up, creates a temp file, and on closing, even logging off, the temp files aren't removed. So I wrote a tiny batch to delete *.tmp, and run as a logoff script, however as this is a loggoff script, it runs with the same users credentials, so therefore, does not delete anything. Can not put it in a shutdown script, as the temp files are on the share/not the local profile on the workstation (besides, the machines aren't always shutdown after a session). DOHH! I know I could schedule a massicare of the tmp files at night across the entire drive, but would prefer not to have to do this. Anyone got any ideas, I've not had much time to dedicate to coming up with a work around. Any help would be appreciated. Many regards Nei;

Hey all, looking for some advice. Environment : HIGH SCHOOL - Computing Students Network : Win 2K/2K3 Hosts: Win XP with Visual Studio 2010 Students can code a module, and run it with the debugger, and it works fine (when it has not yet been saved). As soon as you save the project, trying to run it from the debug command, or launching the built executable generates the Software Restriction Policy block. We can't take out .EXE from the Software restriction policy because that would cause free-for-all, and we can't realistically specify a single filename.exe as that would count on sutdents saving the project with the exact filename, and also would open up possibility for students understanding that filename.exe is not being blocked, and then renaming other applications we are trying to be blocked from running. I would assume there is someway to run code from the debugger that compiles the code inside it's own kind of virtual environment, free from policy settings. Does anyone know if there is a sensible way round this? I may be looking over something blatently obvious. Any contributions greatly appreciated. Regards Neil