Login Agent - Persistent vs Non-Persistent VDIs

[AbhijithB_S]

Hi All, We have a non-persistent VDI set-up in our project, where everytime a user logs in to a VDI, it will be a different one. There is no 1 to 1 mapping of User ID and a VDI. Also, the VDI's are hosted on Citrix. Does Login Agent support this configuration? Or in other words, can we use the Login agent to perform auto-login to any available VDI (on which login agent is configured) using a particular UserID and password?? Please provide insight into this. Thanks.   Regards, Abhijith B S

[SUMEETMANGLESH]

Nope, It does not. I spent a lot of time and did a lot many POCs to make BP work with non-persistent VDI and it did not work. Logic will fail either in login agent or scheduler. BP documentation also suggests the same.

[inian]

Hi abhijit, BP will not support non-persistent VDI. It support only persistent VDI.  Please try to create your own logic for automated login using .net applications.     regards, Inian  

[Sankar_GaneshKo]

Yes. We can use non persistent VDI as BOT.  We are using Non persistent VDI. We are able to run the login agent process to do the login and logout. 

[RamyaVijay1]

Hi,
Can you please provide any documentation you have on non persistent VDI architecture? Thanks!

------------------------------
Ramya Vijay
------------------------------

[Walter.Koller]

Are you sure you are using non-persistent VDI or do you use Citrix VDI pools?
With non-persistent VDI Citrix will create a new instance based on a template, every time the user logs out  all changes done will be discarded. I don't think this set-up would support Blue Prism as key characteristics are spawning and discarding VDI.
There is also the possibility you are using a pool of persistent VDI. This means, you will get a VDI randomly assigned when ever you log on to Citrix but all changes done will stay. When not connected the VCI still runs in the background. But the next time you logon to Citrix you might get another VDI. However, this does not matter for Blue Prism as it will directly communicate with specific VDI, bypassing Citrix pooling. It will just be a little cumbersome for human users via Citrix when trying to access a certain VDI because eg a process got stuck. This can be avoided by using other remote access methods. We used this set-up for quite some time but eventually switched away from Citrix pools to singe VDIs

------------------------------
Walter Koller
Solution Manager
Erste Group IT International GmbH
Europe/Vienna
------------------------------