I get a lot of questions, both internally and from customers, about how Launcher filters work in Login PI. My colleague Mark Plettenberg recently wrote up a good description, which I’ve aggressively borrowed from to put this post together.
I am proud to let you know that version 1.0.4 of Login PI is now available for immediate download on our website. This is a significant update from version 1.0.3, released late last year.
Hi, Adam Carter here, the Login PI product manager. The other day I was reading some feedback from a customer about Login PI (I love getting product feedback. I read it all, and consider all of it for future releases). The customer had a list of feature requests, one of which was support in Login PI for maintenance windows when scheduled Login PI jobs are suspended.
“Login PI supports maintenance windows!” I thought to myself, “it totally does. The dev team even asked me to write a blog post about it.”
Login PI offers two out of the box workloads to monitor your virtualized desktop environment from the perspective of an end-user. These workloads use the same applications as your regular users like native Windows and Microsoft Office apps, but it’s also possible to customize the workloads. When you create a new workload in Login PI you can run into several issues. In this blog I will provide some tips and tricks to debug your customized workloads.
A network share is a critical component in the IT infrastructure of any organization to store and open files. But what would happen if your colleagues can’t reach their corporate data for some time? What if it takes minutes to open or write a file to the network share? This would probably mean a serious loss of time. Many monitoring solutions give you the ability to monitor the I/O load on your SAN or fileserver. These tools often also have the ability to monitor the network. But what if the drive mapping fails? What if your fileserver is saturated? Wouldn’t it be great if there was a way to monitor the entire chain from the perspective of an end-user? Today is your lucky day because in this blogpost I will explain how you can monitor your network share with Login PI.
A huge advantage of Login PI is the fact that it will automatically generate alerts about performance in your virtualized desktop environment--before your end users start to notice issues. These alerts are displayed in the Login PI event log. But what if you are not checking the interface because you are off getting a nice cup of coffee? Wouldn’t it be great if you could automatically receive these alerts in your email Inbox as well? In this blog post I will explain how to set up Login PI to send alerts via email.
I wanted to let you know about some new Login PI training videos that I just published. You can find them below. These are in addition to the other great materials we already have available:
Performance in your virtualized desktop environment will often degrade over time. When this happens, it is so gradual that end users may not even notice. Until they do. Why does it happen? Applications gradually save more files, which again individually increase in file size each time an application is started by the end-user.
Microsoft App-V is a great way to virtualize applications and publish them to the desktop. But App-V publishing can take some time and the application is not always available immediately. This can interfere with a Login PI workload. If the workload attempts to launch applications that haven’t been published to the desktop yet, this will result in application start timeouts reported by Login PI. In this blog post I will describe how to integrate App-V publishing in a Login PI workload.
It’s a big day for VDI today: Login PI 1.0 is available now and you can download the latest version today. As your friendly development lead on Login PI, I can’t wait to get into the details of what’s new since the Release Candidate in December.