As ‘working from home’ has now become the new norm, remote application performance has been put under the spotlight like never before.
As you would expect, I have seen a surge in clients needing to prove their business applications are available and performing well for remote users. Our increased reliance on remote working has highlighted a number of technology issues, especially across the finance sector and public services.
When interacting with enterprise applications, the user experience is important.
Users must be able to smoothly and efficiently interact with the application to be productive and achieve the goals of the enterprise. The applications are expected to be responsive, dependable, and consistent in their presentation.
I love the flexibility of the virtual user, it can handle any application and can go as deep into the application as you like.
This does of course mean the desire to customize workloads to include, for example, your CRM, an Electronic health record or Finance application, increases.
Why send your application packages through a lengthy packaging process to customize them when you can tailor them yourself quickly on the spot? Software packaging for electronic distribution is a well-established practice in many organizations. No matter if applications are packaged using MSI or virtualized using Microsoft App-V or VMware ThinApp, nobody really seems to stop and think about the necessity of it all. Many do not realize that packaging is one of the most expensive and time consuming parts of an application and desktop lifecycle.
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.
Project Virtual Reality Check (VRC) released a new white paper titled “Impact of Microsoft Application Virtualization (App-V) 5.0, Optimizations and Best Practices” last week. This paper contains detailed Microsoft App-V performance data which can be applied to any App-V infrastructure scenario. As a member of Project VRC who was deeply involved in the many Login VSI tests that went into the paper, I would like to share some highlights with you in this blog.
Login VSI supports application virtualization, but how do you integrate App-V within a workload? Depending on which applications are virtualized it is possible to run the medium workload without any modifications. When every application is virtualized some modifications are required. Because Login VSI v4 has a simple workload language, App-V can be easily integrated. In this blog post I will explain the App-V 4.x & 5.x integration with Login VSI 4.0.
Independent Research Project VRC: Phase IV describes pros and cons
Today PQR and Login Consultants released Phase IV of Project ‘Virtual Reality Check’ (VRC). The white paper describes the impact and best practices of application virtualization on a Virtual Desktop Infrastructure (VDI).