Network Category not set to 'DomainAuthenticated' after joining domain.

Question

I have a several hundred Windows 2012 servers that do not update thier network category to 'DomainAuthenticated' after being joined to a domain.  All my networks are unidentified and thus set to public.  I can run the following command and change
them to private, but all documentation says that it should auto-magically change to DomainAuthenticated after joining a domain.  Does anyone have a solution?
Get-NetConnectionProfile
|
where {$_.NetworkCategory
-eq
"Public"}
|
Set-NetConnectionProfile
-NetworkCategory
Private

Answer 1

Hi,
If the server is domain joined, when it starts to detect the network location, the machine will contact a DC via port 389. If this detection successful, it will get the domain profile. And we cannot change
it. If the domain was not found or process failed, NLA will let you to determine which firewall profile will be used, private or public.
For more information about Network Location Awareness, you may refer to the following article. It also applies to Windows 2012.
Network Location Awareness (NLA) and how it relates to Windows Firewall Profiles
http://blogs.technet.com/b/networking/archive/2010/09/08/network-location-awareness-nla-and-how-it-relates-to-windows-firewall-profiles.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.