After installing Certificate Services on Windows 2008 R2, the authenticationAuthority error occurs after restarting

Recently studying 2008 R2, installing AD and certificate on your own computer often has a CertificationAuthority error, as follows:

The certificate server and the DC are installed on the same server. The certificate service is started before the service of the AD is started, so the AD service cannot be contacted and an error is reported. The cause of the problem was found, because this error is only reported when the server is started. It is normal after startup, and has no effect on the system, but it does not look good. It always displays error information. Therefore, the startup type of the certificate service is changed from "automatic" to "automatic (delayed start)", and the dependency of the certificate service is modified. After restarting the server again, the server will report the error message.

Note: Spaces in front of ADWS are required. The modified dependencies are as follows:

The same DNS has similar problems:

DNS Server 4013 Warning Message:

DNS Server is waiting for Active Directory Domain The service (AD DS) signals that the initial synchronization of this directory has completed. The DNS Server service could not be started until the initial synchronization is complete, as important DNS data may not have been replicated to the domain controller. If an event in the AD DS event log indicates a DNS name resolution issue, consider adding the IP address of another DNS server for this domain to the list of DNS servers in the Internet Protocol properties for that computer. Record this event every two minutes before AD DS signals that the initial synchronization has completed successfully.

Workaround:

Setting the DNS SERVER service startup method is "Automatic (Delayed Start)"

The DFS Namespace Service cannot initialize the domain control Cross-forest trust information on the device, but the service will retry the operation periodically. The return code is in the record data.

1, change the DFS Namespace startup type to "Automatic (Delayed Start)",

2, modify the registry key

Run the registry editor To locate the following registration path: \\HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\services\\Dfs Modify the DependOnService key value, restart the line and add “NTDS”.