How to stop sychronize others' files

[Guest]

In a corporate computer environment we have two users, UserA and UserB.

UserA has been using one laptop computer for a while. He has setup a folder
XXX that sychronize with the folder sss1 in the file server. So folder XXX
will have the same content as \\serverName\SSS1, as long as sychronization is
completed successfully. So content of folder sss1 is made available offline.


It works beautifully for a long time. Then recently UserA bought a new
laptop and give its old one to userB.

UserA uses his new laptop and continue to create a folder xxx that maps to
the folder in the file server ( \\serverName\SSS1 ), that is "same as
before". The folder content is also make available offline. This still works
beautifully in the new machine.

UserB starts working on this laptop previously owned by UserA, UserB also
set up its own folder (folder name is say YYY And YYY is NOT equal to XXX)
and mapped to another folder \\servername\SSS2 in the server. UserB sets
this folder contenet available offline also.

When the system try to sychronize the files for userB (at the end of the
day), why it also tries to synchronize the files in ServerName\sss1, is that
normal? I tell you what, it gives out the error mesage "access denied".

I am not surprised to see "access denied" message, because I know userB does
not have the permission of userA's files in \\servername\sss1. However, how
do I tell the system to STOP synchronizing the folder xxx with any previously
offline folders/files owned of userA in the old laptop? .

I only want the system to synchronize folders of userB only (sss2 in
server1, sss1). how could I do that ?

 

[John John]

Sounds like UserA still has an account on the machine and that he still
has the Offline Files option enabled.

http://support.microsoft.com/kb/811660

John

 

[Guest]

Thank you for the link, John. The link points to installing some hotfixes
but I don't know if it means the problem will go away.

BTW, do you mean if we invite userA to do all the following, then the
'problem' will go away?
1) go back to the old laptop and sign himself on
2) disable offlines files option
3) log-off

Thanks.

 

[John John]

Thank you for the link, John. The link points to installing some hotfixes
but I don't know if it means the problem will go away.

It should, that is what they made the hotfix for.

BTW, do you mean if we invite userA to do all the following, then the
'problem' will go away?
1) go back to the old laptop and sign himself on
2) disable offlines files option
3) log-off

Yes, I think that may fix the problem. I would certainly try that
before installing a hotfix that is not yet made available to the the
general public.

John

 

[John John]

See PS below.

It should, that is what they made the hotfix for.




Yes, I think that may fix the problem. I would certainly try that
before installing a hotfix that is not yet made available to the the
general public.

John

PS. Upon rereading the article it says that the problem was corrected
in SP2. Might be one of those "corrections" that doesn't quite work, it
wouldn't be the first time that Microsoft puts out a "fix" that doesn't
fix anything...

 

[Guest]

I have a similar situation, but UserA left the company. The profile was
removed from the computer, but the domain account remained. Everything was
okay until the AD group got around to cleaning up old accounts and remived
it.

The reference to the domain account remains in the registry. I have deleted
it, and it pops back in there.

I was able to uncheck the profile for synchronization, and this appeared to
resolve the issue, until UserB puts the machine into hibernation. It then
throws errors upon entering and leaving/waking up from hibernation. Shutdown
and restart actions do not throw error messages.

Thanks for any insight that anyone might be able to provide.