The gyst of the problem: I'm trying to get CERTAIN users who authenticate through a GPO that has loopback enabled to use a specified local account on all machines instead of creating a brand new account in the Documents & Settings (since they will all be treated the same, personalization of the accounts is not a necessity). Background: I am a systems administrator for a small department in a University. The university has a domain which authenticates all AD users via Kerberos as well. The university somehow also has all the student accounts linked to Kerberos but they are kept seperated from every other type of AD accounts because of FERPA regulations and to keep information of the students private. We can allow students to login to our domain machines using their student accounts by enabling loopback processing in a GPO. The problem: Whenever a student (which we have over 30,000 of them) comes in to our lab and logs in to the machine, a brand new local account is created for them in the Documents and Settings folder. After a while, these folders start eating up quite a bit of space in the computers. The solution I'm looking for: Allow the students to authenticate using their accounts BUT have everyone who logs into these machines that is recognized as a student use a single specific account in the Documents and Settings folder so as to conserve space. I understand it would be so easy to simply create a generic login account and hand it out to students but that would pose as a security risk as anyone can then be given this generic account and we only want registered students to be able to use our labs. Thank you all ahead of time.

I dont think you are going to be able to do that, using XP anyway. If someone knows how, I'd be interested in it as well as cleaning up old profiles in dox and settings is a pain. Only thing I can think of is a script to clean them up at timed intervals but, then there is the fragmenting that would occur.

If you are concerned about eating up disk space then get software that creates a image (of a fresh install of windows configured with drivers and your domain), then everytime the machine is rebooted (nightly) the next morning it is running off the image, if you have 30,000 users then you should have servers setup for network storage so there should be no need to save data locally anyways I beleive one software title is called Deep Freeze does that make sense or do i need to word it differently yup!

Looks like DeepFreeze will be the way to go. This is a huge upset but at the same time a good way to expand on new possibilities. Its looking like Deepfreeze Enterprise edition will give me more tools than I really need and will be the way to go with this. Thank you both for your suggestions.