Questions From The Field…Answered - Login VSI
  • Variant A
  • Variant A
  • login vsi company logo 250x40

    Questions From The Field…Answered

    How does the virtual user handle disconnected sessions?

    Find out in our new Vlog series: “Questions From The Field…Answered”!

    The other day I had the benefit of working with one of our customers in the healthcare practice. They use Login PI to make sure their EHR medical application services are always available throughout their 30 clinics and hospitals, 24 x 7 x 365, and have nearly 30,000 employees. This customer also uses IGEL, which is a supported platform to run the Login PI launchers.

    If you aren’t familiar with Login PI, the virtual appliance is set up to ask the launcher to establish a session to a hosted workspace or application, so that the virtual user can log in, start multiple applications in a particular workflow, interact with those applications and logoff. This can be a continuous process or can happen many times per hour and day if you’d like.

    Given the number of different networks at the clinics and hospitals this customer manages, it makes sense that he would be very interested in what happens if a session suddenly becomes disconnected, or if enabled, automatically reconnects. Networks should be reliable, but sometimes they can be a little flakey, and when it comes to EHR, he wants to make sure everything is quickly accessible and available…ALWAYS.

    So, in this edition of Questions From The Field…Answered, I’m providing a quick video demonstration of how we handle reconnects…it works like this…if a session where we have our Login PI engine running gets disconnected we will detect this and log the virtual user off immediately. This ensures that next time we start a session, the environment is prepped to run the virtual user engine again.

    If the Login PI Environment Login Time is set to a value less than the total time it takes to run the full workload (e.g., 1 minute), then Login PI will immediately log back in after a session gets disconnected. After getting logged back in again, we’ll start the application workflow over to make sure we didn’t miss any important data.

    Here’s what happens in the video:

    1. Have Login PI start a session to a healthcare workspace that runs a radiology application, an EMR application, and MS Excel
    2. We disconnect the session before we have a chance to run through the complete application workflow. We get through the 3D Radiology app, but never get to the EHR application or Excel
    3. We see the session abruptly ended on the disconnect, but seconds later the Login PI Launcher connects back to the workspace with the given user and starts the workflow over…



    About the author
    Blair Parkhill

    Blair Parkhill (@SANspyder) joined Login VSI in the summer of 2015 as the director of products. Blair has been a marketing leader, avid architect and supporter of customer-focused technology solutions and technical marketing since the late 1990s. Residing in tiny homes located in the mountains of Colorado and jungles of Costa Rica, he tries to spend as much time as he can traveling, playing music, exploring the jungle, walking on beaches, and hiking in the mountains – when he’s not playing with the product, geeking out with the latest tech, presenting, testing or blogging.

    Ready to maximize your end-user experience?

    Start maximizing your end-user experience and make your VDI environments run better and operate smoother.

    Start Free Trial   Register for a Live Demo