AD integrated DNS is a great way to get name resolution going in a Windows-heavy network. Changes to DNS zone data are replicated across the environment using robust AD replication mechanisms, providing a globaly consistent data pool with optimal bandwidth […]
In February 2026, Microsoft opened the public preview for DNS over HTTPS in Windows Server 2025. Let’s see if the rewards to be reaped from this are worth the hassle. If you’re the TL;DR type of person, jump right here. […]
I have been very vocal in advocating against using VM snapshots for literally decades. In production, that is. In development, technical presales, or education, on the other hand, they can be a life-saving feature. If you are in a field […]
Update 2025-08-17: The August 2025 CU (KB5063880) fixes the problem describes in this post. Thanks to the AD engineering team at Microsoft for fixing this quickly! TL;DR: If you have an account lockout policy in place and your PDC Emulator […]
Last year I published an interesting finding about SSH remoting in Windows Server which, while not being sensational, did stir up several quite productive discussions. Back then, Server 2025 and its one-click activation of the SSH daemon was still in […]
While preparing my talk for this year’s PSConfEU, I made a discovery that, while not being a major security disaster or anything like that, still surprised me a bit. Started as a skunkworks type side project at Microsoft, SSH wormed […]
(I heard that Google Translator does a decent job on this article, but if you’re looking for the same explanation in English, head over here.) Es ist wirklich viel darüber geschrieben worden, wie man auf Domain Controllern eines Active Directory-Forests […]
Wenn man auf einem nicht-englischen System Shell-Befehle („DOS-Befehle“) aus der PowerShell heraus aufruft, die in ihrer Ausgabe Umlaute beinhalten, so kann es manchmal passieren, dass die Umlaute nicht korrekt dargestellt werden. Dies ist besonders oft in der PowerShell ISE der […]
Manchmal muss ein Skript halt mit erhöhten Rechten laufen. Das erreicht man in der Regel entweder damit, dass man den Aufrufenden mit
|
1 |
#Requires -RunAsAdministrator |
vor den Kopf stößt, oder man macht das Skript „Self-Elevating“:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 |
[CmdletBinding()] Param( [Parameter(Mandatory=$false)] [switch]$RunElevated ) function Test-Admin { $currentUser = New-Object Security.Principal.WindowsPrincipal $([Security.Principal.WindowsIdentity]::GetCurrent()) $currentUser.IsInRole([Security.Principal.WindowsBuiltinRole]::Administrator) } if ((Test-Admin) -eq $false) { if ($RunElevated) { Write-Warning 'We tried to elevate and failed' } else { try { Start-Process powershell.exe -Verb RunAs -ArgumentList ('-noprofile -nologo -noexit -file "{0}" -RunElevated' -f ($myinvocation.MyCommand.Definition)) -EA Stop } catch { Write-Warning ('Error trying to self-elevate: {0}' -f $_.Exception.Message) } exit } } Write-Host "Hello elevated world!" # Code that needs elevation |
Doch was ist, wenn das Skript […]
Im Teil 1 haben wir herausgefunden, wie man mit P/Invoke und ein wenig C# die aktuell gültige Überwachungsrichtlinie sprachunabhängig (und, nebenbei bemerkt, ohne unnützes Daten-Beiwerk) ermitteln kann. Im Teil 2 nutzten wir PowerShell Remoting, um das ganze auf einem entfernten […]
Copyright © 2026 | WordPress Theme von MH Themes
