How can I get winrm to setup firewall exceptions?

Question

_{Tuesday, August 13, 2019 8:14 AM}

This is a copy of the question from https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/how-can-i-get-winrm-to-setup-firewall-exceptions.

I'm running Windows 10 Enterprise Version 1903.

When I run winrm quickconfig in PowerShell as an Administrator it stops with an error stating that one of the connection types is set to public and needs to be changed:

WinRM service is already running on this machine.

WSManFault

Message

ProviderFault

WSManFault

Message = 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.

Error number: -2144108183 0x80338169

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.

When I check the network connections with Get-NetConnectionProfile it returns a single connection which is set to private.

Name : Network

InterfaceAlias : Ethernet 2

InterfaceIndex : 17

NetworkCategory : Private

IPv4Connectivity : Internet

IPv6Connectivity : NoTraffic

I have tried resetting the network settings and adding the firewall predefined inbound rules (Windows Remote Management and Windows Remote Management (Compatability)), but the error still shows up.

What I want to achieve is to change the MaxEnvelopeSize.

All replies (3)

_{Wednesday, August 14, 2019 2:20 PM ✅Answered | 1 vote}

Eventhough PowerShell and the Network Connections Window didn't show any other connections as public, disabling all other network devices fixed the problem.

_{Wednesday, August 14, 2019 8:01 AM}

Hello,

Please check the information in this article to see if they work.

Understanding and troubleshooting WinRM connection and authentication: a thrill seeker's guide to adventure

Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

If that still can't resolve the issue, I suggest you post in PowerShell forum for better answers.

Best Regards,

Leon

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Thursday, August 15, 2019 2:19 AM | 1 vote}

OK, thank you for your update.

Good to hear that you have solved this issue by yourself. In addition, thanks for sharing your solution in the forum as it would be helpful to anyone who encounters similar issues.

If there is anything else we can do for you, please feel free to post in the forum.