Hello
I just went through a login issue with trusted domains.
DomainA and DomainB are trusted but in different Forests.
DomainA is my app server and SQL server while all my AD groups and users are in DomainB.
We simply made the Blue Prism server service log on as a service account from the DomainB. Then it was querying the right global catalog for authentication.
To be able to log the service as a different AD, you have to add that user in the group policy: Log on as a server within Local Policies/User rights Assignment.
Not sure if this could apply to the above issue somehow.
If there is only one user, just change your AD groups of domain. If multiple users in A and one in B, maybe there is a way for user in domain B to run blueprism as a domain A user from the command prompt or Powershell. ex: runas /user:domaina\user automate.exe
What is strange is that when we install blueprism, it recognizes all the users from the start, I think Blue Prism should review their query method to not only check the current forest catalogue on start.
Carol
