{"id":385089,"date":"2024-11-20T14:50:53","date_gmt":"2024-11-20T14:50:53","guid":{"rendered":"https:\/\/www.ninjaone.com\/?post_type=script_hub&p=385089"},"modified":"2024-11-20T14:50:53","modified_gmt":"2024-11-20T14:50:53","slug":"existenz-von-dateien-ueberpruefen","status":"publish","type":"script_hub","link":"https:\/\/www.ninjaone.com\/de\/script-hub\/existenz-von-dateien-ueberpruefen\/","title":{"rendered":"Wie man die Existenz von Dateien oder Ordnern unter Windows mit einem PowerShell-Skript \u00fcberpr\u00fcft"},"content":{"rendered":"

In der modernen IT-Welt kann die Verwaltung und Pflege von Dateisystemen auf zahlreichen Servern und Workstations eine Herausforderung darstellen. IT-Experten und Managed Service Provider (MSPs)<\/a> m\u00fcssen h\u00e4ufig bestimmte Dateien und Verzeichnisse \u00fcberwachen<\/strong>, um die Compliance, Sicherheit und betriebliche Effizienz zu gew\u00e4hrleisten.<\/p>\n

Eine zuverl\u00e4ssige Methode zur Bew\u00e4ltigung dieser Aufgabe ist die Verwendung von PowerShell-Skripten<\/a>, die Automatisierung und detaillierte Kontrolle \u00fcber Windows-Umgebungen bietet. Das mitgelieferte PowerShell-Skript wurde entwickelt, um Benutzer:innen zu benachrichtigen, wenn eine bestimmte Datei oder ein bestimmter Ordner innerhalb eines bestimmten Verzeichnisses oder Unterverzeichnisses gefunden wird, was es zu einem wertvollen Tool f\u00fcr IT-Experten macht.<\/p>\n

Kontext<\/h2>\n

Die \u00dcberwachung des Vorhandenseins und des Speicherorts von Dateien ist aus mehreren Gr\u00fcnden wichtig. Dieser Prozess hilft bei der Aufrechterhaltung der Sicherheit, indem er sicherstellt, dass keine unautorisierten Dateien vorhanden sind, unterst\u00fctzt die Compliance, indem es \u00fcberpr\u00fcft, ob die erforderlichen Dateien zur Verf\u00fcgung stehen, und hilft bei der betrieblichen Effizienz durch die Automatisierung von Routinepr\u00fcfungen. Dieses Skript ist besonders n\u00fctzlich f\u00fcr IT-Experten, die gro\u00dfe Netzwerke oder mehrere Kundenumgebungen verwalten m\u00fcssen. Durch die Automatisierung des Such- und Warnprozesses wird Zeit gespart und das Risiko menschlichen Versagens verringert.<\/p>\n

Das Skript zur \u00dcberpr\u00fcfung der Existenz von Dateien oder Ordnern unter Windows<\/h2>\n
#Requires -Version 5.1\r\n\r\n<#\r\n.SYNOPSIS\r\n    Alert if a specified file or folder is found in a directory or subdirectory you specify.\r\n.DESCRIPTION\r\n    Alert if a specified file or folder is found in a directory or subdirectory you specify.\r\n\r\n.EXAMPLE\r\n    -SearchPath \"C:\" -FileOrFolder \"autounattend\"\r\n\r\n    WARNING: Backslash missing from the search path. Changing it to C:\\.\r\n    [Alert] File Found.\r\n    C:\\Users\\Administrator\\Desktop\\ExampleFolder\\Test Folder 1\\autounattend.xml\r\n    C:\\Users\\Administrator\\Desktop\\ExampleFolder\\Test Folder 2\\autounattend.xml\r\n    C:\\Users\\Administrator\\Desktop\\ExampleFolder\\TestFolder1\\Test Folder 1\\autounattend.xml\r\n    C:\\Users\\Administrator\\Desktop\\ExampleFolder\\TestFolder1\\Test Folder 2\\autounattend.xml\r\n    C:\\Users\\Administrator\\Desktop\\ExampleFolder\\TestFolder2\\Test Folder 1\\TestFolder1\\autounattend.xml\r\n    Attempting to set Custom Field 'multiline'.\r\n    Successfully set Custom Field 'multiline'!\r\n\r\nPARAMETER: -SeachPath \"C:\\ReplaceMeWithAvalidPath\"\r\n    Enter the starting directories for the search, separated by commas. This will include all subdirectories as well.\r\n\r\nPARAMETER: -FileOrFolder \"ReplaceMeWithNameToSearchFor\"\r\n    Specify the full or partial name of a file or folder to find. E.g., 'config' or '.exe'.\r\n\r\nPARAMETER: -SearchType \"Files and Folders\"\r\n    Limit the search to either files, folders, or both.\r\n\r\nPARAMETER: -Timeout \"30\"\r\n    Maximum search time in minutes, halts search if exceeded.\r\n\r\nPARAMETER: -CustomField \"ReplaceMeWithNameOfMultilineCustomField\"\r\n    Optional multiline field to record search results. Leave blank if unused.\r\n\r\n.NOTES\r\n    Minimum OS Architecture Supported: Windows 10, Windows Server 2016\r\n    Release Notes: 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#>\r\n\r\n[CmdletBinding()]\r\nparam (\r\n    [Parameter()]\r\n    [String]$SearchPath = \"C:\\Windows,C:\\Program Files\",\r\n    [Parameter()]\r\n    [String]$FileOrFolder,\r\n    [Parameter()]\r\n    [String]$SearchType = \"Files and Folders\",\r\n    [Parameter()]\r\n    [Int]$Timeout = 30,\r\n    [Parameter()]\r\n    [String]$CustomField\r\n)\r\n\r\nbegin {\r\n    # Set parameters using dynamic script variables.\r\n    if ($env:searchPath -and $env:searchPath -notlike \"null\") { $SearchPath = $env:searchPath }\r\n    if ($env:fileNameOrFolderNameToSearchFor -and $env:fileNameOrFolderNameToSearchFor -notlike \"null\") { $FileOrFolder = $env:fileNameOrFolderNameToSearchFor }\r\n    if ($env:searchType -and $env:searchType -notlike \"null\") { $SearchType = $env:searchType }\r\n    if ($env:timeoutInMinutes -and $env:timeoutInMinutes -notlike \"null\") { $Timeout = $env:timeoutInMinutes }\r\n    if ($env:customFieldName -and $env:customFieldName -notlike \"null\") { $CustomField = $env:customFieldName }\r\n\r\n    # Error out if no search path was given.\r\n    if (-not $SearchPath) {\r\n        Write-Host \"[Error] No search path given!\"\r\n        exit 1\r\n    }\r\n\r\n    # If given a comma-separated list, split the paths.\r\n    $PathsToSearch = New-Object System.Collections.Generic.List[String]\r\n    if ($SearchPath -match \",\") {\r\n        $SearchPath -split \",\" | ForEach-Object { $PathsToSearch.Add($_.Trim()) }\r\n    }\r\n    else {\r\n        $PathsToSearch.Add($SearchPath)\r\n    }\r\n\r\n    # Initialize a generic list for paths to remove or replace.\r\n    $ReplacementPaths = New-Object System.Collections.Generic.List[Object]\r\n    $PathsToRemove = New-Object System.Collections.Generic.List[String]\r\n\r\n    # If given a drive without the backslash add it in.\r\n    $PathsToSearch | ForEach-Object {\r\n        if ($_ -notmatch '^[A-Z]:\\\\$' -and $_ -match '^[A-Z]:$') {\r\n            $NewPath = \"$_\\\"\r\n            $ReplacementPaths.Add(\r\n                [PSCustomObject]@{\r\n                    Index   = $PathsToSearch.IndexOf(\"$_\")\r\n                    NewPath = $NewPath\r\n                }\r\n            )\r\n                \r\n            Write-Warning \"Backslash missing from the search path. Changing it to $NewPath.\"\r\n        }\r\n    }\r\n\r\n    # Apply replacements.\r\n    $ReplacementPaths | ForEach-Object {\r\n        $PathsToSearch[$_.index] = $_.NewPath \r\n    }\r\n\r\n    # Check if the search path is valid.\r\n    $PathsToSearch | ForEach-Object {\r\n        if (-not (Test-Path $_)) {\r\n            Write-Host -Object \"[Error] $_ does not exist!\"\r\n            $PathsToRemove.Add($_)\r\n            $ExitCode = 1\r\n        }\r\n    }\r\n\r\n    # Remove Paths that do not exist.\r\n    $PathsToRemove | ForEach-Object {\r\n        $PathsToSearch.Remove($_) | Out-Null\r\n    }\r\n\r\n    # Error out if no valid paths to search.\r\n    if ($($PathsToSearch).Count -eq 0) {\r\n        Write-Host \"[Error] No valid paths to search!\"\r\n        exit 1\r\n    }\r\n\r\n    # If we're not given a file or folder error out.\r\n    if (-not $FileOrFolder) {\r\n        Write-Host -Object \"[Error] No file or folder given to search for!\"\r\n        exit 1\r\n    }\r\n\r\n    # Timeout must be within a given range in minutes.\r\n    if ($Timeout -lt 1 -or $Timeout -gt 120) {\r\n        Write-Host -Object \"[Error] Timeout is greater than 120 minutes or less than 1 minute.\"\r\n        exit 1\r\n    }\r\n\r\n    # Scope the search to either files only or folders only.\r\n    $ValidSearchTypes = \"Files and Folders\", \"Files Only\", \"Folders Only\"\r\n    if ($ValidSearchTypes -notcontains $SearchType) {\r\n        Write-Host -Object \"[Error] Invalid search type.\"\r\n        exit 1\r\n    }\r\n\r\n    # Test for local administrator rights.\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        $p.IsInRole([System.Security.Principal.WindowsBuiltInRole]::Administrator)\r\n    }\r\n\r\n    # Handy function to set a custom field.\r\n    function Set-NinjaProperty {\r\n        [CmdletBinding()]\r\n        Param(\r\n            [Parameter(Mandatory = $True)]\r\n            [String]$Name,\r\n            [Parameter()]\r\n            [String]$Type,\r\n            [Parameter(Mandatory = $True, ValueFromPipeline = $True)]\r\n            $Value,\r\n            [Parameter()]\r\n            [String]$DocumentName\r\n        )\r\n    \r\n        $Characters = $Value | Measure-Object -Character | Select-Object -ExpandProperty Characters\r\n        if ($Characters -ge 10000) {\r\n            throw [System.ArgumentOutOfRangeException]::New(\"Character limit exceeded, value is greater than 10,000 characters.\")\r\n        }\r\n        \r\n        # If we're requested to set the field value for a Ninja document we'll specify it here.\r\n        $DocumentationParams = @{}\r\n        if ($DocumentName) { $DocumentationParams[\"DocumentName\"] = $DocumentName }\r\n        \r\n        # This is a list of valid fields that can be set. If no type is given, it will be assumed that the input doesn't need to be changed.\r\n        $ValidFields = \"Attachment\", \"Checkbox\", \"Date\", \"Date or Date Time\", \"Decimal\", \"Dropdown\", \"Email\", \"Integer\", \"IP Address\", \"MultiLine\", \"MultiSelect\", \"Phone\", \"Secure\", \"Text\", \"Time\", \"URL\", \"WYSIWYG\"\r\n        if ($Type -and $ValidFields -notcontains $Type) { Write-Warning \"$Type is an invalid type! Please check here for valid types. https:\/\/ninjarmm.zendesk.com\/hc\/en-us\/articles\/16973443979789-Command-Line-Interface-CLI-Supported-Fields-and-Functionality\" }\r\n        \r\n        # The field below requires additional information to be set\r\n        $NeedsOptions = \"Dropdown\"\r\n        if ($DocumentName) {\r\n            if ($NeedsOptions -contains $Type) {\r\n                # We'll redirect the error output to the success stream to make it easier to error out if nothing was found or something else went wrong.\r\n                $NinjaPropertyOptions = Ninja-Property-Docs-Options -AttributeName $Name @DocumentationParams 2>&1\r\n            }\r\n        }\r\n        else {\r\n            if ($NeedsOptions -contains $Type) {\r\n                $NinjaPropertyOptions = Ninja-Property-Options -Name $Name 2>&1\r\n            }\r\n        }\r\n        \r\n        # If an error is received it will have an exception property, the function will exit with that error information.\r\n        if ($NinjaPropertyOptions.Exception) { throw $NinjaPropertyOptions }\r\n        \r\n        # The below type's require values not typically given in order to be set. The below code will convert whatever we're given into a format ninjarmm-cli supports.\r\n        switch ($Type) {\r\n            \"Checkbox\" {\r\n                # While it's highly likely we were given a value like \"True\" or a boolean datatype it's better to be safe than sorry.\r\n                $NinjaValue = [System.Convert]::ToBoolean($Value)\r\n            }\r\n            \"Date or Date Time\" {\r\n                # Ninjarmm-cli expects the  Date-Time to be in Unix Epoch time so we'll convert it here.\r\n                $Date = (Get-Date $Value).ToUniversalTime()\r\n                $TimeSpan = New-TimeSpan (Get-Date \"1970-01-01 00:00:00\") $Date\r\n                $NinjaValue = $TimeSpan.TotalSeconds\r\n            }\r\n            \"Dropdown\" {\r\n                # Ninjarmm-cli is expecting the guid of the option we're trying to select. So we'll match up the value we were given with a guid.\r\n                $Options = $NinjaPropertyOptions -replace '=', ',' | ConvertFrom-Csv -Header \"GUID\", \"Name\"\r\n                $Selection = $Options | Where-Object { $_.Name -eq $Value } | Select-Object -ExpandProperty GUID\r\n        \r\n                if (-not $Selection) {\r\n                    throw [System.ArgumentOutOfRangeException]::New(\"Value is not present in dropdown\")\r\n                }\r\n        \r\n                $NinjaValue = $Selection\r\n            }\r\n            default {\r\n                # All the other types shouldn't require additional work on the input.\r\n                $NinjaValue = $Value\r\n            }\r\n        }\r\n        \r\n        # We'll need to set the field differently depending on if its a field in a Ninja Document or not.\r\n        if ($DocumentName) {\r\n            $CustomField = Ninja-Property-Docs-Set -AttributeName $Name -AttributeValue $NinjaValue @DocumentationParams 2>&1\r\n        }\r\n        else {\r\n            $CustomField = Ninja-Property-Set -Name $Name -Value $NinjaValue 2>&1\r\n        }\r\n        \r\n        if ($CustomField.Exception) {\r\n            throw $CustomField\r\n        }\r\n    }\r\n\r\n    $ExitCode = 0\r\n}\r\nprocess {\r\n    # Error out if local administrator rights are not present.\r\n    if (-not (Test-IsElevated)) {\r\n        Write-Host \"[Error] Access Denied. Please run with Administrator privileges.\"\r\n        exit 1\r\n    }\r\n\r\n    # Initialize generic lists.\r\n    $SearchJobs = New-Object System.Collections.Generic.List[object]\r\n    $CustomFieldValue = New-Object System.Collections.Generic.List[string]\r\n\r\n    # For each given path to search, create a PowerShell job with the provided parameters.\r\n    $PathsToSearch | ForEach-Object {\r\n        $SearchJobs.Add(\r\n            (\r\n                Start-Job -ScriptBlock {\r\n                    param($SearchPath, $FileOrFolder, $SearchType)\r\n                    # We're going to wildcard search either files or folders depending on the parameters given.\r\n                    switch ($SearchType) {\r\n                        \"Files and Folders\" {\r\n                            Get-ChildItem -Path $SearchPath -Filter \"*$FileOrFolder*\" -Recurse | Select-Object -Property FullName, Attributes | ConvertTo-Csv\r\n                        }\r\n                        \"Folders Only\" {\r\n                            Get-ChildItem -Path $SearchPath -Filter \"*$FileOrFolder*\" -Recurse -Directory | Select-Object -Property FullName, Attributes | ConvertTo-Csv\r\n                        }\r\n                        \"Files Only\" { \r\n                            Get-ChildItem -Path $SearchPath -Filter \"*$FileOrFolder*\" -Recurse -File | Select-Object FullName, Attributes | ConvertTo-Csv\r\n                        }\r\n                    }\r\n                } -ArgumentList $_, $FileOrFolder, $SearchType\r\n            )\r\n        )\r\n    }\r\n\r\n    # Convert timeout to seconds as Wait-Job requires seconds.\r\n    $TimeoutInSeconds = $Timeout * 60\r\n    $StartTime = Get-Date\r\n\r\n    # Wait for all jobs to complete or timeout.\r\n    foreach ($SearchJob in $SearchJobs) {\r\n        # Calculate the remaining time.\r\n        $TimeElapsed = (Get-Date) - $StartTime\r\n        $RemainingTime = $TimeoutInSeconds - $TimeElapsed.TotalSeconds\r\n    \r\n        # If there is no remaining time, break the loop.\r\n        if ($RemainingTime -le 0) {\r\n            break\r\n        }\r\n    \r\n        # Wait for the current job with the remaining time as the timeout.\r\n        $SearchJob | Wait-Job -Timeout $RemainingTime | Out-Null\r\n    }\r\n\r\n    # Output a warning if the job fails to complete.\r\n    $IncompleteJobs = $SearchJobs | Get-Job | Where-Object { $_.State -eq \"Running\" }\r\n    if ($IncompleteJobs) {\r\n        Write-Host \"[Error] The timeout period of $Timeout minutes has been reached, but not all files or directories have been searched!\"\r\n        $CustomFieldValue.Add(\"[Error] The timeout period of $Timeout minutes has been reached, but not all files or directories have been searched!\")\r\n        $ExitCode = 1\r\n    }\r\n\r\n    # Our PowerShell Job outputs in CSV format; we'll convert it here.\r\n    $MatchingItems = $SearchJobs | ForEach-Object {\r\n        $_ | Get-Job | Receive-Job -ErrorAction SilentlyContinue -ErrorVariable JobErrors | ConvertFrom-Csv\r\n    }\r\n\r\n    # Identify whether or not we have a match for a file or folder here.\r\n    $FileMatch = $MatchingItems | Where-Object { $_.Attributes -ne \"Directory\" }\r\n    $FolderMatch = $MatchingItems | Where-Object { $_.Attributes -eq \"Directory\" }\r\n\r\n    # If we have a match for a file we'll output that here.\r\n    if ($FileMatch) { \r\n        Write-Host -Object \"[Alert] File Found.\"\r\n        $CustomFieldValue.Add(\"[Alert] File Found.\")\r\n    }\r\n\r\n    # If we have a match for a folder we'll output that here.\r\n    if ($FolderMatch) { \r\n        Write-Host -Object \"[Alert] Folder Found.\" \r\n        $CustomFieldValue.Add(\"[Alert] Folder Found.\")\r\n    }\r\n\r\n    # If we have no matches we'll output that here.\r\n    if (-not $FileMatch -and -not $FolderMatch) {\r\n        Write-Host -Object \"Unable to find $FileOrFolder.\"\r\n        $CustomFieldValue.Add(\"Unable to find $FileOrFolder.\")\r\n    }\r\n\r\n    # For each matching file we'll output their full path.\r\n    $MatchingItems | ForEach-Object { \r\n        Write-Host \"$($_.FullName)\"\r\n        $CustomFieldValue.Add(\"$($_.FullName)\") \r\n    }\r\n\r\n    # Output any failures or errors received.\r\n    $FailedJobs = $SearchJobs | Get-Job | Where-Object { $_.State -ne \"Completed\" -and $_.State -ne \"Running\" }\r\n    if ($FailedJobs -or $JobErrors) {\r\n        Write-Host \"\"\r\n        Write-Host \"[Error] Failed to search certain files or directories due to an error.\"\r\n\r\n        $CustomFieldValue.Add(\"\")\r\n        $CustomFieldValue.Add(\"[Error] Failed to search certain files or directories due to an error.\")\r\n        if ($JobErrors) {\r\n            Write-Host \"\"\r\n            $CustomFieldValue.Add(\"\")\r\n\r\n            $JobErrors | ForEach-Object { \r\n                Write-Host \"[Error] $($_.Exception.Message)\" \r\n                $CustomFieldValue.Add(\"[Error] $($_.Exception.Message)\")\r\n            }\r\n        }\r\n        $ExitCode = 1\r\n    }\r\n\r\n    $SearchJobs | Get-Job | Remove-Job -Force\r\n\r\n    # Attempt to set the custom field using the Set-NinjaProperty function, if provided.\r\n    if ($CustomField) {\r\n        try {\r\n            Write-Host \"Attempting to set Custom Field '$CustomField'.\"\r\n            Set-NinjaProperty -Name $CustomField -Value ($CustomFieldValue | Out-String)\r\n            Write-Host \"Successfully set Custom Field '$CustomField'!\"\r\n        }\r\n        catch {\r\n            if (-not $_.Exception.Message) {\r\n                Write-Host \"[Error] $($_.Message)\"\r\n            }\r\n            else {\r\n                Write-Host \"[Error] $($_.Exception.Message)\"\r\n            }\r\n            $ExitCode = 1\r\n        }\r\n    }\r\n\r\n    exit $ExitCode\r\n}\r\nend {\r\n    \r\n    \r\n    \r\n}<\/pre>\n
 <\/p>\n\n
Greifen Sie auf \u00fcber 300 Skripte im NinjaOne Dojo zu.<\/p>\n
Zugang erhalten<\/a><\/p>\n<\/div>\n
Detailansicht<\/h2>\n
Das Skript arbeitet in mehreren Stufen, die alle zur Gesamtfunktionalit\u00e4t beitragen. Hier ist eine schrittweise Aufschl\u00fcsselung:<\/p>\n
1. Initialisierung der Parameter<\/strong>: Das Skript beginnt mit der Definition mehrerer Parameter:<\/p>\n