Windows 2000 Pro Roaming Profiles

[Alex Reid]

Not sure it this is the Right group but here goes
I have several windows 2000 Pro Machine where the User will Delete an Item
off of the desktop or out of there my documents folder and it will appear to
be deleted
However on the next logoff logon sequence it will return as if it was never
deleted. All users are using roaming Profiles and the my documents is not
redirected but captured as part of the roaming profiles.
Any idea
Alex R Network services

[Todd J Heron]

Sounds like a permissions issue on their roaming profile share. The file
deletion does not update itself when the user logs off. Check the
permissions to the user's folder under the roaming profile share

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

[Justin Warner]

I had this issue once, and found it was a combination of using Folder
Redirection alongside roaming profiles when both of these were pointed at the
same network location. (Eg: Folder Redirection points the desktop to
\\server\share\desktop, and user's roaming profile is pointed at
\\server\share)

When the user logs onto a client, their desktop (and other profile folders)
are cached locally. Because of the folder redirection, when the document was
deleted it was removed from the user's desktop folder on the server, but the
local copy of the cached roaming profile still has the file in it. When the
user logs off, the local copy is written to the server, replacing the deleted
file. Next time they log on, the file is back.
The solution was to either stop using Folder Redirection, or exclude the
Desktop(and/or the My Docs and App Data folders) from the roaming profile.
I hope this makes sense!!

Justin

[lforbes]

Hi,

This is Standard Windows Procedure. I call it "ghosting" and it happens
to me all the time which is why I enabled mandatory profiles with
folder redirection for my users.

When a user logs on, the roaming profile is downloaded from the server
to the local machine. All changes are then done LOCALLY. The reason is
that the file is deleted only "locally" while the user is logged in. On
Logoff, the Roaming Profile is "suppose" to upload to the the "server"
and "delete" the server roaming profile copy of the file. This often
doesn't happen. When in doubt Windows "doesn't" delete files.

It is especially obvious when users log onto to a variety of computers.
They save something on one desktop and logoff which uploads to the
server. They go to another machine and delete the same file. However,
when they go "back" to the previous machine the file is still there
because the "Local" copy on that machine was never deleted.

You can enable Windows to delete roaming profiles on logoff and set to
0 caching profiles. However, even in my network this doesn't always
work. I have a startup script that runs and deletes all the local
cached profiles.

Cheers,

Lara