Synchronize directories and permissions

[Lefteous]

Recently I had to synchronize two volumes. One of the disks had quite restricted permissions which didn't allow me two enter some directories for the current user.
After synchronizing TC showed no differences in the sync tool but back in the file windows I saw many directories haven't been synchronized.
If the problematic directories would not have been in the top level from where I started synchronizing I would have never noticed that many directories haven't been synchronized. This is very dangerous!

This is a real life file management scenario. Please reconsider improving support for "as admin" in synchronize directories. At least inform the user about directories which couldn't be traversed.

[ghisler(Author)]

In fact the sync tool cannot handle restricted directories at all. In such a case, your only option is to run TC with full admin rights for the time of the synchronization.

With the support of folder synchronization, you will at least see these inaccessinble folders as empty folders, and they will still be there as a difference after synchronization.

[Flint]

With the support of folder synchronization, you will at least see these inaccessinble folders as empty folders, and they will still be there as a difference after synchronization.

Even in this case it remains dangerous. Seeing couple of empty folders does not make oneself worry too much.
I agree to Lefteous, there should be some kind of warning message.

[m^2]

With the support of folder synchronization, you will at least see these inaccessinble folders as empty folders, and they will still be there as a difference after synchronization.

Even in this case it remains dangerous. Seeing couple of empty folders does not make oneself worry too much.
I agree to Lefteous, there should be some kind of warning message.

Yep.

[Lefteous]

With the support of folder synchronization, you will at least see these inaccessinble folders as empty folders, and they will still be there as a difference after synchronization.

Yes support for empty directories in synchronize directories could indeed help to solve the problem. Just seeing them as empty directories won't help though. Why? There is no indicator that a directory is inaccessible. I would just consider the directory as empty. So I think the first step would be to display some indicator that the directory cannot be opened.
I cannot make any concrete suggestions how this could be presented to the user as I don't know how synchronizing empty directories is implemented in TC 7.5.

[StatusQuo]

With the support of folder synchronization, you will at least see these inaccessinble folders as empty folders, and they will still be there as a difference after synchronization.

Sound OK to me, as long as one could notice, why these weren't synchronized.

Maybe displaying these dirs with a red background, inverted or similar (as a warning) could be an idea.

[wanderer]

IMHO, a one-time message should appear informing the user that not all files have been synchronized. This message should appear at the end of the sync process to avoid having to press "OK" in the middle of a 2 hours sync process. Of course one could argue "i don't want the sync process to run at all if some files cannot be synchronized"...