Remove Deleted Drive From Syncronization

[DTracy]

One of the workers here has a W2K laptop that is connected to the W2K LAN. He had his local files syncronized with the Server_1. Server_1 died and all data was transfered to Server_5. He re-syncronized his laptop with Server_5 but was unable to delete the entry for Server_1. I have also been unable to remove this entry, and it causes the syncronization routine to execute for long periods of time trying to find Server_1.

How can I remove this unwanted server entry?

Thanks ever-so-much for any assistance rendered.



Best Regards,
David Tracy

 

[bcastner]

This is actually harder than it should be.
You need the resource kit utility cachemov.exe.

http://www.jsiinc.com/SUBI/tip4200/rh4230.htm

 

[DTracy]

Thanks for the reply Mr. Castner.

You're right, this is a lot harder than it should be! I downloaded that cachemov.exe tool and then searched for any instructions I could find on how to use it - which was almost nothing.

I don't get it, how do you use that tool to delete an unwanted shared resource from the syncronization procedure?

Thanks for any suggestions.



Best Regards,
David Tracy

 

[bcastner]

I misunderstood the question.

You need the csccmd.exe utility.

You could use this to disable the older synchronization, or do a file server move:

csccmd.exe /moveshare \\oldservername\sharename \\newservername\sharename

It also has a disconnect option.

http://support.microsoft.com/?kbid=884739

If you have an XP workstation, the utility can be found and extracted with the Windows 2003 Resource Kit:

http://www.microsoft.com/downloads/...69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en

 

[DTracy]

Thank you for the direction Mr. Castner, this made much more sense. I found the Windows 2003 Resource Kit that contained the csccmd.exe utility, however I could not find a Windows 2000 Resource Kit that has that utility. I tried the csccmd.exe from the 2003 on a W2K workstation with mixed results. The utility would operate but would only allow enable/disable commands. Any other command resulted in an error 87. Interestingly, the I had the same results on an XP-Pro workstation. Anyway, the final result was negative. I deleted the syncronization completely from the W2K laptop and made a new sync. The old UNC came back. Could this have anything with the PDC?

Thanks again for your help.



Best Regards,
David Tracy