Windows 2003 R2 - Tracking user dumping files

[pepsi4all]

Do you guys know how I can track a user that dumps large files on my file server? I have this old 2003 r2 server that we use as files server. Each and everyday a person puts gb's and gb's of files. I have 350 users with tons of folders. I am trying to track this person down.

Please help if you know.

 

[ussnorway]

Filtering is a function of user accounts:

Option 1, give each user their own "home drive" to store stuff on… this makes tracking people easy and the "home drive" is a simple script that makes each user a folder with their log-in name and maps it as a drive when they log on. There could be privacy issues here but best practice is to allow at least one Admin account control over these 'home drive' folders so that they can be removed/ edited when people leave the company or "accidently" download porn… Muppets will be Muppets after all!

Option 2, look at your file structure and break it into groups… this really should have been done when you first set the system up but the basic idea is to make this example 1; folder/ drive available to everyone in the help_desk group and the example 2; folder is for people in the accounts group. If the file server just has 350 people all in the one group then IMO its past time to take a hammer to it and build a new file server.

 

[pepsi4all]

Filtering is a function of user accounts:

Option 1, give each user their own "home drive" to store stuff on… this makes tracking people easy and the "home drive" is a simple script that makes each user a folder with their log-in name and maps it as a drive when they log on. There could be privacy issues here but best practice is to allow at least one Admin account control over these 'home drive' folders so that they can be removed/ edited when people leave the company or "accidently" download porn… Muppets will be Muppets after all!

Option 2, look at your file structure and break it into groups… this really should have been done when you first set the system up but the basic idea is to make this example 1; folder/ drive available to everyone in the help_desk group and the example 2; folder is for people in the accounts group. If the file server just has 350 people all in the one group then IMO its past time to take a hammer to it and build a new file server.

Option 1, we have user with its own drive to put stuff on. It is map in their name. Files in that folder I am pertaining about are unclassified. The business needs we have met the criteria for this folder. Reason is, this folder serves for many projects that are shared to everybody that jumps on different offices.

Option 2, we do have folders that are broken to group also and globally user are able to access this kind of folders. I probably could still broken it to more. I also wish I have the luxury of time here.

My question is not to restructure. It is "Do you guys know how I can track a user that dumps large files on my file server?"
Once I track that user, I can teach her to dump her/his files on his own folder or dept folder. The person might have miss the training.

Kindly provide solutions.