Windows 2000 Server

I have a windows 2000 server that allows for remote desktop and is a domain controller.  Sometime over the weekend, a very important directory was deleted somehow.  I really need to find out how this happened.  How can I track down how and who caused this.  It was not a system directory, it was a data folder with crucial information to an in-house application.  As a matter of fact it was on a separate partitian(d:).  What are my options on how to track down what happened????
Who is Participating?
GinEricConnect With a Mentor Commented:
EventViewer, Security, should show all changes of every user.  It might be a little long getting through it.  This assumes you have certain audits on, such as logon success, change permissions, things like that.

The point being, it is most likely somewhere in your logs.

Secondly, it may not actually be gone, or perhaps not fully.  But if you recreate it, it will be gone, replaced by the new creation.

It will take time to track down the event, in any case, but it can be done through the logs.
Kini pradeepPrincipal Cloud and security consultantCommented:
do you have auditing enabled for files and folders, if yes then you could go through the security logs and find out, who did it ( not how it happened) else i dont think there is a way out.
other might know better.

Hi gvector1,

Just one small problem, if you have not set auditing in the past, you may not be able to get this information.

Have a look at the following:

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Auditing has to have been setup previously. But if not, you can eliminate your admins and users one by one... you will need to question them carefully as to not give away what  you are trying to find out.

Good Luck,

i agree with itcoza, if you havent enabled auditing, its gone and there is no trace
gvector1Author Commented:
Well, unfortunately, auditing was not turned on.
:(   not much you can really work with now unless you want to use an undelete software

gvector1Author Commented:
Data loss hurts, but I do have a tape backup to restore data from.  Everything is on the tape minus 1 day.  My main desire was to trace the problem to the cause.  But it looks like I am out of luck.  I will leave this post open for a few days in case someone has any suggestions.  I will close and award points at that time.  Thanks for assistance.
Do you need more information?  The link I added will give you an Idea of how to setup auditing.

Guidlines for security:
More on security:
gvector1Author Commented:
I think we have determine what has caused the problem.  Now we have to figure out how it did it.  We believe that it was the Data Replication service that was running.  We have data replication running from 1 server to another server in another building.  I don't know how as of right now but we believe that the replication service had something to do with it, because the same thing happened this past weekend.  We had auditing turned on this time and it did not show to be caused by any user.  It appeared to happen after server reboot also.  Our server is scheduled to reboot over the weekend and it appeared that the data was wiped out or started being wiped out on reboot.  Any insight or suggestions is appreciated.  That is where we stand as of right now.

Script your reboot to first finish all tasks and to not start any new ones.

Normal reboot for Windows simply times a process and if it isn't finished it just reboots anyway, losing the data, as in replication data.

If the replicator has opened a directory for write, by creating a temp directory then deleting the old one and renaming this new one to the old name, replicator may have a bug in that when a reboot occurs it simply does delete the old one and rename the temp one.  Had you set your reboot script to inspect to see if this was happening and then allowed for it to finish before the actual reboot, you might have saved off the new data.

You probably have to isolate and shut down the replicator before issuing the reboot command.  But you'd also have to disallow new entries, have all users logged off, and pretty much stop all replicating activities.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.