{"id":214966,"date":"2024-03-14T09:36:54","date_gmt":"2024-03-14T09:36:54","guid":{"rendered":"https:\/\/www.ninjaone.com\/?post_type=script_hub&p=214966"},"modified":"2024-03-14T09:36:54","modified_gmt":"2024-03-14T09:36:54","slug":"anleitung-zum-konfigurieren-lm-hash-storage-powershell","status":"publish","type":"script_hub","link":"https:\/\/www.ninjaonesandbox.dev\/de\/script-hub\/anleitung-zum-konfigurieren-lm-hash-storage-powershell\/","title":{"rendered":"Effizientes Konfigurieren des lokalen LM-Hash-Speichers mit PowerShell"},"content":{"rendered":"

DieKonfiguration des lokalen LM-Hash-Speichers<\/strong> spielt in Windows-basierten Systemen eine entscheidende Rolle. F\u00fcr IT-Expert:innen kann die Konfiguration dieses Speichers die Systemsicherheit erheblich beeinflussen. Das bereitgestellte PowerShell-Skript vereinfacht das Ein- und Ausschalten dieser Funktion auf elegante Weise. Wir wollen dessen Bedeutung und seine Funktionsweise n\u00e4her beleuchten.<\/p>\n

Hintergrund<\/h2>\n

Der LM-Hash oder LAN-Manager-Hash ist schon seit einiger Zeit im Umlauf und f\u00fcr die Sicherheitsl\u00fccken bekannt. Im Laufe der Zeit haben viele Sicherheitsexperten empfohlen, LM-Hashes zu deaktivieren, um die Systemsicherheit zu erh\u00f6hen. Manuelle Konfigurationen k\u00f6nnen jedoch m\u00fchsam sein, weshalb Tools und Skripte, wie die hier vorgestellten, f\u00fcr IT-Expert:innen und Managed Service Provider (MSPs<\/a>) von unsch\u00e4tzbarem Wert sind.<\/p>\n

Das Skript<\/h2>\n
#Requires -Version 5.1\r\n\r\n<#\r\n.SYNOPSIS\r\n    Disable or Enable Local LM Hash Storage\r\n.DESCRIPTION\r\n    Disable or Enable Local LM Hash Storage\r\n.EXAMPLE\r\n    -Enable\r\n    Enable Local LM Hash Storage\r\n.EXAMPLE\r\n    -Disable\r\n    Disable Local LM Hash Storage\r\n.EXAMPLE\r\n    PS C:> Disable-LMHash.ps1 -Disable\r\n    Disable Local LM Hash Storage\r\n.OUTPUTS\r\n    None\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.ninjaonesandbox.dev\/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    ProtocolSecurity\r\n#>\r\n\r\n[CmdletBinding(DefaultParameterSetName = \"Disable\")]\r\nparam (\r\n    [Parameter(Mandatory, ParameterSetName = \"Disable\")]\r\n    [switch]\r\n    $Disable,\r\n    [Parameter(Mandatory, ParameterSetName = \"Enable\")]\r\n    [switch]\r\n    $Enable\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    function Set-ItemProp {\r\n        param (\r\n            $Path,\r\n            $Name,\r\n            $Value,\r\n            [ValidateSet(\"DWord\", \"QWord\", \"String\", \"ExpandedString\", \"Binary\", \"MultiString\", \"Unknown\")]\r\n            $PropertyType = \"DWord\"\r\n        )\r\n        New-Item -Path $Path -Force -ErrorAction SilentlyContinue | Out-Null\r\n        if ((Get-ItemProperty -Path $Path -Name $Name -ErrorAction SilentlyContinue)) {\r\n            Set-ItemProperty -Path $Path -Name $Name -Value $Value -Force -Confirm:$false | Out-Null\r\n        }\r\n        else {\r\n            New-ItemProperty -Path $Path -Name $Name -Value $Value -PropertyType $PropertyType -Force -Confirm:$false | Out-Null\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    $Path = \"HKLM:SYSTEMCurrentControlSetControlLsa\"\r\n    $Name = \"NoLMHash\"\r\n    $Value = if ($Enable) { 1 }elseif ($Disable) { 0 }else { throw \"No Param used.\" }\r\n    # Sets NoLMHash to 1\r\n    try {\r\n        Set-ItemProp -Path $Path -Name $Name -Value $Value\r\n    }\r\n    catch {\r\n        Write-Error $_\r\n        exit 1\r\n    }\r\n    Write-Host \"Set $Path$Name to $Value\"\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
Das Skript beginnt mit dem Festlegen der Anforderungen f\u00fcr PowerShell Version 5.1. Hier ist eine schrittweise Aufschl\u00fcsselung seiner Funktion:<\/p>\n