search

raandree / NTFSSecurity

Managing permissions with PowerShell is only a bit easier than in VBS or the command line as there are no cmdlets for most day-to-day tasks like getting a permission report or adding permission to an item. PowerShell only offers Get-Acl and Set-Acl but everything in between getting and setting the ACL is missing. This module closes the gap.
MIT License
431 stars 61 forks source link

Add-NTFSAudit : Issue with parameter position #4

Open raandree opened 8 years ago

raandree commented 8 years ago

This issue was imported from CodePlex

LaurentDardenne wrote 2016-08-22 at 18:25 Hi,

the parameters 'Account' and 'AccessRights' use the same position value (2) :

        [Parameter(Mandatory = true, Position = 2, ValueFromPipelineByPropertyName = true)]
        [Alias("IdentityReference, ID")]
        public IdentityReference2[] Account
        {
            get { return account; }
            set { account = value; }
        }

        [Parameter(Mandatory = true, Position = 2, ValueFromPipelineByPropertyName = true)]
        [Alias("FileSystemRights")]
        public FileSystemRights2 AccessRights
        {
            get { return accessRights; }
            set { accessRights = value; }
        }
Sup3rlativ3 commented 4 years ago

Is this just as simple as changing the value from '2' to '3'?

raandree commented 4 years ago

Hi @Sup3rlativ3, thanks for your help here.

I am currently traveling in South America and won't be able to work until beginning of February.

Yes, is the bug still exists, the fix should be easy.