I didn't know that you were asking users to actually perform the move....one of the benefits of us being a fairly small and linear organisation is that stuff doesn't tend to get moved from drive to drive too often.
On 28 April 2010 21:04, Ben Scott <[email protected]> wrote: > On Wed, Apr 28, 2010 at 12:55 PM, James Rankin <[email protected]> > wrote: > > I don't know whether removing Creator Owner from the ACL actually updates > or > > changes the owner in any way. > > It doesn't change the owner, but that doesn't matter. "CREATOR > OWNER" is a magic ACE that turns into whatever the owner is/was set to > when the ACL is applied. Simply remove the "CREATOR OWNER" ACE and > avoid the problem entirely. > > Why are you using "CREATOR OWNER" in an ACL in the first place? I > think that's your problem. > > > For preserving (or not) permissions on file moves, I find robocopy is the > > way forward ... > > Two problems with that: (1) Requires permission to set the ACL. (2) > Asking your typical user to use ROBOCOPY to move files is ridiculous. > > -- Ben > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > -- "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into the machine wrong figures, will the right answers come out?' I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question." ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
