| Event Information | CAUSE:
This behavior can occur when the server that the Kerberos KDC service attempts to start on is not a domain controller. In this situation, by default, the Startup Type of service on the server that is not a Windows 2000-based domain controller is set to Disabled.
RESOLUTION:
To work around this behavior, set the Kerberos KDC service Startup Type to Disabled on member servers. This service must be set to Automatic only if the server is an Active Directory domain controller.
STATUS:
This behavior is by design.
MORE INFORMATION:
The Kerberos KDC service cannot run on a member server or a stand-alone server. The Kerberos KDC service can only be run on a Windows 2000-based Active Directory domain controller. |
