FlexApp Layering from Liquidware Labs is evolving at a rapid pace. With that in mind we have updated the content with the primary white paper. Here is link to the “FlexApp: Application Layering Technology White Paper”. Continue reading
2015 was an impressive year for product announcements and innovations. Liquidware Labs re-released the FlexApp Layering platform after a significant architecture shift. Customer adoption and validation for FlexApp has been extremely positive. Looking back, something seemed to be missing in the EUC space with respect to application lifecycle management. Application virtualization started off strong but has tapered off lately, primarily because of compatibility challenges. The timing for a platform like Application Layering was perfect as companies push further towards desktop integration with the “Cloud”. FlexApp Layering is poised to take its place as one of the pillars of the application layering space.
The FlexApp Layering Technical FAQ has been released by Liquidware Labs. As customers look to adopt and implement the FlexApp technology, they are bound to have questions. Questions within the FAQ are divided into various sections for faster reference:
- FlexApp Layering Requirements
- FlexApp Layering Installation and Configuration
- FlexApp Storage
- Creating FlexApp Layers
- FlexApp Management
- Updating FlexApp Layers
- FlexApp Layering with remote Desktop Session Hosts / Citrix XenApp
- Troubleshooting FlexApp Layers
- Getting help with ProfileUnity
One of the potential challenges that application layering technology creates is around interlayer application conflicts with respect to the corresponding host operating system. In an effort to address these potential challenges, Liquidware Labs developers have created a feature called Micro-Isolation.
The recent release of ProfileUnity 6.5 was a significant platform improvement for both ProfileUnity and FlexApp. The commitment to robust integration points between ProfileUnity and the FlexApp layering platform is reflected based on the positive feedback from current and new customers alike.
One question that comes up in conversation a lot recently is where App Virtualization stops and App Layering starts. There are typically no wrong answers when attempting to design application solutions around both App Virtualization and App Layering, but what is clear so far is that App Layering has a wider compatibility with enterprise applications. There seems to be another option, why not combine them for a best of breed solution for enterprises. This blog entry will examine the combination of FlexApp Layering from Liquidware Labs and ThinApp from VMware.
A number of years ago when I first started working with ThinApp, I was told they would run faster if they were launched from the local disk versus a network share. For physical or persistent OS, this can be accomplished by copying the ThinApp package locally and then running thinreg.exe against the file(s) or by packaging the application with ThinApp as an .msi package and installing it on the OS. For non-persistent desktops, copying the files locally or running the msi version isn’t really an option because this would need to be done each time a user logs on to a desktop.
FlexApp Layers from Liquidware Labs is focused on application life cycle management and delivery. The platform optimizations allow for seamless integration with many different vendor technologies including Citrix XenApp and XenDesktop.
One of the many challenges within the challenge of a basic application lifecycle centers on the delivery of applications to end users. The number and types of devices leveraged by end users is expanding daily and enterprises are now expected to essentially accept this change and improvise.
I think we can all agree that end-users leverage applications while they interface with desktop operating systems. For years we have heard about small, large, fat, thin tall, short desktops in all kinds of colors. We have been told countless ways that users can access, touch, manipulate, and move these desktops, but what is often lost in the shuffle of all the madness, is the importance of the application itself.
I have been in the desktop application space for a while and customers often say the same thing when the idea of an “Application Assessment” is suggested. I have heard many reasons not to conduct assessments, “It takes too long”, “I don’t want to pay for an assessment”, “We already pulled an inventory from tool X”, “The guy in IT told me we are all set”, “I sat with this guy on a plane yesterday and he thinks application assessments are useless” and my personal favorite “Our apps are working just fine, so why would we need an assessment?”.