network location

Set Network Location to Private in Windows 8 & 10 and Windows Server 2012 & 2016

One of those annoyances that sometimes happen with the new Network Location in Windows 8.x and Windows 10 is that the network gets mis-identified as Public when it should be Private, or the other way around. Changing this in the GUI is certainly possible, but annoying, so let's take advantage of the improved Windows PowerShell support in Windows 8.1 (and later) and do it quickly and easily. First, let's open up an elevated PowerShell window from our limited user session:

PSH> Start-Process WindowsPowerShell.exe -verb RunAs

Now, in that window, let's find out what our current network location is set to:

PSH> Get-NetConnectionProfile
...<snip>...
Name : Unidentified network
InterfaceAlias : vEthernet (Local-10)
InterfaceIndex : 18
NetworkCategory : Public
IPv4Connectivity : LocalNetwork
IPv6Connectivity : LocalNetwork

From this, we see that the problem interface has an Interface Index of 18, so:

PSH> Set-NetConnectionProfile  -InterfaceIndex 18 -NetworkCategory Private

And we're done.

ETA, 3 August, 2016 -- this same problem exists in Windows 10/Server 2016. And the solution is the same. Set-NetConnectionProfile is your friend!

Windows MultiPoint Server Disconnects

There is a known issue with Windows Server 2008 R2 (and Windows 7) that causes the network interface to change “location” from a Domain network to a Public network under some conditions. This is described in MS KnowledgeBase article: 2524478. The situation that causes this is made more likely to happen on a WMS server because of the Loop Back Adapters. I’ve been running this particular hotfix here for more than a week, with no ill effects. And a whole lot fewer WMS disconnects from my RDP clients! If you are using WMS, and using RDP clients, I strongly recommend that you download a copy of this hot fix and apply it if you’re seeing any unexplained disconnects from these clients.

Charlie.

Update1: There’s a new blog post up on the Official SBS Blog that talks about this. If you’re running WMS, you really want to get this hotfix.

Update2: If you’re running through a Remote Desktop Gateway (RD Gateway) to connect to your WMS server, you should install this hotfix on the RDGateway box as well. For example, on my SBS 2011 Standard network, my laptops use applications on the WMS server using RemoteApps. But I have them set to go through the RD Gateway on my SBS server, even when I’m in the office. This allows my connections to stay the same regardless of whether I’m in the office or on the road. I was still getting some disconnects even after installing this hotfix on the WMS server. But when I added them to the SBS server (my RD Gateway, remember), the disconnects went away. I haven’t had one all day. WOOT!