Why do chmod and chgrp not work as expected?
Because the central file server is Windows 2003 Storage Server, the filesystem is NTFS, which has some features that create interoperability issues with other operating systems. The file server presents the shares with NFS Server software that uses Microsoft’s POSIX subsystem for Windows Server. Certain concessions have to be made when translating between the native filesystem and the POSIX subsystem. In particular, chmod and chgrp require a user/group with uid/gid. The POSIX subsystem must be able to map a username and uid (or group and gid) to an individual account (or group) in Active Directory. Although TSG has mapped many users/groups to AD equivalents, it is not possible to map all users/groups. If there is a particular user account or group that is not mapped, but reasonably needs to be, please open a Userhelp ticket with TSG to resolve the problem. Additionally, chmod/chgrp only can set user, group, and other permissions, whereas NTFS can have long Access Control Lists to descr