Remote management with PowerShell

In this post I’ll show how to connect to remote systems using local/AD credential with Powershell. To successfully connect to remote system you should have a local/AD Administrator account be able to gain Admin privileges to remote server.

This how-to is tested on Windows Server 2012 and Windows Server 2016.

Enabling Remote access

  1. Using a remote console, on the remote system launch powershell with Administrator rights


Client setup

On the desktop system there are few steps to follow before trying a connection:

  1. Open PS with Administrator rights
  2. Add servername or IP in the thrusted hosts:
  3. Start WinRM Service with net start WinRM


Time to connect

Enter in remote simply using this syntax:



Test and troubleshooting

To ensure that connection is correctly configured and matched with trusting hosts, you could use Test-WsMan cmdlet:


In some cases you should configure firewall policy to allow incoming the following incoming connection:

  • TCP/5985 = HTTP
  • TCP/5986 = HTTPS

Note and use-case

It’s important to authorize people and allowed host to restrict the access only for domain/system administrator. For this reason is important to specify the a host fqdn or ip in TrustedHosts WSMan entry.

Using powershell with Invoke-Command is an interesting way to manage multiple hosts or make repetitive tasks across multiple hosts.


There is an interesting article here about clear and secure ports:

Thanks to How-to Geek  for the guide


   Send article as PDF