Hello,
Thank you for posting in the Microsoft Community Forums.
It sounds like you're encountering some compatibility or resource contention issues when promoting your Server 2025 to a Domain Controller. Since setting services to "Automatic (Delayed Start)" has helped with Xen Guest Tools and NinjaRMM, it's possible that these services are vying for resources or network connectivity prematurely, before certain domain-related services are fully operational.
Here are a few suggestions that might help:
- Service Dependencies: Ensure that the services for Threatdown/Malwarebytes, NinjaRMM, and Xen Guest Tools have the appropriate dependencies set. This can ensure they start only after the essential domain services are up and running.
- Network Configuration:
- Check the network configuration and DNS settings. Ensure the server can resolve DNS queries correctly and that there are no conflicts.
- Make sure the Domain Controller's IP address is properly set and that there are no duplicate IP addresses in the network.
- Firewall and Security Policies:
- Even though you mentioned the built-in firewall was temporarily disabled, ensure that there are no Group Policy settings being applied that might affect these services when the server becomes a Domain Controller.
- Check any security software that might be running and see if there are any strict policies being enforced upon promotion.
- Event Logs:Investigate the Event Viewer for any warnings or errors related to these services. There might be additional clues as to why they are unable to communicate.
- Service Restart Sequence:Ensure that services that depend on network connectivity or domain services are set to start after those services are guaranteed to be online. This is where "Automatic (Delayed Start)" can be helpful, but you might also consider manually specifying the service start order if needed.
I hope the information above is helpful.
Best regards
Yanhong Liu