Some context: I am augmenting a PowerShell script to create an AD user to execute a batch workflow and the required folders the workflow needs. The ID and network ID's of the support members (including myself) inherits all permissions from the groups that it is in, and the groups that those groups are in.
Write-Log "Setting Permissions on \\$Machine\Batch\Storage\$ASI" -LogPath $LogPath
$PathAcl = Get-Acl -path "\\$Machine\Batch\Storage\$ASI"
# Setup Inherited permissions
$PathAcl.SetAccessRuleProtection($True, $False)
$PathAcl.GetAccessRules($true, $true, [system.security.principal.ntaccount])
# Batch support permisions
$Rule = New-Object System.Security.AccessControl.FileSystemAccessRule($($DomainJobIsToRunIn + '\L_Batch' + "$ASI" + 'Support'), 'Modify,Synchronize', "ContainerInherit, ObjectInherit", "None", "Allow")
$PathAcl.AddAccessRule($Rule)
Write-Log -Message $($DomainJobIsToRunIn + '\Batch' + "$ASI" + 'Support complete.') -LogPath $LogPath
# Commit Changes
Set-Acl -Path "\\$Machine\Batch\Storage\$ASI" -AclObject $PathAcl
Write-Log "Permissions on \\$Machine\Batch\Storage\$ASI setup complete." -LogPath $LogPath
$Machine = Windows server name
$ASI = Application Service ID (in this case, "a$c")
$DomainJobIsToRunIn = AD Domain
After creating the folders and assigning permissions, my user ID, which is in the "support" global group that is in the "support" local group is unable to access the folder. If I open the folder properties and go to Security > Advanced > Continue (attempt the operation with admin permissions) I can see the following: Advanced Security Settings for a$c
If I manually add my ID to the folder with access through the GUI, I can open the folder just fine and the Security tab shows L_Batcha$cSupport as having modify access.
Does anyone have an idea as to what I am doing wrong? I've been searching for a few days now and can't find anything that is similar so far.
Apologies if my question is formatted wrong. This is my first time posting here.