How do I remove an offline file folder in Windows XP Pro using Best
Practices? It is trying to synch to the old DC (Windows 2000),
whenever I logoff. I swapped servers to SBS2003. I want to keep the
synchronization to SBS2003 (new DC).

---

Clarification of Question by larrydz-ga on 05 Feb 2006 21:49 PST

Title: How do I remove a script which is synching to an old Server2000
domain controller?
asked by Larrydz on 02/01/2006 03:51PM PST  
 
  
 


I migrated a client from Server2000 to SBS2003. The Server2000 had all
data stored on workstation my documents stored on the server. When the
client logged off a synch script ran. Now that SBS2003  has been
installed on a new server it runs it's own logoff script on the
workstations (XP Pro SP2). Thats fine, but the old Server2000 script
is also running on the workstations when I logoff. [I can email a
picture of the error if desired]. I looked on the SBS2003 server and
see no Group Policies that I am pushing that are on subject of this
issue (default setting, no strong passwords yet).

When I joined the workstations to the SBS2003 domain, I did not detach
them from the old Server2000 domain (in case you ask).
When I joined the workstations to the SBS2003 domain, I did chhose the
keep the profile setting from the workstation's previous settings.(I
did this to keep the application software settings as close to the old
settings so I would not have to reinstall everything on the
workstations eg. Office)

I used manage the computer settings and looked at all entries. I had
no luck seeing anything relevant here.
I reviewed msconfig and also saw nothing. I could have easily missed
something here.

I am trying to rid the workstations of this script that runs when they log off.
Where should I be looking to see these items?
How do I remove them?

What keywords are key to this issue? 
Is there a white paper or other web resource that I should read to be
educated on this subject?
Is there a RSOP (or other utility) that I can run on the workstations
to see if they have security policies that I missed?
How do I see security policies on the workstations (other than looking
at the SBS2003 server)?

Its nonot a script. Its called offline files. Whenever you redirect My
Documents to a shared folder, Windows automatically enables offline
file to improve performance.

So..your solution is
1. On each users workstation, open My document properties and click on
Restore default. Then reboot. This will tell windows to forget the
sync. Now you log back on and redirect it again to new location.

2. Log on to each machine in SAFE MODE and delete a folder called
"CSC" located under \WINDOWS.
You need to enable Hidden & System files View to see the folder.

CSC contains all the information about offline files and the offline
files themselves. So by deleting it, windows doesnt know about it and
you can start fresh.

Goodluck
Vinod.

Caution regarding the above is advised.
Microsoft specifically states "Do not directly delete or move any
files from the systemroot\CSC folder."
see:
http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/prde_ffs_mosp.asp

Ignore the "Clarification of question" above, it's talking nonsense
and has some very bad advice.

I'm trying to find out how to do this myself.  I know it's possible to
completely clear the cache but don't know if you can remove links to a
server.

So far I've tried viewing the contents of the offline files cache and
deleting any files located on the old server.  My next step will be to
have a look in the registry to see if the old share is still listed
there.

Failing that, you can reset the entire cache by:
Open My Computer
Go to Tools -> Folder Options
Go to Offline Files
Hold down Ctrl+Shift and press the Delete files button.
You will be warned that you're about to reset your cache and the
computer will need restarting.

This procedure can be found at:
http://support.microsoft.com/?kbid=230738

Just posting a follow up on this.  I've not found any way to clear a
folder from the offline cache if the server is no longer available.

I suspect the best practice for this would be to update all the
clients before removing a server, unticking the "Make available
offline" for all the folders.

On the plus side, I can confirm that resetting the offline files cache
will solve this problem.