>

Enable PowerShell Remoting

Configure WinRM so a machine can be managed remotely with PowerShell.

WindowsnetworksystemadminpowershellLow risk
Run Enable-PSRemoting -Force in an elevated PowerShell session.

01Command

Command
$ Enable-PSRemoting -Force

02What it does

The cmdlet starts the WinRM service, creates the listener and firewall rule and registers the endpoints needed for Invoke-Command. Doing this in bulk across a fleet from one script is exactly what the terminal enables; clicking through System settings on each host does not scale.

03Risk

RiskLow risk
RequirementsRun PowerShell as Administrator
!Warning: Remoting widens the attack surface; restrict allowed networks and require HTTPS or Kerberos for untrusted links.

04Undo

✓No undo needed — this command does not change persistent state.

05Sources

  • Enable-PSRemoting
    Microsoft Learn · vendor-doc · 2026-09-20
    Evidence: Configures the machine to receive PowerShell remoting commands.

Last verified: 2026-10-13 · Category: System & Settings

06Related solutions

Reset the Windows network stack with netsh
WindowsnetworksystemDiagnostics

The nuclear option for broken connectivity: rebuild Winsock and the TCP/IP stack to defaults when adapters show 'no internet' despite everything else working.

Medium risk ✓ 2026-09-17
Test a TCP port connection on Windows with Test-NetConnection
Windowsnetworktroubleshootingpowershell

A built-in PowerShell one-liner that answers 'is port 5432/3389/443 actually open through this network?' — no telnet client needed.

Low risk ✓ 2026-09-17
Set a static IP address with netsh from CMD
WindowsnetworksystemTerminal

Configure a fixed IPv4 address, subnet mask and default gateway on any adapter in one line — essential for headless servers and remote workstations.

Medium risk ✓ 2026-09-17