{"id":208539,"date":"2024-01-22T09:25:16","date_gmt":"2024-01-22T09:25:16","guid":{"rendered":"https:\/\/www.ninjaone.com\/script-hub\/einrichten-von-ordner-berechtigungen-verwendung-powershell\/"},"modified":"2024-03-04T19:06:55","modified_gmt":"2024-03-04T19:06:55","slug":"einrichten-von-ordner-berechtigungen-verwendung-powershell","status":"publish","type":"script_hub","link":"https:\/\/www.ninjaone.com\/de\/script-hub\/einrichten-von-ordner-berechtigungen-verwendung-powershell\/","title":{"rendered":"Festlegen von Ordnerberechtigungen mit PowerShell"},"content":{"rendered":"

Die Sicherstellung, dass die richtigen Personen den richtigen Zugriff auf bestimmte Dateien und Ordner haben, ist in der IT von gr\u00f6\u00dfter Bedeutung. Durch die Verwaltung von Berechtigungen werden sensible Daten wirksam gesch\u00fctzt, die Einhaltung von Vorschriften unterst\u00fctzt und die betriebliche Effizienz<\/a>gesteigert. Ein beliebtes Tool zur Bew\u00e4ltigung solcher Aufgaben ist PowerShell, und heute tauchen wir tief in ein Skript ein, das den Prozess der \u00c4nderung von Ordnerberechtigungen\u00a0<\/strong>rationalisiert.<\/p>\n

Hintergrund<\/h2>\n

In einer sich st\u00e4ndig weiterentwickelnden digitalen Landschaft jonglieren IT-Expert:innen und Managed Service Provider (MSPs) st\u00e4ndig mit mehreren Benutzerberechtigungen f\u00fcr verschiedene Dateien und Ordner. Das bereitgestellte Skript ist in solchen Szenarien ein Geschenk des Himmels. Es bietet Flexibilit\u00e4t und erm\u00f6glicht die Zuweisung oder Sperrung von Berechtigungen f\u00fcr mehrere Benutzer:innen \u00fcber mehrere Pfade. Egal, ob Sie mit einzelnen Dateien oder ganzen Verzeichnissen arbeiten, dieses Skript ist f\u00fcr Sie da.<\/p>\n

Das Skript<\/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
Zugriff auf \u00fcber 300 Skripte im NinjaOne Dojo<\/p>\n
Zugang erhalten<\/a><\/p>\n<\/div>\n
Detailansicht<\/h2>\n
Im Kern arbeitet das Skript mit drei obligatorischen Parametern: Benutzer:innen<\/strong>, Pfad<\/strong> und Berechtigungen<\/strong>.<\/p>\n