1

We have recently taken a customer on from a different IT company. All their user home folders where stored in \servername\home$\username in order to keep uniformity across our customers I moved the data to \servername\data\documents\username and pointed the users home folder there in AD.

All is fine apart from two users complaining about some missing documents (but not everything) I can’t find them anywhere, checked the backups and they don’t exist in the old location. I’ve have checked backups and shadow copies right back to three months ago but the files don’t exist anywhere. It’s like they have never been saved on the network even though the recent document shortcuts point to network locations.

I’m genuinely stumped.

3 Spice ups
2

Hi there,

This sounds to me like a profiling issue, however I could be wrong. It would depend on the level of access you and the users have to access the shared files. If you’re a domain admin, then you should be allowed access to most if not all file shares, but if they are gone then the files might have been corrupted/lost and the file locations are actually blank.

Hope it helped!

J

3

I don’t think I’ve ever had a user remember the name of a “missing” folder. Usually requires a lot of wildcard searching. The answer usually fell within 1 of a few options, but the most common was a user was slow on the double click and accidentally moved it up or down one or two folders because the prompt that said “are you sure?” was clicked on yes/ok. The others were it never existed (at least with any name they could recall) or was in some other random location and not where they thought it was.

If I had to guess, it’s a file that never existed that they’re trying to use as a way to say “I did something, but IT can’t find it so I have to start over” or “I’m throwing a hissy fit because I liked the last IT company and I want them back”

The last option, although not likely, but possible. The user NEVER closed the file(s) and the backup software skipped it due to skipping open files.

4

I removed the local profile of the user on the remote computer from the system applet as well as deleted the Users registry key under HKey_local_machine\Software\Microsoft\WindowsNT\Current version\profile list. I then changed the Security permissions on the users RDS_Profiles folder located on our file server so that the user had sole ownership only and removed anyone else including any administrators or Domain admins. The only other user that should have been in there would be the ‘system’ user with Full rights. This worked. it resolved the temporary and roaming profile error and then synched the users data from her RDS profile to the remote desktop.

Regards!