Please could I request a feature regarding the operation of ACLogon.exe? I’ve been speaking to one of your Systems Engineers (Ross Thomson) who has helped me with ACLogon so far. Below is the feedback he gave me regarding the usage of ACLogon. He has already engaged at an engineering level to progress the case.
Auth Connector maintains two different IP-to-user tables for DCQ and ACLogon. When an auth request comes in, it checks the DCQ table first, then checks the ACLogon table only if a match wasn’t found in the DCQ table.
That means if a client is running DCQ, and Auth Connector has the user in both tables, then that user logs out from the workstation and a different user logs in, the first user will be found instead of the second, because AC will check the DCQ table first.
===================
If you think that’s an issue (and you want Auth Connector to check and match Client Query FIRST – let me know and ill feed back to engineering) – cant promise it will change, but will make every effort since you would be the first customer I’m aware of trying to use both at the same time (and this seems logical to me)