Roaming Profile cannot delete files

  • Thread starter Thread starter Rev. Michael Kujawa
  • Start date Start date
R

Rev. Michael Kujawa

When a user deletes files from their roaming profile
(the files are stored normally in their My Docs folder)
the files appear to delete correctly

However when they log off and back on the files are back
as if not deleted.

What is wrong and how do I fix it
 
does the user have permissions to write to their roaming profile. If not,
any changes made to the profile will not be saved and when the user logs in
again his old profile will be used.
 
Yes they do have permissions

I even find as the administrator
when I delete files they reappear
next login
 
which files are you talking about deleting?

I see you said "My Docs" is that part of the profile?

What happens if you add a file to the same folder? Is it there or gone at
logon?

Do you have folder redirection set in active directory?
 
My Documents or Personal
is part of the roaming profile that is cached locally
when a user logs on.

Adding files is not an issue
just deleting them

If I physically delete from the server where profiles are stored
that takes care of the problem, but I do not like having to
be in control of this work-around as it should be automated in
the OS one would think when a user chooses to delete a file
 
oh I didn't know you were locally caching it. Is there a reason you choose
to do that?
 
Isn't this a normal thing?
If not do I need to do a reg hack
on each machine to keep it from caching profiles?
 
don't know what is normal, but what we do is have the profiles and the
user's drive keep seperately and each on the server. so all are profiles
are at \\bbh\dfs\profiles\username (user name of the user) and the user
drives at \\bbh\dfs\users\username. This will the profile and user drive
are kept seperate. Any changes to the user drive are done server side and
you don't have the caching. Our profiles are network but a local copy is
cached. However, the area where adding and deleting files is prevelent (the
user drive) is always server side and never cached.
 
Hmmm
I have my users drive on one server errr NAS I mean
and the profiles stored on the domain controller

Yes a local copy is cached and that I believe
is where the problem is. When a user for any reason signs on
to the domain a local copy is created. Those that logon from
more than one workstation such as myself as administrator
file the ability to delete files from the profile an impossibility.

Saying that however, Even if all workstations I log onto
are logged off and only one workstation with my login is active
I still find the ability to have the profile updated upon logoff
an impossibility.

For users that login to one workstation and one workstation only
this is not an issue.

When a user logs off whatever is removed from the local copy
should be removed from the profile store. But that is not the case.
in regards to more than one local copy.
 
Rev. Michael Kujawa said:
Hmmm
I have my users drive on one server errr NAS I mean
and the profiles stored on the domain controller

Yes a local copy is cached and that I believe
is where the problem is. When a user for any reason signs on
to the domain a local copy is created. Those that logon from
more than one workstation such as myself as administrator
file the ability to delete files from the profile an impossibility.

Saying that however, Even if all workstations I log onto
are logged off and only one workstation with my login is active
I still find the ability to have the profile updated upon logoff
an impossibility.

For users that login to one workstation and one workstation only
this is not an issue.

When a user logs off whatever is removed from the local copy
should be removed from the profile store. But that is not the case.
in regards to more than one local copy.
Click to expand...



There is a group policy for this

Bye
 
Back
Top