Skip to main content
  • EN

🚨 System Administrators Your Attention Please 🚨


Have you deployed or migrated domain controllers to Windows Server 2025? If the answer is yes then be vigilant in case of a reboot!

Indeed, Microsoft has confirmed that Active Directory servers can lose network connectivity after a restart. (Ouch) 

💥Impact?

Authentication problems, inaccessible applications and services, and more... A great way to start your day.

🔍 The reason?

After a restart, the DC firewall network profile switches to standard mode instead of the domain profile.

🛠️️ Remediation?

To date there is no fix available. Microsoft is working on a patch that will be published in a future update.

⚙️ Workaround:

Manually restart the network adapter. You can use the PowerShell command:

Restart-NetAdapter *

✅ Tip:

You can create a scheduled task to automate this command if you need to restart your servers multiple times.

So if your Surebackups failed during the tests it could be the issue. 

Interesting as I had this issue before reverting back to Win2022 for my DCs.  Nice they are working on an update but this needs to be patched ASAP.  Thanks for sharing.

Yikes, that’s not good. Perhaps this powershell command could be used to set it back to a domain network?

Set-NetConnectionProfile -InterfaceAlias Ethernet1 -NetworkCategory "DomainAuthenticated"

I’ve used this before to change networks from public to private. Reference for this PowerShell can be found here. 

Thank you for sharing ​@Stabz 

Yeah, Windows Server 2025 still having some issues with the Firewall component. 

Thanks for this information. Forwarding to my colleagues 👍

I forgot to give you the source !
Here it is: https://learn.microsoft.com/en-us/windows/release-health/status-windows-server-2025#domain-controllers-manage-network-traffic-incorrectly-after-restarting

Comment


Terms & Conditions