www.gsx.com | log in | register

Last update: . Author: Cyril LEROY .

Failure to enable Remote PowerShell for Non-Domain-Joined computers

When configuring Remote PowerShell, a failure to modify firewall exceptions occurs when the computer is not a member of a domain.

This article describes the steps required to enable Remote PowerShell management on a Non-Domain-Joined computer.

PowerShell v3

Symptoms

  • WSManFault code 2150859113: WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Change the network connection type to either Domain or Private and try again. 

How to Solve the Issue

This behavior is observed on Non-Domain-Joined computers (also known as Workgroup) particularly when the active network type is detected as public. To correct the issue, below we will enable Remote PowerShell by passing the security exception and update the trusted hosts list.

Enable Remote PowerShell by passing the security exception and updating the trusted hosts list:

  1. Open a PowerShell window as an administrator.
  2. Execute the following command:
    • Enable-PSRemoting -SkipNetworkProfileCheck
  1.  Open a PowerShell window as an administrator.
  2.  Execute the following command:
    • set-item WSMan:\localhost\Client\TrustedHosts *

Remote PowerShell is now successfully enabled.

 

Microsoft related articles



Not finding what you are looking for?

Have more questions? Submit a request


Was this article helpful?

1 out of 1 found this helpful