Start PowerShell as administrator and run the following command: So in order to allow scripts, we need to change this setting as suggested in yet another answer on : Again, that might be a valid security measure but in this situation it’s merely a pain in the lower back. Of course, that would have been too simple: Microsoft also by default prevents the execution of PowerShell scripts.
In order to work, this script must be started with administrator privileges. It then displays the new settings and waits for the user to press a key. It reads all connection profiles, filters for the one that apply to a network adapter with a given name (which I renamed to make it unique) and changes this profile to be private. $Host.UI.RawUI.ReadKey("NoEcho,IncludeKeyDown") Write-Host "Beliebige Taste um fortzufahren." It gives a PowerShell script which I have adjusted to my needs: So, what can be done? Google turned up lots of different suggestions but the only one that worked for me was this answer on. It used to be possible in Windows 7 but no longer. This means that many things – in particular network shares – do not work.Īnd since Microsoft doesn’t trust users to know what they are doing, there is no easy (GUI) way to change this. Unfortunately Windows sees this setup as an unidentified network and classifies it as a public network. All computers have fixed IP addresses, so there is no DHCP server involved, and provide network shares to each other.
Network wise this is an isolated island, there is no connection to any company LAN or the Internet. Now imagine a computer installed in a special setting that is connected via LAN to some other computers in the same place. The Windows firewall then changes some settings based on this classification. Windows 10 tries to identify networks and based on that classifies them as private or public. Unfortunately in typically Microsoft attitude they think they always know best and that the user is an idiot, so it’s best to keep anything dangerous from him.įast forward to Windows 10 and the issue at hand:
Starting with Windows Vista Microsoft has started to take security really serious.
0 kommentar(er)
