Timestamp Problem Using Synchronization Option

[mjthurgood]

I've set up a synchronization job using the \\?\UNC\<server>\<share> syntax for source and destination. When the synchronization job copies files from the source to the target, the timestamp on the target files is set to the date/time when the copy occurred, rather than the original date/time of the file. Then, during the next synchronization job, these same files are identified as being newer in the target, so they are then copied back to the source with the newer timestamps. I'm using Vice Versa Pro 2, with the Source and Target running Windows Server 2003 Standard. Is there a setting somewhere to have copied files retain the original timestamp?

[mjthurgood]

I just installed the trial version of ViceVersa Pro 2.5 and the problem does not occur in that version, so I guess an upgrade is in order.

[TGRMN Software]

thanks, yes, version 2.5 is better at setting the file timestamps properly on the target (for certain networks and NAS).
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com