New
#1
Network Location Changing on Domained and undomained machines randomly
Hello,
What is going on with Windows 10 and Netowork locations? I work in an enterprise environment and have computers that are domained and some that are not. About 3 or 4 machines out of the 30 or so that run Windows 10 have weird network location issues. There is one machine that is not on the domain running WinX Education 64bit and every time the only local user profile on the machine logs in it sets both Ethernet connections as Public. One ethernet on that machine is to the network and is DHCP and the other is to a piece of DAQ equipment with a static address. I have the set-netconnectionprofile... powershell command in a batch running off task scheduler, but takes time in startup to run the script, so file share and net discovery are active. I know the work around, but what is the problem? I also had a machine that is on the domain show up as a public net location after login. It showed the connection to the domain, but net location was public. I don't have any Group Policy rules pertaining to net locations as it has not been an issue until winX started making it's rounds. I have over 100 machines on this floor and 6 VLANs, so I see a decent cross section of issues, but I cannot find any information other than workarounds or how to's on setting the net location. I want the root of the problem. Anyone?
Thanks in advance!