Login Agent

[RYANRICAFORT1]

I've written a customized process that utilizes the login agent.  In development environment, both logout and login actions are working.  In UAT environment, only the logout works.  The login action does not terminate, but it doesn't actually login the machine either.  Can anybody provide insight?   Thanks in advance.

[John__Carter]

Maybe the credentials being passed to Windows are incorrect?

[RYANRICAFORT1]

Hi John.  Checked and double checked, credentials are correct.  The process passes through the login action but doesn't log in the machine.

[david.l.morris]

Did you verify it's using the same version of the VBO in both environments and both environments have the same version of BP?

[John__Carter]

Good point from David. Also try enabling full logging to try to see what's going on, and check the machine's event log for clues too. Also sanity-check that the machine is set up (CTRL ALT DEL etc) for LA to work.

[Srikanthabburu]

Hi Ryan. Could you please tell me if this issue is resolved as I am facing the same issue

[AmiBarrett]

We ran into this issue on systems which we had RDP'ed into. This can be gotten around by using tsdiscon to unlock the system to the desktop session, but it will require elevated permissions.

[Venkata_Pranav_]

@AmiBarrett ​  Instead of using tsdiscon, can we set time limit for disconnected sessions to "Never" on Remote Desktop Session Time Limits? Wondering if it does the same thing. 

gpedit.msc ----> Browse to Computer Configuration --> Administrative Templates --> Windows Components --> Remote Desktop Services --> Remote Desktop Session Host --> Session Time Limits.

------------------------------
Pranav
------------------------------

[AmiBarrett]

Time limits only apply to active sessions. Once you're disconnected, this policy will have no affect. Even then, it will not revert the system to a console session, which is what you'd get from running tsdiscon.

To quickly clarify here - When you're using your system locally, that's known as a console session. If you connect via TeamViewer or VNC, this leaves that session open. RDP will lock the remote system and bring it to a lock screen so that it can present a remote session to the RDP client connecting to it. Upon disconnection, that system is still locked. The tsdiscon command is the sole exception to this, as you can specify for it to return to the console session in one of the arguments.

------------------------------
Ami Barrett
Lead RPA Software Developer
Solai & Cameron
Richardson, TX
------------------------------