Copying files/folders with NTFS permissions (Using TC 8.01)

[tmx1]

I am trying to copy files & folders from a UNC path to another server on the same domain with the NTFS permissions currently set on the source file server.

Can someone point me in the right direction as to what I need to do?

Currently when I copy the files/folders to the new target server, it only applies the target server permissions.

Is there some option I need to change in TC 8.01 in order for this to work?

Note:
Source Server = Windows Server 2003
Target Server = Windows Server 2012

Thanks.

[MVV]

Try to check corresponding checkbox in copy dialog (you need admin rights).

[tmx1]

DOH!!

I've been using this thing for years and that option was always in my face! I guess this is the first time I needed the function and never paid attention to the Copy box options.


Thanks!

[Phred]

I'll bet you're wondering how you can set that tickbox for every copy operation, as default. I am.
Running as a Standard User, with only occasional resort to an admin account, it's particularly relevant.

[ZoSTeR]

The missing option aside, why would you copy the permissions by default? This would screw up your NTFS permission inheritance all over the place.

[Phred]

Well, yes, Zoster, but only under certain circumstances.
I'm finally trying to make the transition from data-on-the-system-disk to having it on a separate one. So I'm creating a branch M:\Users with, below that:
..\Phred\Documents\
..\Phred\Downloads\
etc
...as well as:
..\SignificantOther\Documents\
..\SignificantOther\Downloads\
etc
..\LessSignificantMinors\Documents\
..\LessSignificantMinors\Downloads\
etc.
While I might lose inheritance, at least they'll have their restrictive permissions carried over from the source.

Just how I'll manage program data and Program Data, I don't quite know.
While I expect the translation of Outlook.pst from
C:\Users\Phred\AppData\Local\Microsoft\Outlook\
to
M:\Users\Phred\AppData\Local\Microsoft\Outlook\
will work, the subordinate data for Outlook and all other programs will still reside on the C:, system, drive. But that's not part of your question.. Hope answered.

[MVV]

Usually each folder C:\Users\SomeUser has full access permissions for SomeUser and for Administrators group.
So if you set similar permissions for M:\Users\SomeUser folder, all inner files/folders will simply inherit these permissions just like in C:\Users\SomeUser.

Only permissions that you've set for some files/folders explicitly must be copied explicitly (again, if you copy permissions for folder, all inner files will inherit them). So let me ask you a question: how often do you set permissions explicitly?

[Phred]

Usually each folder C:\Users\SomeUser has full access permissions for SomeUser and for Administrators group.
So if you set similar permissions for M:\Users\SomeUser folder, all inner files/folders will simply inherit these permissions just like in C:\Users\SomeUser.

Yes, MVV, I agree that's the way it should be, but I have had a terrible time of its working so simply with me. Frequently I have my peer-to-peer LAN contradicting the settings, usually because Everyone is particularly quite often inexact, and with folders and files being owned by SYSTEM at times and by KNOWN INSTALLER(?) at others, etc. I try to rely upon folder inheritance flowing down, but it doesn't always work. : (

Only permissions that you've set for some files/folders explicitly must be copied explicitly (again, if you copy permissions for folder, all inner files will inherit them). So let me ask you a question: how often do you set permissions explicitly?

I can see that a default 'on' setting might not be used often, but it's the type of thing that's a regular feature of our GUIs.
I may be a nervous person, cautious, perhaps, but I am a practitioner of gradualism. I take things slowly, and therefore, repetitively. I recommend the approach. I have copied a large number of folders in the last few days, with both FastCopy and TC, and I admit to liking FastCopy's ACL option setting, and its Listing function: I found a number of files that would have been a complete nuisance if they had been copied. So a step at a time, then another one.. then a slightly bigger one.. is a useful method, IMHO.

I've found a curious characteristic of TC: when I browsed folders with copied NTFS permissions or ACLs, behaviour was different upon inspecting the result. Pressing Enter on a non-permitted folder was rejected at the GUI, but when browsing with the drop-down 'breadcrumb'(?) path, entry was possible. No files were visible, but permission to enter had been given. I hope it's a trivial difference. I'll scan the forum.

So, like a good GUI application, a settable default to 'Copy NTFS Permissions' would be welcome.