Deleted files reappear in roaming profile

By flompio ·
I have a test environment which i am readying for a new network. Everything looked well ...until i noticed when a user logs on they cant delete anything on their desktop or my documents (both of which have a folder redirection GPO). Users are able to create files or folders, although anything deleted on the desktop or my documents reappears when the user logs back in.

We are running a win 2003 terminal server, which hosts the profiles. Users own and have full access to their own profile folders, with system and admin set to full also.

i have also enabled 'delete cached copies of roaming profiles' GPO and still no luck.

Can anyone help on this one?



This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

a new problem

by flompio In reply to Deleted files reappear in ...

i removed the folder redirection and the 'delete cached copies of roaming profiles' GPO's as well as the local profiles, which enables users to delete the files on the desktop.

However now when a user deletes an item it goes to the recycle bin as normal, though when they log back on the item is removed from the recycle.

does anyone have a solution so that the items remain in the bin until the user decides to delete?


Collapse -

This one took me awhile...

by trace.kilgore In reply to Deleted files reappear in ...

I had this same problem.

You cannot have your Folder redirections in the same folder as the roaming profile. Create a seperate share to hold the desktop icons and the My Documents folder. I forget the indepth explanation, but basically it was only checking to see if any documents were new or had been changed.

Collapse -

Deleted files reapperar in roaming profile.

by ecerrante In reply to Deleted files reappear in ...

I think because of seeing has previously deleted files reappear, from the files that constitute the user profile after you restart the client and rerun access AD with your domain account, is due to errant information on the date of change the file. Indeed it may happen that a file is changed, an incorrect system date set to the future, and then happen to synchronize with your central profile server. The next time synchronization algorithm Riscara the file from the server on local profile. We must change the dates in "last modified" file to make them consistent with the current date.
I hope to be helpful.

Back to Networks Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums