Login Agent can't log in.

[HongJooChoi]

Hi, all

I have faced with the problem while testing Login Agent.

According to the following pop-up, it seems Login Agent started successfully along with the system start in the first place, but it couldn't trespass the windows login screen.


The RR is scheduled to run 1 min after the log-in in my local setting and this pop-up came up after I had manually logged in Windows (I did it because the Login-Agent failed). 

The Windows Login screen in my laptop requests (4-digits) PIN number instead of password in my current setting. Can this affect the behavior of Login Agent? ( For some reason, I can't remove the PIN number setting from my laptop which looks like being tied with the group policy of my company).

I would appreciate for your help in advance.



Best regards



------------------------------
HongJoo Choi
------------------------------

[SteveBoggs]

Hi HongJoo,

Best practice when using Login Agent is to bypass any Secure Attention Sequence (SAS) that can interfere with a BOT's ability to begin working. If you're not able to work with your organization's IT team to allow this via Group Policy, you may be able to set up the SAS Proxy functionality outlined in our documentation and in this Knowledge Base article, "How do I bypass Secure Attention Sequence (SAS) and pre-login message when using Login Agent with Blue Prism v6.5 upwards?".

------------------------------
Steve Boggs
Senior Software Support Engineer
Blue Prism
Austin, TX
------------------------------

[HongJooChoi]

Hi, Steve

Thank you for your kind comment.

I managed to figure out how to make it work.
In my case, the Login process was malfunctioning (maybe better say, not fit to my test environment) that I had to revise it accordingly.


Best regards

------------------------------
HongJoo Choi
------------------------------