Main Topics
Browse All TopicsWhen moving a file from one share to another, the security rights of the file stay on the old share it's rights
Say we've got share_a, this share is for support_users (group), and for support_admins (group) both modify rights
next we've got share_b. this is just for support_admins
Now the support admin makes a file, on share_b, but decides it should be on share_a for all the support_users.
so it cuts the file from share_b and pastes it on share_a.
What happens is that the support users cannot access the file because it is still locked on the rights of share_b.
eventough rights are based on a per share level.
Anyone got any idea why this happens? and how to solve it
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I was under the impression that when you copied a file, or moved a file to another disk, it would inherit the permissions of the destination folder; and when you moved a file within a disk it kept it's original permissions.
So I guess the answer is copy the file, then delete the original (or use robo copy).
Yep, that is precisely what you said. ;)
(sorry, I got interrupted while typing my post - I actually started it before yours)
I'm not sure xcopy is useful in this situation, as the point is to NOT preserve NTFS security (the new copy needs to inherit permissions from it's folder), and to MOVE the file - not copy it.
Well is there a REAL solution to this problem, because what KCTS said, is exactly what i concluded, thats why i'm only talking about cutting.
The thing with robo copy xcopy etc. is the fact that 1. Its a copy, and they don't want to copy.
2. They are users, they barely know how their e-mail works. (and thats not a joke!).
On the PC's you wish to alter this behavior, add a DWORD value named "MoveSecurityAttributes" with a value of 0 to HKLM\SOFTWARE\Microsoft\Wi
http://support.microsoft.c
You can modify this behavior (with some exceptions).
Using the registry key I described above, with a Windows Server 2003 server and Windows XP SP2 client, I conducted a simple test. I accessed shared folders using UNC path names, and tested moving (by right-clicking and choosing "Cut") a test file both between \\Server\Share1\FolderA & \\Server\Share1\FolderB, as well as between \\Server\Share1 & \\Server\Share2, and in both cases my test file inherited permissions of the destination folder.
Business Accounts
Answer for Membership
by: masa77Posted on 2008-04-21 at 08:03:46ID: 21402598
With robocopy you can copy files with or without permissions, robo copy is found from windows 2003 server resource kit