Often times I will create simple files on end user computers with createfile or appendfile that they need access to.
When I use createfile or appendfile it gives full permission to SYSTEM and Administrators, but nothing else.
Right now I just call CACLS to modify the permissions on the files after I create them, but I feel like either I am doing something wrong, or there must be a better way that I’m not aware of.
I would think that is just should follow the parent folder file inheritance rules, but that does not seem to be the case.
Can someone shed some light on this topic for me? Thanks.
Both createfile and appendfile create a new file under __BESData\<site>. The permissions in that folder dictate permissions for Adminstrators and SYSTEM only.
If you then move the file to another directory on the drive, the file retains the original permissions (System, Adminstrators). If you copy the file to another location, it gets new ACLS based on the permissions of the folder in which the new copy is created. So just use __createfile or __appendfile as normal, but be sure to copy, rather than move, the file to a directory the users can access.
1 Like
* slaps head with palm *
Thanks for the information. That is a painfully simple answer!
1 Like