Quick Questions if you are aware after the upgrade: 1) Did you manage to install Windows Defender for Servers P2 ? 2) Did you try adding DNS conditional forwarders for DNS resolution on Azure private DNS zones ? 3) In case you run hybrid and you use microsoft cloud entra sync, did you install the client to manage cloud sync from Entra ? Did you manage get a view of server from cloud sync on Entra ? 4) Did you manage to install Microsoft Defender for Identity on 2025 Domain Controller ? 5) Did you manage to install MS Security Compliance toolkit for 2025 domain controllers ?
Question, did you have to update any registry settings to get the parent domain controller to advertise that it was the parent controller, following your process which is the same as server 2022 I received a notice that the domain controller of this domain cannot be contacted, even though I could validate that the domain name would resolve on the secondary soon to be controller. After troubleshooting the issue, I discovered in the SYSVOL registry configuration that the required registry key on the parent domain controller was not actually there, yet on my 2022 server, I can see that the registry entry is visable. Did Microsoft already fix this then in a patch? I haven't tried the 2025 AD build again since then which was about 2 weeks ago.
No. No registry setting needed. All steps were covered in the video. However, DNS must be operating normally and must be able to resolve the domain. If not, then things will be whacky. There is one issue with Server 2022/2025 regarding network profile. But that should not prevent any second or following domain controllers being added.
Quick Questions if you are aware after the upgrade:
1) Did you manage to install Windows Defender for Servers P2 ?
2) Did you try adding DNS conditional forwarders for DNS resolution on Azure private DNS zones ?
3) In case you run hybrid and you use microsoft cloud entra sync, did you install the client to manage cloud sync from Entra ? Did you manage get a view of server from cloud sync on Entra ?
4) Did you manage to install Microsoft Defender for Identity on 2025 Domain Controller ?
5) Did you manage to install MS Security Compliance toolkit for 2025 domain controllers ?
Question, did you have to update any registry settings to get the parent domain controller to advertise that it was the parent controller, following your process which is the same as server 2022 I received a notice that the domain controller of this domain cannot be contacted, even though I could validate that the domain name would resolve on the secondary soon to be controller. After troubleshooting the issue, I discovered in the SYSVOL registry configuration that the required registry key on the parent domain controller was not actually there, yet on my 2022 server, I can see that the registry entry is visable. Did Microsoft already fix this then in a patch? I haven't tried the 2025 AD build again since then which was about 2 weeks ago.
No. No registry setting needed. All steps were covered in the video. However, DNS must be operating normally and must be able to resolve the domain. If not, then things will be whacky. There is one issue with Server 2022/2025 regarding network profile. But that should not prevent any second or following domain controllers being added.