{"id":208537,"date":"2024-01-22T09:00:46","date_gmt":"2024-01-22T09:00:46","guid":{"rendered":"https:\/\/www.ninjaone.com\/script-hub\/aendern-eines-administratornamens-unter-windows-mit-powershell\/"},"modified":"2024-03-04T19:00:44","modified_gmt":"2024-03-04T19:00:44","slug":"aendern-eines-administratornamens-unter-windows-mit-powershell","status":"publish","type":"script_hub","link":"https:\/\/www.ninjaone.com\/de\/script-hub\/aendern-eines-administratornamens-unter-windows-mit-powershell\/","title":{"rendered":"\u00c4ndern eines Administratornamens unter Windows mit PowerShell"},"content":{"rendered":"

In der dynamischen Welt der IT ist die Aufrechterhaltung und Verwaltung der Systemsicherheit von entscheidender Bedeutung. Ein wichtiger Aspekt dabei ist, dass kritische Systemkonten, wie z. B. das Administratorkonto auf Windows-Rechnern, weniger vorhersehbar sind. Eine M\u00f6glichkeit, die Sicherheit dieses Kontos zu erh\u00f6hen, besteht darin, es umzubenennen. Dies verringert nicht nur die Angriffsfl\u00e4che f\u00fcr Brute-Force-Angriffe, sondern erschwert es auch b\u00f6swilligen Organisationen, Standardbenutzernamen zu erraten. Erfahren Sie mehr \u00fcber dieses PowerShell-Skript, mit dem Sie einen Administratornamen unter Windows \u00e4ndern<\/strong>k\u00f6nnen<\/p>\n

Hintergrund<\/h2>\n

IT-Fachleute und Managed Service Provider (MSPs<\/a> ) kennen seit Jahren die Schwachstellen, die mit der Beibehaltung von Standardnamen f\u00fcr wichtige Konten verbunden sind. Ein standardm\u00e4\u00dfiges „Administrator“-Konto, insbesondere auf Windows-Systemen, ist eine offene Einladung f\u00fcr Hacker. Gl\u00fccklicherweise erleichtert das oben gezeigte PowerShell-Skript die Umbenennung dieses Kontos und verbessert so die Sicherheit von Einzelpersonen und Unternehmenssystemen gleicherma\u00dfen.<\/p>\n

Das Skript<\/h2>\n
#Requires -Version 2.0\r\n\r\n<#\r\n.SYNOPSIS\r\n    Renames the Local Administrator Account.\r\n.DESCRIPTION\r\n    Renames the Local Administrator Account.\r\n.EXAMPLE\r\n     -NewName \"NewAdminName\"\r\n    Renames the local Administrator account to NewAdminName.\r\n.EXAMPLE\r\n     -NewName \"Administrator\" -CurrentName \"OldAdminName\"\r\n    Renames the local Administrator account back to its original name.\r\n.EXAMPLE\r\n    PS C:> .Rename-LocalAdministratorAccount.ps1 -NewName \"NewAdminName\"\r\n    Renames the local Administrator account to NewAdminName.\r\n.OUTPUTS\r\n    String[]\r\n.NOTES\r\n    Minimum OS Architecture Supported: Windows 7, Windows Server 2012\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    LocalBuiltInAccountManagement\r\n#>\r\n\r\n[CmdletBinding()]\r\nparam (\r\n    [Parameter(Mandatory = $true)]\r\n    [String]\r\n    $NewName,\r\n    [Parameter(Mandatory = $false)]\r\n    [String]\r\n    $CurrentName = \"Administrator\"\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    $Failed = $false\r\n    if ((Get-Command -Name \"Rename-LocalUser\").Count -gt 0) {\r\n        try {\r\n            Rename-LocalUser -Name \"$CurrentName\" -NewName \"$NewName\" -Confirm:$false\r\n        }\r\n        catch {\r\n            $Failed = $true\r\n        }\r\n        \r\n    }\r\n    else {\r\n        # Unable to find Rename-LocalUser, falling back to using WMIC.exe\r\n        WMIC.exe useraccount where name=\"$CurrentName\" rename \"$NewName\"\r\n        $ExitCode = $LASTEXITCODE\r\n        if ($ExitCode -ne 0) {\r\n            # Some kind of error occurred, likely account was already renamed.\r\n            $Failed = $true\r\n        }\r\n    }\r\n\r\n    if ($Failed) {\r\n        Write-Error \"Failed to Rename $CurrentName to $NewName\"\r\n        exit 1\r\n    }\r\n    else {\r\n        Write-Host \"Renamed $CurrentName to $NewName\"\r\n        exit 0\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