[WAC 1904] Share permissions added directly via PowerShell works, but do not appear in WAC

New Contributor

Dear all,


Yesterday I discover an issue with share permissions in WAC. When I create a new network share via PowerShell directly on the server and attach some permissions to users or groups, those permissions are not visible in WAC file browser - instead of them, there are only the default one. Of course WAC sees that folder is being shared, and share permissions works properly. 


How to add SMB Share access via PowerShell to make it visible in WAC? Or maybe everything is correct but it's a bug in WAC?







2 Replies

Hey @Ult1me 


From what I can tell after some quick testing, it looks like the ACL showing in WAC is not the SMBShare permissions of the folder but rather the NTFS permissions. However, the options in WAC is simplified (deny, read, read/write) and it doesn't appear that an entry will show unless the NTFS permissions match exactly up with the deny, read, read/write entry). 


For example, I added a group with List Folder Contents, Read, and Write NTFS permissions and could see the group in WAC as having Read permissions. If I add 'list folder contents' to the NTFS permissions on the server then the entry doesn't show in WAC. Add on 'full control' in NTFS again, then the entry makes an appears in WAC with Read/Write


Hope this makes some sense!




Hi @HidMov  


I was thinking about the same, especially after looking at sample scripts provided by WAC team, which are using mostly NTFS permissions. It was a little bit harder to test it on Server Core on my own, but your tests confirm my thoughts. Thank you!