Is Login Agent even required if Runtime Resouce state is already Connected

[Anonymous]

Hello, If the runtime resource is setup in a way that it is showing connected in control room and there is a organizational process setup to login to the runtime resource if there is a restart or logoff on the machine (the startup scripts are also setup to run automatically on logon). Thus, this ensures that the state of runtime resource is always shown as Connected in control room. With the above in mind, do we still need Login Agent? If yes, please provide a scenario in which we would need it. thanks Nikhil

[ElvisRomero]

hi nikhiljha1, a don't understand the module login agent, please, do you have any guide outside guide oficial ? please send me to elvishromero@gmail.com thank you.

[Denis__Dennehy]

ElvisITC - there is a data sheet in the product area of the portal related to using login agent, there is also lots of help in the Knowledgebase. The most important thing in relation to the Production resource/robot desktops is that they are secure and cannot be accessed to ensure the security of the logical access model that is put in place as part of the Robotic Operating Model. It does not matter if Login Agent is used (fairly irrelivent if the robot is utilised 24/7 and therefore always logged in), or if access to the robots is simply restricted using the VM tools in use - all that is important is that no one can access the robots whilst they are access production systems containing production data.