Hello,
One problem is that the claim "Adaxes will connect to the first available domain controller from the list." does not seem to work. Shouldn't Adaxes use the next available DC in such case? We have defined several domain controllers on the list, but it seems to use only the first one.
It is correct that Adaxes connects to the first available domain controller from the list. The fact that Adaxes connects to the first specified DC means that connection between the computer where Adaxes service is installed and the DC can be established. Only if connection fails, Adaxes will try to connect to the next DC.
We currently have one of the DCs overloaded, which we are working on fixing, but Adaxes does not work because the DC is "not operational". Shouldn't
Could you specify, at what point you see the error message? Does it occur when performing specific operations in Adaxes? Could you try to remove the overloaded domain controller from the list specified in the Softerra.Adaxes.Service.exe.Config file?
Currently used Adaxes version is 3.8.14823.0. Is there a different behavior with the newest version.
This behavior did not change in newer versions in comparison to the version you are currently using.