The Enable-PSRemoting cmdlet configures the computer to receive PowerShell remote commands that are sent by using the WS-Management technology. WinRM is enabled by default on all Windows Server operating systems since Windows Server 2012 and above, but disabled on all client operating systems like Windows 10 etc. Here are some interesting guides: How to request a certificate signing request in Windows using Microsoft Management Console, how to troubleshoot and fix Windows Admin Center that cannot be reached, and how to Test Network Connection to the Windows Admin Center (WAC) Gateway.
On the Windows server, you literally do not have anything to do to have this service enabled. To configure your servers for remote access, follow the steps below. Here is the syntax to use: Enable -PSReomoting
Launch your server, fire up a PowerShell terminal, and type “Enable-PSRemoting”. This will enable the server for PSRemoting and allow the server to be accessed via remote access.
Add the servers to the TrustedHosts list
Add the host to the TrustedHosts list with the command, for more information, see the following guide on how to add servers to the TrustedHosts.
RestartWinRM service with the command below via PowerShell.
Restart-Service winrm
To test the WinRM Configuration, run the command below.
winrm quickconfig
Method 1
To test remote access using PowerShell Remoting, use the command below, replace “ansible” with your remote computer
Enter-PSSession -ComputerName Ansibleserver
Method 2
To permit a remote connection via PowerShell remoting, use the command below
Enter-PSSession -ComputerName TechDArchive -Credential $Credentials
As shown below, the authentication is successful and I am able to remotely manage the machine via PowerShell Remoting.
I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.