Make sure the domain controller you specify is a global catalog.If you are joining to a specific domain controller you must ensure that Authentication Services can locate and read the configuration information in Active Directory. Check that the Unix host is able to properly resolve the domain name through DNS.Check that the Active Directory account specified during join has rights to join the computer to the domain.If you are unable to join the domain, run the preflight utility to validate your environment.įor more information, see The Authentication Services Pre-Installation Diagnostic Tool in the Authentication Services Installation Guide. Troubleshooting > Unable to join the domain Otherwise, you must create the Authentication Services application configuration in the domain that you join or you must properly configure DNS to return SRV records and join normally, rather than specifying a domain controller when you join.įor more information, see About Active Directory configuration. In this case, you must ensure that the domain controller you specified is a global catalog. This means that Authentication Services cannot resolve other domains in the forest and may be unable to locate the application configuration. If you previously joined to a specific domain controller, Authentication Services disabled DNS SRV record lookups.

Ensure that you have followed the instructions in Configure Active Directory for Authentication Services and that the configuration has been created successfully.ĭuring an upgrade, you may see an error that Authentication Services cannot upgrade because the application configuration cannot be located. The most common installation or upgrade failure is that the Unix host cannot read the Authentication Services application configuration in Active Directory. Troubleshooting > Unable to install or upgrade

Starling Identity Analytics & Risk Intelligence.Verwaltungslösungen für privilegierten Zugriff.Starling Identity Analytics & Risk Management.

Password depot online zugriff