Overwritten profile

I have a 2003 server with roaming profiles setup.  A profile was moved to the server with all the user data but then accidentally overwritten with a blank one.  Any way to get this back? I ran some data recovery utilities but since the files were never actually deleted it didn't find them.  Help would be greatly appreciated.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Do you have any backup tapes.

If not..

Often the only practical way of recovering from a corrupted profile is to delete the current profile and allow the system to create a new one. Your profile can not be deleted while you are logged in. If you would like or need your profile deleted contact the operator for assistance.

In the event that there is something that must be recovered there are several possible methods that may help you recover.

Roaming profiles are backed up to tape nightly but there is no way to be sure that the local version was successfully copied to the server. Consequently there is no guarantee that data in your profile is going to be recoverable. Files that are backed up on tape can be restored to your home directory.

If you log in and do not get your usual user profile you may be able to recover. Do not log out! Contact the operator and ask them to rename the copy of your profile on the server. At this point you can connect to the server and transfer files that are still in the old profile directory to your home directory.

If you receive a dialogue box stating "your locally stored profile is newer than your roaming profile" you will generally want to select the download roaming profile option. This is not always the case. Remember logging in will download your roaming profile and overwrite the local profile. Logging out will overwrite the roaming profile. If you are unsure, the safest option is to cancel and log on to a different machine. If the other machine successfully downloads the correct profile you can safely choose roaming profile. If there are files missing you must first log out of that machine. Then log on to the machine that gave you the original dialogue box. Choose the local profile option. If this loads the correct profile you can log out and your profile should be updated."

Taken from: http://www.cs.umn.edu/help/account/ntprofiles.php
If you have any type of backup system / routine that could have saved this data, just copy it back into the original folder and reboot.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
hindsightAuthor Commented:
There was no backup because the ceo refused to put anything on the server.  I didn't set up the initial network.  I forgot that they had roaming profiles and I switched the local user folder name with the network user folder name in documents and settings.  I have done this thousands of times without issue.  I think when I did that, the profile with all the data was now the network profile on the local pc and logging in overwrote it with the blank roaming profile that was on the server.  I may be screwed.  I am wondering if I turn off roaming for his account and rename the profiles on the system if data recovery software will find it.  I know that sometimes if you try to recover a system file (i.e. my documents) it won't find it because it already exists.
You can switch back from roaming to local, but I'm not sure if that will solve your problem.  Each profile has a unique ID number (listed in the registry).  Even deleted profiles are still listed there.  If the CEO stored everything locally instead of on the server, try logging on locally instead of on the domain.  When you switched to roaming, you only (as far as I know) changed the path location of my documents.  They should still be where they originally were!  The problem is access and ownership.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.