A
ATyler - Life Flight Network
Hello, we're in the middle of our biannual disaster recovery testing and I have noticed a trend with all of our 2012 R2 servers brought up in the isolated recovery environment. They all come up and ask if the network is "Private" or "Public" and it some cases you miss this prompt and it defaults to Public which breaks applications due to bad firewall policy.
Can someone explain to me why the domain profile is not detected and applied? The primary FSMO Domain Controller is accessible in this environment and DNS is fully operational. Same subnet... Sratching my head. I have tried to set the domain profile using gpedit.msc and by using the set-netconnectionprofile powershell command. It seems that you can only set Private or Public using these mechanisms.
I've been all over this post regarding Network Location Awareness and in my case it isn't helpful unfortunately.
Network Location Awareness (NLA) and how it relates to Windows Firewall Profiles
Regards,
Adam Tyler
Continue reading...
Can someone explain to me why the domain profile is not detected and applied? The primary FSMO Domain Controller is accessible in this environment and DNS is fully operational. Same subnet... Sratching my head. I have tried to set the domain profile using gpedit.msc and by using the set-netconnectionprofile powershell command. It seems that you can only set Private or Public using these mechanisms.
I've been all over this post regarding Network Location Awareness and in my case it isn't helpful unfortunately.
Network Location Awareness (NLA) and how it relates to Windows Firewall Profiles
Regards,
Adam Tyler
Continue reading...