Connectivity issues for a domain controller in Performance Cloud VMware
Once a new domain controller (DC) is built or migrated in Performance Cloud VMware, it is possible that the Active Directory domain becomes unavailable, or the network location changes to “Private” instead of “Domain” after a virtual machine reboot. The virtual machine with the DC role started too fast without having all required services running.
The solution for this issue is to add dependencies on services.
- Login to your domain controller.
- Open the registry editor.
- Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc
- In the right pane, double-click the value DependOnService and add DNS to the next available blank line.
Repeat to add NTDS to the next available blank line. Then, click on OK to close the value.
- Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon
- In the right pane, double-click the value DependOnService and add DNS to the next available blank line. Then, click on OK to close the value.
- Reboot the domain controller
The domain controller (DC) should now start all required services with a working Active Directory domain.
If you are still having connectivity issues with the Active Directory domain, please review the following Microsoft articles for troubleshooting steps: