Environment
Situation
Users can't connect with RDP to different domain when AAF Client 6.x is installed.
Invalid credetials error when attempting RDP session to a host that is not in the Advanced Authentication repository
Customer has their own production domain. Users login through AAF via the Windows login to their desktop with password and token. This all works as expected.
Now they have other RDP hosts that they access. The users on the other computers they are accessing are not part of their domain but of the remote domain.
So they login to their workstation as domain1\userx
Then when they attempt the remote session they specify domain2\usery
When the AAF client intercepts the RDP session it attempts to login with the domain1\userx account instead of the credentials that were stored/initiated with the RDP session.
In the case of the domain2 they are prompted for the password of the account builtin/builtin
They click the <- to go back and then enter the proper name again of domain2\usery
Now it attempts the connection but fails.