I find out the answers by checking internally. 1. AD support will be added in 2021'Q4.2. When creating a directory, its permission isn't specified in code API, it just follows default.So I find a way to set ACL inherit flags in the parent directory in Isilon, to force all the new created sub-directories have correct permissions, then problem solved. [IMAGE] [IMAGE] [IMAGE] [IMAGE]
1. When creating SMB share, the folder will be created by root via vRO directly, however the filesystem permission is 755, ACL can only allow root to full control, it will cause other user can’t write files in that SMB share. [IMAGE] [IMAGE] [IMAGE] 2. When creating SMB share, choosing members, only local user/group can be selected, but customer usually uses AD, they need to be able to select AD user/group. [IMAGE] (can't select AD user here) 3. When creating NFS export from vRA through vRO, the folder will be created by root via vRA through vRO directly, however the filesystem permission becomes 700, it’ll cause permission problem for other user in that NFS export. [IMAGE] [IMAGE]  
Isilon/PowerScale vRO bugs?