locally cached user accounts

[n00bius]

On my network, i have a number of users that log onto computers in a lab, and every time they log on they create a user profile (and they don't have a roaming profile). Now aside from going through and deleting all the profiles from the computer what would be an efficient way (hopefully, server-side), to delete the folders after logging off, or to prevent the local profiles from being created all together?

[cross]

the folders have to be created, so that the profile settings and files have a place to live for that user while the system is in use. Weather or not you need it for future use, the computer needs it in order for that user to log on and use the system. I can see no easy way to accomplish this. Usually I would just make a batch file for something like this to delete all the folders, but since there are other folders in there, like All Users, that would not work. Perhaps some one out there knows a way to delete profiles on logoff or to delete profiles after XX time from the server.

Heres a thought, how about creating 1 local logon account for everyone to use, or 1 domain logon for the lab. This way you'd only have 1 profile folder on each system to deal with. Since you dont seem to care about saving individual user files, this may work?

[SirDice]

This may come in handy:
http://www.microsoft.com/downloads/d...displaylang=en

[oofki]

I guess you could write a script that executes the thing SirDice found at every user login except for the current user who is logging in...

[nihil]

I am not sure that this is what you are looking for, but in a school/laboratory environment where multiple users share equipment on a session by session basis, you might look at DeepFreeze by Faronics?

http://www.faronics.com/index.asp?reg=UK

http://www.faronics.com/html/deepfreeze.asp

[n00bius]

heh, we are using deepfreeze, was trying to find a native solution, so we could stop using deepfreeze. It's a really remarkable program, but hellish when you want to update regularly, or if it stop accepting tokens and you can't thaw the machines. (If implemented correctly, from the start, deep freeze is awesome).