In a school environment, we had set up for the students in UserManager, to have their profiles go to \\nt\users\%username% . We want to delete these folders on a semester schedule so the next semester class won't have the classwork from the previoussemester. (the passwords are reset every semester)
But IE has kicked in and put application data, user.dat and other IE folders in the user folder, and even with CACLS or going in folder by folder, it won't let me access or delete these folders (Access Denied!). How do I batch all these folders as far as permissions and delete them all?
I have tried takeing ownership, going into Security file and directory properties and re-applying permissions, but nothing has worked.
This conversation is currently closed to new comments.
I dont know what you can do with batch, but you should be able to delete them by going into the System applet in control panel, go to the user profiles tab, and select the user profiles you want to delete and click the remove button.
I'm wondering if rather than a security problem, the file attributes are simply set to read-only.
From a DOS prompt, you could enter attrib *.* and see whether the read-only bit is set and if so, release it with attrib -r *.* That could be done as part of a batch file that then deleted the directories and files.
If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.
CACL and user.dat
But IE has kicked in and put application data, user.dat and other IE folders in the user folder, and even with CACLS or going in folder by folder, it won't let me access or delete these folders (Access Denied!). How do I batch all these folders as far as permissions and delete them all?
I have tried takeing ownership, going into Security file and directory properties and re-applying permissions, but nothing has worked.