How to Enable and Test PowerShell Remoting on Windows Server
Applies to: Windows Server 2019, 2022 and 2025.
PowerShell Remoting uses WinRM for repeatable remote administration. Domain Kerberos is preferable; workgroup TrustedHosts settings must remain narrow.
Work from console access or a tested recovery path. Changes to remote access, licensing or domain membership can lock out administrators if prerequisites are wrong. Managed Windows VPS options are available at networkmanager.info.
Prerequisites
- Confirm forward and reverse name resolution.
- Use separate privileged credentials.
- Restrict management traffic to approved networks.
- Avoid wildcard TrustedHosts entries.
Step-by-step procedure
Step 1: Inspect WinRM
Check the service and listeners.
Get-Service WinRM
winrm enumerate winrm/config/listenerStep 2: Enable remoting
Configure WinRM and built-in firewall exceptions.
Enable-PSRemoting -ForceStep 3: Test locally
Verify the endpoint from the server.
Test-WSMan localhostStep 4: Test remotely
Run from the administrator workstation.
Test-WSMan SRV-APP01
Enter-PSSession -ComputerName SRV-APP01Step 5: Run a harmless command
Confirm identity and time on the intended target.
Invoke-Command -ComputerName SRV-APP01 -ScriptBlock { hostname; Get-Date }Verification
A WS-Management response and correct hostname confirm transport and target identity.
Test-WSMan SRV-APP01Rollback
Run Disable-PSRemoting -Force from console if enabled in error, then audit firewall and TrustedHosts separately.
Version and operational notes
The feature is available in all target releases; authentication and network scope determine whether deployment is secure.
Official references
For managed deployment and support, visit https://networkmanager.info/.
