Login PI Building Momentum
I wanted to share with you how some early adopter customers are using Login PI today.
What is Login PI?
Login PI works by having virtual users log in to your VDI or Remote Desktop Session environment and report on the performance characteristics of the desktop. The virtual user logs in on a schedule you specify and measures the time it takes to login and launch a set up applications. By default, Microsoft Office apps are timed, but the applications used can be customized to include other apps in your environment. PI can alert IT Administrators when performance times are below established thresholds, or generate reports to show you graphically what performance has been like over a period of time.
A virtual Login PI user opens Outlook
How is Login PI being used?
When you deploy PI, you can specify multiple Launch points where the virtual user session will be initiated. This is useful if you want to test the login time and user experience across a WAN connection, for example. One customer has 100’s of branch locations, but connectivity can be sporadic. By launching a virtual user from each location, they can detect when WAN connectivity is down, because the PI server will generate an alert when a virtual user doesn’t log in as scheduled from a particular location, or if the launcher stops communicating with the PI Server.
Many customers adopt some sort of application virtualization solution as part of their VDI/SBC solution. This can include products like App-V or ThinApp. In these solutions, the apps aren’t installed in the desktop in the traditional sense, but streamed when needed. A configuration change or server outage can cause these apps to not get published to desktops as expected, or the file type associations don’t get assigned to the published apps correctly. If the PI virtual user attempts to launch the apps and they aren’t there, it will generate an alert, notifying IT that virtualized apps aren’t working.
End User Experience Validation
Another customer has data entry locations around the world, all connecting into a single VDI deployment. They noticed that one location wasn’t as productive as the others, and when they enquired at the site, the data entry center blamed poor VDI performance. Because this happened before Login PI was available, IT had to fly someone around the world to see the VDI experience firsthand, only to conclude that the VDI performance appeared to be the same as other locations. With PI, they could have deployed PI launchers at each data entry location, and compared the performance results from each to determine if there was any correlation between VDI user experience and productivity.
Login PI - Logon Timings
How would you use Login PI?
Just two months after making the release candidate generally available, we’re already seeing customers get value out of Login PI, sometimes in ways we hadn’t anticipated. How will you use it? Download your Login PI trial today, and let us know!