I also have this issue but I have domain controllers that are NOT part of this Hyper-V host. If I restart the Network Location Awareness (which
also restarts the Network List Service) It goes back to domain as it should. Now when I reboot this server it will once again put the interface /
network back to public even though this Hyper-V server has been successfully joined to the domain with a static IP.
Now for clarification. This Hyper-V server does NOT have any virtuals configured yet. The only thing that has been configured is a NIC team with
two onboard NICs (LAN ports 3 & 4) and two NICs from an add-in four port card (ports 3 & 4) . The Local LAN connection is dedicated to LAN
Port #1. We also have a dedicated IMM port for out of band access.
Now the ONLY time I can get this server to reboot and STAY in the "Domain" location is if I have PORTFAST enabled on the switch port it is
connected to. Yes, we use STP here in our enterprise. This is not the first time I have had to do this but it doesn't seem right as a co-worker
claims he does NOT need to do this and his Hyper-V server reboots just fine. I have had him check it out and he cannot see any differences
between his servers and mine. Yet mine will always reboot to "public" unless I have portfast enabled. Any thoughts??
Network Admin