Recently, in learning 2008 R2, installing both the ad and the certificate on your own computer often leads to a certificationauthority error, as follows:
The main causes of the problem are:
The certificate server is mounted on the same server as the DC, and Certificate Services is started before the ad service starts, so the ad service is not contacted and an error is made. The cause of the problem has been found, because this error only when the server started to complain, after the start of the normal, the system does not affect, but not good-looking, always show error information. The startup type of Certificate Services is then changed from automatic to Automatic (deferred startup), while the dependency of Certificate Services is modified to resolve. After restarting the server again, the server error message is gone.
NOTE: The space preceding the ADWS is required. The modified dependencies are shown in the following diagram:
Similarly, DNS has similar problems as well:
DNS Server 4013 warning message:
The DNS server is waiting for the Active directory domain service (AD DS) to emit a signal that the initial synchronization of the directory is complete. The DNS Server service cannot start until the initial synchronization completes because important DNS data may not have been replicated to the domain controller. If the events in the AD DS event log indicate a DNS name resolution problem, consider adding the IP addresses of other DNS servers for this domain to the list of DNS servers in the Internet protocol properties of the computer. Log the event every two minutes before AD DS sends a signal that the initial synchronization has completed successfully.
Workaround:
Set the DNS Server service to start as automatic (deferred startup)
The DFS namespace service was unable to initialize the Cross-forest trust information on the domain controller, 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 (deferred startup)
2. Modify registry key value
Run Registry Editor and navigate to the following registration path:
Hkey_local_machinesystemcurrentcontrolsetservicesdfs
Modifies the key value of the DependOnService, resets the row and adds "NTDS".