{"id":208402,"date":"2024-01-22T10:43:43","date_gmt":"2024-01-22T10:43:43","guid":{"rendered":"https:\/\/www.ninjaone.com\/script-hub\/comment-configurer-les-droits-d-acces-aux-dossiers-avec-powershell\/"},"modified":"2024-03-04T19:06:41","modified_gmt":"2024-03-04T19:06:41","slug":"comment-configurer-les-droits-d-acces-aux-dossiers-avec-powershell","status":"publish","type":"script_hub","link":"https:\/\/www.ninjaone.com\/fr\/script-hub\/comment-configurer-les-droits-d-acces-aux-dossiers-avec-powershell\/","title":{"rendered":"Comment configurer les droits d’acc\u00e8s aux dossiers avec PowerShell"},"content":{"rendered":"

Aujourd’hui, nous allons nous pencher sur un script qui simplifie le processus pour modifier et configurer les droits d’acc\u00e8s aux dossiers. <\/strong>S’assurer que les bonnes personnes ont un acc\u00e8s appropri\u00e9 \u00e0 des fichiers et dossiers sp\u00e9cifiques est primordial dans le domaine de l’informatique. La gestion des autorisations prot\u00e8ge efficacement les donn\u00e9es sensibles, contribue \u00e0 la conformit\u00e9 r\u00e9glementaire et am\u00e9liore l’efficacit\u00e9 op\u00e9rationnelle<\/a>. PowerShell est l’un des outils les plus utilis\u00e9s pour ce type de t\u00e2ches.<\/p>\n

Contexte<\/h2>\n

Dans un monde num\u00e9rique en constante \u00e9volution, les professionnels de l’informatique et les fournisseurs de services g\u00e9r\u00e9s (MSP) doivent constamment jongler avec de multiples autorisations d’utilisateurs pour divers fichiers et dossiers. Le script suivant est une aubaine dans de tels sc\u00e9narios. Il offre une grande flexibilit\u00e9, permettant d’attribuer ou de bloquer des autorisations pour plusieurs utilisateurs sur plusieurs chemins. Ainsi, que vous travailliez avec des fichiers ou bien des r\u00e9pertoires entiers, ce script fonctionne.<\/p>\n

Le script<\/h2>\n
#Requires -Version 5.1\r\n\r\n<#\r\n.SYNOPSIS\r\n    Modify User Permissions for files and folder.\r\n.DESCRIPTION\r\n    Modify User Permissions for files and folder. You can assign or block multiple permissions to multiple users, and multiple files and folders.\r\n.EXAMPLE\r\n     -User \"Test\" -Path \"C:Test\" -Permissions FullControl\r\n    Gives FullControl permissions to the user Test for just the folder C:Test\r\n.EXAMPLE\r\n     -User \"Test1\", \"Test2\" -Path \"C:Test\" -Permissions FullControl\r\n    Gives FullControl permissions to the user Test1 and Test2 for just the folder C:Test\r\n.EXAMPLE\r\n     -User \"Test1\", \"Test2\" -Path \"C:Test\", \"C:Temp\" -Permissions FullControl\r\n    Gives FullControl permissions to the user Test1 and Test2 for just the folders C:Test and C:Temp\r\n.EXAMPLE\r\n     -User \"Test\" -Path \"C:TestDocument.docx\" -Permissions FullControl\r\n    Gives FullControl permissions to the user Test for just the file C:TestDocument.docx\r\n.EXAMPLE\r\n     -User \"Test\" -Path \"C:TestDocument.docx\" -Permissions ReadData, Modify\r\n    Gives ReadData and Modify permissions to the user Test for just the file C:TestDocument.docx\r\n.EXAMPLE\r\n     -User \"Test\" -Path \"C:TestDocument.docx\" -Permissions FullControl -Block\r\n    Blocks FullControl permissions from the user Test for just the file C:TestDocument.docx\r\n.EXAMPLE\r\n     -User \"Test\" -Path \"C:Test\" -Permissions FullControl -Recursive\r\n    Gives FullControl permissions to the user Test for the folder C:Test and any folder or file under it will inherit FullControl\r\n.EXAMPLE\r\n    PS C:> .Modify-User-Permissions.ps1 -User \"Test\" -Path \"C:Test\" -Permissions FullControl -Recursive\r\n    Gives FullControl permissions to the user Test for the folder C:Test and any folder or file under it will inherit FullControl\r\n.INPUTS\r\n    Inputs (User,Path,Permissions)\r\n.OUTPUTS\r\n    FileSecurity\r\n.NOTES\r\n    Minimum OS Architecture Supported: Windows 10, Windows Server 2016\r\n    Release Notes:\r\n    Initial Release\r\nBy using this script, you indicate your acceptance of the following legal terms as well as our Terms of Use at https:\/\/www.ninjaone.com\/terms-of-use.\r\n    Ownership Rights: NinjaOne owns and will continue to own all right, title, and interest in and to the script (including the copyright). NinjaOne is giving you a limited license to use the script in accordance with these legal terms. \r\n    Use Limitation: You may only use the script for your legitimate personal or internal business purposes, and you may not share the script with another party. \r\n    Republication Prohibition: Under no circumstances are you permitted to re-publish the script in any script library or website belonging to or under the control of any other software provider. \r\n    Warranty Disclaimer: The script is provided \u201cas is\u201d and \u201cas available\u201d, without warranty of any kind. NinjaOne makes no promise or guarantee that the script will be free from defects or that it will meet your specific needs or expectations. \r\n    Assumption of Risk: Your use of the script is at your own risk. You acknowledge that there are certain inherent risks in using the script, and you understand and assume each of those risks. \r\n    Waiver and Release: You will not hold NinjaOne responsible for any adverse or unintended consequences resulting from your use of the script, and you waive any legal or equitable rights or remedies you may have against NinjaOne relating to your use of the script. \r\n    EULA: If you are a NinjaOne customer, your use of the script is subject to the End User License Agreement applicable to you (EULA).\r\n.COMPONENT\r\n    ManageUsers\r\n#>\r\n\r\n[CmdletBinding()]\r\nparam (\r\n    [Parameter(Mandatory = $true)]\r\n    [ValidateScript(\r\n        {\r\n            # Validate that the User(s) exist\r\n            if ($(Get-LocalUser -Name $_)) { $true } else { $false }\r\n        }\r\n    )]\r\n    [String[]]\r\n    # The user name of the user you want to apply Permissions to a Path(s)\r\n    $User,\r\n    [Parameter(Mandatory = $true)]\r\n    [ValidateScript({ Test-Path -Path $_ })]\r\n    [String[]]\r\n    # File path that you want to apply Permissions to\r\n    $Path,\r\n    [Parameter(Mandatory = $true)]\r\n    # Permission to set the path(s) for the user(s)\r\n    # This accepts the following:\r\n    #  ListDirectory, ReadData, WriteData, CreateFiles, CreateDirectories, AppendData, ReadExtendedAttributes,\r\n    #  WriteExtendedAttributes, Traverse, ExecuteFile, DeleteSubdirectoriesAndFiles, ReadAttributes,\r\n    #  WriteAttributes, Write, Delete, ReadPermissions, Read, ReadAndExecute, Modify, ChangePermissions,\r\n    #  TakeOwnership, Synchronize, FullControl\r\n    [System.Security.AccessControl.FileSystemRights[]]\r\n    $Permissions,\r\n    # Block the specified Permissions for the specified $User\r\n    [Switch]\r\n    $Block,\r\n    # Apply the Permissions down through a folder structure, i.e. inheritance\r\n    [Switch]\r\n    $Recursive\r\n)\r\n\r\nbegin {\r\n    function Test-IsElevated {\r\n        $id = [System.Security.Principal.WindowsIdentity]::GetCurrent()\r\n        $p = New-Object System.Security.Principal.WindowsPrincipal($id)\r\n        if ($p.IsInRole([System.Security.Principal.WindowsBuiltInRole]::Administrator))\r\n        { Write-Output $true }\r\n        else\r\n        { Write-Output $false }\r\n    }\r\n}\r\n\r\nprocess {\r\n    if (-not (Test-IsElevated)) {\r\n        Write-Error -Message \"Access Denied. Please run with Administrator privileges.\"\r\n        exit 1\r\n    }\r\n    $Acl = Get-Acl -Path $Path\r\n    if ($true -in $Acl.AreAccessRulesProtected) {\r\n        Write-Error \"ACL rules are protected for one of the specified paths.\"\r\n        exit 1\r\n    }\r\n    $script:HasError = $false\r\n    $Path | ForEach-Object {\r\n        $CurPath = Get-Item -Path $_\r\n        $User | ForEach-Object {\r\n            $NewAcl = Get-Acl -Path $CurPath\r\n            # Set properties\r\n            $identity = Get-LocalUser -Name $_\r\n            $fileSystemRights = $Permissions\r\n            $type = $(if ($Block) { [System.Security.AccessControl.AccessControlType]::Deny }else { [System.Security.AccessControl.AccessControlType]::Allow })\r\n            $fileSystemRights | ForEach-Object {\r\n                # Create new rule\r\n                Write-Host \"Creating $type $_ rule for user: $identity\"\r\n                # Check if Recursive was used and that the current path is a folder\r\n                if ($CurPath.PSIsContainer -and $Recursive) {\r\n                    $inheritanceFlags = 'ObjectInherit,ContainerInherit'\r\n                    $NewAcl.SetAccessRuleProtection($false, $true)\r\n                }\r\n                else {\r\n                    $inheritanceFlags = [System.Security.AccessControl.InheritanceFlags]::None\r\n                }\r\n                $propagationFlags = [System.Security.AccessControl.PropagationFlags]::None\r\n                $fileSystemAccessRuleArgumentList = $identity, $_, $inheritanceFlags, $propagationFlags, $type\r\n                $fileSystemAccessRule = New-Object -TypeName System.Security.AccessControl.FileSystemAccessRule -ArgumentList $fileSystemAccessRuleArgumentList\r\n\r\n                # Apply new rule\r\n                $NewAcl.SetAccessRule($fileSystemAccessRule)\r\n                try {\r\n                    Set-Acl -Path $CurPath -AclObject $NewAcl -Passthru\r\n                }\r\n                catch {\r\n                    Write-Error $_\r\n                    $script:HasError = $true\r\n                }\r\n            }\r\n        }\r\n    }\r\n    if ($script:HasError) {\r\n        exit 1\r\n    }\r\n}\r\n\r\nend {}<\/pre>\n
 <\/p>\n\n
Acc\u00e9dez \u00e0 plus de 700 scripts dans le Dojo NinjaOne<\/p>\n
Obtenez l’acc\u00e8s<\/a><\/p>\n<\/div>\n
Description d\u00e9taill\u00e9e<\/h2>\n
\u00c0 la base, le script fonctionne avec trois param\u00e8tres obligatoires : User<\/strong> (utilisateur), Path<\/strong> (chemin d’acc\u00e8s), et Permissions<\/strong> (autorisations).<\/p>\n