In NTFS drives, the behavior used to be that, when a file was moved, it would retain the permissions of the original file, if the move was made to a folder on the same volume.
I know this by experience and it can be seen here: https://support.microsoft.com/en-us/kb/310316
But I was trying to show this behavior today to a colleague and it just didn't work. Every single time the file would simply have the permissions from the new folder associated to it.
I've tried in 3 different machines and it no longer works like that. When did it change? And no, the registry setting mentioned previously isn't set.
Any idea when this changed?
Just an example to make it more clear
Suppose I have these folders, in my C drive.
And I have four groups: - Interns - Employees - Managers - Staff (that has the previous 3 as members).
Now, let's consider the permissions (simplified).
- Does not inherit
- Explicitly allows Total Control to Admins
- Explicitly allows Modify to Managers
- Inherits from Shared
- Explicitly allows Modify to Employees
- Inherits from Shared
- Explicitly allows Read to Staff
Now, let's supposed I have a file in the Working folder, called Bullshit.doc.
Previously, if the file was moved (cut/pasted) from the Working to the Final folder, it would retain the original permissions, i.e., Managers and Staff could Modify and Interns would have no permissions.
Now, when I try moving the Bullshit.doc, when moved, will simply inherit the permissions from the Final folder, i.e., it simply forgives that Interns shouldn't have access.
My question is: this changed, didn't it? Or I am going crazy? I'm 99% sure that it worked just like described in the KB.
I know I had problems similar to this in the past, when upper level users moved files between folders (with different set of permissions) and then complained that the interns couldn't read the files. I had to explain more than once that cut/paste wouldn't work, that they need to copy/paste/delete. It was back on Windows 2003 for sure, but I could be at least 2008 R2.
[Edit 2] Now with pictures!!!
Ok, so I decided to try and replicate. With the actual files and not simple examples. Here it is...
Hum... not what I'd expect it. Even if it was just a file, from what I gathered in the KB above, it should keep the permissions. And that's how I remember it behaving.
But it seems it changed. And I can't find an official source of when it happened.
This makes makes me doubt my sanity.