POWER CONTROLS

Remote Power Controls.

Regain control of frozen endpoints instantly. Execute graceful reboots, forced hardware shutdowns, and targeted session logoffs using a highly resilient WinRM pipeline with automated PsExec fallbacks.

SEE HOW IT WORKS
WinRM / RPC Dispatcher ● CONNECTED

[UHDC] REMOTE POWER CONTROLS: LAPTOP-US-4829

[i] Attempting connection to LAPTOP-US-4829 via WinRM...

> Dispatching command: rwinsta.exe console

[UHDC SUCCESS] Power action 'Logoff' dispatched successfully!

Reliability When It Matters Most

When a computer is completely frozen or a rogue application locks the screen, standard remote management tools often fail. This engine utilizes a dual-protocol approach to guarantee your commands reach the Service Control Manager.

Resilient Execution

Attempts to execute native power commands via WinRM first for maximum speed. If the machine is severely locked up and WMI is unresponsive, it automatically falls back to a Base64-encoded PsExec payload.

Session Decoupling

Features a "Force Logoff" option that utilizes legacy Terminal Services commands (rwinsta) to instantly drop the physical console session. This kicks disconnected users off shared kiosks without waiting for a full hardware reboot.

Safety Mechanisms

Standard reboots are deployed with a 60-second timer, giving active users time to save their work. The GUI also includes an "Abort Restart" function to instantly cancel pending reboots if executed by mistake.

INTERACTIVE TRAINING ENGINE
⭐ 150 XP

How Junior Techs Learn This Tool:

When Training Mode is enabled, the UHDC pauses execution to explain the exact command-line syntax used for the specific power action they selected, as well as the fallback logic.

try {
    Invoke-Command -ComputerName $Target -ScriptBlock { shutdown.exe /r /t 60 }
} catch {
    # Fallback if WMI is frozen or WinRM is blocked
    psexec.exe \\$Target -s powershell.exe -EncodedCommand $Base64
}

The In-Person Equivalent

Clicking the Start Menu and selecting 'Restart', holding down the physical power button on the laptop for 10 seconds, or opening Task Manager, going to the 'Users' tab, and clicking 'Disconnect'.

Technical Q&A

Q: Why do we need a PsExec fallback for power controls?
The native Restart-Computer cmdlet and standard WinRM sessions rely heavily on WMI (Windows Management Instrumentation). If a computer is severely frozen, the WMI service is often unresponsive, causing the command to fail. By automatically falling back to PsExec, we bypass WMI entirely and interact directly with the Service Control Manager to execute the native shutdown.exe binary, which is significantly more reliable on locked-up machines.
Q: What exactly is `rwinsta`?
rwinsta stands for "Reset Windows Station." It is a legacy Terminal Services command. By passing the argument console, we are telling the operating system to instantly drop the physical console session (the user sitting at the keyboard). It is much faster than a full reboot because it leaves the Windows kernel and background services running while simply resetting the user interface.
Q: If I accidentally click "Standard Restart" on the wrong PC, can I stop it?
Yes. Because the Standard Restart uses a 60-second timer (/t 60), you have a one-minute window to fix the mistake. Simply run the tool again against the same PC and select the "Abort Restart" option from the GUI. This sends a shutdown /a command, which instantly cancels the pending reboot.