Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Saturday, June 29, 2019 7:17 AM
Hello!
Is there any way how can WinRM run on Public profile? There are pretty good reasons why not to use Private profile (e.g. public IP). I want restrict access in firewall just on local subnet so I don't see any risk running WinRM on Public profile.
It looks that Enable-PSRemoting -SkipNetworkProfileCheck does not help. After running it says that everything is ok, but "winrm quickconfig" returns WinRM firewall exception will not work since one of the network connection types on this machine is set to Public
Running Win 10 1809
Thanks
All replies (4)
Sunday, June 30, 2019 12:44 AM
S.Sengupta,Microsoft MVP Windows and Devices for IT, Windows Insider MVP
Sunday, June 30, 2019 7:57 AM
S.Sengupta,Microsoft MVP Windows and Devices for IT, Windows Insider MVP
I did already read MS documentation, but it doesn't work as usual.
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.
I don't want to change the connection type!!!
Tuesday, July 2, 2019 8:45 AM
hi,
there are two documents for your reference
Windows 10 WinRM connection marked as public
https://social.technet.microsoft.com/Forums/en-US/a41ae1e4-17e1-4466-bf54-3a72d0d61db9/windows-10-winrm-connection-marked-as-public?forum=winserverManagement
Fixing - WinRM Firewall exception rule not working when Internet Connection Type is set to Public
http://www.hurryupandwait.io/blog/fixing-winrm-firewall-exception-rule-not-working-when-internet-connection-type-is-set-to-public
Please Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information
Best Regards
Andy YOU
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, July 2, 2019 7:21 PM
hi,
there are two documents for your reference
Windows 10 WinRM connection marked as public
https://social.technet.microsoft.com/Forums/en-US/a41ae1e4-17e1-4466-bf54-3a72d0d61db9/windows-10-winrm-connection-marked-as-public?forum=winserverManagement
Fixing - WinRM Firewall exception rule not working when Internet Connection Type is set to Public
http://www.hurryupandwait.io/blog/fixing-winrm-firewall-exception-rule-not-working-when-internet-connection-type-is-set-to-publicPlease Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information
Best Regards
Andy YOU
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Hi, the "solution" proposed there says: set all networks to private, then start WinRM, then change profiles back to original values. This is silly. (what about computer restarts etc?)
To be honest: the better (and more elegant) solution is not to use public profile at all and modify all firewall rules for private profile to be secure.
I am wondering what SkipNetworkProfileCheck option is good for? It doesn't work.