"Kelvin" <> wrote in message
news:#...
> I'm fed up with Windows XP synchronization.
> I've been using it to synchronize laptop users files to the server so they
> can get backed up.
> It doesn't synch ALL file types, it doesn't seem reliable\consistent, and
> on the computers (laptops) that I have it Enabled, the laptops disconnect
> from the network frequently and randomly.
>
> I've found these two tools SyncToy and RoboCopy.
>
> For the synchronization of the users My Documents folder I'd like the
> synch to happen as part of the logon script, but not sure if that is
> practical, or the correct approach.
> I could also create a batch file and have them run it on their own, but I
> don't like the idea that they may not synch for months and then their
> laptop goes out and they're missing some important data.
>
> I've tested with RoboCopy a little. I have it set to mirror a couple
> different directory structures.
>
> I created this one for an application we run that I need to update
> occasionally.
> This one seemed to have issues (timing out) when I have it recreate a
> complete folder structure, but if I make minor changes it seems to work
> great. Most of the changes would be small so the timing out issue isn't a
> deal breaker.
> robocopy "\\Prosperity\SharedData\CommonShare\Procede Software\Procede
> Image\Procede Software" "C:\Program Files\Procede Software" /S /E /NP
> /LOG+:"U:\RoboCopy.log" /Z /MIR /R:10 /W:30
>
> This one I created to synch the My Documents folder.
> robocopy "C:\Documents and Settings\%username%\My Documents" "U:\" /S /E
> /NP /LOG+:"u:\RoboCopy.log" /Z /MIR /R:10 /W:30
>
> Any recommendation on the two software options for what I'm trying to
> accomplish?
> Any suggestions on the two RoboCopy examples?
>
> Any input would be appreciated
>
> Thanks
>
> Kelvin
>
> XP workstations
> MS 2003 Servers
> Domain environment
> Using Active Directory
I've never had problems with robocopy timing out. Are you running this over
a direct LAN connection, or over a remote connection over the internet. If
the latter, I would be a bit concerned with any synchronizing technique if
the users have virtually no limits to the volume of files they can store on
their desktops.
We do not support files placed on the local desktop. The policy is that all
files should be maintained in the home folder on the server. Editing
documents there over a remote connection can be hard on the nerves, so I
suspect that some users do as I do - copy it to the desktop, edit it, then
copy it back. I sometimes do this by using a briefcase folder on the
desktop, synching it only as required, and, ideally, when I am connected in
the office.
/Al
|