Microsoft has issued a cautionary note regarding potential accessibility issues with Windows Server 2025 domain controllers following a restart. The concern arises from a situation where affected servers revert to the default firewall profile instead of utilizing the designated domain firewall profile, leading to disruptions in applications and services. This scenario poses a significant challenge for organizations that depend on their Active Directory infrastructure, as domain controllers are essential for user verification and network resource management within corporate settings.
Temporary solution available
In response to the issue, Microsoft has provided a temporary workaround for system administrators. The solution involves manually restarting the network adapter on the impacted servers. This can be accomplished through various methods, including the execution of the PowerShell command: Restart-NetAdapter *.
It is crucial to note that this workaround must be reapplied after each restart of the domain controller, as the problem reemerges with every reboot. To streamline this process, Microsoft suggests setting up a scheduled task that will automatically restart the network adapter whenever the domain controller is restarted, thus minimizing the need for manual intervention.
Launched earlier this year, Windows Server 2025 represents a significant update, introducing a range of new features such as the ability to apply security updates without requiring a reboot and enhanced support for SSDs. Microsoft has characterized this update as the most substantial since 2022, also highlighting several security enhancements, including default encrypted LDAP communication.
Not the first problems
This is not the first instance of challenges arising from Windows Server 2025 since its debut. Previous issues have included freezing Remote Desktop sessions after the installation of security updates. Additionally, in October 2024, an upgrade mishap occurred, resulting in Windows Server 2022 systems being inadvertently upgraded to Windows Server 2025.
As developers work diligently on a permanent resolution to the current domain controller issue, system administrators are left to navigate the interim solution until a more robust fix is made available in a forthcoming update.
Also read: Windows Server 2025 updates cause problems
