tasklist and taskkill in Windows: Find and End Processes from CMD
Resolve a PID to a real process with tasklist, filter by service, session or memory, and end it cleanly with taskkill - including process trees and remote hosts.
Guide
Step-by-step guides: how a command or feature works and how to use it on real Windows, Active Directory, VMware and Linux systems.
How to find and log off RDP sessions in Windows with quser and qwinsta
Use quser, qwinsta and rwinsta to list RDP sessions on a Windows server, spot disconnected ones blocking new logons, and log them off from the command line.
setspn in Windows: manage Service Principal Names and fix Kerberos SPN conflicts
setspn reads, adds, and deletes Service Principal Names (SPNs) on Active Directory accounts. An SPN is the identifier Kerberos uses to match…
dsquery and dsget in Windows: command-line Active Directory queries
You need to find every disabled user account in the Sales OU, and you are logged on to a Server Core box…
PowerShell scripts in Windows Task Scheduler: why they fail and how to fix it
The script runs fine from your terminal. You create a scheduled task, it fires at the right time — and produces nothing.…
Windows Command Aliases: DOSKEY Macros in CMD and Aliases in PowerShell
If you come from Linux, you expect aliases to just work — type alias ll=’ls -la’, press Enter, done. Windows has the…
netsh command in Windows
netsh (Network Shell) is a command-line scripting utility built into Windows that lets you configure and inspect virtually every aspect of networking…
How to read and clear Windows Event Logs with PowerShell
Windows Event Logs accumulate fast. On a busy server, the Application and System logs can hold hundreds of thousands of entries within…
nmap for Windows: network scanning without installing Linux
Network scanning on Windows usually means installing something or switching to Linux. nmap breaks that assumption — it runs natively on Windows,…
wevtutil command in Windows: query and export Event Logs
When something goes wrong on a Windows machine — a service crash, a failed login, an unexpected reboot — the answer is…