Fix Domain Profile Not Detected on Windows Server
In some environments, Windows Server domain controllers may incorrectly apply the “Public” firewall profile instead of “DomainAuthenticated,” especially when internet access is restricted. This video provides a reliable solution for Windows Server 2025, 2022, and 2019 using PowerShell and a scheduled task to ensure the domain profile is correctly detected after reboot. Proper firewall profile detection is essential for Group Policy processing, domain replication, and secure management traffic.
Applies to:
✅ Windows Server 2025, ✅ Windows Server 2022, ✅ Windows Server 2019, ✅ Windows Server 2016
Chapters:
0:00 Introduction
0:33 Problem Description
2:26 Fix -- Windows Server 2025, 2022, 2019
4:02 Scheduled Task to Reset Network Adapter
7:04 Old Fix -- Windows Server 2022, 2019
8:15 Thank you for watching
Glossary:
AD = Active Directory
CA = Certificate Authority
DC = Domain Controller
DNS = Domain Name System
GUI = Graphical User Interface
HKLM = HKEY_LOCAL_MACHINE
ISE = Integrated Scripting Environment
NLA = Network Location Awareness
NLS = Network List Service
OS = Operating System
SCONFIG = Server Configuration
GitHub:
https://github.com/DariensTips
Commands:
$daInterface="Ethernet"
$desiredProfie="DomainAuthenticated"
if (((Get-NetConnectionProfile).NetworkCategory) -ne $desiredProfie) {
Disable-NetAdapter -Confirm:$false -ifAlias $daInterface ; Enable-NetAdapter -ifAlias $daInterface
}
Links:
https://learn.microsoft.com/en-us/pow...
https://learn.microsoft.com/en-us/pow...
https://learn.microsoft.com/en-us/pow...
https://learn.microsoft.com/en-us/tro...
https://techcommunity.microsoft.com/c...
https://techcommunity.microsoft.com/d...
Hashtags:
#WindowsServer #DomainProfileFix #ActiveDirectory #SysAdmin #PowerShell #GroupPolicy